Add /privacy page — single privacy policy for web + app - #12
Merged
Conversation
One canonical privacy policy served at snapbiodata.com/privacy, reused by both the website and the SnapBiodata mobile app. Accurately reflects the on-device data model (biodata never leaves the device; client-side PDF) and Vercel analytics; uses SITE config for name/url/contactEmail. Statically prerendered; lint + tests + build pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
Someone is attempting to deploy a commit to the pythonsst's projects Team on Vercel. A member of the Team first needs to authorize it. |
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
2 participants
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.
Summary
Adds a single canonical Privacy Policy page at
snapbiodata.com/privacy, reused by both the website and the SnapBiodata mobile app (the app links to this same URL — no duplicate policy maintained anywhere).Why
Google Play + App Store both require a public privacy-policy URL that matches the app's data behavior. Keeping one page (here, in the web repo) avoids drift between web and app.
Details
src/app/privacy/page.tsx(App Router, statically prerendered).font-display) and usesSITEconfig for name/url/contactEmail— no hardcoded strings.CLAUDE.md) → consistent with a Play Data Safety answer of "No data collected."layout.tsx) + app-update services (Expo/Apple/Google), retention/deletion, children's privacy, contact.Verification
npm run lint✓ ·npm test(61 tests) ✓ ·npm run build✓ (/privacyprerenders as static).🤖 Generated with Claude Code