This policy explains what we collect, why we collect it, and the choices you have. It covers celentra.io and the Celentra outreach platform. Where you use Celentra through an employer's workspace, that organisation is the controller of the prospect and campaign data it uploads, and we process it on their behalf.
01Overview
Celentra is an outbound sales platform. We handle two broad categories of data: information about our own customers and website visitors, and information our customers load into their workspace about the people they want to reach.
For the first category we act as the controller and decide how the data is used. For the second we act as a processor and only act on our customer's documented instructions, under the terms of our data processing agreement.
02Information we collect
Information you give us
- Account details such as your name, work email, job title, and workspace name.
- Billing details including company address and tax identifiers. Card numbers are handled by our payment processor and never reach our servers.
- Content you create in the product: sequences, message templates, notes, and campaign settings.
- Anything you send us through support requests, demo forms, or community channels.
- Support chat messages and attachments. When you contact us from the signed-in product, we also send your account name, email address, user identifier, workspace identifier and name, and product environment to our support system so we can identify your request.
Information we collect automatically
- Product usage events such as pages viewed, features used, and campaigns launched.
- Device and connection data including browser type, operating system, approximate location derived from IP address, and timestamps.
- Deliverability telemetry available for each connected provider, such as send volume, bounce and complaint rates, and reputation signals. Gmail sending-only connections do not import incoming mail or mailbox-based bounce reports.
Information from third parties
- Contact and company enrichment data from licensed data providers and public sources.
- Profile and integration data from services you authorise, such as Google Workspace, Microsoft 365, LinkedIn, and your CRM, limited by each integration's permissions. Current Gmail connections use basic identity and sending permissions only.
- Referral and attribution data from advertising and analytics partners.
03Google account, Gmail, and Workspace data
This section applies to personal Gmail accounts and Google Workspace accounts connected to Celentra, as well as basic Google account information used for sign-in. Connecting a mailbox is a separate authorization from signing in. Celentra uses Google OAuth, and the Google consent screen identifies the permissions requested before you approve access. The limits in this section govern Google user data even where another section describes broader uses of other personal data.
Current Gmail connections are sending-only. Celentra requests gmail.send and basic OpenID identity scopes; it does not request Gmail read or modify permissions. Gmail Inbox synchronization, incoming reply detection, mailbox actions, and warm-up are disabled, including for accounts with an older broad grant. Previously synchronized Gmail mailbox data remains stored under the retention and deletion rules below and is not a live view of Gmail. Existing Google grants must be revoked and reconnected to replace older permissions with the reduced grant.
Data we access
- Basic Google account and OpenID data, including your email address, display name, profile image, and stable account identifier, to identify the mailbox you selected and show it in your workspace.
- Outgoing message recipients, subject, body, reply references, and attachments that you provide or approve in Celentra, plus message and thread identifiers returned by Gmail when a message is sent.
- Gmail sending access only when you or an authorized workspace workflow requests sending. Celentra does not retrieve new incoming Gmail messages, labels, bodies, or attachments, or change Gmail read, archive, star, trash, or snooze state in sending-only mode.
- Where a workspace separately enables Google Calendar features, the event details needed to create, update, or cancel a Celentra booking, such as the title, time, attendees, description, and location.
How we use Google user data
- Authenticate and identify the connected Google account and mailbox.
- Send messages and attachments that you or your authorized workspace workflows approve, including scheduled messages and replies using previously stored conversation context.
- Record outgoing sending results and provide Celentra's open/click tracking and unsubscribe features. These features do not require reading the Gmail mailbox. Incoming replies and bounces must be reviewed in Gmail; reply-dependent Gmail campaigns are blocked while sending-only mode is active.
- When Inbox AI is enabled for your workspace, previously stored conversation text may be processed to classify replies, identify out-of-office messages, summarize conversations, and generate reply drafts for review. Sending-only Gmail access does not import new incoming conversations for these features. Celentra sends the relevant stored conversation text to its AI processing service to produce those outputs; this is processing for your workspace's features, not model training.
Celentra's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google Workspace APIs are not used to develop, improve, or train generalized or non-personalized AI and/or machine learning models. We do not sell Google user data, use it for advertising or retargeting, share it with data brokers or information resellers, use it to determine creditworthiness or for lending, or build data products for unrelated purposes. We use it only to provide or improve the user-facing Celentra features you request. The general marketing and benchmarking purposes elsewhere in this policy do not authorize those uses of Google user data.
Where we store Google user data
Celentra stores account identifiers, outgoing message content, sending results, and feature outputs in its application database. Previously synchronized Gmail content and mailbox metadata remain stored until removed through the retention and deletion process; changing permissions does not erase these copies. Attachments uploaded or previously copied into Celentra are stored in private object storage. OAuth access and refresh tokens are kept in server-side secret storage through WorkOS Vault; application records refer to those secrets, and tokens are not exposed to the browser. Cloudflare provides Celentra's hosting, background processing, object storage, and AI Gateway infrastructure. Data is protected by encryption in transit and at rest, workspace isolation, role-based permissions, and least-privilege access.
Who receives Google user data and why
- Authorized members of your Celentra workspace can see outgoing messages, previously synchronized mailbox content, and feature outputs according to their workspace permissions. Connecting Gmail in sending-only mode does not import incoming mailbox content into the workspace.
- Google processes the authorized Gmail API requests used to send email. When you send an email, its recipients receive the message content and any attachments you include.
- Our hosting, database, storage, and credential providers process the data needed to operate Celentra. Cloudflare processes application traffic and stored attachments; WorkOS Vault stores OAuth credentials. These service providers process Google user data on Celentra's behalf for the purposes described here.
- For enabled Inbox AI features, previously stored conversation text is processed through Cloudflare AI Gateway by the configured AI model provider, currently OpenAI, to return classifications, summaries, and drafts. Google user data is not used to develop, improve, or train non-personalized AI or machine learning models.
We do not transfer or disclose Google user data for purposes other than providing or improving the user-facing features you request, complying with applicable law, or protecting against abuse and security incidents. A business transfer involving Google user data is subject to the Google API Services User Data Policy and its consent requirements. The general list of sub-processors below does not mean every provider receives Gmail content: advertising, enrichment, and billing providers do not receive it merely because you connect a mailbox.
Human access
Celentra personnel do not read Google user data except with your affirmative agreement to view specified data, where necessary for security purposes such as investigating abuse, where required by applicable law, or where the data has been aggregated and anonymized and is used for internal operations as permitted by Google's Limited Use requirements. Internal access is restricted to authorized personnel with a need to perform the relevant task. Your authorized workspace users' access is governed by your workspace permissions.
Retention, disconnection, and deletion
We retain outgoing messages, previously synchronized Gmail content, attachments, mailbox metadata, and derived feature outputs while they are needed for your active workspace's requested features, subject to the retention process below. Disconnecting a mailbox stops future access and initiates removal of its stored OAuth credentials; it does not automatically erase messages already copied into the workspace. Sending-only mode creates no new Gmail push subscriptions or renewals; older watches expire naturally and their notifications are ignored. You can revoke Celentra's authorization in your Google Account's third-party connections settings at any time. Revocation stops authorized Google API access but does not itself delete Celentra's stored copies.
To request deletion of Celentra's stored Google account information, Gmail content, attachments, and derived feature outputs, email privacy@celentra.io and identify the connected mailbox and workspace. We verify your identity and workspace authority before acting, and coordinate with the workspace controller where applicable. Product deletion controls are also available for supported workspace records. Workspace content follows the retention process below: after subscription termination, it is available for export for 30 days and deleted or anonymized within 90 days. Copies retained for legal obligations or in time-limited backups are restricted to those purposes. Deleting Celentra's copies does not delete the originals in Gmail; sending-only mode does not expose Gmail mailbox deletion actions.
04How we use data
- Provide, operate, and maintain the platform and the integrations you connect.
- Authenticate users, enforce workspace permissions, and prevent abuse of the service.
- Pace sending, validate contacts, and surface deliverability risk before it damages your domain.
- Generate campaign analytics, reply scoring, and reporting for your workspace.
- Improve and troubleshoot the product, including aggregated and de-identified benchmarking.
- Send service notices, billing messages, and — where permitted — product and marketing updates you can opt out of at any time.
We do not sell personal data, and we do not use the prospect data in a customer workspace to train models that serve other customers.
05Legal bases for processing
If you are in the European Economic Area, the United Kingdom, or Switzerland, we rely on the following legal bases under the GDPR and equivalent laws.
- Contract: to deliver the service you or your employer signed up for, including billing and support.
- Legitimate interests: to secure the platform, prevent fraud and abuse, improve our products, and carry out business-to-business marketing in a way that is proportionate and expected.
- Consent: for optional cookies, marketing emails where consent is required, and any processing you specifically agree to. You can withdraw consent at any time.
- Legal obligation: to meet tax, accounting, and lawful request requirements.
06Sharing and sub-processors
We share personal data only where it is necessary to run the service, and always under a written contract that restricts what the recipient may do with it.
- Cloud hosting, storage, and content delivery providers.
- Email and messaging infrastructure used to send and receive campaign traffic.
- Analytics, error monitoring, and support tooling.
- Our self-hosted support chat service at support.celentra.io, which processes support messages and technical connection data when the native chat widget loads and when you use it.
- Payment processing and billing providers.
- Data enrichment providers, where you have enabled enrichment.
- Professional advisers, and acquirers or successors in the event of a merger, acquisition, or asset sale.
A current list of sub-processors is available on request, and customers on a signed data processing agreement receive advance notice of material changes so they have the opportunity to object.
We may also disclose data where we are legally required to do so, or where disclosure is necessary to protect the rights, safety, or property of Celentra, our customers, or the public.
07International transfers
Celentra operates globally, so personal data may be transferred to and processed in countries other than the one you live in, including the United States.
Where data leaves the EEA, the UK, or Switzerland, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses together with the UK Addendum, supported by transfer risk assessments and technical measures including encryption in transit and at rest. Enterprise customers can request regional data residency so that campaign data stays in a chosen region.
08Data retention
We keep personal data only for as long as we need it for the purposes described in this policy, or for as long as our customer instructs us to.
- Account and billing records: for the life of the account and then as required by tax and accounting law.
- Workspace content and campaign data: for the term of the subscription. After termination it is available for export for 30 days and then deleted or anonymised within 90 days.
- Product usage logs: typically retained for 13 months in identifiable form.
- Security and audit logs: retained for up to 24 months to support investigations.
- Support conversations and attachments: deleted after 12 months without activity unless a legal hold applies. Encrypted daily backups expire under a 30-day retention policy; deletion is repeated after a recovery before service is reopened.
09How we protect data
We maintain administrative, technical, and physical safeguards designed to protect personal data against unauthorised access, loss, and misuse. These include encryption in transit and at rest, role-based access control, least-privilege internal access, continuous monitoring, and regular third-party testing.
No system is perfectly secure, but if a breach affects your personal data we will notify you and the relevant supervisory authority within the timeframes the law requires. You can read more about our programme on the security page.
10Your rights and choices
Depending on where you live, you may have some or all of the following rights over your personal data.
- Access a copy of the personal data we hold about you.
- Correct data that is inaccurate or incomplete.
- Delete data where we no longer have a lawful reason to keep it.
- Restrict or object to certain processing, including direct marketing and profiling.
- Receive your data in a portable, machine-readable format.
- Withdraw consent at any time, without affecting processing already carried out.
- Lodge a complaint with your local data protection authority.
To exercise any of these rights, contact us using the details below. We will verify your identity before acting and will respond within the period the applicable law requires — usually one month. If your data sits inside a customer's workspace, we will forward your request to that customer and support them in responding.
11Cookies and similar technologies
We use cookies and similar technologies to keep you signed in, remember preferences, measure how the site performs, and understand which campaigns bring people to us.
- Strictly necessary cookies keep sessions secure and cannot be switched off.
- Preference cookies remember settings such as language and billing cycle.
- Analytics cookies help us understand aggregate usage and improve the product.
- Marketing cookies measure the performance of our advertising, where you have consented.
The native support chat widget loads automatically on our public website and on supported signed-in workspace pages. It uses cookies to maintain your conversation and sends technical connection data to our self-hosted support service. The separate contact form uses our email service and Cloudflare Turnstile. You can clear and block cookies in your browser. We do not currently load optional analytics or advertising cookies on this website. If we introduce these cookies, we will provide consent controls before loading them.
12Children's data
Celentra is a business tool and is not directed at anyone under 16. We do not knowingly collect personal data from children. If you believe a child has provided us with personal data, contact us and we will delete it.
13Changes to this policy
We may update this policy as the product and the law evolve. When we make material changes we will update the effective date at the top of this page and, where appropriate, notify you in the product or by email before the change takes effect.
14Contact us
For privacy questions or data requests, contact Celentra at privacy@celentra.io. Include enough information to identify the relevant account or workspace, but do not send passwords or OAuth tokens.
Customers who need a signed data processing agreement, our list of sub-processors, or help with a data subject request should contact their account team or use the form at the bottom of this page.
This policy describes Celentra's current data practices as of 7 October 2026. We update the dates above when our practices materially change.