Inter-office memo
- To
- Everyone
- From
- Enjoy Agentic Industries
- Date
- November 5, 2026
- Re
- Privacy policy
Privacy policy.
This policy covers Enjoy’s website, desktop app, web app, and iOS app. It explains what information we handle and why.
1.Your work and AI providers
Your projects, files, and conversations are stored on the computer running Enjoy. When you connect another device, workspace content travels through an end-to-end encrypted connection. Our relay handles connection information, but cannot read that encrypted content.
Enjoy has no AI model of its own. The agents you use, such as Claude Code or Codex, run on your computer with your own account at the company that makes them, and send that company what they need to carry out your request: your messages and the photos and files you attach, your answers to their questions, project files they open, the output of commands they run, and earlier messages in the conversation. The companies are Anthropic for Claude Code, OpenAI for Codex, Google for Antigravity, SpaceXAI for Grok Build, Meta for Muse Code, and the providers you set up in OpenCode. They use it to produce the agent’s replies and do the work you asked for, and handle it under their own privacy policies and your account settings with them. A connected service you use receives what you send it in the same way.
You decide what goes to an agent: you type your messages and answers and choose what to attach. The iPhone and iPad app uses the camera or your photo library only when you take or choose a photo, and removes its location data before sending it to your computer. Before anything from the iPhone or iPad app reaches an agent, the app asks your permission and names each company. Not now sends nothing, and you can change your answer in the app’s Settings, under AI providers.
We share your work with these AI providers only to carry out what you ask, and only through agents you choose to use. Each provides the same or equal protection for it as this policy, under its own privacy policy and terms. People you grant access to can see the work you share.
2.YouTube
When you connect a YouTube channel, Enjoy uses the YouTube API Services to post the videos you approve to it. By connecting, you agree to YouTube’s Terms of Service, and Google handles your information under the Google Privacy Policy.
Enjoy asks Google for permission to upload videos to your channel and to view your YouTube account, which it uses only to show your channel’s name and picture, so you can see which channel a video goes to. Google’s permission is saved only on the computer where you connected the channel, in Enjoy’s credential storage, which uses your system’s keychain if you turned it on. It is never sent to our servers, and Enjoy doesn’t give it to agents. When you post a video, Enjoy sends the file and the title, description, and other details you approved straight from that computer to YouTube. We do not collect, keep, or share your YouTube data on our servers.
Disconnecting the channel in Enjoy, under Your account, deletes the saved permission from your computer and revokes it at Google. You can also remove Enjoy’s access at any time in your Google Account’s security settings.
Google’s permission stays on your computer until you disconnect the channel. A post’s details, including its title, description, video link, and your channel’s name, are saved with its conversation in your project on your computer until you delete the conversation. None of this is on our servers, so there’s nothing there for us to keep or delete. “How we protect your data,” below, explains how it’s protected.
We don’t sell Google user data or use it for advertising, and we don’t use it to develop, improve, or train AI models. Enjoy sends it only to YouTube, to post what you approved: not to our servers, and not to agents or AI providers.
Enjoy’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
3.TikTok
When you connect a TikTok account, Enjoy uses TikTok’s Login Kit and Content Posting API to post the videos you approve to it. TikTok handles your information under its Privacy Policy, and posting from Enjoy means you agree to TikTok’s Music Usage Confirmation.
Enjoy asks TikTok for permission to read your account’s display name and picture, so you can see which account a video goes to, and to post videos to it. TikTok requires an app’s secret to sign in and to renew a sign-in, so those two steps pass through our server, which adds Enjoy’s secret, passes TikTok’s answer back to your computer, and keeps nothing. Your TikTok permission is saved only on the computer where you connected the account, in Enjoy’s credential storage, and Enjoy doesn’t give it to agents. When you post a video, Enjoy sends the file and the caption and settings you chose straight from that computer to TikTok.
Disconnecting the account in Enjoy, under Your account, deletes the saved permission from your computer and asks TikTok to end it. You can also remove Enjoy in TikTok, under Settings and privacy, Security, Apps and services permissions.
Your TikTok permission stays on your computer until you disconnect the account. A post’s details, including its caption, video link, and your account’s name, are saved with its conversation in your project on your computer until you delete the conversation. We don’t keep any of it on our servers. “How we protect your data,” below, explains how it’s protected.
We don’t sell TikTok information or use it for advertising, and we don’t use it to develop, improve, or train AI models. Enjoy uses it only to show which account a video goes to and to post what you approved, and doesn’t give it to agents or AI providers.
4.Instagram, Facebook, and X
When you connect an Instagram, Facebook, or X account, Enjoy uses that platform’s API to post the videos and other posts you approve to it. Meta handles your Instagram and Facebook information under its Privacy Policy, and X handles yours under its Privacy Policy.
Enjoy asks each platform for permission to read your account’s name and picture, so you can see which account a post goes to, and to publish to it. That permission is saved only on the computer where you connected the account, in Enjoy’s credential storage, and Enjoy doesn’t give it to agents. Where a platform requires an app’s secret to sign in or to renew a sign-in, those steps pass through our server, which adds Enjoy’s secret, passes the answer back to your computer, and keeps nothing. When you post, Enjoy sends the file and the details you approved from that computer to the platform.
Disconnecting the account in Enjoy, under Your account, deletes the saved permission from your computer and asks the platform to end it. You can also remove Enjoy in the platform’s own settings. A post’s details are saved with its conversation in your project on your computer until you delete the conversation. We don’t keep any of this on our servers, sell it, use it for advertising, or use it to develop, improve, or train AI models.
5.Information we collect
- Account and billing: your name, email, sign-in information, subscription status, and payment references. You make your account with Google or your email, in Enjoy or in the web app; a computer that used Enjoy while it was free can go on using it there without one. When you start your free trial or subscribe, we give your email to Stripe, our payment provider, which takes your payment card and processes your payments. Enjoy does not store your full payment card details.
- Downloads and signing in: when the start page starts your download, we record it under a random code with your IP address, browser User-Agent, the ad and browser references described below, and where your visit came from. When you make your account or sign in in the Enjoy app, we keep your email, a random installation identifier, the operating system, and the app version, so the installation is tied to your account and, where we can, to the visit that downloaded it. If you ask the start page on a phone to email you the link, we use your email for that one message.
- Connections and security: device and computer identifiers, names, access permissions, and technical information such as IP addresses and session information needed to operate and protect the service.
- Support: messages, contact details, and attachments you choose to send us. We publish testimonials only with your permission.
- App usage: feature events, such as starting a conversation, with a random installation identifier, timestamp, app version, operating system, and plan. These reports exclude message text, file contents, and project names. They are enabled by default; turn off Share usage statistics in desktop app settings to stop future reports and clear pending ones. Actions from connected devices can be counted by the desktop app.
6.Website analytics and storage
We measure the website ourselves. On your first visit, our server sets a first-party cookie, enjoy_visitor, holding a random identifier that lasts up to 400 days, and the website reports the pages you view, how long you look at them and how far you scroll, the site or campaign link that sent you, and what you click, such as downloads, links to other sites, and forms. Our server works out your browser, operating system, device type, and country from your request; it does not keep your IP address for this, and it stores only a hash of the identifier. When the start page records your download, we keep the identifier’s hash with it, so the visits that led to a download, your account, and your first payment count as one journey. We use this to improve the website and Enjoy, and we don’t share it.
To test changes, we may show you one of several versions of a page. Your version is kept in another first-party cookie, enjoy_x, for up to 400 days, so you keep seeing the same one, and we compare what people who saw each version did afterward.
We also use Plausible to understand visits, downloads, sign-ups, and free trials. It collects information such as pages visited, referral sources, browser and device type, and approximate location, without analytics cookies. The start page reports a download from your browser; our server reports when you make your account or sign in in the Enjoy app, with the IP address and browser User-Agent kept with your download and where your visit came from, so they count as the same visit, and when your free trial starts. Plausible events exclude your email, account identifiers, and workspace content. See Plausible’s data policy.
When you arrive from another site or a campaign link, the website keeps that site’s address (without its query), the link’s campaign tags, and the page you landed on for as long as the browser tab is open. The start page sends them with your download, and if you then make your account in the Enjoy app we store them with it to understand which sources bring new people to Enjoy. A visit you start yourself keeps nothing.
We also use OpenAI Ads to measure visits, sign-ups, and paid subscriptions from advertising. The website pixel may use browser identifiers, and we store an ad click reference in a cookie for up to 30 days so it can follow you from the website to the start page. When you make your account or sign in in the Enjoy app, our server reports it to OpenAI with the time, the ad and browser references kept with your download, IP address, User-Agent, and a SHA-256 hash of your normalized email address for conversion matching. The hash is not your raw email address, but it can be used to match your conversion. We keep this matching data with your sign-up so that, if you later pay for Enjoy, our server can report the first payment’s time and amount to OpenAI with the same matching data. We exclude workspace content. We delete this matching data once the payment is reported, or 60 days after you sign up if it isn’t. See OpenAI’s privacy policy.
We use Meta’s pixel and Conversions API to measure visits, downloads, sign-ups, and paid subscriptions from Meta ads. The website loads Meta’s pixel, which sets browser identifiers and reports page visits and, on the start page, the download, and we store a Meta ad click reference in a cookie for up to 90 days so it can follow you from the website to the start page. Our server reports the download, your sign-up, and your first payment to Meta, with their times, the Meta browser and click references, IP address, and User-Agent kept with your download, a SHA-256 hash of your account identifier, and a SHA-256 hash of your normalized email address for conversion matching. We exclude workspace content. We delete this matching data once the payment is reported, or 60 days after you sign up if it isn’t. See Meta’s privacy policy.
We use Google’s tag to measure visits and downloads from Google ads. The website loads Google’s tag, which sets browser identifiers and, when you arrive from a Google ad, stores Google’s ad click reference in a cookie for up to 90 days, and reports to Google your page visits and when the start page starts your download or emails you the download link. Our server also keeps Google’s click reference with the enjoy_visitor identifier for up to 90 days, and if that visit leads to a free trial, reports the reference and the time the trial started to Google, then deletes the reference. We exclude workspace content. See Google’s privacy policy and how Google uses information from sites that use its services.
We use X’s pixel to measure visits and downloads from X ads. The website loads X’s pixel, which sets browser identifiers and reports to X your page visits and when the start page starts your download or emails you the download link. We exclude workspace content. See X’s privacy policy.
We use LinkedIn’s Conversions API to measure sign-ups from LinkedIn ads. When you arrive from a LinkedIn ad, we store LinkedIn’s ad click reference in a cookie for up to 90 days so it can follow you from the website to the start page. When you make your account or sign in in the Enjoy app, our server reports it to LinkedIn with its time, the LinkedIn click reference kept with your download, your IP address, and a SHA-256 hash of your normalized email address for conversion matching. We exclude workspace content. We delete this matching data once the sign-up is reported, or seven days after you sign up if it can’t be. See LinkedIn’s privacy policy.
We store preferences such as your appearance choice on your device. Account services use cookies or local storage to keep you signed in. If you follow a link to book a call or join our community, that service’s privacy policy applies.
7.How we use and share information
We use information to run Enjoy, connect your devices, manage subscriptions, respond to support requests, prevent abuse, and improve the product. We do not sell your personal information or use your workspace content for advertising.
We share information with service providers needed for hosting, payments, email delivery, and support, and when you direct us to share it. We may also disclose information when legally required or necessary to protect people and the service. Providers may process information in countries other than yours.
8.How we protect your data
We use these safeguards to keep your information confidential and secure, including sensitive data such as the permissions you give Enjoy to reach your Google, TikTok, and other connected accounts:
- On your computer: the permissions you give YouTube, TikTok, and the other platforms you connect are saved only on the computer where you connected them, in Enjoy’s credential storage. That’s a private file in Enjoy’s app data, which on macOS and Linux only your user account can read, or your system’s keychain if you turn it on, which encrypts them. Enjoy clears sign-in tokens from memory when it’s done with them.
- In transit: Enjoy reaches Google, YouTube, TikTok, the other platforms you connect, and our servers only over encrypted HTTPS connections. You connect an account on the platform’s own page in your browser, using OAuth, so Enjoy never sees your password there.
- Your approval: agents can only draft a post, and Enjoy doesn’t give them your permissions. Nothing is posted until you approve it on its card, so neither an agent nor instructions in something it reads can post on its own.
- Between your devices: workspace content travels through an end-to-end encrypted connection, which our relay cannot read.
- On our servers: we never store the permissions you give Google, TikTok, or other platforms, or your data from them. Our website and account service use HTTPS, our server reaches its database with its own restricted login over a verified encrypted connection, account passwords are stored only as salted hashes, and Stripe holds your payment card details.
No system is perfectly secure. If you think your data or account has been affected, disconnect the account in Enjoy and tell us at help@enjoy.dev.
9.Keeping and controlling your data
We keep service information for as long as needed to provide Enjoy, meet legal and accounting obligations, and resolve disputes. Local project files remain under your control; deleting an account does not delete files on your computer or information held by your AI providers.
You can disable usage statistics, revoke shared access, and remove local files. To request access, correction, or deletion of personal information we hold, email help@enjoy.dev. We may need to verify your identity. Depending on where you live, you may have additional rights, including objecting to processing or contacting your privacy regulator.
10.Changes and questions
We’ll update this page and its date when this policy changes. For privacy questions, contact help@enjoy.dev.