Sealing happens on the user’s side
Servers store and serve sealed records. They never receive anything that would let them open one.
How Ghostables is built, how to report a vulnerability, and a plain account of what our technology does not protect against.
These rules govern the Ghostables Platform and are written into its engineering specification. Our WordPress products document where they differ.
Servers store and serve sealed records. They never receive anything that would let them open one.
No key material is sent to a server, written to the database or shared with Ghostables, under any circumstances.
Protected values are never written to storage in a readable form.
Every comparison involving a secret value is written so its timing reveals nothing about the value.
The part of Ghostables that seals and verifies data has no ability to make network requests.
We use only widely reviewed, standard techniques. We do not invent our own.
Honest disclosure of residual risk is part of the Standard. These are the limits we tell every customer about.
Engineering detail
Available to customers and certification candidates under NDA
Third-party assessment
Not yet completed. We will publish its scope and summary here when it is
Your environment
The platform runs in your systems. Ghostables does not receive or host your protected data
If you believe you have found a security issue in any Ghostables product or in this website, please tell us privately before disclosing it anywhere else.
Email hello@ghostables.io with “Security report” in the subject line. We acknowledge every report within 72 hours.
Our marketing pages load no third-party scripts, fonts or trackers. Our enquiry forms send only what you type into them, and nothing is shared with advertisers.