Skip to content

Legal

Data Processing Agreement

Our Article 28 UK GDPR commitments to the businesses that use ClientTurn, in one document: what we process, how we protect it, who helps us, and what happens at the end.

Version
1.0 — 28 September 2026
In force from
28 September 2026
Governing law
England and Wales

Who you are contracting with

ClientTurn is a trading name of Blackwellen Limited, a private company limited by shares registered in England and Wales under company number 16482166.

Registered office: 61 Bridge Street, Kington, Herefordshire, HR5 3DJ, United Kingdom. This is also our address for service of formal notices.

Support: support@clientturn.com · Legal, data protection and formal notices: legal@clientturn.com. These are the only two mailboxes we operate.

Blackwellen Limited is not currently registered for VAT. No VAT is charged on our invoices, and none may be reclaimed on them. We will publish our VAT number here and begin charging VAT from the date registration takes effect.

1. About this agreement

This Data Processing Agreement (“DPA”) is between Blackwellen Limited, trading as ClientTurn (company number 16482166, registered office 61 Bridge Street, Kington, Herefordshire, HR5 3DJ, United Kingdom) (“we”, the processor), and the business that holds a ClientTurn workspace (“you”, the controller). It is the contract required by Article 28(3) of the UK GDPR.

It forms part of the Terms of Service (clause 16) and is accepted when you accept those terms. It sets out the same commitments as section 7 of our Privacy Policy in one standalone document, with the annexes a procurement or security review asks for. If you need a countersigned copy for your records, write to legal@clientturn.com.

2. Definitions

“UK GDPR”, “personal data”, “processing”, “controller”, “processor”, “data subject” and “personal data breach” have the meanings in the UK GDPR and the Data Protection Act 2018. “Customer Personal Data” means personal data we process on your behalf in providing the service, as described in Annex 1. “Sub-processor” means a third party we engage to process Customer Personal Data.

3. Roles and scope

For Customer Personal Data you are the controller and we are your processor. You decide which leads and contacts are processed, why, and which channels, rules and integrations are used.

For the account data of your own users (sign-in, billing, support) we are an independent controller, as described in the Privacy Policy. This DPA does not apply to that data.

Where you take a payment through a quote or invoice link, you are the merchant of record through your own payment provider account; ClientTurn sends the link and reads the payment result for you.

4. Processing on your instructions

We process Customer Personal Data only on your documented instructions. Your instructions are this DPA, the Terms, and the configuration you set in the product (sources, questions, rules, channels, integrations and retention settings).

If the law requires us to process it otherwise, we will tell you first unless the law forbids it. We will tell you if we believe an instruction infringes data protection law.

You are responsible for having a lawful basis, for the transparency information you give data subjects, and for complying with PECR when you use the service to send electronic marketing.

5. Confidentiality

Everyone we authorise to process Customer Personal Data is bound by a duty of confidence and has access only as far as their role needs.

6. Security

We implement the technical and organisational measures in Annex 2, which are appropriate to the risk under Article 32. We may change them to keep pace with threats and technology, but will not reduce the overall level of protection.

7. Sub-processors

You give general written authorisation for us to engage the sub-processors listed in Annex 3 and on our sub-processor register, which is the current list.

  • We give at least 30 days’ notice by email before a new sub-processor starts processing Customer Personal Data, and update the register at the same time.
  • You may object on reasonable data protection grounds within the notice period by writing to legal@clientturn.com. If we cannot resolve it, you may end the affected part of the service and receive a pro-rata refund of prepaid fees for it.
  • Each sub-processor is bound by written terms no less protective than this DPA, and we remain liable to you for its performance.
  • We do not use data brokers or paid contact-enrichment vendors.

8. International transfers

The primary database is in London (eu-west-2). Where a sub-processor processes Customer Personal Data outside the United Kingdom, we rely on UK adequacy regulations or on the International Data Transfer Addendum to the EU Standard Contractual Clauses (or the International Data Transfer Agreement), supported by a transfer risk assessment. Annex 3 gives the location of each.

Retell AI (the optional AI voice agent) processes and stores call data in the United States (Amazon Web Services US regions). The transfer relies on the UK International Data Transfer Agreement or the Standard Contractual Clauses with the UK Addendum, under Retell AI's data processing agreement.

