Privacy Policy

1. Who we are

TPSClear is a UK Telephone Preference Service (TPS) and Corporate TPS (CTPS) list-cleaning service operated by Voll Studios Ltd, a company registered in England and Wales (company number 09302803, registered office 5 Brayford Square, London, England, E1 0SG). Voll Studios Ltd is registered with the Information Commissioner's Office under registration number ZC135838. In this policy "TPSClear", "we", "us" and "our" refer to Voll Studios Ltd in our capacity as operator of the TPSClear service.

For privacy queries, contact us at privacy@tpsclear.co.uk.

2. The service this policy covers

TPSClear is delivered in two ways:

• REST API. A direct screening interface used by customers building TPS/CTPS compliance into their own systems.
• Native CRM integrations. Applications for HubSpot and Zoho CRM, with Pipedrive in marketplace review and Salesforce, Microsoft Dynamics 365 and Capsule CRM in build. These call the API on the customer's behalf and write verdicts back to CRM records.

This policy applies to all of them and to the marketing site at tpsclear.co.uk.

3. Roles under UK GDPR

Customer data submitted for screening (CRM records, API request payloads, or numbers entered in the free checker): the customer (the organisation or individual that holds a TPSClear account or uses the free checker) is the data controller. TPSClear is the data processor, processing this data on the customer's documented instructions to perform the screening service. A Data Processing Agreement (DPA) covers this relationship; see section 12.

Marketing-site visitors and account holders: for example, anyone who emails us, submits a form on the site, or opens a TPSClear account. TPSClear is the data controller.

4. What data we process

4.1 Customer data (as processor)

Across both the API and CRM integrations:

• UK and Australian phone numbers submitted for screening. We normalise these to E.164, query the TPS and CTPS registers or the Australian Do Not Call Register, and return a verdict.
• The screening verdict returned or written back: TPS-listed, CTPS-listed, TPS and CTPS-listed, Clean, Not a valid UK number, Unknown, or Do not call (opt-out) for a number on the customer's own suppression list, and for Australian numbers On the DNCR, Not on the DNCR or Not a valid AU number, with a timestamp.
• In a connected CRM (HubSpot, Pipedrive or Zoho CRM): we read the phone fields and record IDs of the records TPSClear screens, and we write the verdict and the time of the check to the TPSClear fields on those records.
• Account identifiers required to authenticate the request: CRM-side OAuth tokens, API keys, customer account IDs.
• Optional metadata the customer chooses to send with API calls, for example a request reference for the customer's own audit trail.
• Numbers entered in the free checker at tpsclear.co.uk/tps-check and tpsclear.co.uk/ctps-check. Each number is checked in memory and the verdict is returned on the page. The number and the verdict are not stored, cached or logged.

We do not require, request, or rely on names, email addresses, or other personal data attached to the phone numbers being screened. The screening operation works on the number alone.

4.2 Account holder and marketing-site visitor data (as controller)

• Email address, name, organisation, a phone number if you ask us to call you back, and any message content sent to us. Enquiries sent through a form on this site or by email also go to the recipients listed under "Enquiries" in section 6.
• Account information when an account is created or a CRM app is installed: account ID, billing contact, and acceptance records for these terms and the DPA. For a CRM installation we also keep the CRM account's ID and domain, the company name where the CRM supplies it, and the email address of the user who installed or connected the app.
• Operational telemetry: request timestamps, error logs, usage counts. We do not log phone numbers alongside this telemetry.
• For the free checker, a count of each visitor's checks that day, held against a one-way hash of the visitor's IP address, never the address itself.
• Standard server logs (IP address, user agent) retained for security and abuse-prevention purposes.

5. Why we process it (lawful bases under UK GDPR)

• Contract. To deliver the TPSClear screening service to customers and account holders.
• Legitimate interests. To secure the service, prevent abuse, improve performance, monitor usage against fair limits, and respond to support enquiries. We balance these interests against your rights.
• Legal obligation. Where we are required by law to retain records or respond to lawful requests.

6. Sub-processors

We do not sell or share customer data with third parties for marketing purposes. We share data only with the sub-processors who help us run the service and, for Australian numbers, the Do Not Call Register (section 7):

