Privacy policy
Effective date: 6 November 2026 · Last updated: 12 November 2026
1. Who we are
mindsweep is operated by João Silva (“we”, “us”), who is responsible for your data under this policy. Questions about this policy or your data, and any request under §10: privacy@mindsweep.si.
2. What we collect
- Your account: your email address and name, how you sign in (a one-time email link or Google), your time zone and your settings. Signing in with Google shares the basic profile Google sends with it: name, email address and profile picture. If you signed up with a promo code or through someone’s invitation link, we keep which code or whose link it was. The person who invited you sees how many people joined through their link and how many of them pay, never who.
- What you connect, and only that:
- Gmail (read-only, unless you choose to send a nudge): when you connect, your mail from the last 30 days, Sent included; after that, new mail as it arrives. We skip chats, spam, trash and the Promotions, Social and Forums categories. From each message we keep its sender, recipients, subject, date and text, and the names, types and sizes of its attachments, never the attachments themselves. We never delete or change mail, and we send none on our own: the one message we ever send from your address is a follow-up (“nudge”) that you have read and pressed Send on, after you have given Google a separate permission for it. We do not keep that message; it is in your Sent mail like any other you send, and is read from there like the rest.
- Slack (read as you; we never post): your direct and group messages, the channel conversations, public or private, where you wrote or were mentioned, and the names and email addresses of the people in them, so that a Slack colleague and an email contact are one person.
- Google Calendar and Google Tasks (events read-only; we never create, change or delete events): the events on your primary calendar from 7 days ago to 60 days ahead, each with its title, time, link and the email addresses of its guests and organiser, never its description, location or conference details. We use them to show what is open with the people you are about to meet and to date a commitment due “after the board meeting”. Our copy is refreshed every 15 minutes and deleted when you disconnect. When you choose Add to Google Calendar on a commitment, we make it a Google Task in a task list of our own, “mindsweep”, and keep the two in step: ticking either one ticks the other. We read your task lists’ names only to find ours, and never read or change the tasks in your other lists.
- Granola or Fireflies, with the personal API key you give us: your meeting notes (in Granola, your private notes too), summaries and transcripts, with each meeting’s title, time and attendees.
- Your capture address and the Capture box: what you forward to the address or type into the box. Attachments sent to the address are dropped; we keep their names, types and sizes.
- The browser extension, if you use it (mindsweep for Chrome): what you type into it, and text you select on a web page and choose to send with it. It sends that text and nothing else of the page: not its address, its title or the rest of what it says, and it reads no page until you select something and open it. We also keep when you signed it in and when it last used its access.
- Assistants you connect: each one’s name as it gives it, when you connected it, whether it may change your commitments, and when it last used its access. We do not keep what it asks us or what we answer.
- What we derive: commitments (a short title, who owes whom, a due date), the short quotes they came from, the people involved, and the rules mindsweep learns when you correct it.
- Billing: handled by Stripe; we keep your subscription status, not your card.
- Service telemetry: identifiers, error codes and timings, never the content of your messages.
- This website: Vercel Web Analytics counts page views without cookies (the page, the referring site, country, browser and device type).
3. How we use it
Only to give you mindsweep: your ledger of commitments, Review, the daily digest, reminders you ask for and your export; to keep the service secure and working; and to measure, in counts that carry no message content, whether the beta works. We do not sell your data, use it for advertising, or share it except as §5 to §7 say, as you send it yourself with Ask, or as an assistant you connect reads it at your request, below.
Ask. When you ask for help with one of your commitments (swipe its card up in the Sweep, or choose Ask), we write a prompt about it for you to take to Claude or ChatGPT. To write it, Anthropic’s Claude reads the commitment and, while we still hold them (§8), a few of the messages, conversations or meetings it came from, the first and the newest, as in §5; a long one is cut to the parts nearest where the commitment was said. You see the prompt first and can change it. It leaves only when you choose Open in Claude, Open in ChatGPT or Copy prompt, and you send it there yourself, under that service’s own terms. Anthropic (for Claude) and OpenAI (for ChatGPT) are not our processors for this: their terms and privacy policies apply to what you send them. The first time, we show you a note saying so, and record the date of the first open or copy you make with the note on screen (it is in your export). The prompt travels in the address of the link that opens the chat, so it is kept in your browser’s history; a prompt too long for a link is copied to your clipboard instead, and the chat opens empty for you to paste it in. We do not store the prompt or put it in our logs (Anthropic, which writes it for us, keeps it only as §5 says); we count only where you took it and whether a full message was read, without its words.
Assistants. If you connect Claude or another assistant to mindsweep (see mindsweep.si/assistants), it can read your commitments when you ask it to, and change them if you allow it. It gets only what it asks for: commitment titles, the people involved and their email addresses, dates, the short quote a commitment came from where you are asked to decide on it, and, asked about one commitment, up to three of the messages, conversations or meetings behind it, with short quotes and links. It never gets a message’s full text. Nothing is shared until you approve the assistant on our page, where you can also limit it to reading; you can disconnect it at any time in Settings › Assistants, and its access ends at once. The assistant’s provider (Anthropic for Claude, OpenAI for ChatGPT, and so on) is not our processor for this: you chose to connect it, and its own terms and privacy policy apply to what it receives. We record each change an assistant makes, as we record your own, but not what it asked or what we answered.
The browser extension. mindsweep for Chrome is our own software, a second window onto your account. A line you type or select and send with it is read the way the Capture box reads one (§5) and added to your commitments. It shows what you owe and what you are owed: each commitment’s title, the person’s name, its due date and how often it recurs, never a quote or the text of a message. So that it opens at once, it keeps in your browser’s own storage a copy of the open commitments it last showed, its sign-in, and anything you typed that has not been sent yet, such as a line added while you were offline. That copy is on your computer, outside the encryption in §9, and can be read by anyone who can open your browser profile. It is removed when you sign out of the extension, when you disconnect it in Settings › Account (the next time the extension opens) or when you remove the extension from Chrome. Disconnecting ends its access at once. We record each change you make with it, as we record those you make in the app, but not what you typed beyond the commitment itself.
4. Google user data and Limited Use
mindsweep’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
We ask Google for read-only access to Gmail (gmail.readonly) only to find the commitments in your mail, to notice
when they are kept, and, when you ask for it, to write a prompt about one of them (Ask, §3) or to answer an assistant you connected (§3). If you choose to send a
follow-up from mindsweep, we also ask, at that moment and not before, for permission to send mail (gmail.send), used
only to send the message you approved when you press Send. If you connect Google Calendar, we also ask for read-only access to your calendar’s events
(calendar.events.readonly) and for Google Tasks (tasks), only for the uses in §2; calendar events and tasks are
never sent to an AI model. In particular: data from Gmail, Google Calendar and Google Tasks is used only to provide the
features in §3; it is not transferred to
others except the processors in §7 that make those features work, the Ask prompt you send yourself to Claude or
ChatGPT (§3), which leaves only when you open or copy it, after you have seen it, and what an assistant you connected
and approved yourself reads at your request (§3); showing you your own commitments in mindsweep’s browser extension
is part of mindsweep and not a transfer; it is never used for advertising or sold; no person
reads it unless you agree to it for specific messages (§6); and it is never used to train or improve AI models, ours
or anyone’s. The rules mindsweep learns from your decisions are yours alone and are not pooled with other users’.
5. How AI reads your messages
Mail we recognise as bulk or automated is set aside by fixed rules before anything else happens. To find commitments, the text of a message, conversation or meeting is then sent to Anthropic’s Claude API, which processes it in the United States and returns what it found. Anthropic acts as our processor and does not use it to train models. Under our current terms Anthropic deletes inputs and outputs within 30 days; content its safety systems flag may be kept for up to 2 years. If Anthropic confirms zero data retention for our account, we will update this section. A line you send with the browser extension, typed or selected from a page, is read the same way and on the same terms.
Three yes-or-no judgments about what was found (whether a line is a real commitment, whether a later message delivers it, whether two lines say the same thing) are made by TypeSafe AI’s decision model, which is sent the same few lines and answers only with probabilities. TypeSafe acts as our processor. It is reached through Vercel’s AI Gateway, and every such request is sent under zero data retention: TypeSafe does not keep the lines or its answer once it has answered, and does not use them to train models. Vercel’s gateway passes the lines on and does not log or keep them. It records that a request was made, to which model, and its size, cost and duration.
6. Who can see your data
You. Our support tools cannot read your messages, quotes or commitments. The people who run mindsweep’s servers do not read your content, except when you ask us to (for example, about a specific message in a support request), when it is needed to investigate abuse or a security incident, or when the law requires it; every use of the keys that decrypt it is logged. The one exception is a quality review you may be asked to join: each week we would show you a few of the items mindsweep listed for you, and a person on our team reads only the ones you approve. Every such read is logged.
7. Processors we use
| Processor | What it holds | How long |
|---|---|---|
| Vercel (US) | the app; request logs with ids and paths, no message content; page counts | 1 day |
| PlanetScale (US) | the database; message content encrypted with a key for you alone | backups kept 2 days |
| Google Cloud (US) | the encryption keys; key-use audit logs | audit logs 400 days |
| Anthropic (US) | message text while it is read (§5) | up to 30 days; flagged content up to 2 years |
| TypeSafe AI, through Vercel | the lines a yes-or-no judgment is made on, while it is made (§5) | not kept: zero data retention (§5) |
| Inngest | job ids and timings, no content | 7 days |
| Cloudflare | emails to your capture address while in transit; failed deliveries | up to 72 hours |
| Resend | the emails we send you (titles of commitments, no quotes) | as Resend’s terms set, up to 30 days |
| Stripe | billing and payment | under Stripe’s terms |
| Sentry, Axiom, Better Stack | error reports, logs and uptime checks: ids and codes only | up to 90 days |
8. How long we keep it
- The full text of messages, conversations and meetings is deleted 60 days after it was sent or held.
- Commitments, their short quotes and the people involved stay until you delete them or your account.
- The browser extension’s copy in your browser (§3) is kept until you sign out of the extension, disconnect it or remove it. A sign-in you have not used for 30 days ends by itself, and the copy goes with it.
- Disconnecting a source stops all reading from it. We revoke our access at Google and Slack ourselves; Granola and Fireflies give us no way to do that, so delete the key in their settings as well. What was already read follows the rules above.
- When a free trial ends and you have not subscribed, we stop reading every source you connected and stop the daily email. Nothing is deleted because of it: your ledger stays, to work from and to export, and what was already read follows the rules above. Subscribing starts the reading again, from where it stopped.
- Deleting your account (Settings → Account) revokes our access to every source, destroys your encryption key and deletes your data the same day. Backups that still hold your encrypted data expire within 2 days, and without the key they cannot be read.
- After a deletion we keep, under an internal id and with no email address or message content, the days you used mindsweep, your Review and quality-review decisions and your subscription status, to measure the beta, for up to 2 years. Billing records (what you paid and when) are kept by us and by Stripe for as long as tax and accounting law requires, usually 7 years.
9. Security
Message content is encrypted at rest with a key unique to you, held in Google Cloud KMS. All traffic is encrypted in transit. Access to production is limited to the people who run mindsweep, with two-step verification, and logged.
10. Your choices and rights
- Export everything as JSON or CSV from Settings → Account.
- Disconnect any source at any time (§8).
- Correct or delete any commitment in the app, or delete your account.
- Ask us at privacy@mindsweep.si to see what we hold about you, to correct it, to delete it or to stop a use of it. We answer within 30 days and never charge for it. We may ask you to confirm the request from your account’s email address.
- We do not sell or share your personal information as California law defines those words, and we do not use it for targeted advertising. California residents have the rights above under the CCPA, and we will not treat you differently for using them.
- In Canada, if you are not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca).
11. Where your data is processed
In the United States. During the beta mindsweep is offered in the United States and Canada only (outside Quebec). If you use it from elsewhere, your data is still processed in the United States.
12. Children
mindsweep is not for anyone under 16, and we do not knowingly collect data from them. If you believe someone under 16 has an account, write to privacy@mindsweep.si and we will delete it.
13. Changes
We will post changes here and email you before any change that reduces your rights.