Draft: to be reviewed by a lawyer before it is published. Not legal advice.
Privacy policy
Last updated (effective date): [date]
This policy is written in English and Chinese. The English version governs; the Chinese version is for reference only.
1. Who we are and what this policy covers
The sharing service, Workspace AI and usage data of Mushroom are provided by Jiteng Xu, an individual developer based in Shenzhen, China (“we”, “us”). For anything about privacy, write to privacy@pickmushroom.com.
This policy covers: the “Share link” feature in Mushroom and the share pages on pickmushroom.com; project forwarding addresses (you forward a client’s email to a project’s address, and it becomes client feedback in Mushroom); Workspace AI (the AI models we provide in Mushroom for automatic organizing, the AI bar and the agent in Mushroom), whose content passes through our service to the model providers (section 14); the usage data Mushroom sends us (section 12); and the problem reports you choose to send us (section 16).
Early access: if you ask for early access on our homepage, we keep the email address you give, and which AI tools you use if you say, only to email you when your invite is ready; we keep them for 12 months at most and then delete them, and you can ask privacy@pickmushroom.com to delete them sooner.
Mushroom itself runs on your computer and does not upload your library to us. Only these leave your computer: the version you choose to share; the email you forward to a project address; what is sent to a model when you use Workspace AI (for background organizing, a file’s title and first paragraph; when you use it yourself, what you ask it to work on), passed through our service to the model provider and not kept by us; usage data; and the reports you choose to send. Once you connect a mailbox, Mushroom reads it directly on your computer, and your mail does not pass through us (section 13).
Where this applies: The first version is offered to users in the United States, and this policy is written under U.S. law. People elsewhere can download and use it, but we do not market, price or provide local services for any other country or region. Before we offer the service in Europe, the United Kingdom, Japan or elsewhere, we will update this policy and tell you in advance.
2. Two kinds of people
| Users | Clients | |
|---|---|---|
| Who | People who sign in to Mushroom, create share links or use Workspace AI | People who open a share link to look at it and leave feedback, without signing up |
| Their relationship with us | We provide the service to you under the terms of service. We handle your account, usage, device identifier, subscription and usage data as this policy describes | What you leave on a share page is for the user who shared it with you. We keep it and pass it on for that user, handle it on the user’s instructions, and use it for nothing else |
The same applies when a client’s email to a user is forwarded to a project address, and when a file a user gives Workspace AI contains personal information about clients or other people: we process it on the user’s behalf, only to provide the features the user asks for. We do not sell it, share it, use it for training, or combine it with other data we hold. The user must have the right to use this information in this way and, where needed, tell their clients (terms of service, section 3).
3. What we collect and why
| Data | Whose | Why |
|---|---|---|
| Email address | Users | Signing in (a code by email, or the address Google or Apple gives us when you sign in with them; Apple’s relay address if you chose “Hide My Email”), and telling you about new comments (you can turn this off) |
| Sharer name | Users | So clients see who shared the page |
| Signed-in devices (device name, sign-in method, times) | Users | So you can see and sign out other devices; account security |
| Display language | Users | To email you in your language |
| What you share: the files of the version you chose, its title, “What changed”, who it’s for | Users | To show it to clients |
| How many times a link was opened, and when it was last opened | Users’ links | Shown on the card; who opened it is not recorded |
| A comment’s text, where it is pinned, and its time | Clients | Passed on to the user who shared the page; we process it for that user |
| A client’s follow-ups (replies under a comment) and their times | Clients | Passed on to the user who shared the page; shown under that comment to anyone with the link |
| The sharer’s replies to clients and their times; which comments are “addressed”, and in which version | Users | Shown to clients on the share page (the user’s own copy is what counts; ours is only there to show clients) |
| When “Approve” was clicked or withdrawn | Clients | Passed on to the user who shared the page |
| Delete codes and withdraw codes (only their hashes) | Clients | So whoever left a comment or follow-up can delete it, or withdraw an approval |
| Email forwarded to a project address: body, attachments, subject, the names and addresses in its sender and forwarding chain, and times | Forwarded by users; mostly written by clients | Passed to the user’s Mushroom, where it becomes client feedback in that project; attachments go into the project. We process it for the user |
| Project forwarding addresses (16 random characters, unrelated to the project’s name) and which project each belongs to (an ID in Mushroom, not its name); registered sender addresses, verification codes (only their hashes), and how many emails arrived | Users | To tell which user’s project an email is for; to accept only mail forwarded from addresses you registered, so others can’t push things into your address |
| Content sent to Workspace AI when you use it yourself (the AI bar, “Ask an agent”, handing a task to Mushroom, writing a cover note, the check before sending, placing client feedback): the passage or files you chose, what you asked for, and the project’s files, comments and client feedback the agent reads step by step | Users (may include clients’ personal information) | Passed to the model provider to do what you asked, with the result returned to your Mushroom; passed through only, never kept |
| Content sent to Workspace AI for background organizing (filing into projects, summaries, search re-ranking, judging whether a file is a deliverable): a file’s title and first paragraph | Users | Automatic organizing; passed through only, never kept; for the model provider, see section 5. You can turn it off at any time (then only this computer’s rules are used) |
| Content sent to Workspace AI to split a client’s email (the points this computer’s rules can’t split, and the file’s outline) | Written by users’ clients | To split an email into separate points of feedback and put each in the right place; passed through only, never kept. You can turn it off in Settings › Account & email › Email |
| Device identifier: a random token created the first time you use Workspace AI (kept in your computer’s keychain); after public launch, also Apple DeviceCheck’s two bits (whether this computer has had its free credits, and whether it was flagged for abuse) | Users’ devices | To track free credits and prevent abuse; not used for analytics, and kept apart from the random ID in section 12 |
| Workspace AI usage: device or account, purpose, model, token counts (including those read from the cache), estimated cost, credits charged and time; no content | Users | Credits, billing, reconciliation and overall limits |
| Subscription (once paid plans start): the subscription status, country, and payment and renewal times Paddle gives us; we never see card numbers | Users | Starting and renewing Pro; tax records |
| Usage data (section 12): a random ID, event names and counts, a summary of each Workspace AI task, error signatures, version and system; no content | Users’ devices | To know which features are used, what goes wrong, and whether it got fixed |
| Reports you choose to send (section 16): the parts you ticked | Users | To find and fix problems |
| IP address | Everyone | Only used while a request passes, to limit request rates and stop abuse and password guessing; never written to the database, and no access logs. When you use Workspace AI, also used to see which country you are in (Workspace AI is not offered in mainland China in the first version), and not written down either |
What we don’t collect: clients’ names, email addresses, phone numbers or companies (except where written in email forwarded to us); precise location, biometrics, health information, bank card numbers or government ID numbers; any tracking cookies, advertising IDs or third-party analytics; anything in your library you didn’t share (other versions, comments, sources, prompts, file paths); and the content sent to Workspace AI itself (passed through, never written down).
Where it comes from: from you directly (signing in, sharing, forwarding, sending reports); generated as you use Mushroom and share pages (open counts, usage, usage data); from your clients (feedback on share pages, email you forward); from Google and Apple (the email address they give us when you sign in with them); and from Paddle (subscription status, country).
4. Cookies, browser storage and Do Not Track
| What | Whose | What for | How long |
|---|---|---|---|
The share page’s password session cookie (HttpOnly, Secure, SameSite=Strict, for that one link only) | Clients opening a link with a password | Not having to enter the password again after entering it correctly | 12 hours |
| The browser’s localStorage: delete codes (for comments and follow-ups), withdraw codes, versions seen, when you last looked | Clients | So you can delete your own comments and follow-ups and withdraw an approval on this device, see “Updated to v4”, and tell which replies are new. When you last looked is the time of the newest item you saw | Until you clear it (one click under “Privacy” at the bottom of the share page) |
All of these are needed for features you ask for, so there is no consent banner.
Do Not Track and Global Privacy Control (GPC): We do not track you across websites, and we do not let third parties track you on our pages, so a browser’s “Do Not Track” signal does not change what we do. When we receive a GPC signal, we treat it as a request not to sell or share your personal information; we don’t sell or share it anyway.
5. Who gets it
We give personal information only to the people below and to companies that provide services for us (service providers), and only for the purposes stated. Service providers handle it under their agreements with us and may not use it for anything else.
- The user who shared the link: receives clients’ feedback and approvals.
- Others with the link: see the list of comments on the share page (without names) and the replies under them.
- Service providers (subprocessors): in the table below. The same table is also on its own page, Subprocessors.
- When the law requires it: we give it to law enforcement or courts when a valid subpoena, court order or similar legal process requires it, and tell you first where we are allowed to.
- If the business is transferred: in a merger, acquisition or sale of this service, the data goes with the service to whoever takes it over; we will tell you in advance, and they will handle it as this policy describes.
| Subprocessor | What it does for us | Personal information it handles | Where data is stored and processed | Training and retention |
|---|---|---|---|---|
| Cloudflare, Inc. (United States) | Hosts the share pages, the API, the database and file storage; runs our relay service for Workspace AI; receives usage data and problem reports | Accounts, links, shared files, comment threads, usage, device identifiers, usage data; problem reports (encrypted only) | Database and file storage restricted to the United States (Cloudflare’s U.S. data jurisdiction); requests are handled in the Cloudflare data center nearest the visitor | Kept as we configure it (privacy policy, section 7); the sharing service logs errors only, kept 7 days |
| Cloudflare, Inc. (Email Routing) | Receives email forwarded to project addresses, rejects spoofed mail by the sender domain’s SPF, DKIM and DMARC, and passes the rest to our service | Forwarded email: body, attachments, and the names and addresses written in it | Received on Cloudflare’s global network; stored in the United States once passed to our service | Deleted as soon as the user’s Mushroom has collected it |
| Cloudflare, Inc. (Workers AI) | Runs Workspace AI’s models for agent edits and Workspace AI tasks in Mushroom, and for background organizing (filing into projects, summaries, search re-ranking, judging whether a file is a deliverable). The models are open models (DeepSeek V4.1 Flash, gpt-oss-120b, and Kimi K2.6 as the agent’s backup), run by Cloudflare itself, not through the APIs of DeepSeek, Moonshot AI or any other model maker; no data goes to those companies | What the user asks it to work on; for background organizing, only a file’s title and first paragraph | Cloudflare’s global network (GPUs in more than 200 cities); not restricted to the United States | Not retained after processing; not used for training |
| Fireworks AI (backup, only when needed) | Runs the same open model (DeepSeek V4.1 Flash) when Workers AI is over capacity (rate-limited) | As Workers AI | United States [to check] | Not retained and not used for training by default [to check] |
| Resend | Sends sign-in codes, new-comment notifications, and the codes for registering a sender address for a forwarding address | Recipient addresses and the text of these emails | Sent through Tokyo; data stored in the United States [to check] | Sending records, kept for [to check] |
| Verifies who a user is when they choose “Sign in with Google” (users only, never clients) | The user’s Google account email address | United States | — | |
| Apple | Verifies who a user is when they choose “Sign in with Apple”; relays notification emails when they chose “Hide My Email”; after public launch, DeviceCheck records whether this computer has had its free credits and whether it was flagged for abuse (users only, never clients) | The email address or Apple’s relay address; two bits (no content, and they don’t say who you are) | United States | — |
| Paddle (once paid plans start; contracting entity [to check]) | Collects subscription payments and handles sales tax, invoices and refunds; it is the merchant of record | Payment details (it collects them; we never see them), subscription status, country | [to check] | Under Paddle’s privacy policy and tax law |
- No selling, no sharing, no training: We do not sell personal information, do not “share” it for cross-context behavioral advertising, do not give it to advertisers, and do not use it to train any model. Our agreements with the model providers above do not allow them to train on Workspace AI content [to check].
- Adding or changing a subprocessor: we first update the Subprocessors page and this table, with the date of the update; a new subprocessor only handles data from then on. Replacing a provider with one of the same kind on the same terms is not announced separately; if a change is material (the new provider keeps data longer, trains on it, processes it outside the United States, or handles a new category of personal information), we tell you in Mushroom at least [30] days in advance.
- The interface does not name the model in use; every model we use is listed here. We do not offer a choice of “only models from certain countries”. Mistral AI, listed before as a backup, is not used now.
- When you borrow an agent on your computer or use your own API key, the content is governed by the terms between you and that provider (section 14), not by this table.
- Mailboxes you connect (section 13): Mushroom fetches mail directly on your computer from Google (Gmail API), Microsoft (Microsoft Graph) or your mail provider (IMAP), and Apple Mail is read on your computer; the mail does not pass through us and does not go to anyone in the table. When a client’s email is split into points, the points this computer’s rules can’t split or place, and the file’s outline, are sent to a model: with your own API key, to that provider; with Workspace AI, through our service and not kept, to [to be decided: which provider]. Until that is decided, Workspace AI does not split email and only this computer’s rules are used. The whole email is never sent.
6. Where data is processed and who can see it
| Data | Where it is stored | Who can see it |
|---|---|---|
| Accounts, links, shared files, comment threads, usage, device identifiers, usage data | Cloudflare’s database and file storage, restricted to the United States (Cloudflare’s U.S. data jurisdiction) | Us (in Shenzhen, China, through Cloudflare’s dashboard and our own admin page, only to run the service and investigate problems) |
| Reports you choose to send | As above, stored encrypted with the developer’s public key | Only the developer, who decrypts them on the developer’s own computer with the private key (section 16) |
| Email forwarded to a project address | Received on Cloudflare’s global network and stored in file storage in the United States; deleted as soon as your Mushroom has collected it | Our service passes it on automatically; we don’t open it |
| Content sent to Workspace AI | Only passes through our relay service on Cloudflare; for where the models run, see section 5 | The model providers, as section 5 describes; not us (we don’t keep it) |
| The library on your computer, mailboxes you connect, what is read on your computer | Your computer | Only you |
Stored in the United States does not mean processed only in the United States: your request first reaches the Cloudflare data center nearest you, where it is decrypted and handled by our service, which then reads and writes the database and files stored in the United States. For where content sent to Workspace AI is processed, see section 5.
We operate this service from Shenzhen, China. When we handle your account, answer your requests, or look at usage data and the reports you send, we access the service providers above from China. China’s laws differ from those of the United States.
7. How long we keep it
| Data | How long |
|---|---|
| Shared files | Deleted at once when the link is revoked; 30 days after it expires (within those 30 days it can be extended and opened again). When the link moves to a new version: with “Client can see earlier versions” on, the latest 3 versions are kept, each deleted 90 days after it was replaced, and any the user takes down are deleted at once; with it off, earlier versions are deleted at once |
| Comment threads: clients’ comments and follow-ups, the user’s replies, “addressed” | Deleted 90 days after the last activity (a new follow-up, a reply, marking it addressed), or with the link 30 days after it is revoked or expires, whichever comes first. A reply the user withdraws, or a follow-up a client deletes, is deleted at once; a comment its client deletes is deleted at once with its whole thread, the user’s replies included |
| Clients’ approvals | Kept on the server for 30 days after the user’s Mushroom has collected them, then deleted; any not collected are deleted with the link |
| The link itself (title, who it’s for, times) | Deleted 30 days after it is revoked or expires |
| Sign-in codes | Deleted once used, or after 10 minutes |
| Sign-in sessions | End when you sign out, or after 90 days unused |
| Accounts | Deleting an account deletes all its links, files and comments at once; the account record itself is deleted 30 days later (so a mistaken deletion can be undone) |
| Email forwarded to a project address (body, attachments) | Deleted from the server as soon as your Mushroom has collected it; if never collected, 30 days after it arrived; at once when you delete your account |
| Project forwarding addresses | Deleted 30 days after being turned off or replaced (mail forwarded in that time is still bounced); at once when you delete your account |
| Registered sender addresses | Deleted when you remove them or delete your account; if registered but never verified, one day after the code expires |
| Content sent to Workspace AI | We don’t keep it: it is only in memory while being passed on. For how long the model providers keep it, see section 5 |
| Workspace AI usage records | [e.g. 13 months], for billing and reconciliation; an account’s part is deleted at once when the account is deleted |
| Device identifiers | Deleted [e.g. 12 months] after last use; Apple’s two bits are stored by Apple, and we clear them after [to be decided] |
| Usage data (daily counts, task summaries, error signatures) | Deleted after 180 days |
| Reports you choose to send | Deleted after 90 days, or at once when you click “Delete”; the copy the developer downloads to their own computer to read is deleted once the problem is dealt with |
| AI request logs synced automatically during the trial (only if you turned it on) | Deleted after 30 days; syncing stops when the trial ends, and the rest is deleted within 30 days |
| Subscription records | Kept as tax law requires [to check: how many years], by Paddle and by us |
| Logs | The sharing service logs errors only (no email addresses, no content), kept 7 days in Cloudflare, not one line per request; we keep no access logs of our own; Workspace AI’s relay service writes no logs. How long Cloudflare keeps its own request metadata (URLs, times, firewall events): [to check] |
The comments a user’s Mushroom has collected are kept on the user’s own computer, not with us; whether to delete them is up to the user.
8. Your rights
Whichever U.S. state you live in, we give you the rights below (the rights that California and other states with privacy laws require, we give to every user alike):
| Right | What it means |
|---|---|
| To know and access | Which personal information we have about you, where it came from, why we have it and who we gave it to; and a copy you can take elsewhere |
| To delete | Deleting the personal information we hold about you (except what the law requires us to keep, such as tax records for a subscription) |
| To correct | Fixing what is wrong |
| To opt out of sale and sharing | We don’t sell or share it, so you don’t need to ask |
| To limit the use of sensitive personal information | We use it (for example, the content of other people’s email forwarded to us) only to provide the features you ask for, never to infer characteristics about you, so there is no separate switch |
| Not to be treated differently for using these rights | You won’t get fewer features or pay more because of it |
| To appeal | If we turn down your request, you can reply to appeal; we will answer within 45 days and explain why. If you are not satisfied, you can contact your state’s attorney general |
- How to ask: in Mushroom, Settings › Account & email lets users change their sharer name, sign devices out, revoke links and delete their account; a project’s “Mail” lets them turn off or replace its forwarding address and remove registered sender addresses; Settings › General › Usage data lets them turn usage data off and delete reports they sent, and Settings › Advanced › Stats on this computer lets them clear it. For anything else, write to privacy@pickmushroom.com.
- How soon we answer: we confirm receipt within 10 business days and answer within 45 days; if we need longer, we tell you why within those 45 days and take at most 45 days more. We do this whichever state you live in.
- How we verify it’s you: reply from the email address you sign in with, or confirm after signing in to Mushroom; for usage data and reports, include the random ID or report code shown in Settings. If we can’t verify you, we can only answer the parts that are not about you personally.
- Asking through someone else: you can; the person acting for you needs your signed written permission, and we may also confirm with you directly.
- Workspace AI: in Settings › AI & models you can turn off background organizing, or stop using the models we provide altogether; usage records are deleted with your account; to delete a device identifier and its usage records, write to privacy@pickmushroom.com with the device number shown in Settings [to be decided].
- Clients and other people in files Workspace AI worked on, or whose email was forwarded in: please ask the user of that Mushroom, who can delete it there. For the few days an uncollected email is with us, you can also write to privacy@pickmushroom.com and say which email.
- Clients: on the same device, you can delete your own comments and follow-ups directly and withdraw an approval. For anything else (for example, deleting every comment you left on a link), write to privacy@pickmushroom.com and say which link. As we don’t know who you are, we may ask you for the words of a comment and roughly when you left it, to confirm it’s yours. We will act within 45 days, and may ask the user who shared the link to act with us, as for this content the user is the one who decides how it is used.
9. Security
Link addresses are 128-bit random and can’t be guessed; passwords are stored only as hashes; shared web pages run on a separate domain in a sandbox and can’t read anything on the share page; every connection uses HTTPS; session tokens and mailbox authorizations are kept in the keychain of the user’s computer; reports you choose to send are encrypted with a public key, and the server holds only the encrypted copy. No method is perfectly secure. If there is a data breach, we will notify the people affected promptly as the applicable state laws require, and the state attorney general or other authorities where required.
10. Children
The service is meant for working adults and is not directed to children under 13, and we do not knowingly collect their personal information (the U.S. Children’s Online Privacy Protection Act, COPPA). If you believe we have collected information from a child under 13, write to privacy@pickmushroom.com and we will delete it. The terms of service require users to be at least 18 (terms of service, section 1).
11. Changes
If this policy changes in a way that matters, we will tell you in Mushroom and here at least [30] days in advance, and change the “Last updated” date above. If we want to use data we already have for a new purpose (for example, if we once said “not used for training” and later want to train on it), the change only applies to data collected after it, unless you first give us your express consent. We will never quietly change the terms to reuse old data.
12. Usage data from Mushroom (no content)
By default, Mushroom sends us usage data, so we know which features are used, what goes wrong, at which step Workspace AI tends to fail, and whether it got fixed. It contains no content, and you can turn it off at any time.
| What is sent | What is not |
|---|---|
| Event names (such as “new arrival”, “handed to agent · feedback file written”, “sent · shared”, “saved”) and counts, totaled by day | File contents, file names, paths, titles, project names, comment text, prompts, the model’s answers |
| One summary line for each Workspace AI task, in fixed words and banded numbers only: where it started, which way it went (ours, an agent borrowed on your computer, your own key), which kinds of files, how many steps, which tools were used and whether they worked, how it ended, the category of any failure, at which step and tool it failed, how many times it asked you, banded time and token counts, whether you kept the result or discarded it, the reason you clicked when you discarded it, and how many changes you undid after keeping it; also a random 6-character code, shown on that line when a task fails, so if you tell us the code we can find the line | What you asked for, what the AI said, the tools’ arguments, what was read or changed, model names, error text |
| Error signatures: the area where an error happened, its type, and the place in our own code, sent at most once a day with a count | Error messages (which often contain paths and file names) |
| Mushroom’s version, the macOS major version, the chip, the display language | Computer name, user name |
| A random ID (created the first time Mushroom opens, and replaced when you clear the data), to keep one computer’s data together | Account, email address; this ID is not linked to your account or email address, nor to Workspace AI’s device identifier; the IDs of cards, projects and share links |
| The date (which day; no hours or minutes) | The exact time |
- Where it goes: to our own sharing service (hosted on Cloudflare), never through any third-party analytics. Only the developer can look at it, on an admin page that admits only the developer through Cloudflare Access.
- IP address: as with every other request to the sharing service, only used while the request passes, to limit rates; never written to the database.
- How long: deleted after 180 days.
- How to turn it off: “Turn off” on the line at the top the first time Mushroom opens, or the switch “Send usage data (no content)” under “Usage data” in Settings › General. Once off, nothing more is recorded or sent, and anything not yet sent is cleared at once. Its “Details” show, exactly as sent, what was sent last and the latest task summaries and error signatures; you can clear it all in Settings › Advanced › Stats on this computer, which gives you a new random ID.
- Your rights: this ID is not linked to your account or email address, and we don’t use it to find out who you are. To see or delete what we have received, write to privacy@pickmushroom.com with the
trialIdshown under “What’s in the exported file” in Settings › Advanced › Stats on this computer.
13. What Mushroom reads on your computer (not uploaded)
The first time it opens, Mushroom starts looking on your computer for files made by AI, without first asking you to choose where or to agree; when it’s done, it says at the top how many it found, what it read and where to turn it off, and you can undo what it found in one click. All of this is read on your computer and is not sent to us. Once files are in Mushroom, background organizing sends their titles and first paragraphs to Workspace AI to file them into projects and summarize them (section 14; on by default everywhere, and you can turn it off); content leaves your computer otherwise only when you share it or ask an agent to change it (section 3, and the explanation in Settings › AI & models).
| What it reads | Why | How much | How to turn it off |
|---|---|---|---|
Agents’ local records: Claude Code (~/.claude/projects), Codex (~/.codex), WorkBuddy (~/.workbuddy-ai) | To recognize which files they wrote, and from which of your requests; to see what they are doing right now | Which file was written, when, and from which request; for their status, only fields such as tool names and times. The request you made is kept in your local library and shown on the card | Settings › Collect & organize, “Read Claude Code, Codex, and WorkBuddy session history” |
| The “Where from” of files in Downloads (the download address macOS records) | To recognize which AI website a file was downloaded from | Only the address, to tell which service it was; files downloaded from anywhere else are not taken in | Remove “Downloads” in Settings › Collect & organize |
Agents’ own folders (~/Documents/Codex, ~/Claude, ~/WorkBuddy AI and so on, read only if they exist) | What is in them was made by that agent | The files themselves | Remove them in Settings › Collect & organize |
| Files taken in | To show, compare and keep versions | The card points to the original file; files from Downloads are copied into your library (on your computer) | “Delete” on the card, then “Remove from Intelligent Workspace” |
Mailboxes you connect (in Settings › Account & email › Email: IMAP with an app password; Gmail or Outlook / Microsoft 365 with one-click sign-in, read-only scopes gmail.readonly and Mail.Read; or Apple Mail) | To put clients’ replies into the right project as client feedback, with attachments as new versions | Only the body and attachments of two kinds of mail: mail from clients you have sent to, and replies to mail you sent. In Sent, only mail from the last 30 days with a project file or share link, and only to note the recipients (to recognize clients). Other mail is filtered out on the mail service’s side by sender and conversation (for Apple Mail, inside Mail), and not downloaded. Nothing is marked read, moved, deleted or sent | “Disconnect” in Settings › Account & email › Email, then delete the app password in your mailbox’s settings (for one-click sign-in: disconnecting Gmail also tells Google to revoke access; for Outlook, revoke it under “Apps and services” in your Microsoft account. For Apple Mail, turn it off in System Settings › Privacy & Security › Automation) |
- No whole-disk scanning: only the places above, and the folders and files you open or drag in yourself.
- macOS folder-access prompts: shown by the system, only when Mushroom uses that folder; if you decline, nothing breaks, it just recognizes fewer files.
- Only files with evidence of where they came from: files without evidence (your own photos, online banking pages, reference material) are not taken in, and file times and contents are never used to guess.
- Mailboxes are connected only by you: unlike the things above that are read on opening without asking first, a mailbox is read only after you connect it yourself in Settings › Account & email › Email (entering an app password, signing in with Google or Microsoft in your browser, or allowing the system to let Mushroom control Mail). Once connected: the app password and the one-click sign-in credentials (refresh tokens) are kept only in this computer’s keychain, never in the library, in logs, or sent to us; the clients recognized (email addresses and their projects), how far it has read, and which messages came in are kept in this computer’s app data; incoming feedback and attachments are in your local library; so they can be moved to another project, incoming messages are kept as they are on this computer for 30 days, then deleted; the few the home screen asks you to place in a project stay on this computer until you answer. When it can’t read (offline, an expired app password, permission not given by the system), it only says so in Settings, and reminds you once about an expired app password or missing permission. For when points of feedback are sent to a model, see the end of section 5: on by default everywhere, and you can turn it off in Settings › Account & email › Email.
14. Workspace AI (the models we provide)
Automatic organizing, the AI bar and the agent in Mushroom use the models we provide by default (called “Workspace AI” in the interface). You can also borrow an agent you are signed in to on your computer (Claude Code, Codex), or add your own API key, which is then used first.
| Case | What is sent | Default | What it says beside the result or in the explanation | How to turn it off |
|---|---|---|---|---|
| You use Workspace AI yourself (“Ask an agent”, Workspace AI tasks, handing a task to Mushroom…) | The passage or files you chose and what you asked for; the files, comments and client feedback in this project the agent reads step by step | Sent when you click | “Workspace AI · not kept, not used for training” | Turn off “Use Workspace AI” in Settings › AI & models; excluded projects and locations are never sent |
| Background organizing (filing into projects, summaries, search re-ranking, judging whether a file is a deliverable) | A file’s title and first paragraph | On (everywhere): explained the first time Mushroom opens (on the home page’s “Found N files made by AI” card, or on the first page when nothing was found) | “Not used for training; the model’s maker may keep it a while against abuse (usually up to 30 days)”, with the details in this policy | “Use Workspace AI for organizing in the background too” in Settings › AI & models; exclude projects and locations |
| Splitting a client’s email (end of section 5) | The points this computer’s rules can’t split, and the file’s outline | On (everywhere) | A line of explanation in Settings › Account & email › Email | Turn it off in Settings › Account & email › Email; the whole email then goes on the whole file |
| Borrowing an agent on your computer | As when you use it yourself | Borrowed when you use it yourself; borrowing it for background organizing is off by default, explained once when you turn it on | “Your Claude Code · model name”, with “Data is handled under your settings with Anthropic” beside it (OpenAI for Codex). We don’t say “not used for training” for it: it is your own account, under your settings there | Settings › AI & models |
| Your own API key | As when you use it yourself | Used first once added | “Your key · model name”, under that provider’s API terms | Delete the key |
- Passed through only, never kept: content goes through our relay service (hosted on Cloudflare) to the model provider, only in memory; the relay writes no logs and records no content, only usage (section 3).
- Where “not kept” and “not used for training” are said: the ways you use it yourself and background organizing are all handled now by models Cloudflare runs itself, which keep nothing after processing and do not train on it, so we say “not kept, not used for training” for all of them. Which provider handles which is in section 5. Everything we say must be something we can keep to; if we change it, the change only applies to data from then on (section 11).
- Signing in is needed for the hosted agent; automatic organizing and the AI bar work without signing in, with free credits per device (section 3, “Device identifier”); automatic organizing and splitting client email use no credits, and are capped by how many files and emails a day.
- The same everywhere: one way of working in every region, with one exception: Workspace AI is not offered in mainland China in the first version, where only this computer’s rules, an agent borrowed on your computer or your own API key are used (judged by the country our service sees).
- Marked as AI: results that Workspace AI wrote, rewrote or summarized say “Workspace AI” beside them.
- Version history: who changed each version, and with which model, is kept in the library on your computer and not sent to us.
15. Google user data
- What is read: once you authorize it with your Google account (scope
gmail.readonly, read-only), Mushroom reads on your computer: mail from clients you have sent to and replies to mail you sent (body and attachments), and the recipients of mail in Sent from the last 30 days with a project file or share link. Other mail is filtered out on Gmail’s side by sender and conversation, and not downloaded. - How it is used: only to put clients’ replies into the right project in Mushroom as client feedback and new versions, a feature you can see. It is not used for advertising, not sold, not given to anyone, and not used to train general-purpose AI models.
- Where it is kept: the authorization token is in your computer’s keychain; what is read becomes feedback and versions in the library on your computer; our servers hold no Gmail data. When points of feedback are sent to a model to be split, only those points and the file’s outline are sent, passed through our service and not kept (end of section 5).
- Who gets it: no one (when splitting, it goes to the model provider for processing, which may not train on it). Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- How to revoke: “Disconnect” in Settings › Account & email › Email removes the authorization from your computer and also tells Google to revoke it; you can also revoke it at any time under “Third-party apps & services” in your Google Account.
- Gmail connected with an app password (IMAP) is likewise read only on your computer and used as above.
16. Reports you choose to send us
- Where they are sent from: after a Workspace AI task fails or you click “Discard”, “Tell the developer” on that line; and “Report a problem…” in the Help menu and ⌘K. When a task fails, Workspace AI drafts a note about what went wrong on your computer, shown as a card under that line; it opens only when you click “Look”, and you decide whether to send it after reading and editing it (the draft is written by the same model the task used, uses no credits and, with your own API key, isn’t counted in your usage, happens at most once per task, and is not itself sent to us).
- You tick what goes in: “How this task went (no content)” and “What you asked for and what the AI said last” are ticked by default; each step’s tool calls, changes, screenshots, logs (the last 500 lines, with your user name replaced by
~), your email address, and the memory record left by a crash are not. Before sending, you see the full text exactly as it will be sent, and can remove any part; email addresses, phone numbers and long strings of digits are masked by default until you click to reveal them. Please don’t include your clients’ names or contact details. - Who can read them: only the developer (an individual in Shenzhen, China). A report is encrypted on your computer with the developer’s public key before it is sent, and the server holds only the encrypted copy; the developer decrypts it in their own browser by choosing the private key file on their own computer, and the private key is never uploaded. Every time a report’s encrypted copy is fetched, a line is recorded (who, which report, when). Reports are not given to model providers, not used for training, and not used to adjust credits.
- How long: deleted after 90 days. Under Settings › General › Usage data › Sent you can follow each one (received, read, fixed) and delete it at any time; once deleted, it is gone from the server at once.
- Optional automatic syncing during the trial: people who signed the trial consent form can turn on “Trial: send my AI request log to the developer automatically” (off by default). Once on, roughly every hour the log of what was sent to models from then on (each request’s content and answer, including one line for each Workspace AI task and one for each follow-up on its result) is sent automatically, encrypted the same way, and kept 30 days; you can turn it off at any time, and it turns off by itself when the trial ends. Nothing from before you turned it on is sent.
17. Residents of other states
The privacy laws of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Iowa, Delaware, Nebraska, New Hampshire, New Jersey, Tennessee, Minnesota, Maryland, Indiana, Kentucky, Rhode Island and other states give residents the right to access, delete, correct and take a copy of their personal information, to opt out of targeted advertising and sale, and to appeal. Whether or not these laws apply to us, we give users in every state the rights in section 8, including the right to appeal. We do not sell any personal information and do not do targeted advertising.
Nevada residents can ask us not to sell their personal information by writing to privacy@pickmushroom.com; we don’t sell it anyway.