• Vercel Inc. (United States; functions run in London, and UK and EU traffic is served from the nearest edge region): application hosting, serverless API execution, and privacy-friendly web analytics.
• Supabase, Inc. (managed Postgres in an EU region): database hosting for the screening result cache, screening audit records, account metadata, OAuth installation records, and per-installation screening configuration.
• DigitalOcean, LLC (service hosted in London, United Kingdom): hosting for our own TPS/CTPS register service, which checks numbers against the register files Voll Studios Ltd is licensed for.
• Fly.io, Inc. (service hosted in London, United Kingdom): standby hosting for our own TPS/CTPS register service, used only when the main host is unavailable. Numbers are checked in memory and not stored.
• Selectabase Ltd (United Kingdom): licensed TPS/CTPS screening provider performing register lookups for customers not yet on our own register service, and the first fallback when it is unavailable.
• Data8 Ltd (United Kingdom): licensed data partner for TPS/CTPS register data, held in reserve and not currently used for lookups.
• Simunix Ltd (T2A) (United Kingdom): licensed data partner for TPS/CTPS register data, used as the second fallback when other lookups are unavailable.
• 3G Telecommunications Ltd (hlrlookup.com) (United Kingdom; hosted in Ireland): mobile network status lookups for dead number checks. It receives the phone numbers you ask us to check and keeps results for 30 days.
• TMT Analysis Ltd (TMT ID) (United Kingdom; hosted in Germany and Finland): the second provider of mobile network status lookups for dead number checks, used when hlrlookup.com is unavailable and to compare result quality. It receives the phone numbers you ask us to check.
• Stripe, Inc. (and Stripe Payments Europe Ltd): payment processing and subscription billing. Stripe handles billing details only; no screening data.
• Resend, Inc. (United States): transactional email for account and service notifications; no screening data.
• Cloudflare, Inc.: DNS and email routing for the tpsclear.co.uk domain.
• Google (Google Ireland Ltd, Google Workspace): business email for support and privacy correspondence.

Enquiries. When you send an enquiry through a form on this site or by email, your name, email address, the details you give and your message are sent to Anthropic, PBC (United States), whose Claude model drafts our reply; to TypeSafe AI, whose Jev model sorts the enquiry; and to Telegram, which delivers the enquiry and the draft to our founder. These recipients may process the data outside the United Kingdom. They receive no customer screening data.

The CRM platforms we connect to are not TPSClear sub-processors. For CRM-integration customers, the TPSClear app connects to your own CRM account, which is your own CRM environment under your own agreement with the CRM provider:

• HubSpot: the TPSClear app runs inside your own HubSpot portal.
• Pipedrive (Pipedrive OÜ, Estonia): the TPSClear app connects to your own Pipedrive company account.
• Zoho CRM (Zoho Corporation): the TPSClear app connects to your own Zoho CRM organisation, in the Zoho data centre your account uses (for example EU, UK, US or Australia).

When a Pipedrive or Zoho CRM customer uninstalls the app or revokes its access, we delete the stored OAuth tokens once we detect it and stop screening. Verdicts already written to your CRM stay on your records until you delete them.

A current list of sub-processors with locations and transfer mechanisms is published at tpsclear.co.uk/subprocessors. We require sub-processors to provide appropriate security and data-protection commitments, and we notify active customers at least 30 days before adding or replacing a sub-processor.

7. International transfers

Some sub-processors may process data outside the United Kingdom and the European Economic Area. Where they do, we rely on UK-approved transfer mechanisms, including the UK International Data Transfer Addendum and equivalent Standard Contractual Clauses, to safeguard the data.

Australian phone numbers submitted for checking are sent to the Do Not Call Register, kept by the Australian Communications and Media Authority (ACMA) in Australia, and the register's answer is returned to the customer. Where the customer is bound by the Privacy Act 1988 (Cth), sending Australian numbers to TPSClear in the United Kingdom may be a cross-border disclosure under Australian Privacy Principle 8.

8. Retention

