We read everything.
We keep almost nothing.

This Privacy Policy explains how Unfold ("Unfold," "we," "our," or "us") collects, uses, and protects your information when you use Unfold Work, our AI mail agent, together with the website at unfoldwork.ai and related services (the "Service"). If you connect a Google account, please read the section on Google user data with particular care.

Our principle is simple, and the rest of this page is the detail behind it: Unfold Work reads your mail where it lives, works on it in memory, and keeps only a small notebook of derived signals and settings. We never build an archive of your email, we never use your mail to train generalized AI models, and everything derived from a mailbox is deleted the moment you disconnect it. The few things that belong to your account rather than to a mailbox, your notification settings and any alert channel you add, are deleted when you delete your account.

1. Who this applies to

The Service is a business tool intended for professionals aged 18 or over. It is not directed to children, and we do not knowingly collect information from anyone under 18. The Service is currently in beta: you can create an account yourself by signing in with Google or Microsoft.

2. Information we collect

2.1 Information you provide

• Contact details: when you send us a question through the contact form on our site, we collect your email address, the message you write, and your approximate country, so we can answer you.
• Account information: when you create an account, we collect your name and the email address you sign in with.
• Your rules and preferences: the settings you configure, such as your VIPs, quiet hours, the strictness dial, and the corrections you make to the agent.
• Communications: the content of messages you send us for support or feedback.

2.2 Mailbox data (when you connect a mailbox)

With your explicit authorization through Google's consent screen, Unfold Work connects to your Gmail or Google Workspace mailbox using Google OAuth. We request the narrowest scopes that let the Service work:

• Read access to your mail so the agent can read incoming and recent messages, understand threads, and decide what needs your attention.
• Label and draft access so the agent can apply its own reserved label namespace and place suggested replies in your Gmail drafts. Google grants this as a single scope, gmail.modify, and that scope is broader than what we do with it: it also permits sending. We use it to read, to label inside our own namespace, and to write drafts. The one place it sends is the Send button inside a draft you have opened and read, which is off until you turn it on and which tells Gmail to send that one draft. Nothing else in the Service sends. We never move, archive, delete, or mark your mail read, and the scope does not permit permanent deletion at all.

If you connect a Microsoft 365 or Outlook mailbox instead, the same applies through Microsoft's consent screen and the Microsoft Graph API. Two of the permissions listed on that screen are worth naming plainly. Mail.ReadWrite lets the agent read your mail and write its own categories and drafts; it also permits deleting and moving mail, which we never do. Mail.Send lets the Service send from your address, and it has exactly two uses: delivering your brief to your own inbox as mail from you to yourself, because Graph offers no other way to place a message in a mailbox, and the Send button inside a draft you have opened and read, which is off until you turn it on. Nothing else in the Service sends. Everything in this policy about what we derive, what we keep, and what we delete applies identically whichever provider you connect.

You can review or revoke this access at any time in your Google Account or Microsoft account security settings, or by disconnecting inside Unfold Work.

2.3 What we derive and keep (the notebook)

From the mail we read, we keep a small set of derived artifacts, and nothing more:

• Decisions and reasons: a score, a label, and one line of why for each message, so every call the agent makes stays auditable.
• Signals: one-line facts, each pointing back at its source email. These are deletable line by line.
• A working copy of recent mail: encrypted per account, kept on a rolling 30-day basis and then gone. This is a working copy, never an archive.
• A voice profile: a model of how you write, not what you wrote, so reply drafts sound like you.
• Correspondence patterns: who you exchange mail with and how often, as counts and timings only, never message content.

2.4 Information we collect automatically

• Usage and device data: how you interact with the Service, along with device type, browser, and IP address.
• Cookies and analytics: our website uses cookies and analytics tools, including Google Tag Manager and the services it loads, to understand traffic and improve the site. You can control cookies through your browser settings.

3. Google user data and Limited Use

Unfold Work's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• We use Google user data only to provide and improve the user-facing features of Unfold Work, namely triaging your inbox, surfacing Signals, drafting replies, and sending one of those drafts when you press Send on it.
• We do not transfer or sell Google user data to third parties for advertising, marketing, or any other unrelated purpose.
• We do not use Google user data to train, develop, or improve generalized or standalone AI or machine-learning models. Any learning happens only for your own account, to serve you.
• We do not allow humans to read your Google user data unless you give explicit consent, it is necessary for a specific security investigation or to comply with applicable law, or the data has been aggregated and anonymized. Every such access is logged.

4. How we use your information

• To read and classify your mail and decide what genuinely needs your response.
• To produce your morning brief, deltas, catch-ups, and Signals.
• To draft replies in your voice for you to review, edit, and send yourself.
• To learn who matters to you and honor the rules and guarantees you set.
• To create and manage your account and provide the Service.
• To respond to support requests and send service-related notifications.
• To secure the Service and detect, prevent, and address abuse or technical issues.
• To comply with legal obligations.

5. AI processing

