ClearedOn Sub-processor List
Version 0.3-draft · 10 October 2026 · NOT IN FORCE — for solicitor review
Public list of the sub-processors Kefilab uses to provide ClearedOn. It mirrors Annex C of the ClearedOn Data Processing Agreement; where they differ, the DPA prevails. Items marked [TO CONFIRM: …] are open.
Kefilab (a trading name of Baldev Singh Badesha), 301 Bath Road, Hounslow, London TW3 3DB, provides ClearedOn as a processor for the firms that subscribe to it. Each firm is the controller of the data about its people. A sub-processor is a third party Kefilab engages that processes that data.
Current sub-processors
| Sub-processor | What it does for ClearedOn | Personal data it handles | Where | Transfer mechanism |
|---|---|---|---|---|
| Supabase, Inc. | Database, authentication and file storage | All data in the Service, including identity and evidence files (which are stored encrypted with a per-firm key) | Data hosted in London, UK (AWS eu-west-2). Company established in the USA | None needed for storage — data is hosted in the UK. [TO CONFIRM: safeguard for any remote access from the US under Supabase's DPA (UK Extension to the EU–US DPF and/or SCCs + UK Addendum)] |
| Netlify, Inc. | Application hosting and serverless functions | Data passing through application functions; Netlify does not store register data | Functions run in London (eu-west-2). The global edge network/CDN caches static assets only (scripts, styles, images). Company established in the USA | As for Supabase. [TO CONFIRM] |
| Resend (Plus Five Five, Inc.) | Transactional email: sign-in codes, signing links and codes, reminders, and notifications to firm users | Recipient email address, delivery metadata and the message. Messages never contain documents or the personal data held on the register — only links and codes, plus the recipient's own first name in emails to people who receive a signing link. Emails to firm users never name the person or the check | USA | Restricted transfer. Primary: Resend's certification under the UK Extension to the EU–US Data Privacy Framework. Fallback: EU SCCs with the UK Addendum in Resend's Data Processing Agreement. Supported by a transfer risk assessment. [TO CONFIRM: ClearedOn-specific TRA recorded and Resend DPA covers the ClearedOn account] |
| Stripe (Stripe Payments Europe, Ltd / Stripe, Inc.) | Billing of subscribing firms | Firm billing contact and payment details only. No data about firms' staff, starters, contractors or agency workers | [TO CONFIRM: contracting entity and location] | Stripe acts for Kefilab's own billing (Kefilab as controller); listed for transparency |
Customer-directed integrations (not Kefilab sub-processors)
| Provider | When | Notes |
|---|---|---|
| Clio | Only if a firm has connected its Kefilex (below), and that Kefilex is connected to the firm's own Clio | Detection only. Clio's API cannot create users, so ClearedOn asks the firm's Kefilex, which asks the firm's Clio through the firm's own Clio connection, whether a given work email address is an enabled Clio user. A read-only lookup by email address, used to tick off the "set up Clio" task and to confirm a leaver's Clio account is disabled. Clio is the firm's own system, used under the firm's own agreement with Clio |
| Google (Google Workspace) | Only if and when a firm chooses to connect its own Google Workspace for account provisioning | Planned — a future feature, not available at the date of this list. Engaged under the firm's own agreement with Google |
| Microsoft (Microsoft 365) | Only if and when a firm chooses to connect its own Microsoft 365 for account provisioning | Planned — as above |
| The firm's AI assistant (for example Anthropic for Claude, OpenAI for ChatGPT) | Only if a firm admin switches on the AI connector, and then only for the people who connect their assistant | Engaged under the firm's own account and agreement with the provider. Receives only what the connected person's assistant asks for: documents, firm facts, compliance position holders, review dates and, if the firm allows it, names, roles and acknowledgement dates of people on the register and audit log actions. Never identity, right-to-work or DBS documents or details, personal contact details, signing links or signatures. Usually outside the UK (the USA); that transfer is the firm's, under its agreement with the provider (DPA clause 4.4(c)) |
[TO CONFIRM: the solicitor's view on whether these are customer-directed integrations (the Kefilex approach, DPA clause 4.4) or should be listed as Kefilab sub-processors.]
Kefilab's own services (not third-party sub-processors)
| Service | When | Notes |
|---|---|---|
| Kefilex (Kefilab's legal practice management product) | Only if a firm chooses to connect its own Kefilex, using a key specific to that firm | ClearedOn can ask the firm's Kefilex to create a login for a starter (sending the starter's name, work email address and the Kefilex role the firm chose) and to deactivate a leaver's login. Kefilex never creates administrator accounts this way and accepts only addresses on the firm's own email domain. Kefilab is the firm's processor for both ClearedOn and Kefilex, so this is processing within Kefilab's own services on the firm's instructions (DPA clause 4.5). Kefilex's data is hosted in London, UK (eu-west-2), like ClearedOn's |
[TO CONFIRM: whether Kefilex should be listed among the sub-processors above for transparency, even though it is Kefilab's own service.]
Not a sub-processor
GitHub hosts ClearedOn's source code. It holds no customer data and is not a sub-processor.
DigiCert, Inc. runs the timestamp authority that timestamps the seal on each signed copy ClearedOn stores. It receives only a SHA-256 hash of the seal (a fixed-length fingerprint from which nothing about the document or the people in it can be recovered) and returns a signed time. It receives no personal data and is not a sub-processor. [TO CONFIRM: the solicitor agrees a hash sent for timestamping is not personal data.]
How we tell you about changes
- We give subscribing firms 30 days' notice of any intended addition or replacement of a sub-processor, in the Service or by email to the firm's administrator (DPA clause 4.1).
- During that period a firm may object on reasonable data-protection grounds. If we cannot offer a reasonable alternative within 30 days, the firm may terminate the affected part of the Service (or the subscription) without penalty and receive a refund of fees paid for the period after termination (DPA clause 4.3).
- Each sub-processor is bound by a written contract imposing the same data-protection obligations as our DPA, and we remain fully liable for its performance (DPA clause 4.2).
- If a change involves a transfer outside the UK, we put a valid transfer mechanism and, where required, a transfer risk assessment in place first.
- Every version of this list is kept; the date of the current version is shown at the top.
Questions: Data Protection Lead, [TO CONFIRM: contact mailbox].