Terms of Service

This is a structural placeholder, not the published Terms of Service.

The real terms need to be sourced from the product codebase’s ui/policies/ directory and reviewed by counsel before this page goes live. This draft exists to demonstrate the versioning mechanism: each published revision should carry a version and effectiveDate in its frontmatter, and a visitor’s recorded consent should always resolve to the exact version that was live at the time they accepted it — never to whatever is live today.

What this page needs before launch

1. Final terms copy from ui/policies/, reviewed for accuracy against the current product (subscription billing, wallet top-ups, refund handling, service-level expectations).
2. Confirmation of the effective date and version number to use for the first published revision.
3. A decision on how prior versions are archived and linked from this page once revisions ship, so an old consent snapshot still resolves to readable text.