Terms of Use

CaseAnchor is a platform for agreements. A case holds the agreement, the discussion around it, and the poll that closes it. These terms describe the ground rules for using that: what the platform does, what you put into it, and what happens to what you anchor.

• Use the platform and the services it depends on
• The case data you place in it
• The commitments that get recorded on anchoring
• How changes to the specification are handled

Finalising an agreement is a defined, repeatable process: the record is fingerprinted and sealed, and what is registered is a fingerprint rather than the agreement itself.

• One agreed representation of the agreement
• A verifiable fingerprint
• A verifiable record per agreement
• The poll result is sealed together with the agreement

Access follows the case. Participants are listed on the case together with their role and public keys, and assertions are device signature-compatible JSON. How credentials, sessions and key custody are configured is part of your deployment.

• Participants and roles are defined on the case
• Participants are recorded per case
• Each signature is recorded with the result
• Access follows your deployment configuration

There is no published rate card. Drafting, discussion and polling are the day-to-day flow inside a case. Anchoring is the step that hashes, signs and records the commitment, and that is what gets quoted. In-app payments are out of scope for the platform.

• Drafting, discussion and polling happen inside a case
• Anchoring is quoted per deployment, with the breakdown given in writing
• Billing happens outside the product
• Service levels belong to the commercial agreement

The agreement lives in the platform's own storage. The register holds a fingerprint only. Retention periods are configured per deployment.

• Encrypted before storage
• Keys held outside the app
• Keys held outside the app
• A fingerprint, never the content

Service levels are part of a commercial agreement, not of a marketing page. Nothing here states an availability figure, a response time or a credit, because those belong in the agreement that covers your deployment.

• No availability figure is published on this page
• Uptime commitments are made only in a signed agreement
• Support and response terms are agreed in writing
• Ask us for the terms that apply to you

Liability caps, indemnification and governing law are agreed in writing for each deployment, because they depend on your jurisdiction and your contract. When the platform specification changes, the spec files change with it, and this summary is updated alongside them.

• Liability and indemnification are agreed per deployment
• Governing law and dispute process are set in the agreement
• The published specification is the reference
• Changes to the specification are reflected in these summaries