feat(legal): single POLICY_LAST_UPDATED constant + refresh stale "January 2025" #100

Merged
YousifShkara merged 1 commit from feat/bunyip-upgrade-07-legal-dates into main 2026-06-10 08:08:07 +02:00
Owner

Terms of Service and Privacy Policy both rendered "Last updated: January 2025" while the site footer showed "© 2026". The implicit signal "this site is stale" is corrosive on a paid SaaS landing page, and the two pages were drifting independently because the literal lived in two places.

Adds const POLICY_LAST_UPDATED: &str = "June 2026" at the top of content.rs and routes both legal-page renders through it. The constant carries a comment that names the maintainer policy: bump the date the SAME COMMIT you re-read the policy body for accuracy, never just to make the page look fresh. The commit becomes the signal that the text was reviewed; a stale date is then a real signal too.

Future bumps are a one-line change at the constant; the two Last updated: … lines automatically follow. Closes audit finding 11 (Terms / Privacy stale dates). See docs/bunyip-upgrade/07-content-page-dates.md for the full spec.

Terms of Service and Privacy Policy both rendered "Last updated: January 2025" while the site footer showed "© 2026". The implicit signal "this site is stale" is corrosive on a paid SaaS landing page, and the two pages were drifting independently because the literal lived in two places. Adds `const POLICY_LAST_UPDATED: &str = "June 2026"` at the top of `content.rs` and routes both legal-page renders through it. The constant carries a comment that names the maintainer policy: bump the date the SAME COMMIT you re-read the policy body for accuracy, never just to make the page look fresh. The commit becomes the signal that the text was reviewed; a stale date is then a real signal too. Future bumps are a one-line change at the constant; the two `Last updated: …` lines automatically follow. Closes audit finding 11 (Terms / Privacy stale dates). See `docs/bunyip-upgrade/07-content-page-dates.md` for the full spec.
feat(legal): single POLICY_LAST_UPDATED constant + refresh stale "January 2025"
All checks were successful
Create release / Create release from merged PR (pull_request) Has been skipped
Check / fmt / clippy / build / test (pull_request) Successful in 1m2s
2d45ba676a
Terms of Service and Privacy Policy both rendered "Last updated: January 2025" while the site footer showed "© 2026". The implicit signal "this site is stale" is corrosive on a paid SaaS landing page, and the two pages were drifting independently because the literal lived in two places.

Adds `const POLICY_LAST_UPDATED: &str = "June 2026"` at the top of `content.rs` and routes both legal-page renders through it. The constant carries a comment that names the maintainer policy: bump the date the SAME COMMIT you re-read the policy body for accuracy, never just to make the page look fresh. The commit becomes the signal that the text was reviewed; a stale date is then a real signal too.

Future bumps are a one-line change at the constant; the two `Last updated: …` lines automatically follow. Closes audit finding 11 (Terms / Privacy stale dates). See `docs/bunyip-upgrade/07-content-page-dates.md` for the full spec.
YousifShkara deleted branch feat/bunyip-upgrade-07-legal-dates 2026-06-10 08:08:08 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
psa-systems/bunyip!100
No description provided.