Your infrastructure stores it. It cannot read what it stores.

Ghostables seals sensitive data on the user’s side before it is sent anywhere. Servers, databases, backups and the people who run them hold only sealed records.

Operator-blind by design

The keys that open a person’s data are created and kept on their side. They are never sent to your servers, never stored beside the data and never shared with Ghostables.

A full copy of your database, taken by anyone for any reason, is a copy of sealed records.

  • Opening data takes the person’s password, a second factor and a PIN
  • Only the records on screen are ever open, and only while they are on screen
  • Nothing your operators can access will open a record on its own
The user’s side Sealing happens here Amara Okafor Type 2 diabetes Keys stay here Application serversDatabaseBackups and replicas

One answer to four different threats

A stolen backup

Backups, snapshots and replicas contain sealed records. The keys that would open them were never in the database to steal.

A compromised server

Records already stored stay sealed, because nothing on the server can open them. Data entered while an intruder controls the service is at risk until they are removed.

An insider

Administrators keep the system running without being able to read what it holds. Full access to the infrastructure is not access to the data.

A legal demand

A demand made to the operator yields only sealed records. Lawful requests go to the people who hold the keys.

A compromised key exposes a moment, never the archive

The keys in use are replaced continuously and the old ones destroyed. Records written before a compromise stay sealed, and anything exposed is limited to a narrow recent window.

One long-lived key Exposed back to day one With Ghostables Sealed history, unaffected PastMoment of compromise

Find out where sealed data fits in your systems

Our engineers will map your sensitive data and show you which protections apply, before you commit to anything.