Privacy

How we handle your data. Last updated 2026-05-19.

At LeadSafe, we care about your privacy. This page tells you what we collect, why we collect it, who else sees it, and how long we keep it. Plain English. If anything’s unclear, email go@leadsafe.io and we’ll explain.

1. Our promise

We only collect what we need to run LeadSafe for you. We don’t sell your data. We don’t use it to train AI models. We don’t track you across the internet.

2. Two roles, depending on whose data it is

LeadSafe is a B2B service. We handle two kinds of personal data, and our legal role is different for each.

• Your data as a LeadSafe customer. We’re the controller. We decide what to do with your account email, business name, billing details, and settings. If you want to exercise your rights, you come to us.
• Your customers’ data, flowing through LeadSafe. We’re the processor. You’re the controller. We hold and route this data on your instructions; the rights and obligations for end-customers rest with you. If one of your customers asks where their data is or wants it deleted, they ask you first, and you tell us what to do.

3. What we collect

For your LeadSafe account: your email, business name, phone number, billing details, and the settings you choose (calling hours, quiet windows, data retention preferences).

Through LeadSafe, on your behalf: leads’ names and contact details, the messages they send you, transcripts of inbound calls, recordings of those calls. Plus the integration credentials you set up (Cal.com webhook secrets, OAuth tokens, billing identifiers).

And usage analytics: pages viewed, actions taken inside LeadSafe, errors that happen. First-party only — no Google Analytics, no Mixpanel, no advertising pixels.

LeadSafe is built for businesses, not children. If a child’s data ends up in LeadSafe through one of our customers, email us and we’ll work with that customer to remove it.

4. Why we collect it

To run the service you signed up for. That means: handling your inbound enquiries, running the AI voice agent, sending follow-up sequences, routing bookings into your pipeline, and billing you for usage.

Under applicable data protection laws, we rely on the contract between us (the LeadSafe terms you agreed to) as the lawful basis for your account data. For your customers’ data that flows through LeadSafe, your lawful basis applies — usually legitimate interest, sometimes consent. Establishing that basis is your responsibility as the controller of your customers’ data.

5. Who else sees your data

To run LeadSafe we use a small number of trusted third parties — for hosting, email and SMS, voice transcription, error monitoring, and billing. They only process your data on our instructions, under contracts that include data protection commitments.

For the full list, see our sub-processors page.

If we add or change a sub-processor in a way that materially affects how your data is handled, we’ll email you before the change takes effect.

6. How long we keep it

Your account data: while your account is active, plus 90 days after you cancel. After that we delete or anonymise it.

Your customers’ lead data and conversation history: while your account is active. Deleted within 90 days of cancellation.

Call recordings: per your recording_retention_months setting (default 6 months). Auto-deleted after that window.

Call transcripts: per your transcript_retention_years setting (default 6 years — aligned with UK business-record retention norms).

Billing records: 6 years, regardless of account status, to meet HMRC requirements.

7. Where your data lives

Your data is primarily stored in the UK and EU. Some of the third parties listed on our sub-processors page operate from the US — transfers there are covered by the UK’s International Data Transfer Addendum to the EU Standard Contractual Clauses.

We currently operate in the United Kingdom. If we expand to other regions, we’ll update this policy.

8. How we protect your data

Everything between your browser and our servers travels over HTTPS. Data at rest is encrypted at the database layer. Sensitive credentials (OAuth tokens, integration secrets) sit in encrypted columns.

We isolate every customer’s data using row-level security policies at the database layer. One LeadSafe customer can’t see or change another’s data, even at the database level.

Inbound webhooks from your integrations are cryptographically verified, so we only act on genuine events from the services you’ve authorised.

Production database access is limited to our engineering team, gated by single sign-on, and audited.

9. Your rights

Under applicable data protection laws, you have the right to:

• See the personal data we hold about you.
• Have anything inaccurate corrected.
• Have your data deleted.
• Receive your data in a portable format you can take elsewhere.
• Restrict or object to how we’re processing your data.
• Withdraw consent at any time, where we relied on consent in the first place.
• Complain to your data protection authority — in the UK, that’s the Information Commissioner’s Office at ico.org.uk.

Email go@leadsafe.io to exercise any of these rights. We’ll respond within 30 days, usually sooner.

If you’re a customer of one of our customers, your request goes to them first — they decide what happens to their customers’ data; we just process it on their instructions.

10. Cookies

We only use essential cookies — the ones that keep you signed in and remember where you are in onboarding. No analytics cookies, no advertising pixels, no third-party tracking. Full details on the cookies page.

11. Changes to this policy

We may update this policy from time to time. The “last updated” date at the top of the page reflects the most recent change. If we make a material change — new sub-processor, change of legal basis, change of retention — we’ll email you before it takes effect.