Security

Tearline is built on public UK register data, not your desk’s premium licences or its confidential material. This page states what is true today and what is still being built, with nothing said in the present tense unless it is.

Where the data comes from

We are building our own store of UK public-register data: Companies House accounts, charges, officers and PSCs, used under the Open Government Licence. We never resell premium vendor data, and no vendor licence is needed to use Tearline.

If your desk wants its own premium data next to ours, an optional connector is on the roadmap. It is never the model Tearline runs on.

What is sent to a model provider

Public Companies House filings are sent to the Anthropic API to be read. Anthropic is a sub-processor for public filings only. Client documents and tips are never sent to Anthropic or to any other model provider.

The MNPI wall

What the platform learns is how desks work, never what any one desk knows. The shared plane it learns from is de-identified by construction: it can hold only normalised labels, concept keys, one-way hashed tenant identifiers and counts, never a figure and never a raw tenant id.

On the roadmap: there is no confidential-tip intake in the product today, so the wall has not yet been tested against the thing it exists to stop. The design has no toggle to switch it off and no anonymised exception, but it has not yet been exercised against a real tip.

Tenant isolation

On the roadmap. Row-level security is written and forced on 14 tenant tables, and a non-owner database role is defined for it. It has not yet run against a production database. This becomes a present-tense claim once the two-tenant isolation check has passed in production.

Training

No model is trained on client data today. The contractual form of that commitment, in a signed agreement, is being drafted and is not yet in place.

Compliance posture

No compliance certification exists yet. SOC 2 is on the roadmap, ahead of the first enterprise renewals: no audit has started and no auditor is engaged. We are built to be examined, not to avoid it.

Questions

For a security or data-protection question ahead of a pilot, use the design-partner request form and say what you need. We will follow up from there.