Step 1
Write a policy
Terms, privacy, or any legal text. Draft it, then publish a frozen version. Apps fetch this copy instead of guessing the wording.
EasyPoliciesLedger
Write a policy, attach it to a module (a product screen), connect an app, record agreement, then audit the exact text later. Follow the map — you do not need a walkthrough from someone else.
Five steps, always in this order. The names below are generic; after you sign in, Getting started shows what this instance already has.
Step 1
Terms, privacy, or any legal text. Draft it, then publish a frozen version. Apps fetch this copy instead of guessing the wording.
Step 2
A module is a product screen such as signup or billing. Attach the policies that screen must show. Saving it updates that screen on every connected app.
Step 3
Register the product and copy the API key once onto the server. The app asks the hub by module key for copy, status, and recording agreement.
Step 4
The app or embed records who agreed, which policy version, and which module. That row is append-only.
Step 5
In People, open the app and user id. You see which modules they were assigned, what they signed, and the exact text plus hash.
v1 · force · mandatory
v1 · prompt · mandatory