Data handling · anchor-spec v2.0.0

Privacy Policy

What CaseAnchor stores, where it stores it, and how it is encrypted. Claims that would need an audit or a certificate behind them are not made on this page.

View the specification See root hash definitions

Referenceanchor-spec v2.0.0

Hash algorithmVerifiable

EncryptionEncrypted, keys held outside the app

QuestionsUse the contact page

Specification:1d8bbf8d9cf6542fd9461426f63b1a2032b2d15b2845be56bb4c1419c4145b29

Article 01

What the platform stores

CaseAnchor keeps the agreement in its operational storage and registers only a fingerprint of it. This document describes that split and what it means for your data.

Held in the operational stores

The following stay in the platform's own storage:

Agreement text and attachments
Case metadata, participants and public keys
Messages, polls, and their hashes
File references including content hash and provider

Registering a record does not move it out of this storage, and it does not remove it from it either.

Article 02

Encryption and key custody

Agreement content is encrypted before it is stored, and the encryption key is held outside the application.

System-wide key record

The encryption key is managed centrally.

External key custody

The key itself is held outside the application, not inside it.

Retention periods are configured per deployment. Ask us for the configuration that applies to you.

Article 03

Operational logs

The platform needs operational logs in order to run and to be supported. What is kept, and for how long, is a deployment decision rather than a fixed promise on this page.

Deployment-definedLog scope and retention are set per deployment instead of being promised here.

No trackers on this siteThis website loads no behavioural advertising or analytics trackers.

Ask for specificsRequest the logging and retention configuration for your own deployment.

Article 04

What is recorded

The register is not a copy of your data. It holds a fingerprint: which record, when, and where the agreement itself lives.

Stays in the operational storesprimary storage · records storage

Agreement text and filesDocuments and attachments stay in the platform's own storage.
Participant dataNames, contact details and identity information stay in the operational stores.
Encryption keysEncryption keys are never written to the register.

Goes into the registerCommitment only

FingerprintA verifiable fingerprint of the record.
Entity identity and timeWhich record it was, and when.
Source pointerWhere the agreement itself lives.

the register answers two questions: does this commitment exist, and has it ever been altered. It is not a query engine, and dashboards, search and cross-entity analytics are served from a read model in primary storage.

Article 05

Where the platform runs

CaseAnchor is built as a service platform with encrypted storage, role-based access and audit logging across every step of a case.

Component	Technology	Role	Where the data goes
Primary store	primary storage	Primary records	Your deployment
Payload store	records storage	Discussions and files	Your deployment
File storage	file storage	Agreements and attachments	Provider of your choice

Article 06

Access, correction and deletion

Because the records live in the operational stores, access, correction and deletion are applied there. the register keeps the commitment, which is what makes a removal visible rather than silent.

Applied to the operational stores

Requests are applied to the records held in the platform's storage, where the agreement actually lives.

The commitment is not edited

A fingerprint already registered is not rewritten. Whether a request can be satisfied in full depends on the register and on your jurisdiction, and we will tell you plainly rather than promise otherwise.

Need a data processing agreement?

Ask us. Terms are agreed in writing, not generated automatically by this page.

Article 07

Questions and complaints

Questions about this document, or about how your data is handled, go through the contact page on this site.

Where to send itCaseAnchorUse the contact form on this site, and tell us which case and which section the question is about.

What helps us answer fasterplatform/specsQuestions about how records are handled are answered directly by the published specification.

How a record is committed

Fingerprinted, sealed, then registered

VERIFIED_LEGAL_SPEC

Commitment hash9f83778d06b0436360541e450b299

Signature0x88F0B891A990CD435

Algorithm Sealed and verifiable

Defined in the published specification.