How records are hashed, signed, encrypted and anchored
CaseAnchor does not claim certifications it does not hold. What it has is a written specification: how a record is fingerprinted, sealed and stored, and what happens to your data at each step.
How the data model works
Records are fingerprinted and sealed before they are stored, agreement content is encrypted with the key held outside the application, and what is registered is a fingerprint rather than the content itself.
Hashing and signing
fingerprint and sealedA finalised agreement is fingerprinted and sealed, so the record you hold can be checked against what was agreed.
Encryption and key custody
encryption with keys in outside the applicationAgreement content is encrypted before it is stored, and the encryption key is held outside the application.
record register
Commitments, not copiesWhat gets registered is a fingerprint of the record — not the agreement itself. The agreement stays where it belongs, and what is registered answers whether it exists and whether it has ever been altered.
Legal terms
The privacy policy and the terms that govern use of the platform. Where a claim would need an audit or a certificate behind it, this page does not make it.
CaseAnchor keeps the case payload in its operational databases and only the commitment in the register. Anchoring a record does not lift it out of those stores.
Encrypted before storage The real key is held in an outside the application rather than inside the application.
Retention periods and key disposal are configured per deployment. Ask us for the specifics of your configuration.