ClearedOn Security Overview
Version 0.3-draft · 10 October 2026 · NOT IN FORCE — for solicitor review
For procurement, IT and compliance reviewers. Company-authored; it states only measures that are built. Questions to [TO CONFIRM: contact mailbox].
ClearedOn is a staff compliance and access register for regulated firms, built and operated by Kefilab (a trading name of Baldev Singh Badesha), 301 Bath Road, Hounslow, London TW3 3DB, registered with the UK Information Commissioner's Office — registration ZC207164 [TO CONFIRM: registration covers ClearedOn]. For every person who works for or through a firm, it records what they agreed to, what checks and training were done, and what access they were given, and produces evidence for the firm's regulators.
Because the Service holds identity documents, right-to-work evidence and DBS certificate information, it is designed on the assumption that everything in it is sensitive.
Addresses
- clearedon.com — the public website and legal pages.
- app.clearedon.com — the firm app, and the signing links that starters and agency signatories receive.
- admin.clearedon.com — Kefilab's own admin area.
The firm app and the admin area have separate sign-ins.
Roles
- The firm is the controller of its people's data. Kefilab is the processor, under a UK GDPR Article 28 Data Processing Agreement that forms part of the subscription.
- People who sign documents or provide evidence (starters, employees, contractors, agency workers, agency signatories) have no account. They act through emailed links confirmed with emailed one-time codes, or through My ClearedOn at app.clearedon.com/me: they enter the email address their firm has for them and a one-time code sent to it. A My ClearedOn session lasts at most 12 hours and ends after 2 hours of inactivity; only a hash of the code and of the session is stored. After someone's last day they can still sign in for 30 days, read only: they can read and download what they signed, and the database refuses anything they try to sign, upload or send. After that they cannot sign in. It shows only that person's own documents, checks and training, at one firm at a time. Where the firm allows it, they can also log a client complaint, a gift or an undertaking, and record training with a certificate; they then see only the reference, status and dates of what they sent, never the firm's notes.
Data residency — UK
- Database, authentication and file storage: Supabase, London (eu-west-2).
- Application and serverless functions: Netlify, London (eu-west-2). Netlify's global edge network serves the static application files (scripts, styles, images).
- The one exception is transactional email (sign-in codes, links and notifications), delivered by Resend, a US-established provider — a restricted transfer safeguarded by Resend's certification under the UK Extension to the EU–US Data Privacy Framework, with SCCs + UK Addendum fallback. ClearedOn emails never contain documents or the personal data held on the register — links and codes only. Emails to a starter or agency signatory also contain that person's own first name; emails to firm staff never name the person or the check, and contain only a link to sign in.
Firm isolation and database protection
- Row-level security is enabled and forced on every table, separating data by firm, in the database itself.
- Database guards protect the compliance record. Even a firm's own users cannot directly mark a person cleared, mark a document signed, approve an agency or change a signing link; those changes happen only through ClearedOn's own controlled steps.
- The database's automatic web API (Supabase Data API) is switched off. The browser never talks to the database directly.
- Permission to change a record does not by itself grant permission to read it.
- Permission checks on every page and action, on top of the database rules, decide what each user may see and do within their own firm.
- Automated isolation tests run on every change to the code. They 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
- Uploaded identity and evidence files are encrypted with a per-firm AES-256-GCM data key. Each firm's key is itself encrypted ("wrapped") by a master key held only in the server environment — never in the database. Access to the database alone does not unlock the file keys.
- Connector keys: a firm's Kefilex connector key is stored encrypted with a master key held only in the server environment.
- In transit: TLS on every connection, with HSTS.
- In the browser: a strict Content Security Policy with a fresh random value (nonce) for every page load, so that only ClearedOn's own scripts can run; and framing is blocked, so other sites cannot embed ClearedOn's pages.
- [TO CONFIRM: encryption at rest of the database and backups (provider-managed) — not stated until confirmed for ClearedOn.]
Access control
- No public sign-up. Firm user accounts exist only by invitation.
- Firm users sign in with a one-time code sent by email plus a mandatory authenticator-app (TOTP) second factor. Two-factor cannot be switched off. Users can reset their own authenticator, which signs them out.
- Sign-in attempts and code entry are rate-limited.
- Sessions end after 2 hours of inactivity, and at most 12 hours after sign-in.
- Firm users have roles and permissions set by the firm's administrator. Every view of an uploaded file is permission-checked and logged.
- Kefilab staff have no standing access to firm data. To give support, a Kefilab platform administrator must open a support session on one firm: the reason is visible to the firm, the session is read-only, it ends after at most 60 minutes and cannot be extended or back-dated, and it is recorded in the firm's audit log. Identity documents are never visible during a support session. Kefilab staff can read a firm's audit log only during such a session.
Connectors
Connectors are the firm's choice and are off unless the firm connects them.
- Kefilex (Kefilab's own legal practice management product). With a firm-specific key, ClearedOn can ask the firm's Kefilex to create a login for a starter (sending name, work email and the chosen Kefilex role) 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. The key is stored encrypted (see Encryption).
- Clio — detection only. Clio's API cannot create users. ClearedOn asks the firm's Kefilex, which asks the firm's Clio through the firm's own Clio connection, whether a given work email 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.
- Microsoft 365 and Google Workspace connectors are planned, not built.
AI connector
The firm can let its people connect ClearedOn to their own AI assistant (Claude, ChatGPT) as an MCP connector. The assistant runs on the firm's own subscription with its provider; ClearedOn holds no AI model keys and sends nothing to an AI provider unless a connected person's assistant asks.
- Off until a firm admin switches it on, accepting a disclosure that is recorded, and only after the firm has recorded its data protection impact assessment decision (done, with its date, or not needed, with the reason). ClearedOn records that decision; it does not read the assessment. Switching it off ends every connection at once.
- Firm admins are emailed when someone connects an assistant: who, which assistant, what it may do, and whether its provider is in the firm's supplier register. By default only Claude and ChatGPT may connect, recognised by where they send people back, not by the name they give.
- Connecting needs a full sign-in (email code and authenticator). The person chooses one firm and what to allow, never more than their own role. Kefilab accounts cannot connect.
- OAuth 2.1 authorization code flow with PKCE (S256). Access tokens last an hour; refresh tokens work once (reusing one ends the connection) and stop at the firm's limit, at most 90 days. Tokens are random, stored only as SHA-256 hashes, valid only for ClearedOn's connector address, and checked in the database on every request: ending a connection, disabling a login, removing the permission or switching the connector off takes effect immediately.
- Enforced in the database, not only in the app. A connection is pinned to its one firm (even for someone who belongs to several). It holds at most three permissions (read people records, read the audit log, write drafts), each only if granted, and is refused outright, by the database, identity and evidence records, signing links, signatures, billing and settings. It can create drafts and suggestions only: it cannot publish a document version, decide whether a change is material, record a review, change who receives a document, add or change a compliance date, or touch people on the register. Calendar dates and supplier review notes it suggests wait for a person with that permission to accept them.
- Every request is logged: who made the connection, which assistant, the request, a fingerprint of exactly what was returned and which records it touched, and the outcome. Each is chained into the tamper-evident audit log, and every change a request makes is tagged with it. Full answers to read requests are kept only if the firm opts in (up to 90 days).
- Rate limits per connection and per firm; firm admins are emailed if a connection reads an unusual number of people records in a day.
Documents and approval
- Documents can be uploaded files or written in ClearedOn as text that uses the firm's recorded facts (address, office hours, insurer, compliance position holders). Written documents are rendered to PDF deterministically: the same text and facts always give the same file and SHA-256 fingerprint, and that file is what people sign.
- Publishing is one controlled step in the database, open only to people with permission to publish. A draft can be sent to a named approver; while it waits it cannot be changed. The person publishing decides whether the change is material (people re-acknowledge it) or minor. A published version can never be changed or deleted.
- Changing a firm fact re-drafts every written document that uses it and sends each to its review owner; nothing is published by the change itself. A material change to a document flags the documents that refer to it for review.
Notifications
Each firm user can switch off the automatic emails ClearedOn sends them (access-task digest, people-not-responding alerts, expiry warnings, compliance dates, register deadlines, people no longer cleared). These emails never name the person or the check — only a link to sign in. Register emails carry the register, its reference (such as BRE-2026-004) and the deadline, never what happened or who is involved.
Calendar links
- A firm user can make a private calendar link so their compliance dates appear in Google Calendar, Outlook or Apple Calendar. The link is random and shown once; ClearedOn stores only its SHA-256 hash.
- The feed contains dates and titles only, never a person's name or details, because the calendar provider's servers fetch and keep it. Each entry links back to ClearedOn, where the detail is behind sign-in.
- Each fetch is read as that user, read-only and limited to that one firm, so the feed shows only what they could see in the app. It stops working at once when the user resets or stops it, a user admin stops it, the user is disabled, or the firm is suspended. Fetches are rate limited.
People after day one
- ClearedOn shows whether each person working is still cleared: expiring checks, the yearly SRA register check of practising certificates, required training and documents due again. It is worked out when shown, not stored.
- Nothing happens automatically when someone stops being cleared: their access and engagement stay as they are, and the COLP is emailed (no name or reason in the email) so a person decides.
- Nobody checks their own record: the database refuses someone accepting their own training or confirming their own practising certificate.
Concerns (speaking up)
- Where a firm switches it on (it is off until the firm does), staff can report a concern from My ClearedOn in their own name, or, for the kinds the firm allows, anonymously from a public page that is not linked to their sign-in and stores no IP address or device details with the report. An anonymous reporter gets a follow-up key; only its hash is stored.
- The report and every message are sealed with the firm's data key on the server before storage (AES-256-GCM), so a copy of the database or a backup alone does not reveal them.
- A case is open only to the people on its access list: the person it was routed to and anyone they bring in with a recorded reason. No role sees every concern; Kefilab support sessions and the AI connector are refused. If the reporter chooses the alternate route, the usual recipient is shut out of the case and never notified.
- Each case keeps its own hash-chained log. The firm's audit log records once a day only that case logs changed, with a count and a fingerprint, never which case.
- The places anyone can go outside the firm (the SRA, the ICO and Protect) are always shown on the form.
- Six years after a case closes, its text and messages are deleted; the reference, kind, dates and outcome category are kept.
Registers
- A firm keeps its complaints, data protection complaints, personal data breaches, subject access requests, regulatory breaches, gifts and hospitality, undertakings, file reviews and conflicts in ClearedOn. Each entry's deadlines start from when it was received (or, for a breach, when the firm became aware), counted in working days and ICO months using the GOV.UK bank holidays for the firm's part of the UK. ClearedOn fetches that public list weekly; nothing is sent to GOV.UK.
- A deadline stops only when someone records it as done (with the time) or not needed (with a reason). Each deadline keeps the rule it started with, so a later change to the firm's settings never rewrites an old record.
- Personal data breaches are restricted to the firm's data protection lead, its COLP, and whoever owns or handles the breach; regulatory breaches to its COLP, its COFA, and whoever owns or handles them. Other registers need the view registers permission.
- Register content is never read through the AI connector. It can read counts for a period (how many were opened and closed, and whether deadlines were met), and only for registers the person's own role can read that are not restricted: never personal data breaches, regulatory breaches or concerns. A Kefilab support session can read the firm-visible registers but never a personal data breach or a regulatory breach, and cannot change anything.
- The permanent audit log records register changes without their content: who did what and when, the reference and status, and a fingerprint of the row. The detail is kept in the entry's own append-only timeline, visible only to people who may see the entry.
- Files attached to an entry are held in a private storage bucket and opened only through ClearedOn, which records each view.
- Once an entry has been closed or withdrawn for its register's period (15 years for undertakings and regulatory breaches, six years for every other register, data breaches included), the daily job deletes its files, details, notes and timeline. The reference, dates, status and the record of each deadline (when it was due and when it was met) are kept, and the deletion is logged in the audit chain.
Suppliers
- A firm keeps its supplier and outsourcing register in ClearedOn: what each supplier does, what personal data it handles and where, the transfer safeguard, and whether it supports a critical function.
- The supplier list is visible to everyone at the firm. Contracts, data processing terms and certificates are visible only to people who manage suppliers or view the registers, are never read through the AI connector, and are held in a private storage bucket, opened only through ClearedOn, which records each view.
- Each supplier's review is a date on the compliance calendar, and is marked done only when a review is recorded on the supplier's page. Reviews are append-only until the supplier's content is deleted, six years after it ends.
Signatures and evidence
- Signers use a simple electronic signature confirmed by an emailed one-time code (a signing link or My ClearedOn), or, for a firm user who is also on the register, by their full sign-in.
- A policy is acknowledged ("I have read and understood this"); a contract or undertaking is agreed to, and can be declined. Each signature records which, with the exact wording shown.
- A firm countersigns with a typed name and a confirmation that the person signs for the firm with authority to do so, recorded like any other signature; once a firm names its authorised signatories, only they can countersign. A second executed copy carries both certificates; the signer's own copy is kept unchanged.
- Deeds are never signed electronically in ClearedOn: a deed needs a witness, so a document marked as a deed is not sent for e-signature, and the firm records the date it was executed and witnessed outside ClearedOn.
- Nobody approves their own exceptions: the database refuses a firm user accepting, waiving or recording their own checks, countersigning their own document, recording their own access or moving their own deadline.
- Each signed document carries a SHA-256 fingerprint, and an executed PDF with a signature certificate is produced.
- Every executed and countersigned copy ClearedOn stores is sealed: a PAdES digital signature (ETSI.CAdES.detached) with ClearedOn's document-sealing certificate, and a timestamp from DigiCert's timestamp authority, which receives only a hash. Anyone can open the PDF in a PDF reader and see that it is unchanged since ClearedOn issued it; the certificate's fingerprint is published below. If the timestamp authority cannot be reached, the copy is sealed at once and the timestamp is added within the hour, stored as a second file; the first copy is never replaced. The certificate is ClearedOn's own (readers show the signer as not yet trusted unless they trust it); its private key is stored encrypted with the master key and used only by the server, and is never shown, even to Kefilab's administrators.
- Firms can export reports (CSV), evidence packs (PDF) and signed documents at any time.
- The firm compliance pack (a ZIP of the annual review, reports and evidence files, for an auditor or an SRA visit) holds only what the person exporting may see, and never concerns or identity documents. It is stored in a private storage bucket for at most a day, served by a five-minute signed link, recorded in the audit log with its SHA-256 fingerprint, and then deleted.
Audit log — tamper-evident
- An append-only, hash-chained audit log records every action, including reads, exports and sign-ins.
- Because each entry is chained to the one before it, alteration or deletion of an entry is detectable. The firm can verify the chain itself from within the Service.
- Register entries are logged without their content; see Registers.
Fault ledger
- Genuine faults — a failed background step, a payment event that could not be applied, a connector failure, an unexpected error when saving — are recorded in a fault ledger that only Kefilab staff can see.
- The first sighting of a new fault emails Kefilab's administrators.
- Fault records hold technical codes only. They are designed never to hold a firm's register data: email addresses and database row values are stripped before a fault is recorded.
Data lifecycle
Retention defaults are built in. A firm can shorten them but cannot switch them off. Every deletion is logged, and the record that a check took place is kept.
| Data | Default deletion |
|---|---|
| Identity document and DBS certificate images | 6 months after the check |
| Right-to-work copies | 2 years after employment ends |
| Personnel and training records | 6 years after employment ends |
| Candidates withdrawn or not hired | 6 months |
| Register entries (complaints, breaches, subject access requests, undertakings and the rest) 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; firms cannot change them yet) |
| Supplier documents, reviews and contact details | 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 [TO CONFIRM: post-termination treatment — see DPA clause 9.4] |
On cancellation, the firm has a 90-day export window, after which its data is deleted from production systems, with backups expiring on rotation [TO CONFIRM: backup regime].
Sub-processors
Supabase (London) · Netlify (London functions; static assets on global CDN) · Resend (transactional email, US — restricted transfer safeguarded as above) · Stripe (billing of the firm only; no staff data). Kefilex is Kefilab's own service, used only if the firm connects it; Clio is the firm's own system, reached through the firm's Kefilex for a read-only lookup. Google and Microsoft only if and when a firm connects its own account for provisioning (planned, at the firm's choice). Thirty days' notice of changes, with a right to object — see the ClearedOn Sub-processor List and DPA.
What we have not yet done
We state these plainly so reviewers do not have to ask:
The AI connector has been tested against ClearedOn's own test suite and a local OAuth client; it has not yet been certified or listed by Anthropic or OpenAI.
An internal security review was carried out in October 2026 and its findings addressed. No independent penetration test has yet been carried out. [TO CONFIRM: whether one is planned, and by when.]
No Cyber Essentials or other certification is held. [TO CONFIRM: whether Cyber Essentials is planned.]
[TO CONFIRM: any other gaps to disclose — for example backup and point-in-time recovery, a public status page, and a formal breach-response runbook for ClearedOn.]