Enfold Privacy Policy
Version 1.1. Effective October 13, 2026.
Enfold is an email client for Gmail and Google Calendar. It shows, searches, and sorts your mail, and offers features that help you organize your mail and calendar. It uses your Google data only to provide the features you see and use in the app. Its AI features run on OpenAI, which does not train on your mail. We never sell your data or use it for ads.
This policy explains what Enfold collects, what it does with it, who else receives it, how long we keep it, and how you delete it. It covers the Enfold app at mail.tryenfold.com and our website at https://www.tryenfold.com.
1. Who we are
Enfold is made by Fork Labs Inc., PO Box 20067, New York, NY 10014, United States. In this policy, "Enfold", "we", and "us" mean Fork Labs Inc.
Questions, requests, and complaints: privacy@tryenfold.com. We answer within 30 days.
2. Google user data
Enfold is an email client for Gmail. With your permission, Enfold retrieves the mail in your Gmail and the events in your Google Calendar. It changes them only when you choose to in Enfold, for example when you archive a message or add an event. This section describes exactly what Enfold does with data it receives from Google.
Limited Use
Enfold's use and transfer of raw or derived user data received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
This means:
- We use your Google data only to provide the Enfold features you see and use in the app.
- We transfer it to others only to provide those features, as section 4 lists, to keep the service secure, to comply with the law, or as part of a merger or sale of the company with your consent.
- We never use it for advertising, including targeted, personalized, or interest-based ads. We never sell it. We never give it to advertisers, advertising platforms, data brokers, or information resellers.
- We never use it to decide whether you can get credit or a loan.
- We do not use Google Workspace data, including Gmail and Calendar data, to develop, improve, or train generalized or non-personalized AI or machine learning models. OpenAI, our AI provider, does not train its models on it either.
- No person at Enfold reads your Google data, with three exceptions: (1) you give us explicit permission for specific messages, for example to fix a problem you report, (2) we need to investigate abuse or a security incident, or (3) the law requires it.
What each permission is for
When you connect your Google account to Enfold, Google asks you to allow the permissions below, for Gmail and Google Calendar. Enfold asks for nothing more.
| Permission | What Enfold retrieves or does | Feature |
|---|---|---|
gmail.modify (read, compose, send, and change your Gmail) |
Retrieves your messages, threads, labels, and attachments. Changes labels when you mark done or not done, mark read or unread (opening an email marks it read), star, or report spam, and moves threads to trash. Creates, saves, and sends drafts when you write and send them, and deletes a draft you discard. Watches for new mail. Enfold cannot permanently delete mail, except a draft you discard, which Gmail then deletes for good. | Your inbox and every mail view, reading, search, writing and sending, attachments, categories, Orders, Events, News, draft review |
calendar.events (view and edit events on all your calendars) |
Retrieves the events of the day you look at, on calendars you can see. Adds, changes, or deletes an event only when you choose to in Enfold. Google then emails the people you invited. | The day view beside an email, and adding an event from an email |
calendar.calendarlist.readonly (see the list of your calendars) |
Retrieves your calendars' names, IDs, and time zones, your access to each, and which ones you show. | Choosing the calendar for an event, and the day view |
openid |
Retrieves your Google account's stable ID. | Linking the mailbox to your Google account, so one Gmail connects to one Enfold account |
email |
Retrieves the address of the Google account you connect. | Showing which Gmail is connected |
Separately, you sign in to Enfold with Google through Clerk, our sign-in provider. Clerk receives your name, email address, and profile picture from Google. Enfold uses your Clerk sign-in to identify your account, and gives your email address to Stripe for billing (section 4).
Enfold retrieves Calendar data only to show it to you and to make the changes you choose in Enfold. When you add an event, Enfold keeps Google's IDs for the event and its calendar.
Derived and aggregated data
From your Gmail data, Enfold derives categories, orders, events, news stories, search text, search embeddings, and contacts. Enfold keeps and uses them only for you, under the same rules as the Google data they come from, and deletes them as sections 6 and 7 state.
Enfold does not create aggregated or anonymized data from your Google data, and does not share or sell any. Our service logs and our records of paid service calls hold only counts, sizes, durations, and token counts, with no mail content. We use them only to run, secure, and bill Enfold.
3. How Enfold uses AI
Enfold uses AI for the features below. OpenAI is our only AI provider. We use OpenAI's API, which is its service for businesses, not ChatGPT.
| Feature | What it does | What we send to OpenAI |
|---|---|---|
| Categories | Sorts each new message into a category, for example News, Orders, or Conversations | The sender, recipients (To), subject, date, a few mail headers that show whether it is list mail, a reply, or an automatic message, the message text, and the category Enfold gave the thread before. Also the same for up to five earlier messages in the thread |
| Orders | Finds orders and shipping updates in order mail | The sender, subject, date, message text, the text of links, and the descriptions and parts of the addresses of images in the email |
| Events | Finds flights, stays, reservations, tickets, and appointments in event mail | The sender, subject, date (with the email's or your UTC offset), and message text, including the words of links and the descriptions of images |
| News | Finds the stories in newsletters and sets them into a daily or weekly edition | The sender, subject, date, and newsletter text. To set the edition, the headlines and summaries it found, the newsletters' names, and the edition's date |
| Search | Turns your messages into numbers (embeddings) so search can find mail by meaning | The subject, sender, recipients (To and Cc), attachment names, and message text, in short parts |
| Draft review | Reviews a draft when you choose to in Enfold | Your draft, its recipients (To and Cc), subject, up to 6,000 characters of the message you reply to or forward, as quoted in your draft, with its sender and date (and, for a forward, its subject and recipients), earlier review rounds, and today's date |
Requests for categories, orders, events, news, and draft review also carry one-way hashes made from your Enfold account ID: one so OpenAI can detect abuse without knowing who you are, one to keep your requests in their own cache.
We do not use any personal data, including your mail, to train AI models, and we do not let others do so.
What OpenAI does with it:
- OpenAI does not use data sent through its API to train or improve its models.
- OpenAI does not store our requests or its answers in its API for later use. Enfold turns that storage off (
store: false), and OpenAI's embeddings service has none. To speed up repeated requests, OpenAI can keep an encrypted cache of a request for up to 24 hours. - OpenAI keeps logs of API requests for up to 30 days to detect abuse, unless the law or the prevention of harm requires longer. This applies to our requests too. If OpenAI's automated systems flag a request as possible abuse, OpenAI can keep it longer and its authorized staff can review it.
AI results can be wrong. An email can contain text written to mislead an AI, so a category, order, or event can be wrong. AI results never send, delete, or move mail by themselves.
4. Who receives your data
We share data only with the providers below, with Google as this section states, and in the cases at the end of this section. Each provider gets data only for the purpose listed, and only as much as that purpose needs. Our subprocessor list has the same information and we keep it current.
The Enfold app
| Provider | Purpose | Data | Location |
|---|---|---|---|
| OpenAI | AI features (section 3) | The parts of your mail listed in section 3 | United States (OpenAI can process data in other countries) |
| Amazon Web Services | Hosting, database, file storage, job queues, malware scans of attachments (Amazon GuardDuty), and the server that loads remote images in email | Everything Enfold stores, and the Calendar events Enfold shows or changes for you, which pass through AWS without being stored | United States (Ohio, us-east-2) |
| Google (Cloud Pub/Sub) | Tells Enfold that new mail arrived | Your Gmail address and a Gmail change number. No message content. Google keeps an undelivered notice for up to 1 day | Google Cloud (region chosen by Google) |
| Clerk | Sign-in and sessions | Your name, email address, and profile picture from Google. Your IP address and browser details, because your browser connects to Clerk to sign in. Clerk runs its sign-in service on Cloudflare, so Cloudflare handles all sign-in traffic and sees your IP address and browser details. Clerk may also use Cloudflare Turnstile to check that a sign-in comes from a person, not a bot | United States |
| Stripe | Billing and sales tax | Your email address and your Enfold account ID. The card, billing name, and billing address you give Stripe. Your IP address and browser details, because your browser connects to Stripe when you pay or add a card. Enfold never receives your full card number. Of your payment details, Enfold uses only the country of your card or payment method and your billing country, to check that Enfold is available to you, and stores none of them | United States |
Google itself also receives what Enfold does in your Gmail and Calendar, because that is where your mail and events live.
Our website
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Vercel | Hosting the website | Visit requests, including IP address | United States |
| Supabase | Storing the waitlist and visit events | See section 9 | United States |
Our email
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Google (Google Workspace) | Our email, including your messages to privacy@ and support@ | What you write to us | United States |
We disclose data when the law requires it, for example under a valid court order. If Fork Labs Inc. is merged or sold, we ask for your explicit consent before your Google data moves to the new owner.
5. How we protect your data
- Encryption in transit. We use TLS (HTTPS) between your browser and Enfold, and between Enfold and Google, OpenAI, Clerk, Stripe, and our database.
- Encryption at rest. Our database, its backups, and our file storage are encrypted with keys in AWS Key Management Service. Keys rotate automatically.
- Google tokens. The token that lets Enfold access your Gmail and Calendar is stored encrypted, with a key in AWS Key Management Service that only the Enfold service that talks to Google can use. Each encrypted token works only for its own Gmail account.
- Isolation between users. Every table that holds your data has database rules that return only your own rows to a request made for you. A few internal database functions have wider access, for example to find your account when you sign in, to handle new-mail notices from Google, to run scheduled sync, billing, and cleanup, and to make search fast. They run fixed queries and return only IDs, numbers, dates, and yes or no answers, never text. Their database roles cannot sign in. Enfold then loads your data under the rule above.
- Attachments and images. Attachments you download and files you upload are scanned for malware before you can get them. Images shown inside an email are not scanned for malware. Before your browser shows one, Enfold checks that it is a PNG, JPEG, GIF, or WebP image, from its own bytes, and that its size is within limits.
- Logs. Our service logs hold fixed codes and numbers only. They never hold your mail, your email address, your account ID, or your IP address.
- Access by our team. Only Enfold's founders have administrative access. A founder accesses user data in our database or file storage only in the four cases in section 2, and only with the other founder's approval, given in advance or, in an urgent incident, right after. AWS records every administrative action on our infrastructure in a log that no one can change or delete. Each entry is kept for one year, then deleted automatically.
- AI output. We treat AI output as untrusted. It can only change Enfold's own records about your mail: categories, orders, events, and news. It cannot send, delete, move, or label mail, change your calendar, or open a link without your action in Enfold.
If a security incident affects your data, we will tell you and Google without undue delay, and within the time the law requires.
6. How long we keep data
| Data | Where | How long |
|---|---|---|
| Your sign-in ID (from Clerk), time zone, and consent record (when you agreed to Enfold's notice before connecting Gmail, and to which version) | Our database | Until you delete your account. Then the sign-in ID is replaced with a placeholder, and the time zone and consent record are cleared |
| Your sign-up date and plan dates | Our database | Kept with the billing records below |
| Your name, email address, and profile picture | Clerk | Until you delete your account |
| Connected Gmail: address, Google account ID, granted permissions, and sync position | Our database | Until your data is deleted after a disconnect |
| Google token for Gmail and Calendar | Our database, encrypted | Until you disconnect. See section 7 |
| Message details: sender, To and Cc, reply-to address, subject, Gmail's preview text, date, labels, size, Gmail's IDs, and a few headers (Message-ID, In-Reply-To, Auto-Submitted, Precedence, the Date header's offset, and whether it is list mail). Bcc for mail you send and your drafts | Our database | As long as the message is in your Gmail |
| Message bodies (the full text and HTML) of mail that arrived in the last 7 days | Our database | Until 7 days after the message arrived |
| Message bodies of older mail, stored to give the AI the earlier messages of a thread when new mail arrives, or to build search | Our database | 24 hours after we fetch them for a thread, 1 hour for search |
| Attachments and images from mail of the last 7 days | AWS file storage | Until 7 days after the message arrived |
| Attachments you open from older mail, and files you upload to a draft | AWS file storage | 7 days from the copy or upload |
| Attachment names, types, and sizes | Our database | As long as the message is in your Gmail |
| Search text: the main text of each message, up to 64 KB, for the newest 365 days of mail and all new mail | Our database | As long as the message is in your Gmail |
| Search embeddings | Our database | As long as the message is in your Gmail and not in spam or trash |
| Categories, orders, events, and news stories. Orders keep what the email prints, such as items, totals, the delivery address, and tracking links | Our database | As long as the message is in your Gmail. An order or event stays while any of its emails does. Orders and events you marked done, newsletter senders, and news editions stay until you disconnect or delete your account |
| Contacts: names and addresses of people you write to or hear from, with counts | Our database | As long as mail with that person is in Enfold |
| Calendar events | Not stored | Not kept. For events you add: Google's IDs for the event and its calendar, as long as the event is in Enfold |
| Billing records: plan, dates, status, and your Stripe customer ID | Our database and Stripe | 7 years after your plan ends, for tax records. Stripe keeps its customer record, with your email address, billing name and address, and your Enfold account ID, for tax records |
| Records of each paid service call: date, feature, model, token or byte counts, duration, status, cost, and the provider's request ID. No mail content | Our database | Up to 7 years, under your internal Enfold account ID. After you delete your account, our database holds no name, email address, or sign-in for that ID, but the ID stays linked to your Stripe customer record, which keeps your email address for tax records |
| Database backups | AWS | 7 days. Backups expire on their own |
Messages leave Enfold when they leave your Gmail. Enfold learns that a message left your Gmail when it syncs your mail. When you delete a message for good in Gmail, Enfold then deletes its details, text, embeddings, categories, and the news stories found in it. A news edition keeps the headlines and summaries written for it until you disconnect or delete your account. If syncing stops, because your Google access ended or your plan ended, Enfold keeps what it has until you reconnect, disconnect, or delete your account. After a disconnect or account deletion, the 30-day deletion in section 7 applies.
At expiry, cached bodies, attachments, and images stop being available at once. Bodies are deleted soon after, usually within the hour. Files and images are gone from storage within 10 days.
Images in email. Many emails contain images that load from the sender's servers. Enfold loads them through its own server on AWS, so senders never see your IP address or your browser. Enfold loads the images of new mail when it arrives, and of the last 7 days of mail when you connect Gmail. For most mail, this tells the sender only that the email arrived, before you open it. Some images still load when you open or view them: in spam, trash, and drafts, in emails with more than 100 images, and photos shown in Orders and Events, and some in News. For those, the sender can tell roughly when you looked, but never your IP address or browser. After 7 days, opening the email loads its images again through Enfold's server. The sender can then tell roughly when you opened it, but still not your IP address or browser.
If your plan ends. Enfold stops syncing your mail and stops AI work on it. Your data stays at least 30 days, so you can come back. You can delete it sooner at any time.
7. Disconnecting Gmail and deleting your account
Disconnect a Gmail. Enfold stops using its Google access at once and revokes that access at Google, usually within an hour. If Google's revoke keeps failing, Enfold keeps trying for up to 72 hours, then deletes the encrypted token anyway and asks you to remove Enfold in your Google Account. A disconnect is also a request to delete Enfold's data for that Gmail. Your mail stays in Gmail.
Delete your account. Enfold disconnects every Gmail, cancels your subscription, and deletes your Clerk sign-in. You are signed out. Your mail stays in Gmail.
What we delete, and when. Within 30 days of a disconnect or an account deletion, we delete everything Enfold holds for that Gmail: message details, bodies, search text, embeddings, attachments, categories, orders, events, news, and contacts. For an account deletion, we replace your sign-in ID with a placeholder and clear your time zone and consent record. The account record stays, holding only your Stripe customer ID and plan dates, for the billing and paid-call records. Leftover file copies in storage are gone within 10 days. Backups keep a copy for up to 7 more days, then expire. We keep only the billing and paid-call records in section 6, which hold no mail content. Records of paid service calls stay for up to 7 years under your internal Enfold account ID. Our database holds no name, email address, or sign-in for that ID, but our billing records keep your Stripe customer ID, so the ID stays linked to Stripe's customer record, which keeps your email address for tax records.
Remove access in Google. You can also remove Enfold at myaccount.google.com/connections. This stops Enfold's access, but it does not delete the data Enfold holds. To delete it, disconnect in Enfold, delete your account, or email us.
Ask by email. Write to privacy@tryenfold.com from the address of your Enfold account to ask for deletion, or for a copy of the data Enfold holds about you. Our help page has the steps.
8. Other data we collect in the app
- Account. Your Clerk ID, your time zone as your browser reports it, your consent record, and your plan dates.
- Billing. Stripe handles your card and billing. Enfold never receives your full card number. Of your payment details, Enfold uses only the country of your card or payment method and your billing country, to check that Enfold is available to you, and stores none of them.
- Cookies. The app sets four of its own: Clerk's session cookies (sign-in),
enfold_oauth(for 10 minutes while you connect your Google account for Gmail and Google Calendar, to protect the connection),theme(your light or dark setting, 1 year), andzone(your time zone, to pick the background painting, 1 year). The app shows no ads. - Do Not Track and Global Privacy Control. Neither Enfold nor any third party collects information about your activity across other websites on our app or our website. We treat a Global Privacy Control signal as a request to opt out of sale and sharing. We do neither.
9. Our website
Our website at https://www.tryenfold.com is separate from the app. It never receives Google data.
- Waitlist. If you join the waitlist, we store your email address, the page and ad you came from, and the visitor and session IDs below. We keep it until you ask us to remove it.
- Visit events. The site records which pages you view and what you click, including steps of the waitlist form. When you leave the email field, it records the part of the address after the @, not the whole address. It also records your country (from your IP address, which we do not store), browser type, screen size, color setting, time on the page, the site that linked you, and ad campaign tags in the link. We have no set deletion date for these records.
- Cookies and browser storage.
v, a random visitor ID (1 year).tz, your time zone offset, to pick the background painting (1 year).split-welcome-positioning, which version of a page you see (30 days). For each browser tab, a session ID and an ad key that end when you close the tab.
10. People who email Enfold users
Enfold processes mail sent to our users only to provide Enfold to them, as this policy describes. To ask about your data, write to privacy@tryenfold.com.
11. Your rights
You can ask us to access, correct, or delete your personal information, or for a copy of it, at privacy@tryenfold.com. We will not treat you differently for asking.
We confirm a request by replying to your account's email address. An authorized agent can ask for you with your signed permission. If we refuse a request, reply "appeal" and we answer within 45 days.
We do not sell or share your personal information.
12. Who Enfold is for
Enfold is for people 18 and older in the United States. We do not knowingly collect data from anyone under 18. If you think we did, email us and we will delete it.
13. Changes to this policy
We will email you and show a notice in the app at least 14 days before a material change takes effect. Before Enfold uses your Google data in a new way, we will ask for your consent again. Each version of this policy carries its version number and effective date.