Trust Center.
Cleyo reads your mailbox and calendar and sends messages in your name, so this page sets out what we hold, where, and who else is involved. Anything your security team needs that is not here, email support@cleyo.io.
Last updated: July 22, 2026
Hosted in the EU
The application, the database and every mailbox, calendar and LinkedIn connection are processed inside the European Union.
Encrypted
AES-256 at rest, TLS in transit. Access credentials are separately encrypted with AES-256-GCM.
Yours to take or delete
Export everything or erase your account from inside the product, without contacting us.
Never sold, never used for training
We do not sell personal data, and our AI providers are contractually barred from training on it.
No silent recording
The meeting notetaker joins as a visible participant named “Cleyo Notetaker” and appears in the attendee list.
Where your data lives
HetznerISO 27001
Application and background workers · Helsinki
SupabaseSOC 2 Type II
Database, authentication, file storage · on AWS
UnipileSOC 2 Type II, Google CASA Tier 2
Mailbox, calendar and LinkedIn connectivity · on Scaleway
StripePCI Level 1, SOC 2 Type II
Payments
RecallSOC 2, ISO 27001
Meeting recording and transcription · on AWS
Where the company data comes from
Hiring signals and job-posting data are licensed from a third-party provider. That is a one-way street: we send it a description of the companies you are looking for, which is firmographics only, such as an industry, a country, a headcount range or a job title. No contact from your workspace, and no personal data of any kind, is sent to it, which is why it is not in the sub-processor list below.
Most of it never leaves the EU
A company is looked up in the enrichment index once, the first time somebody opens it, and the record is then written into your workspace in Ireland. Every read after that is served from the EU. Opening the same company a second time, next week or next year, sends nothing to the United States.
The same holds for the rest of your workspace. Your contacts, campaigns, messages, meeting transcripts and notes are stored and served from Ireland, and the US services we use are called only at the moment they are needed: the index when a company is first researched, the hiring-signal provider when a search runs, the model provider when something is drafted or summarised, the recorder when you ask it to join a meeting.
International transfers
Where a provider processes data outside the EEA, the transfer is covered by the EU Standard Contractual Clauses in our agreement with that provider. Our Data Processing Agreement passes the same commitments through to you.
What Cleyo can access, and what it can do
Every integration is connected by you and can be disconnected by you at any time. This is the complete list.
Email, Gmail and Microsoft 365
How it connects. Through Unipile's hosted authentication. You sign in on your provider's own page. Cleyo never sees your password and never holds your mailbox credentials.
Permissions granted. Here is the consent screen in full. A Google connection requests gmail.send, gmail.readonly, gmail.modify and gmail.labels for the mailbox, and calendar and calendar.events alongside them. A Microsoft 365 connection requests the equivalent mail permissions plus Calendars.ReadWrite.
Several of those are wider than what Cleyo does with them, and the calendar pair is the clearest case: both grants allow writing, and Cleyo never creates, moves or deletes an event. The section below sets out what is actually done with each.
What Cleyo actually does with that access:
- sends the messages you have written and scheduled
- retrieves a single message by its identifier, so a reply lands in the right thread
- receives a notification when mail arrives, to detect replies to your campaigns
What Cleyo does not do
- It does not browse or search your mailbox.
- It does not open or store attachments.
- It does not keep a copy of your mailbox.
Incoming mail that does not match one of your campaigns is discarded and never stored. Where a reply is matched, we store the reply text, the sender address and the subject, so it can appear in your Cleyo inbox.
Note. The permission Google grants is broader than what Cleyo uses. That is a property of Google's scope model, because there is no narrower scope that still allows threading a reply. The list above is what the software actually does, and we will walk a security team through the code paths on request.
Calendar
There are two ways a calendar reaches Cleyo, and they are not granted alike. Both are set out below.
Through Cleyo's own Microsoft application, for the notetaker, the grant is offline_access openid email https://graph.microsoft.com/Calendars.Read. Read-only, and over your own calendars: it does not include Calendars.Read.Shared, so calendars other people have shared with you are not visible to Cleyo at all.
Through a connected mailbox, the calendar comes with the mailbox. A Microsoft 365 connection carries Calendars.ReadWrite and a Google connection carries calendar and calendar.events, and both of those allow writing. That is what the provider offers for a mailbox connection; there is no narrower pair that still returns the events.
Cleyo never writes to a calendar. It does not create, move or delete events, on either grant. What it does is read events in a window from yesterday to thirty days ahead, so the product can show your schedule and know which meetings carry a video link. Calendars you can only read, such as public holiday subscriptions or a colleague's calendar shared read-only, are skipped.
Meeting notetaker
The notetaker joins a meeting as a visible participant named “Cleyo Notetaker”, records it, and produces a transcript and structured notes.
- Which meetings. Auto-join is a single setting in your workspace. When it is on, the notetaker is scheduled for calendar events that carry a Zoom, Google Meet or Microsoft Teams link. Every individual meeting also has its own toggle, so you can keep auto-join on and switch off any single call.
- Recordings. Video is deleted automatically thirty days after the meeting.
- Transcripts and notes stay in your workspace until you delete them or close your account.
- In-person recordings you start yourself are transcribed and then the audio file is removed.
LinkedIn does not offer a partner API for outreach, so Cleyo connects using your LinkedIn session, captured by the Cleyo browser extension and kept in sync so the connection does not drop.
How that credential is protected:
- encrypted at rest with AES-256-GCM
- readable only by our backend service role, with no user-facing API able to return it
- every write is recorded in the audit log
- deleted the moment you disconnect LinkedIn or close your account
What Cleyo can do on LinkedIn. View a profile, send a connection request, send a message to an existing connection, and send an InMail. It acts only on the people you have added to a campaign, within the daily limits you set.
Replies come back, and only replies. When somebody answers a message Cleyo sent, that answer is matched to the conversation it belongs to and its text is stored, so it can appear in your Cleyo inbox and stop the rest of the sequence. A message in any conversation Cleyo did not start matches nothing and is discarded unread.
What Cleyo does not do
- It does not browse or search your LinkedIn inbox, and it never reads a conversation it did not start.
- It does not post.
- It does not interact with anyone outside your campaigns.
Browser extension
The extension has permission for linkedin.com only. It cannot read any other site. It keeps your LinkedIn connection alive, shows your Cleyo queue while you are on LinkedIn, and lets you add a profile to a campaign. When a profile cannot be matched through our enrichment provider, it reads the public details shown on the page you are viewing: name, headline, company and photo.
Applicant tracking systems
Cleyo syncs with Loxo using an API key you generate in your own Loxo account, stored encrypted. Your contractual relationship for that data is with Loxo directly.
What Cleyo does automatically on your behalf
A single consolidated list, so there is no doubt:
- send email
- send a LinkedIn message
- send a LinkedIn connection request
- send an InMail
- join, record and transcribe a meeting
- read calendar events
- retrieve a single email to thread a reply
- look up contact details through our enrichment provider
- write activity back to a connected ATS
Everything is scheduled by you, inside limits you set. Cleyo has no autonomous mode: nothing is sent that you did not create or approve, and the reply assistant drafts replies but never sends them.
Sub-processors
These are the third parties that may process personal data on our behalf. We will give at least thirty days' notice before adding a new one, and you may object by writing to support@cleyo.io.
HetznerISO 27001
Application hosting
SupabaseSOC 2 Type II
Database, authentication, file storage
UnipileSOC 2 Type II, Google CASA Tier 2
Mailbox, calendar and LinkedIn connectivity
StripePCI Level 1, SOC 2 Type II
Payments and billing
RecallSOC 2, ISO 27001
Meeting recording and transcription
ApolloISO 27001, SOC 2 Type II
Contact search and enrichment
OpenRouter
AI model routing
GroqSOC 2 Type II
AI inference and speech-to-text
On the public website only
These run on cleyo.io and never inside the signed-in application. They see visitors to our marketing pages, not the contents of anybody's workspace.
DataFast
Website traffic analytics · cookieless, stores nothing on your device
Microsoft Clarity
Heatmaps and session replay · loads only once you accept cookies
Crisp
Support chat · loads only once you accept cookies
AI processing
What is processed. Cleyo uses language models to draft campaign messages, summarise and classify replies, produce meeting notes from transcripts, and research companies. Depending on the feature, that means prospect names, job titles and companies, the text of replies you receive, and meeting transcripts.
Who processes it. OpenRouter and Groq.
Retention and training. Both are configured for zero data retention: your prompts and the model's output are not stored, and neither provider may train on them. Groq is contractually barred from training on customer inputs or outputs.
One exception
Company research uses a web search tool. Zero-data-retention routing does not extend to search tools, so a research query leaves that boundary. Those queries contain company names and research questions, not the personal data of your contacts.
Data retention
| Data | Retained |
|---|---|
| Account, campaigns, contacts, messages | While your account is active |
| Meeting video | 30 days, then deleted automatically |
| Meeting transcripts and notes | While your account is active, or until you delete them |
| In-person recording audio | Deleted once transcribed |
| Mailbox and LinkedIn credentials | Deleted when you disconnect the integration |
| Replies that do not match a campaign | Never stored |
| Audit logs | While your account is active, deleted with your account |
When you delete your account we erase your data, cancel any scheduled notetaker, and delete the connected accounts held on your behalf at our providers. Backups roll off within thirty days.
Your controls
- Export everything. Settings, then Privacy & Data, then Download my data. A complete JSON export, immediately, without contacting us.
- Delete everything. Settings, then Privacy & Data. Immediate and irreversible.
- Turn off the notetaker globally or for any individual meeting.
- Disconnect any integration at any time, which deletes the stored credential and pauses anything depending on it.
- Do-not-contact list. Block a person or an entire domain across your whole workspace.
How we protect your data
- Encryption. AES-256 at rest and TLS in transit. Mailbox and LinkedIn credentials are encrypted separately with AES-256-GCM, with authenticated encryption and a per-record initialisation vector.
- Isolation. Every workspace is separated at the database level by row-level security, so one customer's query cannot reach another's data.
- Least privilege. Credential fields are readable only by backend service roles and are never exposed through any user-facing interface.
- Audit logging. Sends, connections, disconnections, exports and deletions are recorded.
- Rate limiting on authenticated endpoints, and verification of every inbound webhook.
- Hardened delivery. Strict transport security, clickjacking and MIME-sniffing protections, and sanitisation of all user-supplied HTML.
- Secrets are held in environment configuration on EU infrastructure, never in source control.
Independent assurance
Cleyo runs on independently audited infrastructure, and the commitments we make about your data are contractual.
- Our core infrastructure providers are independently audited, and what each one holds is on its row in the two lists above. Each publishes its own trust documentation, which we can point you to. Reports we hold under confidentiality cannot be redistributed.
- We sign a Data Processing Agreement including the EU Standard Contractual Clauses.
Available on request
Email support@cleyo.io:
- Data Processing Agreement, with technical and organisational measures and SCCs
- Completed security questionnaires
- Detailed data-flow documentation
- Microsoft 365 permission detail
- Answers to anything specific to your deployment
Reporting a security issue
If you believe you have found a vulnerability, email support@cleyo.io. We will acknowledge within one business day. Please do not disclose publicly until we have had a chance to fix it.
Changes to this page
We keep this page current and date every change. Material changes to our sub-processor list are announced at least thirty days in advance.
Cleyo
support@cleyo.io