Demo consuming app

Academy signup

The app asks the hub whether this person already agreed. It only shows the full text when a policy is new or a newer version was published.

Continue as a learner
External id is whatever your app already uses for the person.
Terms of Servicev1 · first agreement

Terms of Service

Last updated: 1 September 2026.

By creating an account or using a product that relies on EasyPoliciesLedger, you agree to these Terms.

1. The service

EasyPoliciesLedger is a central registry for legal documents and recorded acceptances. Consuming applications remain responsible for presenting the current published version before they collect an acceptance.

2. Your obligations

You must not misrepresent the version a person agreed to, store API keys in client-side code in production, or alter recorded acceptances.

3. Changes

When we publish a new version, consuming apps should call the status API and, depending on the document's re-consent mode, block access, prompt, or grandfather existing agreements.

4. Contact

Questions about these terms: legal@example.com

Privacy Policyv1 · first agreement

Privacy Policy

Last updated: 1 September 2026.

What we collect

When a consuming app records an acceptance we store: an opaque external user id, the document slug and version, a SHA-256 hash of the accepted text, source (placement or URL), IP address, user agent, and timestamp.

Why

We keep this ledger so you can answer data-subject access requests and prove which text a person agreed to.

Retention

Acceptances are append-only. Administrators can export them as CSV. Deleting a subject from a consuming app does not automatically erase hub records unless you request deletion.

Contact

privacy@example.com