trails-cool/trails
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
trails/docs/legal-archive
History
Ullrich Schäfer 32661a0163
Add visibility disclosure to the binding German privacy text 
The previous commit only added a bullet to the English-only Privacy
Manifest appendix. The formal, binding German sections (which the
policy explicitly declares authoritative) didn't mention visibility
at all — and the paired English summary under each section likewise
didn't.

Add a sentence under §2 "Erhobene Daten und Zwecke → Nutzerinhalte"
explaining the visibility setting, defaults, and world-visibility
consequences. Mirror in the section's English summary paragraph. Keep
the Privacy Manifest bullet as an additional plain-language mention.

Re-rendered docs/legal-archive/privacy-2026-04-20.md; both languages
present (verified).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-19 09:14:15 +02:00
..
imprint-2026-04-19.md Seed docs/legal-archive with Terms / Privacy / Imprint snapshots 2026-04-19 07:51:41 +02:00
privacy-2026-04-19.md Seed docs/legal-archive with Terms / Privacy / Imprint snapshots 2026-04-19 07:51:41 +02:00
privacy-2026-04-20.md Add visibility disclosure to the binding German privacy text 2026-04-19 09:14:15 +02:00
README.md Convert render-legal to TypeScript 2026-04-19 07:52:53 +02:00
terms-2026-04-19.md Seed docs/legal-archive with Terms / Privacy / Imprint snapshots 2026-04-19 07:51:41 +02:00

README.md

Legal archive

Frozen snapshots of the Terms of Service, Privacy Policy, and Impressum at each version. Kept so we can always answer "what did the Terms / Privacy text say on a given date" without digging through git blame.

Why

  • Terms: users accept a specific version at registration (users.terms_accepted_at + users.terms_version). The version string is the date in this folder — so there is always a file here matching every value that exists in that column.
  • Privacy: users don't "accept" a privacy policy, but GDPR Art. 13/14 requires us to tell users how their data is processed at the time it's processed. If a regulator or user asks what the policy said on YYYY-MM-DD, this folder answers.
  • Impressum: less legally critical, but free to snapshot for symmetry.

When to add a file

Whenever any of these three texts change materially, run the snapshot step as part of the change:

  1. Bump TERMS_VERSION / PRIVACY_LAST_UPDATED in apps/journal/app/lib/legal.ts to today's date.
  2. Re-render the affected page(s) into this folder as <doc>-YYYY-MM-DD.md.
  3. Commit the bump and the new snapshot in the same PR.

A trivial wording tweak or typo fix does not need a new snapshot; only changes that affect meaning / behaviour / purposes / third parties / legal basis / retention / etc.

File naming

<doc>-YYYY-MM-DD.md where <doc> is one of terms, privacy, imprint, and the date matches the Last updated line in the corresponding legal page on the day the snapshot was taken.

How to render

Snapshots are extracted from the TSX source by stripping JSX tags / attributes and resolving the operator.* placeholders plus the constants from apps/journal/app/lib/legal.ts. One-liner (from repo root):

node --experimental-strip-types scripts/render-legal.ts <doc> \
  > docs/legal-archive/<doc>-YYYY-MM-DD.md

where <doc> is one of terms, privacy, imprint.