Legal pages editor guide¶

Where to edit¶

1. In the CMS sidebar, open Settings.
2. Open Legal pages.
3. Edit the Privacy Policy or Terms of Service section, then save.

There is one Legal pages screen, not a list. You edit the same screen every time; there's no "add new" or "create page" step.

What each page has¶

• Title — plain text, shown as the page's heading. Rename it freely; it doesn't affect the URL.
• Body — a stack of blocks. Click the + button to add a block and pick its type:
  • Text — rich text. Formatting is deliberately limited: bold, italic, links, bullet and numbered lists, and two heading levels (Heading 2, Heading 3) for section breaks.
  • Table — a grid for tabular content, such as the Purpose / Legal Basis table in the Privacy Policy. See Add a table.

There's no Heading 1 in the Text block. The Title field is the page's one top-level heading — start your sections at Heading 2.

Add a table¶

1. In the body, click + and choose Table.
2. Click a cell and type. Tab moves to the next cell; Enter moves down a row.
3. To add or remove rows and columns, right-click any cell. The menu has Insert row above, Insert row below, Insert column left, Insert column right, Remove row, and Remove column. Right-click is the only way to change the table size — there is no drag-to-expand.
4. To turn the top row or first column into headers, use the Table headers dropdown above the grid. The dropdowns above the grid only mark headers; they don't add or remove cells.

What the copy must include for app-store approval¶

These URLs go on the Apple and Google app-store listings, and a reviewer opens the page to check it. Two things must be in the body copy, or a reviewer can reject the listing:

• Who it applies to. Name the app and the company or estate the policy covers. A reviewer rejects a policy that could belong to anyone.
• A last-updated date. State when the copy last changed, for example "Last updated 26 August 2026". Update it whenever you edit the copy.

The page is deliberately plain, with no site header, menu, or footer, so it also sits cleanly inside the app's own screen. Keep the identifying details in the copy rather than expecting a header or footer to carry them.

Publishing¶

Saving publishes immediately. Settings screens have no draft state and no preview — check the wording before you save, then confirm it live at the page's URL (below).

Where it's published¶

Open either URL after saving to confirm the change. This plain URL is the one that goes on the app store listing; the mobile app loads the same page (with ?format=embed) in its in-app webview.

Adding another legal page¶

The two pages above ship with fixed URLs (/privacy-policy/, /terms-of-service/) so the same link can go on the app store listing without ever changing. A third page — a new URL — needs an engineer to add the field and the route; it isn't something this screen can grow on its own.