ClearedOn Data Processing Agreement
Version 0.3-draft · 10 October 2026 · NOT IN FORCE — for solicitor review
Adapted from the Kefilex Data Processing Agreement v1.3 (14 August 2026). Structured on the recognised model: Annex A — details of processing; Annex B — technical and organisational measures; Annex C — sub-processors. Items marked [TO CONFIRM: …] are open and must be resolved before this DPA is put into force.
This Data Processing Agreement ("DPA") forms part of the ClearedOn Terms of Service between Kefilab, a trading name of Baldev Singh Badesha (a sole trader), of 301 Bath Road, Hounslow, London TW3 3DB, ICO registration ZC207164 [TO CONFIRM: registration current and its description covers ClearedOn] ("Kefilab", the processor), and the subscribing firm ("the Firm", the controller), and applies whenever Kefilab processes personal data on the Firm's behalf in providing the ClearedOn service ("the Service"). Capitalised terms not defined here have the meaning given in the Terms of Service.
Parties and contacts. The controller is the Firm identified at signup — its legal entity name, entity type, company number (where applicable), registered or trading address, and regulator and registration number. [TO CONFIRM: what ClearedOn captures and verifies about the Firm at signup — Kefilex verifies against the regulator's public register.] The Firm can record a compliance contact email and a data protection contact email in the Service. The Firm's data-protection contact is the data protection contact it records there or, if none is recorded, its designated administrator, unless the Firm nominates another contact in writing. The processor is Kefilab, 301 Bath Road, Hounslow, London TW3 3DB; data-protection contact: Data Protection Lead, [TO CONFIRM: contact mailbox]. Kefilab is established in the United Kingdom, so no UK Article 27 representative is required. Kefilab maintains a recorded Article 37 assessment of whether a statutory data protection officer is required and will keep it under review. [TO CONFIRM: the existing Article 37 assessment (8 August 2026) was made for Kefilex only; it must be re-run to cover ClearedOn, which processes criminal-offence data (DBS certificate information) as a core part of the Service.]
1. Roles and scope
1.1 The Firm is the controller of the personal data processed in the Service about its people — its employees, starters and candidates, contractors, agency-supplied workers, individuals who sign on behalf of Agencies, and its own Firm Users — and of the audit log of activity in its workspace. Kefilab is the Firm's processor.
1.2 Kefilab is an independent controller only of: (a) the Firm's own account, contract and billing records, and correspondence with the Firm about the Service; and (b) enquiries made to Kefilab through clearedon.com. These are described in the ClearedOn Privacy Notice.
1.3 "Data Protection Law" means the UK GDPR and the Data Protection Act 2018 ("DPA 2018"), and where applicable the EU GDPR.
2. Details of processing
The subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects are set out in Annex A.
3. Kefilab's obligations as processor
Kefilab shall:
(a) process the personal data only on the Firm's documented instructions (this DPA, the Terms of Service, and the Firm's configuration of the Service — including the people it invites, the documents and evidence it requests, and the retention periods it sets — being those instructions), unless required otherwise by law — in which case Kefilab will inform the Firm unless prohibited;
(b) ensure persons authorised to process the data are bound by confidentiality obligations;
(c) implement the technical and organisational measures described in Annex B, maintaining a level of security appropriate to the risk, taking particular account of the identity documents and criminal-offence data the Service holds;
(d) assist the Firm with data-subject requests (access, erasure, rectification, portability) and with the Firm's obligations under Articles 32–36 UK GDPR, including any data protection impact assessment the Firm carries out for its use of the Service, taking into account the nature of processing. This assistance is provided at no charge. Where a request is manifestly unfounded or excessive, in particular because it is repetitive, Kefilab may charge a reasonable fee reflecting its administrative cost, having first told the Firm and agreed it;
(e) notify the Firm without undue delay after becoming aware of, targeting 24 hours and in any event within 48 hours of confirming, a personal-data breach affecting the Firm's data, with the information reasonably required for the Firm's own regulatory assessment, and keep the Firm updated as the position develops. This leaves the Firm comfortable margin within its own 72-hour clock to the ICO. Reasonable costs of investigating and responding to a breach (including forensics, legal advice and regulatory correspondence) are borne by the party responsible for the breach, subject to clause 10. [TO CONFIRM: a ClearedOn breach-response runbook equivalent to the Kefilex one exists before launch.];
(f) at the Firm's choice, delete or return all personal data at the end of the subscription (clause 9), unless law requires retention;
(g) make available information reasonably necessary to demonstrate compliance with this DPA, and allow for and contribute to audits — satisfied in the first instance by Kefilab's written security documentation, completed questionnaires, and the Firm's own ability to verify the integrity of its audit log in the Service; on-site audits by agreement, at the Firm's cost, no more than annually;
(h) immediately inform the Firm if, in Kefilab's opinion, an instruction from the Firm infringes Data Protection Law, and pause the affected processing until the Firm confirms or withdraws it; and
(i) maintain the records of processing required of a processor by Article 30(2) UK GDPR.
Nothing in this DPA relieves Kefilab of its own responsibilities and liabilities as a processor under Data Protection Law.
3A. The Firm's obligations as controller
Article 28(3) requires this contract to set out the controller's obligations and rights as well as the processor's. The Firm shall:
(a) ensure it has a lawful basis for the personal data it processes in the Service and, where that data falls within Article 9 or Article 10 UK GDPR, an applicable condition for it;
(b) give lawful and accurate instructions — including through its own configuration of the Service, the people it invites, the documents and evidence it requests, the retention periods it sets and the integrations it enables — and ensure those instructions comply with Data Protection Law;
(c) be responsible for the accuracy, quality and legality of the personal data it provides, and for its own transparency obligations to the people on its register and to Agency signatories, including telling them that Kefilab acts as its processor;
(d) manage its own Firm Users' access, including designating administrators, setting roles and permissions (in particular who may view identity documents and DBS information), and removing access promptly when a person leaves; and
(e) respond to data-subject requests forwarded under clause 7, which remain the Firm's to answer.
The Firm has the right to the assistance, information, audit co-operation, notification and deletion provisions set out in clauses 3, 4 and 9.
3B. Criminal-offence data and special-category data
3B.1 DBS certificate information processed in the Service is personal data relating to criminal convictions and offences within Article 10 UK GDPR and section 10 DPA 2018. The Firm confirms that, before it records or uploads such information, it will have (a) a lawful basis under Article 6, (b) a condition in Part 1, 2 or 3 of Schedule 1 DPA 2018 (for example the employment condition in paragraph 1), and (c) where Schedule 1 requires one, an appropriate policy document, and that it will request only the level of check it is legally entitled to request.
3B.2 Kefilab will: (a) store only the DBS information the Firm's configuration asks for; (b) by default, delete any image of a DBS certificate six months after the check, keeping the record that the check took place (the Firm may shorten this period but not disable it); (c) restrict viewing of uploaded evidence to Firm Users holding the relevant permission, and log every view; and (d) not use such information for any purpose other than providing the Service to the Firm.
3B.3 Identity documents (for example passports and driving licences) may incidentally reveal special-category data — a photograph may indicate racial or ethnic origin, or religious belief, and some documents show place of birth or nationality. The Service does not extract, analyse or categorise that information; it stores the document image as evidence of the check only. The Firm will not use the Service to process that information for any other purpose.
4. Sub-processors
4.1 The Firm gives general written authorisation to the sub-processors listed in Annex C. Kefilab will give 30 days' notice of any intended addition or replacement (via the Service or email), during which the Firm may object on reasonable data-protection grounds. An addition or replacement takes effect as an update to Annex C without amending the body of this DPA.
4.2 Where Kefilab engages a sub-processor, it will put in place a written contract imposing the same data-protection obligations as those set out in this DPA, in particular the obligation to provide sufficient guarantees of appropriate technical and organisational measures. Kefilab remains fully liable to the Firm for the performance of each sub-processor's obligations, subject to clause 10.
4.3 If the Firm objects under clause 4.1 and Kefilab cannot within 30 days offer a reasonable alternative that meets the objection, the Firm may terminate the affected part of the Service (or, where the sub-processor is needed for the whole Service, the subscription) without penalty, and Kefilab will refund any fees already paid for the period after termination. Neither party is otherwise liable for the termination.
4.4 Customer-directed integrations. The Firm's own Clio account, and any Google Workspace or Microsoft 365 account the Firm connects when those connectors are available, are the Firm's own systems, engaged by the Firm under its own agreement with the provider, and are not Kefilab sub-processors. In particular:
(a) Clio (detection only). Clio's API does not allow other systems to create Clio users. Where the Firm has connected its Kefilex (clause 4.5), the Service may ask 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. This is a read-only lookup by email address, used to tick off the "set up Clio" task for a starter and to confirm that a leaver's Clio account has been disabled. [TO CONFIRM: whether the Firm's own Clio relationship, reached in this way, needs a sentence in this DPA beyond this clause (for example on where Clio holds the Firm's data).]
(b) Google Workspace and Microsoft 365 connectors are planned, not built. When available, Kefilab will transmit to the provider only the data needed to carry out the account action the Firm instructs (for example a person's name, work email address and role). [TO CONFIRM: these connectors are a future feature; the data fields sent, and whether the solicitor agrees these are customer-directed integrations rather than sub-processors, to be settled before they ship.]
(c) AI assistants (the AI connector). Where a Firm admin switches the AI connector on (Terms clause 8.6), each Firm User whose role allows it may connect an AI assistant (such as Claude, provided by Anthropic, or ChatGPT, provided by OpenAI) under the Firm's own account and agreement with that provider. The provider is engaged by the Firm and acts for the Firm; it is not a Kefilab sub-processor. Kefilab sends it only the data that the connected user's assistant asks for, within the limits below, and only while the connection lasts:
- documents and their versions, firm facts, compliance position holders (name and work email), review dates and document dependencies;
- the compliance calendar (dates, their owners and whether each was done), and counts for a period: how many register entries were opened and closed and whether their deadlines were met, for registers the user's role can read other than personal data breaches and regulatory breaches; supplier reviews and gaps; and, where the user may see people records, how many people are cleared and how many have completed each training course. Never the register entries themselves, concerns, supplier documents or training records;
- where the Firm allows it and the user's role permits, the names, team roles, engagement status and stage of people on the register and which document versions each has acknowledged and when; and the Firm's audit log (actions only, without recorded values);
- never identity, right-to-work, proof-of-address or DBS documents or their details, criminal-offence data, personal email addresses or telephone numbers, signing links, signatures or their technical data, or connector keys. The Service's database refuses these to a connection whatever the user's role.
The Firm is responsible, as controller, for its agreement with the provider (including use of data for model training), for any international transfer that sending data to the provider involves, and for informing the people on its register. Every request made through a connection is logged and visible to the Firm (Annex B). [TO CONFIRM: the solicitor's view that an AI assistant connected by the Firm in this way is a customer-directed integration, consistent with (a) and (b), rather than a Kefilab sub-processor.]
4.5 Kefilex (Kefilab's own service). Kefilex is Kefilab's legal practice management product, for which Kefilab is also the Firm's processor. Where the Firm connects its own Kefilex to the Service with a key specific to the Firm, the Service may send Kefilex a starter's name, work email address and the Kefilex role the Firm chooses, so that Kefilex creates a login for them, and may ask Kefilex to deactivate a leaver's login. This is processing within Kefilab's own services on the Firm's instructions, not an engagement of a third-party sub-processor. Kefilex's data is hosted in London, UK (eu-west-2). Kefilex will never create administrator accounts in this way and accepts only email addresses on the Firm's own email domain. The Firm's Kefilex key is stored encrypted with a master key held only in the server environment. The connection is off unless the Firm connects it. [TO CONFIRM: whether Kefilex should nonetheless be listed in Annex C and the Sub-processor List for transparency, even though it is Kefilab's own service.]
5. International transfers
The personal data on the Firm's register — including identity documents, right-to-work evidence, DBS information, signed documents and the audit log — is stored and processed in the United Kingdom: the database, file storage and application functions run in the London (eu-west-2) region listed in Annex C. The exception is transactional email, addressed below.
Points of detail, stated rather than glossed:
- Static assets only on the CDN. Content cached on Netlify's global network is static application assets — scripts, styles, images. Pages containing the Firm's data are generated on demand by functions in London (eu-west-2) [TO CONFIRM: no edge caching of authenticated pages, checked against response headers]. Requests are routed through Netlify's edge network in transit.
- Transactional email. Email the Service sends (sign-in codes, signing links and codes, reminders, and notifications to Firm Users — access-task digests, alerts that a starter has not responded, and expiry warnings) is delivered by Resend, a US-established processor, which stores email data in the United States. By design, these emails never contain documents or the personal data held on the Firm's register — they carry a link or a code only — with one exception: an email to a Signatory or Agency signatory includes that recipient's own first name. Emails to Firm Users never name the person or the check concerned; they contain only a link to sign in. The personal data disclosed to Resend is the recipient's email address (and, for a Signatory, their first name), delivery metadata and the message itself. [TO CONFIRM: whether any email includes the Firm's name in the subject or body.] Disclosing that data to Resend is a restricted transfer to the US. It is covered by Resend's certification under the UK Extension to the EU–US Data Privacy Framework and, as a fallback safeguard, by the EU Standard Contractual Clauses with the UK Addendum incorporated in Resend's Data Processing Agreement, supported by a transfer risk assessment. [TO CONFIRM: that the signed Resend Data Processing Addendum covers the Resend account used for ClearedOn, and that a ClearedOn transfer risk assessment has been recorded — the Kefilex one (8 August 2026) assumed different email content.]
- US-parented hosting providers. Supabase and Netlify host the Service's data and functions in London, but are companies established in the United States. [TO CONFIRM: each provider's position on any remote access to data from outside the UK (for example by support or engineering personnel), and the transfer mechanism in its data processing terms (UK Extension to the EU–US Data Privacy Framework certification, and/or EU SCCs with the UK Addendum or the UK IDTA). The Kefilex documents treat both providers as UK-hosted and do not address this point; it should be stated here once confirmed.]
If a sub-processor requires a transfer outside the UK, Kefilab will put in place a valid transfer mechanism (a UK adequacy regulation ("data bridge"), the UK IDTA, or the EU SCCs with the UK Addendum) and complete a transfer risk assessment where required before any transfer, and notify the Firm under clause 4.
Transfers made by the Firm. Where the Firm engages workers through an Agency outside the United Kingdom, or otherwise gives people outside the UK access to its systems or data, any restricted transfer that results is made by the Firm as exporter, and the transfer mechanism and transfer risk assessment are the Firm's responsibility. The Service can be used to collect the Agency's signature to documents such as an IDTA or UK Addendum, but Kefilab is not a party to those transfers and does not advise on them. A Signatory opening a signing link while outside the UK is not a transfer by Kefilab.
6. Confidentiality and Kefilab access
6.1 Kefilab acknowledges that the Firm's data is confidential and includes identity documents and criminal-offence data.
6.2 No standing access. Kefilab personnel have no standing access to the Firm's data. Access for support is possible only through a support session that a Kefilab platform administrator must open on the Firm's workspace alone, stating a reason that is visible to the Firm; the session is read-only, lasts at most 60 minutes, cannot be extended or back-dated, and is recorded in the Firm's audit log. Identity documents are never visible during a support session. Kefilab personnel can read the Firm's audit log only during such a session. [TO CONFIRM: whether a support session can open other uploaded evidence files — in particular DBS certificate images and right-to-work copies — or is limited to records and metadata.]
6.3 Kefilab will refer any third-party demand for the Firm's data to the Firm unless legally prohibited, and will not voluntarily disclose it.
7. Data-subject requests
7.1 Kefilab will forward to the Firm, without undue delay, any data-subject request it receives that relates to the Firm's data, and will not respond directly except to redirect the requester to the Firm. This applies equally to requests from Signatories and Agency signatories, who are told in the ClearedOn Privacy Notice that the Firm is their controller.
7.2 The Service gives the Firm the means to respond itself — including viewing and exporting a person's record, evidence pack and signed documents, and correcting or deleting records — and Kefilab will assist under clause 3(d) where those means are not enough.
8. Security
The measures in Annex B (summarised from the ClearedOn Security Overview, provided with this DPA) apply, including per-firm isolation enforced in the database and the application, database guards over the compliance record, per-firm encryption of uploaded files, permission-checked and logged access to evidence, a tamper-evident audit log, mandatory two-factor sign-in for Firm Users, no standing Kefilab access, a fault ledger designed never to hold the Firm's register data, and UK data residency subject only to the clause 5 email transfer.
9. Return, deletion and retention
9.1 During the subscription, the Service applies the default retention periods in Annex A. The Firm may shorten them but not disable them. Each deletion is logged, and the record that a check took place is kept after the underlying document or image is deleted.
9.2 At any time, the Firm can export its reports (CSV), evidence packs (PDF) and signed documents from the Service.
9.3 On termination or expiry, the Firm has a 90-day window in which Kefilab will, on request, provide a full export of the Firm's data, free of charge and in machine-readable form. After that window — or earlier, on the Firm's written request — Kefilab deletes the Firm's personal data from production systems, with backup copies expiring on backup rotation within 30 days [TO CONFIRM: the ClearedOn backup regime (frequency, retention and point-in-time recovery window) so that this period is accurate], unless retention is required by law. Kefilab's own controller records (billing, accounting) are retained per statutory requirements. Kefilab will provide written confirmation of deletion on the Firm's request. Encrypted files whose per-firm data key is destroyed cannot be recovered. [TO CONFIRM: whether destruction of the per-firm data key forms part of the deletion process; remove this sentence if not.]
9.4 Audit log after termination. [TO CONFIRM — open policy point: the product design keeps the audit log for the life of the account plus six years. Article 28(3)(g) requires deletion or return at the end of the services unless law requires storage. Options for the solicitor: (a) the audit log is returned in the export and deleted with everything else; (b) Kefilab retains it as a controller in its own right for establishing or defending legal claims, disclosed in the Privacy Notice; or (c) some other basis. This draft assumes (a) until decided.]
10. Liability and order of precedence
Liability under this DPA is subject to the limitations and exclusions in the Terms of Service (including the data-protection cap in clause 13.5 of those terms). If this DPA conflicts with the Terms of Service on data-protection matters, this DPA prevails.
Annex A — Details of processing
Subject matter: provision of the ClearedOn staff compliance and access register to the Firm.
Purpose: to let the Firm record, for every person who works for or through it, what they agreed to, what checks and training were done, and what access was given; to collect signatures to the Firm's documents from its people and from Agencies; and to produce evidence packs and reports for the Firm's Regulator(s), its obligations under regulations 21 and 24 of MLR 2017, and the ICO; and to keep the Firm's registers (complaints, data protection complaints, personal data breaches, subject access requests, regulatory breaches, gifts and hospitality, undertakings, file reviews and conflicts), with their deadlines; and to keep the Firm's register of suppliers, their documents and reviews.
Duration: the subscription term plus the 90-day post-termination export window (clause 9), subject to clause 9.4.
Nature of processing: hosting and storage; encryption of uploaded files; display to authorised Firm Users; sending signing links, one-time codes, reminders and Firm User notifications by email (including, where the Firm chooses, sending a document only on a person's start date); displaying the Firm's logo to its Signatories on their signing pages; recording simple electronic signatures and producing executed documents with signature certificates; tracking checks, training and access against the Firm's configured requirements, including after day one (expiring checks, practising certificates, training and documents asked for again on each document's cadence), and telling the Firm's COLP when someone stops being cleared; where the Firm allows it, letting its people record training and log complaints, gifts and undertakings themselves in My ClearedOn; where the Firm connects them, the Kefilex and Clio connectors in clauses 4.4 and 4.5; where the Firm switches it on, the AI connector in clause 4.4(c), including keeping documents written in the Service as text with the Firm's recorded facts (such as its address and its compliance position holders) and rendering them to PDF; keeping the Firm's registers and working out their deadlines (using the public GOV.UK bank holiday list), with deadline reminders and breach alerts by email that carry only the register, reference and deadline; reporting and export; scheduled deletion under the retention defaults; audit logging.
Categories of data subjects:
- the Firm's employees, and starters and candidates in the Firm's onboarding process;
- contractors and consultants engaged by the Firm;
- agency-supplied workers, including workers based outside the United Kingdom;
- individuals who sign documents on behalf of Agencies;
- the Firm's own Firm Users (administrators, compliance officers, managers);
- people who make a complaint or a subject access request to the Firm (who may be its clients or former clients), people whose personal data is affected by a breach the Firm records, and people named in the Firm's other registers (for example the giver or recipient of a gift, the recipient of an undertaking, or the parties to a conflict);
- contacts at the Firm's suppliers;
- people who report a concern to the Firm through the Service (named or anonymous), and anyone named in a concern.
Categories of personal data:
- identity and contact details — name, email address, telephone number, postal address, role and job title, start and leaving dates, employer or Agency;
- identity documents — images and details of passports, identity cards, driving licences and similar documents (which may incidentally reveal special-category data: see clause 3B.3);
- right-to-work evidence — document images and details, share codes or check outcomes as recorded by the Firm, and expiry dates;
- proof of address documents;
- DBS certificate information (criminal-offence data — Article 10 UK GDPR): as configured by the Firm, which may include the level of check, certificate number, issue date, the outcome as recorded by the Firm, and an image of the certificate;
- professional details — practising certificates and registration numbers, qualifications, and training and AML training certificates and completion records (including training people record for themselves and whether the Firm accepted it), and the Firm's yearly check of each solicitor on the SRA's public register (the SRA number, the date, the result and who checked);
- standing — whether each person working is still cleared, worked out from the records above when it is shown (it is not stored and never changes anyone's access by itself);
- documents agreed and signatures — the documents presented, the fact, time and method of agreement, one-time-code verification events, SHA-256 document fingerprints, executed PDFs and signature certificates;
- access records — which systems and access the Firm recorded as given to or removed from each person and, where the Firm uses the connectors, the Kefilex role chosen for a person's login and whether a work email address is an enabled Clio user;
- register records — what the Firm records in its registers: for example the complainant's or requester's name, a summary, the outcome, the categories of data and number of people affected by a breach, the risk decision, any ICO, SRA or Legal Ombudsman reference, a gift's giver, recipient and value, an undertaking's recipient and terms, a file review's findings, the parties to a conflict, notes, and files the Firm attaches. The Firm decides what it writes; a breach record may describe special-category or criminal-offence data that was affected;
- concern reports — what a person reports to the Firm in confidence (whistleblowing, harassment, a data breach, client money or something else) and the messages on the case, sealed with the Firm's data key before storage and readable only by the people on the case's access list; they may describe special-category or criminal-offence data. Anonymous reports are stored with no IP address or device details;
- supplier records — the Firm's suppliers, the contact name and email it records for each, what personal data each handles and where, and the contracts, data processing terms, certificates and reviews the Firm keeps on file (which may name individuals);
- Firm settings — the compliance and data protection contact email addresses the Firm records, and each Firm User's choice of which automatic emails to receive;
- technical data — IP addresses, device and browser information, timestamps, and sign-in and session events; and
- the audit log of actions in the Firm's workspace, including views, exports and sign-ins; and, where the Firm uses the AI connector, a log of every request made through each connection (who made the connection, which assistant, the request, a fingerprint of the answer and the records it touched, and the outcome).
Special-category and criminal-offence data: see clause 3B. DBS certificate information is criminal-offence data and is processed only as the Firm configures. Special-category data is not sought, but may be visible incidentally in identity-document images, and a breach record may describe special-category or criminal-offence data affected by the breach. Breach records are visible only to the Firm's data protection lead, its COLP and the Firm Users who own or handle them.
Retention defaults (applied automatically; the Firm may shorten but not disable them; each deletion is logged and the record that the check happened is kept):
Data Default deletion Identity document images 6 months after the check DBS certificate images 6 months after the check Right-to-work copies 2 years after employment or engagement ends Personnel and training records 6 years after employment or engagement ends Records of candidates withdrawn or not hired 6 months Register records and their files Undertakings and regulatory breaches: 15 years after the entry is closed or withdrawn; every other register, data breaches included: 6 years (the reference, dates and deadline record are kept); fixed periods the Firm cannot change yet Supplier records, documents and reviews 6 years after the supplier ends (its name and dates are kept) Concern reports and messages 6 years after the case closes (the reference, kind, dates and outcome category are kept) Audit log Life of the account plus 6 years — subject to clause 9.4
Annex B — Technical and organisational measures
These measures are described in more detail in the ClearedOn Security Overview, which is provided with this DPA. They are:
- UK data residency. Database, authentication and file storage on Supabase in London (eu-west-2); application functions on Netlify in London (eu-west-2). Static application assets only on Netlify's global CDN. One disclosed exception: transactional email (clause 5).
- Per-firm isolation and database protection. Row-level security is enabled and forced on every table, separating data by firm, and every page and action is also permission-checked. Database guards additionally stop even the Firm's own users from directly altering the compliance record (marking a person cleared, a document signed or an Agency approved, or changing a signing link); those changes happen only through the Service's own controlled steps. Permission to change a record does not by itself grant permission to read it. The database's automatic web API (the Supabase Data API) is switched off; the browser never talks to the database directly. Automated isolation tests run on every change to the code and fail the change if any firm could see or change another firm's data, if any table lacks row-level security, or if access controls are weakened.
- Encryption of uploaded files and connector keys. Identity and evidence files are encrypted with a per-firm AES-256-GCM data key. Each firm's data key is itself encrypted ("wrapped") by a master key held only in the server environment, never in the database. A Firm's Kefilex connector key is likewise stored encrypted with a master key held only in the server environment.
- Controlled access to evidence. Every view of an uploaded file is permission-checked and logged.
- Signature integrity. Signed documents carry SHA-256 fingerprints, and an executed PDF with a signature certificate is produced for each signing.
- Tamper-evident audit log. An append-only, hash-chained audit log records every action, including reads, exports and sign-ins. The Firm can verify the chain itself.
- Strong sign-in. Firm User accounts exist only by invitation; there is no public sign-up. Firm Users sign in with a one-time code sent by email plus a mandatory authenticator-app (TOTP) second factor. Sign-in attempts and code entry are rate-limited. Sessions end after 2 hours of inactivity and at most 12 hours after sign-in. A Firm User can reset their own authenticator, which signs them out. The firm app (app.clearedon.com) and Kefilab's admin area (admin.clearedon.com) have separate sign-ins. Signatories have no account; they act through emailed links confirmed by emailed one-time codes.
- No standing Kefilab access. Support access requires a reason-stated, read-only support session on one firm, opened by a platform administrator, visible to the Firm, ending after at most 60 minutes, which cannot be extended or back-dated, and recorded in the Firm's audit log. Identity documents are never visible during it, and Kefilab staff can read the Firm's audit log only during such a session (clause 6.2).
- Encryption in transit and web hardening. TLS on every connection and HSTS; a strict Content Security Policy with a fresh random value (nonce) for each page load, so that only the Service's own scripts can run; and framing of the Service by other sites blocked.
- Data-minimised email. Emails never contain documents or the personal data held on the register — links and codes only, plus the recipient's own first name in emails to Signatories. Emails to Firm Users never name the person or the check. Each Firm User can switch off the automatic emails sent to them.
- Retention enforcement. Scheduled deletion under the Annex A defaults, with every deletion logged.
- Fault ledger. Genuine faults (for example a failed background step, a payment event that could not be applied, a connector failure, or an unexpected error when saving) are recorded in a fault ledger that only Kefilab staff can see, and the first sighting of a new fault emails Kefilab's administrators. Fault records hold technical codes only and are designed never to hold the Firm's register data (email addresses and database row values are stripped).
- AI connector controls. The AI connector is off until a Firm admin switches it on. A connection is made only after the Firm User signs in in full (email code and authenticator), chooses one firm and what to allow (never more than their own role), and is limited to the period the Firm admin sets (at most 90 days). It uses the OAuth 2.1 authorization code flow with PKCE; tokens are random, stored only as SHA-256 hashes, valid only for the Service's connector address, and checked in the database on every request, so ending a connection, disabling a login, removing the permission or switching the connector off takes effect immediately. A refresh token works once; reusing one ends the connection. In the database a connection is pinned to its one firm, holds at most the permissions to read people records, read the audit log and write drafts, and is refused identity and evidence records, signing links, signatures, billing and settings outright. It can never publish a document version: publishing is done only by a person with permission to publish, through one controlled step. Requests are rate-limited, and Firm admins are emailed if a connection reads an unusual number of people records in a day. Every request is logged and chained into the tamper-evident audit log, and every change it makes is tagged with the request.
- Security review. An internal security review was carried out in October 2026 and its findings addressed. No independent penetration test has been carried out.
[TO CONFIRM before this Annex is finalised: encryption at rest of the database (provider-managed); the backup regime; and any additional organisational measures (staff confidentiality terms, breach-response runbook, access reviews). None of these is stated above because it is not yet confirmed for ClearedOn.]
Annex C — Sub-processors
| Sub-processor | Purpose | Personal data | Location | Transfer safeguard |
|---|---|---|---|---|
| Supabase, Inc. | Database, authentication, file storage | All Service data, including encrypted evidence files | Data hosted in London, UK (eu-west-2); company established in the USA | No transfer in normal operation (UK-hosted). [TO CONFIRM: mechanism for any remote access from the US — see clause 5] |
| Netlify, Inc. | Application hosting and serverless functions | Data in transit through functions; no data stored | Functions in London (eu-west-2); global edge/CDN serves static assets only; company established in the USA | As for Supabase. [TO CONFIRM — see clause 5] |
| Resend (Plus Five Five, Inc.) | Transactional email — sign-in codes, signing links and codes, reminders, Firm User notifications | Recipient email address, delivery metadata, message (no documents or register data, other than a Signatory's own first name in emails to them) | USA | Restricted transfer: UK Extension to the EU–US Data Privacy Framework, with EU SCCs + UK Addendum fallback; transfer risk assessment — see clause 5 |
| Stripe (Stripe Payments Europe, Ltd / Stripe, Inc.) | Billing of the Firm | Firm billing contact and payment details only — no data about the Firm's people | [TO CONFIRM: contracting Stripe entity and data location] | Kefilab's own controller purpose; listed for completeness |
Customer-directed integrations (not sub-processors — clause 4.4): Clio, the Firm's own system, reached only through the Firm's Kefilex and the Firm's own Clio connection, for a read-only check of whether a work email address is an enabled Clio user; and Google (Google Workspace) and Microsoft (Microsoft 365), only if and when the Firm itself connects them for account provisioning — planned, and not available at the date of this draft; and the AI assistant each Firm User connects through the AI connector (for example Anthropic for Claude, OpenAI for ChatGPT), under the Firm's own agreement with that provider, only if the Firm switches the connector on (clause 4.4(c)).
Kefilab's own service (not a third-party sub-processor — clause 4.5): Kefilex, only if the Firm connects it. Whether it should be listed in the table above for transparency is open (see clause 4.5).
Additions and replacements are notified under clause 4.1 and take effect as updates to this Annex.
Signed by incorporation into the ClearedOn Terms of Service, or on request as a countersigned standalone document.