Privacy Policy
Clean, operated by Clean AI Labs, Inc. · Last updated October 28, 2026
This policy explains what data Clean collects, why we collect it, how it is stored and shared, and the controls you have. It covers four things:
- The Clean web app at app.tryclean.ai, where your workspace finds, researches, and works prospects.
- The optional Gmail connection, which a workspace member can turn on to see their email history with chosen prospects in Clean and, if they switch it on, to send the email campaigns they launch in Clean from that Gmail account. This is Google user data, and the sections below are written to comply with the Google API Services User Data Policy, including its Limited Use requirements.
- The “Clean for LinkedIn” Chrome extension, an optional connection a member uses for insights on their prospects and for the LinkedIn campaigns they launch. The sections below are written to comply with the Chrome Web Store Limited Use and data disclosure requirements.
- The optional CRM integrations with Attio and HubSpot, which a workspace member can connect so the prospects the workspace keeps in Clean also appear in the CRM its team works in. See CRM integrations.
By using the service, connecting Gmail or a CRM, or installing the extension you agree to this policy.
Who we are
Clean is a product of Clean AI Labs, Inc. Clean is organised into workspaces: a workspace belongs to one company, and its members are the teammates that company has invited. Data a member connects to Clean lives inside that workspace, and leaves it only as this policy describes, for example when the workspace connects its own CRM. You can reach us any time at hello@tryclean.ai.
The Gmail connection: what it is
Connecting Gmail is optional and off until a workspace member turns it on. When they do, that member signs in with their own Google account, reviews Google's consent screen, and then chooses which prospects Clean may read mail for: all prospects in the workspace, or one saved list. Clean syncs the email threads between that Google account and those prospects, and shows them on each prospect's record as a per-prospect inbox, so the workspace can see the conversation history it already has with the people it is working, next to the research Clean has assembled on them. The member can also switch on sending campaigns from that Gmail account, as described in What Clean sends from your Gmail.
What we request from Google
- Gmail read access (the
https://www.googleapis.com/auth/gmail.readonlyscope). Clean uses it for two things only: to search for and read messages to or from the prospects you chose, and to read the email threads of the campaign emails Clean sent for you, so it can tell when a prospect replied, bounced or asked to unsubscribe. Clean never modifies, labels, archives or deletes mail. - Send email on your behalf (the
https://www.googleapis.com/auth/gmail.sendscope). Clean uses it only to send the emails in campaigns launched in Clean, as described below. Clean does not create or send drafts. - Basic profile information from Google sign-in: the email address of the connected account, used to label the connection and to match your own address on each thread.
What we read, and what we do not
Clean reads only mail to or from the prospects your workspace chose, and, if you send campaigns from Gmail, the threads of the campaign emails Clean sent for you (see What Clean sends from your Gmail). For each thread with a chosen prospect we store the message headers (from, to, cc, date, subject), the message text, and Google's thread and message identifiers so the inbox stays in sync and duplicates are not created. We also store the OAuth token Google issues so Clean can keep working without asking you to sign in again.
Nothing else in the mailbox is fetched. Clean does not scan the whole inbox, does not read mail with people you did not choose apart from those campaign threads, and does not keep anything outside them. If you change which prospects you chose, Clean only ever reads threads with the prospects currently chosen.
What Clean sends from your Gmail
Clean sends email from your Gmail account only when all of these are true:
- you switched on Send campaigns from this Gmail in Clean (it is off until you do);
- you created and launched the campaign in Clean. A teammate's campaign never sends from your mailbox;
- the recipient is a prospect someone in your workspace added to that campaign.
Each campaign is a short sequence: a first email and follow-ups a few days apart, sent as replies in the same thread. Clean sends them one at a time, on weekdays, inside the campaign's sending hours in your time zone, and never more than 40 a day from one mailbox. Every email includes a link the recipient can use to unsubscribe. A prospect's sequence stops as soon as they reply, their address bounces, or they unsubscribe, and Clean will not email someone who unsubscribed again.
For each email Clean sends, it stores the subject and text, the recipient, the time it was sent, and Gmail's message and thread identifiers, so the campaign can follow up in the same thread and show its results. For replies to those emails, Clean stores only that a reply, bounce or unsubscribe happened and when. It stores the reply's text only if that prospect is also one you chose for reading mail.
People who receive a Clean campaign email can stop further emails at any time with the unsubscribe link in the email, by replying to ask, or by emailing hello@tryclean.ai.
How Gmail data is stored
- Encrypted. Synced messages and OAuth tokens are encrypted in transit (TLS) and at rest.
- Bounded. Storage is limited to the threads with the chosen prospects and the campaign records described above. Clean does not build a copy of your mailbox.
- Workspace-private. Gmail data is scoped to the workspace that connected it. It is never visible to any other workspace, never published, and never pooled across customers.
Who can see Gmail data
Members of your workspace. The per-prospect inbox is a shared view: teammates in the same workspace can see the synced threads on the prospects they are working, in the same way they can see the prospect's research and notes. If you would rather not share a particular account's mail with your team, do not connect it.
Clean staff do not read your mail. No one at Clean looks at synced message content in the normal course of operating the service. Humans may access it only in the narrow cases Google's Limited Use policy allows: with your explicit permission (for example to debug a support request you raised), where necessary for security purposes such as investigating abuse, to comply with applicable law, or for internal operations where the data has been aggregated and anonymised.
Gmail data is not sold, rented, shared with advertisers or data brokers, or transferred to anyone other than the infrastructure providers that host Clean (cloud hosting and managed database providers acting as our processors under contract), and then only as needed to run the service.
How we use Gmail data
Solely to provide the Gmail features you turned on: showing your workspace its email history with its prospects, sending the email campaigns you launched, and stopping a campaign for a prospect who replied, bounced or unsubscribed. We do not use Gmail data for advertising, for profiling anyone outside your workspace's own prospect list, to determine creditworthiness or for lending purposes, or to develop, improve, or train generalised artificial intelligence or machine learning models.
When Gmail data is deleted
- When you disconnect. Disconnecting Gmail in Clean deletes the token Clean stored, so Clean can no longer use your Gmail, and deletes every synced message and thread for that connection from live systems immediately. Records of campaign emails Clean already sent stay in that campaign's history. To also remove Clean from your Google Account, use your Google Account permissions page.
- When a member leaves. If the member who connected the account leaves or is removed from the workspace, their Gmail connection is closed and its synced mail is deleted the same way.
- When a workspace is deleted. Deleting a workspace deletes every Gmail connection and all synced mail inside it.
- When you revoke from Google. You can also remove Clean's access at any time from your Google Account permissions page. Syncing and sending stop as soon as Google rejects Clean's token. Disconnect Gmail in Clean, or email us, to have the synced mail deleted.
Residual copies in encrypted backups expire on their normal rotation, no later than 30 days after deletion from live systems.
Google Limited Use disclosure
Clean's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
The Chrome extension: what it collects
The extension has a single purpose: to securely connect, and keep connected, the user's own LinkedIn account to their own Clean account, so Clean can work through that account on the prospects the user's workspace is working. Through it Clean reads those prospects' profiles and work history, and the user's connections to them, to add insights to each prospect's record, and sends the LinkedIn connection requests and messages in campaigns the user launches in Clean (see What Clean sends from your LinkedIn). To do that, the extension handles the following data, and nothing else:
- The account you confirm and its sign-in session. The extension identifies the LinkedIn account you are signed into and shows its display name and profile link. Only after you confirm that account does it send that account's sign-in session to Clean. The session is encrypted inside the extension before it leaves your browser, and only Clean's connection service can decrypt it.
- Basic browser details. Your browser type and version, language, and time zone, which the connection uses together with the session you confirmed.
- Connection state. The extension briefly stores the detected account and, after you confirm, the encrypted session until Clean receives it. It is removed once Clean receives it or it expires, and uninstalling the extension removes it.
What the extension does NOT collect
- Browsing history, search queries, typed text, messages, posts, feed content, or profile-page content.
- Your LinkedIn password or two-factor codes. You enter those only on LinkedIn's own sign-in page.
- Payment details, or anything from your browser beyond the sign-in session of the account you confirmed.
- Any data from sites other than linkedin.com and your own Clean dashboard.
What Clean sends from your LinkedIn
Clean sends LinkedIn connection requests and messages from your account only for campaigns you created and launched in Clean, and only to prospects someone in your workspace added to that campaign. Clean does not post, react, accept invitations, or change your profile or settings. Disconnecting LinkedIn in Clean stops all sending from your account.
How we use extension data
The session is used only to read LinkedIn data for your workspace's prospects and to send the campaigns you launch, at your direction. It is never used to post, react, accept invitations, or change your profile or settings. We do not use any of this data for advertising, for profiling anyone outside your workspace's own prospect list, or for any purpose unrelated to the extension's single purpose.
CRM integrations: Attio and HubSpot
A workspace can connect an Attio workspace, a HubSpot account, or both, so the prospects it keeps in Clean also appear in the CRM its team works in. Connecting is optional and off until a workspace member clicks Connect in Clean and approves access on the CRM's own consent screen. From then on, Clean sends data to that CRM at your workspace's direction, and only to the CRM account your workspace connected. Clean does not send data to a CRM nobody in your workspace connected.
What Clean sends to your CRM
- People: name, email addresses, phone numbers, job title, LinkedIn profile URL and the company they work at, for each prospect your workspace has added to its CRM in Clean.
- Companies: name, website domain and LinkedIn page URL.
- Lists: each list your workspace keeps in Clean, with its members as list entries.
- Custom columns: each column your workspace adds in Clean becomes a field on people in the CRM, with each person's value.
- A Clean record ID on each person and company (the
clean_entity_idfield), so Clean can find the records it wrote and update them instead of creating duplicates.
Clean sends this when your workspace first connects (a copy of what it already keeps in Clean), whenever someone in the workspace adds, edits or lists a prospect, and in a check about every 30 minutes. Clean never deletes people, companies or lists in your CRM. Synced Gmail messages, LinkedIn sign-in sessions and other extension data are never sent to a CRM.
What Clean reads from your CRM
The sync runs both ways, so Clean also reads people from the CRM your workspace connected. It does this for two reasons: to recognise people who are already in your CRM, so Clean updates them instead of creating duplicates, and to bring edits your team makes in the CRM back into Clean.
- Who is already in your CRM. Clean keeps a private index of the people in the connected CRM: name, email address, phone number, job title, LinkedIn profile URL, who or what created the record, and the CRM's own timestamps for it. For HubSpot it also keeps the contact's company, its lifecycle stage and status fields, and the record owner. The index is used to match records, to show counts on your connection page, and to let research skip people you already have. It never appears in your prospect list.
- People you ask about in chat. A member of your workspace can ask Clean's chat about people in that index, for example who at a company is already in your CRM; viewers cannot. People who exist only in your CRM stay out of your prospect list until a member asks chat to add them. Chat then shows a card listing exactly who it would add, and Clean adds them, linked to their CRM records, only when the member who asked confirms. Nothing is sent to those people.
- Edits to people Clean synced. When someone changes the name, email, job title, phone or LinkedIn URL of a person Clean synced, Clean copies that change onto the prospect in Clean, the way a teammate's edit would land, and records which fields changed (never the values) in its audit log. Where Clean has no value for one of those fields, it fills it from the CRM.
Clean checks the CRM for changes about every five minutes. Clean does not read deals, notes, tasks, emails, meetings or custom objects. A workspace member can turn off “Bring edits into Clean” on the connection, and Clean then stops reading that CRM; it keeps sending to it. Data read from your CRM stays inside your workspace, like the rest of its Clean data. It is never shown to or used for any other workspace.
Once data is in your CRM, the CRM provider holds it under your own agreement with them. Attio and HubSpot are services you choose and connect; they are not processors Clean uses to run its own service.
When you disconnect a CRM
- Sending and reading stop. Clean asks the CRM to revoke its access and destroys its stored access token.
- The index is deleted. Clean deletes its index of the people in your CRM as part of the disconnect.
- Your CRM keeps what it has. Everything Clean already wrote stays in your CRM, where you can edit or delete it. Clean does not delete it.
- Clean keeps the links. Clean keeps the CRM record IDs of the prospects it synced, so reconnecting the same CRM updates those records instead of duplicating them. Edits already brought into Clean stay on the prospect in Clean. Deleting the workspace deletes the links, and you can email us to have them deleted sooner.
If you remove the Clean app from inside Attio or HubSpot instead, Clean loses access straight away and the sync stops. Disconnect in Clean as well, or email us, to have the index deleted.
How we share data
We do not sell or rent your data, and we do not transfer it to third parties except as needed to run the service or as you direct. Data flows to your own Clean workspace; to the infrastructure providers that host it (e.g. cloud hosting and managed database providers) acting as our processors under contract; and, when your workspace connects Attio or HubSpot, to that CRM account, as described in CRM integrations. Gmail data and LinkedIn sign-in sessions are never sent to a CRM. We may also disclose data where required by law, or to protect the security of the service and its users. We do not use or transfer your data to determine creditworthiness or for lending purposes. This use complies with the Google API Services User Data Policy and the Chrome Web Store Limited Use requirements.
Storage, security, and retention
Synced Gmail data, OAuth tokens, CRM access tokens, and LinkedIn sign-in sessions are encrypted at rest and transmitted only over HTTPS. What the extension keeps in the browser stays in its own storage on your device. We keep data only for as long as the connection that produced it is active, and delete it on disconnect as described above (for Gmail, records of campaign emails already sent stay in that campaign's history; for a CRM, Clean keeps only the record links described in that section). You can also request deletion at any time by emailing us.
Your controls
- Disconnect Gmail from your Clean workspace settings to stop Clean using your Gmail and delete all synced mail.
- Switch off Send campaigns from this Gmail (Settings > Integrations > Gmail) to stop all sending from your mailbox at once.
- Pause or delete a campaign in Sequences.
- Remove Clean's access directly from your Google Account permissions page.
- Change which prospects Gmail reads mail for (all prospects or one saved list) at any time; Clean only reads threads with the prospects currently chosen.
- Disconnect a LinkedIn account from your Clean dashboard to stop Clean using it, including campaign sending, and delete its stored session.
- Uninstall the extension to stop all local collection immediately.
- Disconnect Attio or HubSpot from Settings > Integrations in Clean to stop the sync, revoke Clean's access and delete Clean's index of the people in that CRM.
- Turn off “Bring edits into Clean” on a CRM connection to stop Clean reading that CRM while it keeps sending to it.
- Email hello@tryclean.ai to request export or deletion of your data.
Children
Clean is a business tool and is not directed to children under 16. We do not knowingly collect data from children.
Changes to this policy
We may update this policy as the product evolves. Material changes will be reflected here with a new “Last updated” date, and where appropriate in the app, the extension, or by email to workspace administrators.
Contact
Questions about this policy or your data? Email hello@tryclean.ai. You can also visit our support page.