Legal
Privacy Policy
Last updated: November 11, 2026
This Privacy Policy explains what information Hooky (“Hooky”, “we”, “us”) collects when you use our mobile application, our Visual Studio Code extension, our relay and speech services, and this website at hooky-ai.com(together, the “Services”), how we use that information, who we share it with, and the choices you have. We have written this policy in plain language. Where defined terms are used, they are explained the first time they appear.
1. Summary
Hooky connects your phone to AI agents and supported apps on your computer. Paired-session messages are encrypted between your phone and computer; our relay forwards them without reading their content. Chat and saved workspace history live in encrypted storage on your phone, with local encrypted backup and restore. Our backend stores account, subscription, usage and routing records. Voice processing, screen streaming, casting, the Files workbench and your chosen agent have separate data paths, described below.
2. Who is the controller of your data?
The controller for personal data processed through the Services is the operator of Hooky (the “Operator”). You can contact us about this policy or any privacy matter by writing to privacy@hooky-ai.com.
3. Information we collect
3.1 Information you provide directly
- Account information. You can sign in with GitHub, Google, Apple (on iPhone) or email and password. For GitHub, Google and Apple sign-in, we process the identity and profile fields returned by the provider, such as account ID, name, email address (which may be an Apple private relay address) and avatar. For Sign in with Apple we also keep a token that lets us revoke the sign-in when you delete your account. Email accounts use an email address and a stored password hash. We also store account profile settings and linked sign-in methods. This data authenticates you and associates service access, purchases and pairing records with your account. It does not provide a cloud archive of your chats.
- Early-access email. If you submit your email address on an access-request or signup form on hooky-ai.com, we store that email address solely to notify you when Hooky becomes available and to send occasional launch-related updates. If you also allow website analytics, the request can include limited campaign and referral information to help us understand which links lead to requests.
- Content you send to the Services. Chat messages, file content you choose to upload, screenshots, prompts for the AI agent, and similar inputs that you submit through the app or extension. Voice features also process recordings, live audio, transcripts and text used to produce spoken replies.
- Support and feedback. If you contact us, we keep the contents of your message and our reply.
3.2 Information collected automatically
- Connection metadata. QR pairing authorizations, session tokens, device identifiers generated by the app, IP address of the connecting device, timestamps, and basic diagnostic information (operating system version, app version). This information is used to establish and maintain the connection between your phone and your computer through the Hooky relay.
- Push notification tokens.If you allow the app to send notifications, your device’s push token (from Apple Push Notification service or Firebase Cloud Messaging) is sent to our relay backend so that we can deliver a notification when your AI agent needs your attention.
- Access and usage records. We process account entitlement records and feature-usage counters, such as relay traffic and voice duration, to apply access and usage limits. Where store purchase validation is enabled, this can also include store transaction identifiers and subscription status. Current purchase availability is described in the app and on this site.
- Server logs. Our servers automatically record standard request information (IP address, request path, response code, timestamp, user agent) for security, abuse prevention, and diagnostic purposes.
3.3 Website analytics, advertising and your choices
Analytics and advertising tags run by default unless you have refused them. The bottom notice lets you turn off optional tracking or choose categories separately in the website’s cookie preferences. The early-access form works without either category.
- Analytics. While analytics is enabled, Google Analytics measures page visits and interactions such as access button clicks, starting a form, submission attempts, errors and successfully saved new requests. We use these reports to improve the website and measure campaign results.
- Advertising.While advertising measurement is enabled, we can use Google Analytics advertising features, including Google signals after explicit permission, together with connected Meta and LinkedIn tags. Our server-side conversion tools require an explicit Marketing choice. They help measure visits and conversions and create audiences for showing Hooky ads to previous visitors. A provider’s tag only runs when that integration is enabled. These providers may associate visits with their own browser identifiers or accounts, according to their policies and your settings with them. Google advertising features require your advertising permission in addition to analytics permission. While advertising tags are enabled, validated ad-click identifiers from a landing link (such as Google click IDs, Meta’s fbclid or LinkedIn’s li_fat_id) can be passed to the relevant advertising tools to connect a visit or conversion to an ad. Google and Meta click IDs are not added to the campaign attribution stored with your early-access email. After an explicit Marketing choice, a LinkedIn click ID may be kept with a pending server conversion. Tags may retain their own browser identifiers in cookies or other browser storage.
- Campaign attribution.While analytics is enabled, we can save limited campaign labels, the referring website’s hostname, a page path and a timestamp in your browser for up to 90 days. We use the first and most recent known source to understand how you reached the website. These fields can also be saved with an early-access request. We filter campaign values and do not include arbitrary query strings or form contents in this attribution data.
Website analytics and advertising tags are on by default unless you have refused them. The bottom notice and Cookie preferences let you turn off all optional tracking or choose categories. We distinguish this default opt-out basis from an explicit choice; default collection is not recorded as affirmative consent. Google Analytics storage is enabled by this default configuration and can use cookies. Google advertising consent flags require an explicit choice. Previously saved refusals, including older choices, continue to apply.
After an explicit Marketing choice under this notice, a newly saved early-access request may also be sent to LinkedIn through its Conversions API. We send a SHA-256 hash of your trimmed, lowercased submitted email and, when available, a LinkedIn click identifier. LinkedIn uses these to match the conversion to an account or ad interaction. A hash remains personal data; it is not anonymous. We do not send the raw email in these conversion events. Before submission, form-stage events use only an available LinkedIn click identifier, never the entered email or its hash. These events are separate from saved-request conversions. Pending delivery identifiers are kept for at most seven days and are removed after successful delivery or final failure. Browser matching identifiers are retained for up to 90 days while advertising stays enabled.
Our Google Analytics event fields do not include your email address, an email hash, your Hooky account details, or the contents of a form. We do not add your IP address to these event fields. When an optional tag connects to its provider, that provider still receives network information such as your IP address and browser details, and may use cookies or similar identifiers under its own policy.
Open Cookie preferenceson the website to change or withdraw your choice. Withdrawal stops future optional tracking for the categories you turn off. We disable local optional tracking immediately and wait briefly for the server to acknowledge withdrawal before reloading. If delivery fails, we retain a necessary pending-withdrawal record and retry on the next load or when connectivity returns; optional tags remain blocked during that retry. When your withdrawal reaches our server, we cancel pending LinkedIn events associated with this browser. We keep a hashed withdrawal token for up to 90 days solely to prevent delayed events from being sent. Requests already in flight may complete; withdrawal does not automatically erase information already received by a provider or saved with a request. We remember affirmative choices for up to 180 days. Older saved refusals continue to apply until you change them; clearing browser storage may remove them. When you withdraw a category, we remove optional first-party cookies that our website can access and the advertising identifiers in the Google, Meta and LinkedIn browser-storage keys used by this website. Cookies set on a provider’s own domain must be managed through your browser or that provider’s settings. Clearing browser storage or using a different browser can require you to choose again.
3.4 Device permissions
We do not request access to your contacts or calendar. The app requests permissions for features such as microphone recording, camera pairing, photos, files and notifications. You can manage these permissions in your device settings. Host screen capture and computer actions also depend on permissions on the connected computer.
4. How your content is stored and transmitted
- QR pairing and encrypted messages. Scan the QR code shown by the Hooky extension to pair your phone and computer. Pairing binds device keys. Paired-session message payloads are encrypted between those devices; the relay cannot decrypt them. The relay connection also uses TLS/WSS. This protects the paired message channel, not every data path used by every feature.
- Delivery and notifications. The relay forwards encrypted messages without keeping a chat-history archive. Your computer holds undelivered output until the phone acknowledges receipt. Catch-up therefore requires that computer to become reachable. Notification content is sealed for the paired device; the relay and push providers process routing data to deliver it.
- Account and service storage. Our backend stores account profiles, linked sign-in methods, subscriptions, purchase and usage records, pairing authorizations and push registrations. These are separate from phone-local history. The current service does not use Firestore or another server history store to retain your chat content.
- Files workbench. The browser VS Code workbench runs on your connected computer and can use a Cloudflare tunnel. Tunnel traffic, including workspace content you view or edit, passes through that provider. This is a separate path from encrypted paired-session messages.
- Audio and agent processing.Voice recordings and live audio are sent through speech services for transcription. Text for spoken replies is sent for speech synthesis. Transcripts you send become chat content. Depending on the language and available voices, spoken replies use a hosted speech service or your phone’s voices. Your chosen agent sends relevant prompts and context to its provider under that provider’s terms and policies. These requests are separate from the encrypted relay message channel.
- Screen streaming and casting. Screen images and video travel through the streaming transport and may use relay services. When you cast, a compatible TV or receiver receives the stream. These media paths are separate from chat-message encryption; this policy does not claim that every stream or cast is end-to-end encrypted.
- On-device history and backups.On iOS and Android, chat history, drafts, saved workspaces and durable attachments are stored in an encrypted database on your phone. Viewing or sharing an attachment can create a temporary local file. History & backup exports a password-protected encrypted archive to a location you choose and imports it locally. Hooky does not upload these archives or recover history when you sign in on a new phone. Exported archives remain wherever you saved them; that destination may have its own storage or sync policy.
5. How we use information
We process personal data for the following purposes and on the following legal bases (in jurisdictions where this terminology applies, such as the EU/EEA and the United Kingdom):
- To provide the Services. Authenticating you, pairing your devices, routing encrypted messages between them, processing voice input and spoken replies, applying feature-access limits, and sending push notifications you have opted into. (Legal basis: performance of a contract.)
- To keep the Services secure. Detecting and preventing abuse, brute-force attacks, and unauthorised access. (Legal basis: legitimate interests.)
- To improve the Services. Aggregated, non-personal diagnostics about errors and reliability. (Legal basis: legitimate interests.)
- To notify you of launch and updates. If you joined the waitlist or subscribed to launch updates. (Legal basis: consent. You can withdraw it at any time.)
- To measure website use and campaigns. Optional analytics helps us understand visits and access requests. Optional advertising measurement helps us measure ads and reach previous visitors. Website tags run by default with the opt-out choices described above. Email-hash matching through our Conversions API requires an explicit Marketing choice. You can turn optional tracking off in Cookie preferences.
- To comply with law. Where we are required to retain or disclose information to comply with a legal obligation. (Legal basis: legal obligation.)
We do not sell or rent the early-access email list. Optional advertising data sharing is described in section 3.3. We do not use your content to train artificial intelligence models.
6. Third-party services
Hooky uses external providers to operate the Services and connect to the agents you choose. Their own terms and privacy policies also apply to their processing:
- GitHub, Inc.— used for authentication (OAuth) and, if you enable it, GitHub Copilot integration in the IDE. See GitHub’s Privacy Statement.
- Anthropic, PBC.— used to translate terminal output into explanations when you request that feature, and to power Claude Code when you choose that agent. See Anthropic’s Privacy Policy. Relevant input is sent to Anthropic for processing.
- OpenAI.— provides Codex when you select that agent. Prompts, workspace context and agent interactions are processed according to your agent setup and OpenAI account terms.
- Deepgram.— processes recorded and live audio for speech-to-text and reply text for speech synthesis when you use enabled voice features.
- Microsoft Azure.— processes text for speech synthesis in supported languages when Azure speech is configured, including Armenian. Other languages may use your phone’s available voices.
- Apple Inc.— provides Sign in with Apple and delivers push notifications through Apple Push Notification service. App Store services process in-app subscription purchases.
- Google LLC.— provides Google sign-in, Firebase Cloud Messaging for notifications. Google Play may also process purchases where enabled. With your website analytics permission, Google Analytics processes website measurement data. With your additional advertising permission, enabled Google Analytics advertising features can support ad measurement and visitor audiences. See Google’s Privacy Policy.
- Meta.— when connected and allowed by your advertising choice, Meta Pixel processes website events for ad measurement and visitor audiences. See Meta’s Privacy Policy.
- LinkedIn.— when connected and allowed by your advertising choice, LinkedIn tracking pixels process website visits and conversions for ad measurement and visitor audiences. See LinkedIn’s Privacy Policy and Cookie Policy.
- Cloudflare.— provides the tunnel used to reach your browser VS Code workbench remotely.
- Hosting providers. Our relay server and waitlist backend run on third-party infrastructure providers in the regions we operate. They process data on our behalf under data processing agreements where required.
We do not send your early-access email address or its hash through these advertising tags. Optional advertising providers process the website data described in section 3.3 under their own terms and privacy settings.
7. International transfers
Our infrastructure providers may process data in regions outside of your country of residence, including the European Union and the United States. Where personal data is transferred outside of the European Economic Area or the United Kingdom, we rely on appropriate safeguards (such as Standard Contractual Clauses) recognised under applicable data protection law.
8. Retention
Phone-local history, exported backups, account and purchase records, operational logs, usage records and push registrations have separate lifecycles. Signing out does not erase the phone’s history. Deleting an account in the app removes its local database and key on that phone after the server confirms deletion. It does not remove archives you exported or data on other devices. We do not promise a fixed automatic deletion time for all service records.
Browser campaign attribution expires after at most 90 days. Our Google Analytics cookies are configured with a 90-day lifetime without extending it on each visit; consent preferences expire after at most 180 days. Attribution saved with a request follows that request’s retention and deletion process. Advertising and analytics providers apply their own retention settings and policies.
Early-access email addresses are used for access and launch updates. To stop those updates, or to request deletion of account data, legacy server-held content or other personal information, contact privacy@hooky-ai.com. To delete your account, follow the steps on hooky-ai.com/delete-account. We handle requests subject to applicable legal obligations. Earlier service versions used server-side message storage; this description of the current system is not a claim that every historical copy has already been removed. External providers apply their own retention policies to data they process.
9. Your rights
Depending on where you live, you may have the following rights with respect to your personal data:
- access to a copy of the information we hold about you;
- correction of inaccurate or incomplete information;
- deletion of your data (sometimes called the “right to be forgotten”);
- restriction or objection to certain types of processing, including processing based on our legitimate interests;
- portability of the data you have given us;
- withdrawal of consent at any time, where processing is based on consent;
- the right to lodge a complaint with your local data protection authority.
To exercise any of these rights, write to privacy@hooky-ai.com. We will respond within the timeframes required by applicable law. We may need to verify your identity before acting on certain requests.
10. Security
Paired-session message payloads use authenticated end-to-end encryption between the phone and computer. The relay forwards encrypted frames over TLS/WSS and cannot read their content. Pairing and authentication restrict workspace access. Account data, hosted speech, agent-provider requests, the Files workbench and screen/cast media have separate protections as described above. Keep your devices and agent credentials secure. No system can be guaranteed to be perfectly secure, and we work to fix reported security issues.
11. Children
Hooky is intended for software developers and is not directed at children. We do not knowingly collect personal data from children under 16. If you believe a child has provided us with personal data, please contact us and we will delete it.
12. Changes to this policy
We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date at the top of this page and, where the changes are material, we will provide a more prominent notice (for example, an in-app message or an email to subscribers).
13. Contact
Questions or requests about this Privacy Policy can be sent to privacy@hooky-ai.com.