Privacy Policy — Unlockers.ai

Last updated: October 13, 2026

1. Who we are

Unlockers is a brand operated by U & B Consulting Services (Unlock & Boost), a French SAS registered under SIREN 988 696 860, with its registered office at 7 B rue de Paris, 38600 Fontaine, France. It is the data controller for the processing described here.

For any question or request: contact [at] unlockers.ai .

2. What this policy covers

This policy applies to the two Unlockers applications that access a Google account with its owner's permission:

Unlockers CRM (crm.unlockers.ai): the Unlockers team's internal sales tool. Each team member can connect their own Google account to see, from a contact's record, their Gmail conversations and meetings with that contact, prepare drafts, send e-mails and book time in their calendar.
Unlockers MCP Access: a connector that lets the user's AI assistants (for example Claude Code or Claude Cowork) access one or more of their Gmail or Google Workspace accounts.

The rest of the unlockers.ai website is not covered by this document.

3. Google data we access

We only request access to the data needed for the features you use, and only after you explicitly agree on Google's consent screen.

Unlockers CRM

Gmail (gmail.modify scope): reading the headers and snippets of threads exchanged with a CRM contact (sender, recipients, subject, date, snippet), creating drafts and sending the e-mails you write or approve. The CRM never deletes your e-mails.
Google Calendar (calendar.events scope): reading your events to show the meeting history with a contact and find free slots, creating the events you ask for.
The e-mail address of the connected Google account.

Unlockers MCP Access

The Google services you choose to authorize: Gmail (reading, labels and drafts), Calendar, Tasks, Contacts, Docs, Sheets, Slides, Forms and Drive (read-only), within the permissions Google shows when you connect. This data is read and used only on your own computer, by the AI assistant you use, in response to your requests.

4. How we use this data

Only to provide the application's user-facing features, at the request of the signed-in user: showing a contact's history, writing and sending an e-mail, scheduling a meeting, producing a summary.
Each team member uses their own Google account: the CRM never acts on one person's mailbox with another person's access.
AI summaries (CRM): when you ask for a contact summary or a follow-up draft, the relevant information (the contact's record, subjects and snippets of your exchanges, meeting dates) is sent to Anthropic's Claude API, which returns the text. The resulting summary is saved in the contact's record.

Limited Use. Unlockers CRM's and Unlockers MCP Access'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. In particular:

we do not use this data for advertising, and we do not sell it;
we only transfer it to third parties as necessary to provide or improve user-facing features, for security purposes, or to comply with applicable law;
no one reads your data unless you explicitly agree, for security purposes (such as investigating abuse), to comply with applicable law, or after it has been aggregated and anonymized for internal operations;
we do not use this data, nor allow anyone to use it, to develop, improve or train generalized artificial intelligence or machine learning models.

5. What we keep, and for how long

Unlockers CRM

Google access token (refresh token) and the connected account's address: kept as long as your Google account is connected to the CRM. They are deleted as soon as you click "déconnecter" (disconnect), revoke access from your Google account, or your CRM account is closed.
E-mail and calendar content: read on the fly for display and not stored by the CRM, except for the summaries you request (saved in the contact's record) and the information you enter yourself.
User account (name, e-mail address, role): kept as long as you are a team member.
Technical logs (timestamp, IP address, requests): kept as long as needed for troubleshooting and the security of the service.

Unlockers MCP Access

Access tokens are stored on your computer, and your Google account data travels there directly from Google. Unlockers neither receives nor stores your tokens or the content of your accounts.

6. Where the data is, and who can access it

Hosting: the CRM's servers are rented from Hetzner Online GmbH, in the European Union. Only the service's administrators can access the data there.
Anthropic PBC (United States), provider of the Claude API, receives the excerpts needed for the summaries and drafts requested in the CRM. Under its commercial terms, Anthropic does not use data sent through the API to train its models. This transfer outside the European Union is covered by the European Commission's Standard Contractual Clauses.
With Unlockers MCP Access, your data is processed by the AI assistant you chose, under your own account and its provider's terms.
We do not sell, rent or share your data with anyone else.

7. Security

All traffic uses encrypted connections (HTTPS). The CRM's Google tokens are kept server-side, in a database that is not exposed to the internet, and are never sent to the browser. Access to the CRM is restricted to authenticated team members.

8. Your rights

Under the General Data Protection Regulation (GDPR) and French data protection law, you have the right to access, rectify, erase, restrict, object to the processing of, and port your data. To exercise them, write to contact [at] unlockers.ai . We answer within one month.

You can revoke our applications' access to your Google account at any time from Third-party apps with account access, or, for the CRM, with the "déconnecter" (disconnect) button.

If you believe your rights are not respected, you can lodge a complaint with the French data protection authority, the CNIL.

9. Cookies

The CRM only uses the storage strictly needed for your sign-in (authentication session). No advertising or analytics cookies.

10. Changes

We will update this page if our applications or practices change; the date at the top shows the latest version. Users affected by a significant change will be informed.