9. Data subject requests

We help you answer requests from data subjects through the product (search, export, suppression, anonymisation and deletion tools, and the privacy request inbox in Settings), and by responding to reasonable requests for further help. If a request reaches us directly we pass it to you without undue delay and do not answer it ourselves unless you ask us to.

10. Personal data breaches

We notify you without undue delay, and in any event within 24 hours of becoming aware, of a personal data breach affecting Customer Personal Data. The notice gives what we know at that point: the nature of the breach, the categories and approximate numbers of people and records, the likely consequences, and what we are doing about it. We follow up as we learn more.

We will help you meet your own obligations to notify the ICO within 72 hours and, where the risk is high, the people affected.

11. Impact assessments

Taking into account the nature of the processing and the information available to us, we assist you with data protection impact assessments and any prior consultation with the ICO. Our security questionnaire answers and data-flow description are available on request.

12. Deletion and return

For 30 days after your subscription ends you may export your data using the export tools, or ask us for a machine-readable copy free of charge. After that, and in any event within 90 days, we delete or irreversibly anonymise Customer Personal Data, except records the law requires us to keep and minimised suppression records kept only so that someone who opted out is not contacted again. Deleted data leaves our encrypted backups as they expire.

13. Information and audits

We make available the information needed to demonstrate compliance with this DPA, starting with this document, the sub-processor register and our security questionnaire answers. Where that is not enough, you (or an independent auditor bound by confidentiality) may audit on at least 30 days’ notice, no more than once in any 12 months except after a personal data breach, during business hours and without access to other customers’ data. Each party bears its own costs.

14. Liability and order of precedence

Each party’s liability under this DPA is subject to the limits in clause 20 of the Terms, except where the law does not allow it to be limited. If this DPA conflicts with the Terms on the processing of Customer Personal Data, this DPA prevails.

15. Term and changes

This DPA lasts as long as we process Customer Personal Data for you. We may update it to reflect changes in law or in the service; we will give at least 30 days’ notice of any change that reduces your protection. The version and date at the top of this page identify the text in force.

16. Our registration and contact

Blackwellen Limited is registered with the Information Commissioner’s Office, registration number ZC160806. Data protection questions and notices under this DPA go to legal@clientturn.com.

Annex 1. Details of the processing

Subject matter
Provision of the ClientTurn service: receiving leads, instant follow-up, deterministic qualification, booking, quoting and invoicing links, optional AI voice calls, and reporting.
Duration
The customer's subscription, plus the exit and deletion period in section 12.
Nature and purpose
Collecting, recording, organising, storing, retrieving, transmitting, analysing, restricting and erasing personal data so the customer can respond to, qualify and convert its own enquiries and prospects.
Categories of data subject
The customer's prospective and existing clients and their staff (leads and contacts), people who sign or pay a quote, and the customer's own authorised users.
Types of personal data
Name, business email address, phone number supplied on a lead form, job title and company, lead form answers, message and email content, qualification answers, booking details, quote and invoice details (including signer name, email, IP address and user agent), call metadata, transcripts and, where enabled, recordings, and campaign attribution identifiers.
Special category data
None intended. The product does not ask for it and customers must not collect it through the service. Any volunteered in a free-text reply is held only as part of that message.
Frequency
Continuous, for as long as the customer uses the service.

Annex 2. Technical and organisational measures

Tenant isolation and access control

  • Every tenant table carries a workspace identifier and has Postgres row-level security enabled, so one workspace's session cannot read another's rows even if application code is wrong.
  • Workspace roles (owner, admin, member, viewer) plus per-person permissions for outbound sending, integrations and billing, checked on the server for every action, whether it comes from the app, the API or MCP.
  • Platform administration uses a separate sign-in, is checked against the database on every request, and requires the operator to re-enter their password (step-up) within the last 30 minutes before any change.
  • Workspace API keys are scoped and can be revoked at any time.

Encryption and secrets

  • TLS in transit for all traffic, with HTTP Strict Transport Security (including preload).
  • Encryption at rest provided by the database and object-storage platforms.
  • Mailbox passwords a customer enters are encrypted in the application (AES-256-GCM) before storage; integration tokens and webhook secrets are held in tables only the server can read.
  • Service keys, provider tokens and webhook secrets are server-side only: never in a browser bundle, a public environment variable or a response body.

