timescale.info
Sign inSign up

How OpenChronology was built

Every merged pull request of openchronology/timeline-app, its first week of commits and its releases; and before them the 2020 PureScript editor, from snapshots of its deleted repositories in the Wayback Machine. Written to this server through the HTTP API.

327 moments · 2020-03-09T00:15:08Z CE – 2026-11-02T20:11:21Z CE · by @athan · @athan

#381 · The privacy policy covers YouTube videos played on the landing pages

  • timeline-app
  • pull request
  • videos

Adds an **Embedded videos** section to `legal/PRIVACY.md` for the click-to-load YouTube videos the landing and audience pages can show (`LANDING_VIDEO`, `LANDING_VIDEO_ `, #379/#380), and points to it from the cookies paragraph and from the list of what the service includes. It describes the behaviour as built: nothing loads from YouTube or Google until a visitor presses play; then YouTube's player loads from youtube-nocookie.com, Google receives the visitor's IP address, browser and device information, the site's address as referrer and their use of the player, and YouTube may store cookies; the service sends YouTube nothing about accounts or timelines; and it is independent of the Google Analytics choice. **Effective date and `POLICY_VERSION` are unchanged**: this is written as a clarification of an opt-in, per-click feature, not a material change, so accounts aren't asked to agree again. If you consider it material, bump the date in `legal/TERMS.md`/`legal/PRIVACY.md`, `POLICY_VERSION` in `server/policies.mjs` and `oc_policy_version()` in `server/schema.sql` together (see docs/authentication.md). Merge before (or with) the first `LANDING_VIDEO*` setting on timescale.info.

Sources

Open #381 · The privacy policy covers YouTube videos played on the landing pages in the timeline