feat(website): Add privacy policy page - #952
Open
kotevcode wants to merge 1 commit into
Open
Conversation
Add /privacy-policy documenting website analytics (GA4/GTM, ads), download.antseed.com delivery telemetry, desktop app local-only storage and update checks, and protocol/on-chain privacy properties. Linked from the footer next to Terms of Service. Motivated by reputation-service categorization (McAfee WebAdvisor flags the site as suspicious with a stale parked-domain category) and Google Ads policy, both of which expect a privacy policy as a trust signal.
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.
Description
McAfee WebAdvisor currently flags antseed.com as Suspicious with stale categories ("Parked Domain", "Blogs/Wiki") from before launch. Google Safe Browsing is clean and Norton Safe Web rates the site safe — McAfee recategorization is being requested separately. One concrete trust-signal gap on our side: the site had a Terms of Service but no privacy policy (also expected by Google Ads policy, which we actively run).
This adds
/privacy-policy, written against what we actually collect:Footer now links it next to Terms of Service.
Changelog
Updated
CHANGELOG.md(Unreleased → Added).Test plan