Terms of Service + Privacy Policy (starting-point templates)
Public /terms and /privacy pages pre-filled from site.config (company name + contact always right), each carrying an on-page 'have a lawyer review this' notice you remove after legal sign-off. The privacy policy honestly describes what THIS stack collects (account details, CRM records, feedback with page context, session/theme/locale cookies) so it starts true. Footer links + a consent line ('by creating an account you agree to Terms & Privacy') on all three signup surfaces (operator, member portal, lead-capture landing).
If you are building a front end
Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: none — static content from site.config.
Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.
- How to turn it on
- Always on; edit the copy for your business and remove the template notice.
- Who can use it
- public (middleware PUBLIC_PATHS /terms /privacy).
- The API behind it
none — static content from site.config- Where it lives
- /terms/privacyfooter/signup/m/:slug/signup/lp/:slug
Machine-readable
This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.