Legal pages: privacy policy + EULA at /privacy/ and /eula/ #253
Reference in New Issue
Block a user
Delete Branch "feature/legal-pages"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hosts the privacy policy (
/privacy/) and the EULA (/eula/) as static pages via the render sidecar, and links them from the landing footer alongside the existing offer + feedback. First slice of the documents track for the Android/RuStore release (RuStore needs a hosted privacy-policy URL).What
ui/legal/privacy_ru.md+ui/legal/eula_ru.md, reworked from the source documents.renderLegalHtmlgeneralised out ofrenderOfferHtml; newrendererroutesGET /privacy/+GET /eula/(static, no backend fetch; 301 from the slashless form); markdown baked into the image.@legalcaddy matcher now covers /offer/ + /privacy/ + /eula/; CI probes assert each page's canonical URL + the seller INN (so a missing route can't fall through to the landing).Decisions applied (from our interview)
Please review
Not in this PR
Contour-safe: no schema/wire change; pure content + a static render route + an edge matcher + docs.
Author ui/legal/{privacy,eula}_ru.md, reworked from the source documents: the seller INN is unified (290210610742), contacts unified to the Telegram bot + email + postal address, the EULA governing-law clause leads with Russian law + jurisdiction as residence tiers, the single-binding-language clause is dropped, data collection is scoped to voluntary/support provision, and "Компания" is no longer shout-cased. Serve both as static pages through the render sidecar, reusing a shared renderLegalHtml generalised from renderOfferHtml: new GET /privacy/ and GET /eula/ (301 from the slashless form), the markdown baked into the image, no backend fetch. Route them at the edge via the @legal caddy matcher with a CI probe asserting each page's canonical URL + the seller INN, so a missing route cannot silently fall through to the landing. Add the two links to the landing footer. Docs baked in: ARCHITECTURE (renderer legal pages + edge routing), FUNCTIONAL (+_ru) footer, renderer/README routes. Tests: renderer legal.test.mjs, ui renderLegalHtml unit, landing footer e2e.