To classify mail and draft replies, Unfold Work sends the necessary content to AI providers acting as our subprocessors. We contractually bind these providers to zero-retention and no-training terms: they process your content to return a classification or a draft, and keep nothing afterward. Your mail is not used to train generalized AI models, and there is no cross-customer learning on your content. During the current release, Unfold Workroutes AI through Unfold's own configured providers only.

6. What we never do

• We never build an archive of your email.
• We never store attachment contents.
• We never write your mail content into our logs.
• We never train AI models on your mail.
• We never sell your personal information or your Google user data.
• We never send a reply on our own. Sending is always your press, on a draft you have read. We never delete or hide your mail. Nothing goes out unless you press send.

7. How we share your information

We do not sell your personal information. We share it only with service providers who help us run Unfold Work, under contracts that limit them to that purpose:

• Google: the source of your mail, which stays in your Google mailbox.
• Cloud infrastructure and key management: our hosting and encryption key providers, used to run the Service and protect data at rest.
• AI providers: under the zero-retention, no-training terms described in Section 5.
• Email and analytics providers: to handle contact-form and service-related email and to understand website traffic.
• Paddle (payments): Paddle.com is our Merchant of Record and handles all purchases, billing, and taxes. If you subscribe, you provide your payment details directly to Paddle under Paddle's privacy notice. We never see or store your card number: we receive only your subscription status, plan, billing period, and the identifiers needed to keep your account active. Payment data is never used for anything else, and it never touches the mail pipeline.

Our subprocessors, as of the date at the top of this page:

• Google Cloud:application hosting, background job queues, mailbox change notifications, and the key management service that holds each mailbox's encryption key.
• Neon: database hosting. Mail bodies in the database are ciphertext under keys Neon never holds.
• Cloudflare: web hosting and delivery for this site and the app, and storage for profile avatars.
• Auth0 (Okta): sign-in. Auth0 holds your login identity, never your mail.
• Paddle: payments, as merchant of record (see above).
• Resend: account-lifecycle email such as a mailbox going dark or an ownership change. Never your mail content.
• AI providers: Google, Anthropic and OpenAI, whichever our current release routes to, under the zero-retention, no-training terms in Section 5.

We update this list on this page when it changes. We may also disclose information where required by law, to enforce our Terms, to protect the rights and safety of Unfold and our users, or in connection with a merger, acquisition, or sale of assets.

8. Data retention and deletion

The encrypted working copy of recent mail is kept on a rolling 30-day basis and then deleted. Derived artifacts (decisions, Signals, voice profile, correspondence patterns, and your mailbox rules) are kept while the mailbox they came from is connected.

When you disconnect a mailbox, the order matters: the key that decrypts its working copy is destroyed first, rendering that copy unrecoverable, and then every row derived from that mailbox is deleted. Encrypted backups age out within 30 days. If our database were exposed, an attacker would find scores, pointers, and a sketch of how you write, along with the one-line Signals we already showed you, but not the contents of your mailbox. Your mail was never stored with us.

A small set of things belongs to your account rather than to any one mailbox: your notification settings (quiet hours, interrupt limits, timezone) and, if you add one, the Slack or Teams webhook that carries your alerts. The webhook is encrypted under a key tied to your account and is never shown again after you save it. Because these were never a mailbox's, disconnecting a mailbox does not delete them; they stay until you remove them in Settings or delete your account. Deleting your account destroys that key first, then deletes the rows.

9. Security

• Encryption in transit (TLS) and at rest, using per-account keys held in a managed key service, separate from the data.
• Per-user tenant isolation.
• Access controls, authentication, and logging of any human access to content.
• Log redaction so mail content does not enter our logs.

We are pursuing Google restricted-scope verification and CASA Tier 2 assessment before public launch. No method of transmission or storage is completely secure, and while we work hard to protect your information we cannot guarantee absolute security.

10. Your rights and choices

Depending on where you live, you may have rights to access, correct, delete, export, or restrict the processing of your personal information, and to object to processing or withdraw consent. In practice, the strongest controls are always in your own hands: you can disconnect a mailbox at any time, which deletes what we hold for it as described in Section 8, and you can delete your account at any time from Settings in the app, which disconnects and purges every mailbox you connected and deletes your settings and any alert channel. To exercise any other right, contact us at [email protected] and we will respond within the timeframe required by applicable law.

If you are in the European Economic Area, the United Kingdom, or Switzerland, our legal bases for processing are the performance of our contract with you, your consent (for connecting your mailbox and for marketing), our legitimate interests in operating and securing the Service, and compliance with legal obligations. If you are in California, you have rights under the CCPA, including the right to know, delete, and not be discriminated against for exercising them; we do not sell personal information. If you are in India, you have rights under the Digital Personal Data Protection Act.

11. International data transfers

Your information may be processed in countries other than your own, including where our infrastructure and providers operate. Where required, we rely on appropriate safeguards, such as standard contractual clauses, to protect your information when it is transferred.

12. Changes to this policy

We may update this Privacy Policy from time to time. We will post the updated version here and revise the "Last updated" date, and we will provide additional notice for material changes where required.

13. Contact us

If you have questions or requests about this policy or your data, contact us:

Want the plain-language version, with a full inventory of what we keep? See how we handle your data on the home page.