feat(dashboard): link privacy policy from the analytics notice - #198
Merged
Conversation
The injected notice previously carried only the one-line summary. Under the cautious reading that visitor_month_hash is pseudonymous personal data, GDPR Art. 13 expects visitors to be able to find the full disclosure, and CNIL guidance expects the site's privacy policy to describe the measurement even for consent-exempt analytics. The URL is a named constant so the next site reusing this snippet has one place to point at its own controller's policy. No styling was needed: style.css unsets link styling and underlines links outside headings and tables, so the anchor inherits the notice's muted grey, and the page header's <base target="_blank"> already opens it in a new tab. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The analytics notice injected into every generated dashboard page (added in
#149) carried only the one-line summary.
docs/design-decisions/031-analytics-ingestion-design.mdalready anticipatesthis: under the cautious reading that
visitor_month_hashis pseudonymouspersonal data, GDPR Art. 13 expects visitors to be able to find information
about the processing, and the CNIL guidance expects the site's privacy policy
to describe the measurement even for consent-exempt analytics. A footer notice
alone satisfies the letter of that; a linked policy is the stronger posture.
The footer notice on every generated page becomes:
🤖 Generated with Claude Code