Integrity of inbound data

  • Every inbound webhook's signature or shared secret is verified before the payload is trusted, and events are de-duplicated so a replayed event cannot cause a second action.
  • All inputs, filters, uploads and webhook payloads are validated against a schema.
  • Outbound fetches of customer-supplied web addresses are restricted to public addresses, with every redirect re-checked.

Files

  • Files are stored in a private bucket and served only through short-lived signed links (5 minutes by default).
  • Uploads are limited by type and size; SVG images are refused.

Accountability

  • An append-only audit log records administrative and data-changing actions with the actor and time; workspace owners and admins can export it.
  • Rate limits on sign-in, public forms, exports, the API and webhooks.
  • Every contact decision (why a message was or was not allowed) is recorded with the rules in force at the time.

Resilience

  • Daily encrypted database backups held by our database provider in the United Kingdom.
  • A documented restore runbook. Point-in-time recovery and a recorded restore drill are being put in place and will be listed here when complete.
  • A public status page reporting the health of each part of the service.

AI

  • AI assistance is optional and off by default. Deterministic rules make every qualification and follow-up decision; the AI never composes a binding price, quote, availability or service-area promise.
  • Azure OpenAI runs in the EU; customer data is not used to train models.

Annex 3. Sub-processors

The current list, with the personal data each can see and the transfer mechanism relied on, is on the sub-processor register. At the date of this version:

ProviderPurposeLocation
SupabaseCorePrimary application database, authentication and file storage. Holds workspace accounts, leads, messages, qualification answers and audit records.London, United Kingdom (eu-west-2)
VercelCoreHosting and delivery of the application and marketing site, including request routing, function execution and short-lived operational logging.United States (primary compute), with a global edge network
StripeCoreSubscription billing, checkout, card processing, invoicing and tax calculation. Card details are entered into Stripe-hosted fields and never reach our servers.European Union and United States
Cloudflare R2CoreObject storage for workspace logos, uploaded CSV import files, support attachments, quote and invoice PDFs and, where voice recording is turned on, call recordings; and network protection in front of the site. Stored files are served only through short-lived signed URLs.European Union jurisdictional restriction applied to stored objects
TwilioCoreDelivery of outbound SMS and WhatsApp messages and receipt of inbound replies, including delivery receipts and opt-out keywords. Where a customer turns on the AI Voice Sales Agent, also the dedicated phone number and the telephone connection for its calls.Ireland and United States
Retell AIOnly if enabledRuns the AI Voice Sales Agent's calls: speech recognition, the voice, and the real-time connection between the call and ClientTurn's agent. Only used when a customer turns voice on.United States, hosted on Amazon Web Services US regions (Retell AI's privacy policy: data is primarily stored and processed in the United States).
ResendCoreTransactional email: sign-in and verification messages, billing notices, product notifications, and follow-up email to leads where email follow-up is configured.United States
Microsoft Azure OpenAI ServiceOnly if enabledOptional AI assist. Classifies the intent of an inbound reply and extracts a candidate answer to a question the customer has already configured. It never composes a price, quote, availability or service-area commitment, and the deterministic rules always make the decision.European Union (EU data boundary; customer data is not used to train models)
Google PlacesOnly if enabledCompany discovery for Find Leads: finds businesses matching the customer's search (industry and area) so their own websites can be read. Only used when a customer runs a Find Leads search.European Union and United States
Meta Lead AdsCustomer-enabledSource of the leads a customer receives. Meta delivers lead form submissions and campaign attribution fields for the pages and forms the customer connects.European Union and United States
Google CalendarCustomer-enabledReading availability and writing bookings into the connected calendar, where a customer connects one.European Union and United States
CalendlyCustomer-enabledBooking pages and appointment records, where a customer connects Calendly instead of a calendar.United States
Advertising platformsCustomer-enabledWhere a customer connects an advertising account for attribution, we return conversion signals for the leads that platform generated.European Union, United Kingdom and United States
CRM and notification destinationsCustomer-enabledWhere a customer connects a CRM or Slack, we push the lead and its status into that system on the customer's instruction.Determined by the customer's own tenancy with that provider