#282 · The privacy policy and terms have pages of their own, and take effect
- timeline-app
- pull request
On 25 October 2026 at 17:08:33 UTC, OpenChronology’s timeline-app development history records the merge of pull request #282, “The privacy policy and terms have pages of their own, and take effect.” The record concerns a change to the software used to create, read and compare timelines. Closes #281. - `/privacy` and `/terms` render `legal/PRIVACY.md` and `legal/TERMS.md` as real pages (headings, paragraphs, links) through `server/help.mjs`'s renderer, via a new `components/policy-page.jsx`. `/legal` keeps everything together and links to them. - Footer: Terms · Privacy · Licenses. Sign-up, the analytics prompt and the sitemap link to the new pages. - The policies take effect on 25 October 2026. The contact is **privacy@timescale.info**. They state the real hosting (DigitalOcean, United States), nginx logs (14 days), a size-limited service log and pre-upgrade database backups, and that Google Analytics is used with consent. - New **Google user data** section: only the Google account identifier is kept; no name, email or picture; tokens discarded; no sharing, advertising or AI training; adheres to the Google API Services User Data Policy including Limited Use; how to unlink or revoke. - `COPYRIGHT.md` uses the same contact and states that no DMCA agent is registered. `LAUNCH.md` records what's done. The offline `legal.html` drops the draft labels. Tests: `npm run build` succeeds, and `npm run test:platform` passes, now also checking the `/terms` and `/privacy` titles. `npm test` passes 304 of 305: the one failure is the README-contents check, which only fails locally because of agent worktrees under `.claude/`. **Source:** [Project record](https://github.com/openchronology/timeline-app/pull/282).
Sources
Related
Open #282 · The privacy policy and terms have pages of their own, and take effect in the timeline