• Screening verdicts written to a customer's CRM remain on the customer's records for as long as the customer keeps them; their retention is under the customer's control.
• Screening audit log. Each API screening request produces an audit record, referenced by the X-Request-Id returned in the response, containing the request id, the numbers screened, and the verdicts. Audit records are retained for 24 months, then deleted; on accounts that first bought before 21 October 2026 they are retained for 12 months, the period in the DPA in force when they bought. We keep them to support dispute resolution and to give customers billing and compliance evidence for each screen.
• Free checker. Numbers entered and their verdicts are not retained. The daily check counts are deleted after two days.
• Dead number check results. Each dead number check stores the number, its status (live, switched off, dead or undetermined) and the time of the check. These records are retained for 12 months, then deleted.
• CRM screening log. Each check made inside a connected CRM produces a log entry containing the time, the record ID, the phone field, the verdict and what triggered the check, and in HubSpot the number screened. Entries are retained for 24 months, then deleted. We keep them as the customer's compliance evidence and to calculate usage.
• Screening result cache. For API and CRM screening, a definitive verdict is cached against the screened number so that repeat screenings of the same number within 27 days do not incur a fresh billed register lookup (TPS registrations become enforceable after 28 days and the register data can be a day behind, so a verdict is safe to reuse within that window). Cached verdicts are deleted no later than 60 days after the underlying check.
• Platform operational logs (Vercel function invocation logs, error traces, request metadata) are retained per our hosting platform's defaults, typically around 30 days for production deployments. Phone numbers are not written to these error and telemetry logs.
• Operational telemetry (timestamps, error codes, usage counts) is retained for up to 12 months, then deleted or fully anonymised.
• Customer account records are retained for as long as the account is active, plus 12 months after closure for legitimate-interest record-keeping, unless a longer period is required by law.

9. Your rights

Under UK GDPR you have the right to:

• access the personal data we hold about you;
• have inaccurate data corrected;
• have your data erased in certain circumstances;
• restrict or object to certain types of processing;
• data portability where applicable;
• lodge a complaint with the Information Commissioner's Office (ico.org.uk) if you believe we have not handled your data properly.

To exercise any of these rights, email privacy@tpsclear.co.uk. For data we process on behalf of a customer (CRM records or API submissions), please direct requests to the customer who is the controller; we will assist as the processor.

10. Cookies and analytics

The TPSClear marketing site does not set marketing or advertising cookies. Strictly necessary cookies may be set for session, security, and load-balancing purposes by our hosting provider.

We use Google Analytics 4 to understand aggregate site usage (which pages get visited, what country traffic comes from, which referrers send visits). Google Analytics is loaded with UK GDPR consent mode set to denied by default, so it does not set tracking cookies on your device unless you explicitly consent in future via a banner we may introduce. Until then, Google receives cookieless modelled pings only, which contain no identifiers we could use to recognise you across visits. IP addresses sent to Google Analytics are anonymised at collection. You can opt out of Google Analytics in any browser by enabling Do Not Track or installing the official Google Analytics opt-out browser add-on.

We also use Vercel Web Analytics, provided by our hosting provider, to count page views and visits. It sets no cookies and stores no IP addresses; visits are counted with a hash that resets every 24 hours. Like Google Analytics, it is not loaded when your browser sends Do Not Track or Global Privacy Control.

11. Security

We protect data with industry-standard measures: encryption in transit (TLS 1.2 or higher), encryption at rest for the configuration and OAuth-token records we hold in our hosted database, scoped API keys, role-based access controls, and principle-of-least-privilege practices for staff. No system is perfectly secure; we will notify affected customers and the ICO of any qualifying data breach in line with UK GDPR requirements (within 72 hours of becoming aware, where applicable).

12. Data Processing Agreement

Our Data Processing Agreement is published at tpsclear.co.uk/dpa. It applies automatically and forms part of the Terms of Service. It covers the standard UK GDPR processor obligations: processing on documented instructions, confidentiality, security measures, sub-processor controls, assistance with data-subject requests, breach notification, and return or deletion of data on termination. A countersigned copy is available on request from privacy@tpsclear.co.uk.

13. Changes to this policy

We may update this policy from time to time. Material changes will be announced on this page and, where appropriate, by direct communication to active customers. The "Last updated" date at the top of the page reflects the most recent change.

14. Contact

Email privacy@tpsclear.co.uk or write to Voll Studios Ltd at the registered address above.