Privacy Policy

Esta página también está disponible en español.

1. Who we are and scope

LealUp, operated by LEALUP SPA, is a Customer Success (CS) platform for B2B SaaS companies. Our customers ("Customers") use it to manage the health, adoption, renewal and communication of their own customers. This policy explains what data we process, for what purposes, and what rights you have. With respect to data a Customer uploads or connects about its accounts and contacts, LealUp acts as a data processor on the Customer's behalf.

2. Data we process

Account and identity: name, email, organisation, role (authentication is handled by our identity provider, Clerk). Product usage: usage events, technical logs and metrics. Customer data: account and contact profiles, notes, tasks, meetings, health and revenue (MRR) metrics, and the communications the Customer chooses to record. Integration data: content and metadata from the services the Customer authorises (see sections 4 and 6).

3. How we use data, and legal basis

We use data to provide and operate the service, authenticate users, generate Customer Success signals and insights, send the notifications the Customer configures, provide support, and comply with legal obligations. Legal bases (GDPR, where applicable): performance of the contract, legitimate interest, consent (optional integrations) and legal obligation. We do not sell personal data and we do not use it for advertising, nor do we transfer it to data brokers.

4. Google API data (Gmail and Google Calendar)

When a user connects their Google account, LealUp accesses Google data only with the permissions the user grants, and only to deliver the features described below. All four permissions are granted on a single consent screen; there is no per-permission opt-in.

How email sync works

To determine which messages relate to a customer, LealUp must read the messages in the connected mailbox — the Gmail API does not support server-side sender filtering on the incremental sync path. Reading and storing are different things, and the difference matters. LealUp reads the messages in the mailbox within a rolling time window, compares each message's participants (sender, recipients and those copied) against the registered contacts of the workspace's customers — by exact address, not by domain, and excluding the mailbox owner's own address — and then, depending on the result:

• No customer contact matches: the message is discarded and not stored. Your personal or work-unrelated correspondence never reaches our database.
• One customer matches: the message (headers and body) is attached to that customer's timeline, visible to authorised users of that workspace, and its content is analysed to generate Customer Success signals (sentiment, churn risk, unanswered threads).
• Two or more customers match: the message is placed in a triage queue ("Unmatched Emails") so a workspace user can indicate which customer it belongs to. This happens when a registered contact works with two of your customers, or when the thread includes participants from both. These messages are not analysed by AI models.

For attachments we store only the file name, size and type — never the file contents.

Limited Use

LealUp'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 use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.

Specifically, with respect to data — raw or derived — obtained from Google restricted scopes: we use it only to provide or improve the user-facing features described above; we do not transfer or sell it for advertising, credit assessment, or to data brokers; we do not allow humans to read it except with the user's explicit consent, for security purposes, to comply with applicable law, or in aggregated and anonymised form; and we do not use it to develop, improve or train artificial intelligence or machine learning models (see section 5).

Revocation and disconnection

You may revoke LealUp's access to your Google account at any time from your Google account permissions page, or by disconnecting the integration inside LealUp. On disconnection we revoke the tokens with Google, delete the tokens we had stored, and syncing stops.

Email and meetings already attached to a customer's timeline are retained: they constitute the Customer's business record about its own customer, and LealUp processes them on the Customer's behalf rather than on the individual user's. One employee disconnecting their mailbox or changing their password does not erase their organisation's record of the commercial relationship. To request their deletion, direct your request to the Customer — LealUp will assist (see sections 7 and 9).

If we lose access to your account without you disconnecting the integration — for example after a password change or a revocation from Google — we stop syncing and ask you to re-authorise. We do not automatically delete customer history in that case, because we cannot distinguish a deliberate revocation from a technical interruption.

5. Artificial intelligence and AI subprocessors

LealUp uses AI models for features such as sentiment analysis and account insights. LealUp does not train or develop its own AI models with user data. Processing is performed by inference through external providers — OpenAI and Anthropic — whose API terms state that data submitted is not used to train their models. We maintain data processing agreements (DPAs) with these providers and send only what is necessary to produce the requested feature.

6. Who we share data with

We share data only with providers that help us operate the service, under contract and with confidentiality and security obligations: Clerk (identity), Railway (hosting), Resend (transactional email), OpenAI and Anthropic (AI inference), and the integrations the Customer enables (such as HubSpot, Pipedrive, Stripe, Slack, WhatsApp via Kapso, or Microsoft). We maintain an up-to-date subprocessor list, available on request.

This applies to both raw and aggregated or anonymised data: we do not share, transfer or sell it to any other category of third party — in particular not to advertisers, ad networks, data brokers or credit assessment services — for any purpose other than providing or improving user-facing features.

7. Data retention and deletion

Why customer history is retained on disconnection. Email and meetings attached to a customer constitute the Customer's business record about its own customer, and LealUp processes them on the Customer's behalf. The decision to delete them rests with the Customer, not with the individual user who connected the mailbox.

For deletion requests outside these flows, write to [email protected]; we respond within 30 days.

8. Security

We apply reasonable technical and organisational measures, including:

• Encryption in transit (TLS) on all connections to the service and to third-party APIs.
• Encryption of OAuth tokens at rest: access and refresh tokens for Google and all other integrations are encrypted with keys we manage before being stored, and are never written to logs.
• Encryption at rest for the database and file storage, provided and managed by our infrastructure providers.
• Key and secret management through our infrastructure provider's environment configuration, with restricted access and rotation on any suspicion of exposure. Secrets are never committed to source control.
• Tenant isolation: every record belongs to a workspace and queries are filtered by it at the data access layer, with automated tests verifying that one Customer's data is not visible to another.
• Role-based access control within each workspace, and audit logging of authentication, permission changes, exports and destructive operations.
• Minimal internal access: LealUp personnel access to production data is limited to what is necessary to operate the service and handle support, and requires multi-factor authentication.

9. Your rights

Depending on your jurisdiction (GDPR/CCPA and equivalents), you may have the right to access, rectify, delete, port or object to the processing of your data. For data we process on a Customer's behalf, direct your request to that Customer; we will assist them. Write to us at [email protected]. You can revoke LealUp's access to your Google account at any time from your Google account permissions page.

10. International transfers

We may process data in countries other than yours (where our providers operate). Where applicable, we use appropriate transfer mechanisms such as Standard Contractual Clauses.

11. Minors

LealUp is a B2B product and is not directed at minors; we do not knowingly collect their data.

12. Changes

We may update this policy. We will publish the current version at this URL with its update date and, for material changes, give notice by reasonable means.

13. Contact and controller identification

Data controller: LEALUP SPA, RUT 78.455.929-7, Av. Pdte. Kennedy 5600, Of. 507, Vitacura, Santiago, Chile. You can exercise your rights or raise privacy questions by writing to our privacy contact / Data Protection Officer: [email protected].