Contact Us

AN APPLICATION OF ORMAS

Certified Deletion

THE QUESTION IT ANSWERS

What data is in here, and can I remove it?

01

The problem

GDPR Article 17 is enforced. A data licence terminates. A contributor requests removal. A regulator asks exactly what data is in your model. Currently, the only legally compliant answer is to retrain the model from scratch, costing $100,000–$500,000 per incident.

02

What it delivers

Routes the memorisable portion of each source's training signal into named, bounded, deletable structures. Removing the specific structure cleanly removes the source-specific capacity. Hands the requester a cryptographically signed deletion certificate alongside a mathematically bounded statement of residual influence.

03

Who it is for

A fit for

  • Any institution that trains on data it does not own outright and carries a strict deletion obligation

Funded via compliance budgets.

04

How it works

Certified Deletion is built from 4 of the six capabilities of the ORMAS architecture. Each is a property of how the network trains, not a tool bolted on afterwards.

  1. 01ACCOUNTEmit a bounded, timestamped, causally attributed record of every modification the network made to itself.
  2. 02DETECTIdentify which samples are damaging which component, and separate mislabelled from hard-but-correct.
  3. 03ISOLATEAllocate dedicated capacity bound to a named sample set, under a bound, with the binding recorded.
  4. 04SUPPRESSRemove an isolated component and ship without it, with a bounded statement about what changed.

05

In your industry

This is why ORMAS is one product rather than seven. Certified Deletion is the same mechanism in every row below — only the customer's own vocabulary changes.

Medical
contributor withdrawal
Finance
client data rights
Biotech
licensed compound data
AI lab
opt-out corpus
SaaS
termination clause

06

Markets using it

07

Questions

No. ORMAS is one product under one licence, and Certified Deletion is one of the seven things it is proven at. You turn on what your situation needs; there is no separate purchase, no separate integration and no separate contract.

The mechanism does not know what industry it is in. What changes between them is the noun, not the method — the table above is the same mechanism with each sector's own vocabulary substituted, which is why one product serves all of them.

On your infrastructure. The licence is on-premise and per-institution: nothing is sent to a third party, there is no hosted tier, and no usage metering phones home. In a hospital enclave or a controlled environment, that is a requirement rather than a preference.

Pre-book ORMAS with Certified Deletion in scope.

Every engagement starts with one specific problem — a run that died, an audit that asked a question you could not answer, a dataset you cannot vouch for.

We reply within a few days. Every message is read by a person.

Pre-book a deployment

One licence, no price list. Terms are agreed per institution and written into the contract, and pre-booking fixes them ahead of general availability.

Useful to bring

  • What you train, and roughly at what scale
  • The obligation driving it — SR 26-2, the EU AI Act, Article 17, a PCCP, an internal policy
  • What a failed run currently costs you to diagnose
Pre-book a deployment