Draft privacy policy page at /privacy/ (#634, #635)#949
Open
Draft privacy policy page at /privacy/ (#634, #635)#949
Conversation
Adds a starter privacy policy as a server-rendered Django view at jandig.app/privacy/, prerequisite for Meta Quest VRC.Publishing and VRC.Quest.Privacy submission and for LGPD/GDPR compliance. The wording is a first pass written from the engineering side: it inventories what the codebase actually collects (account fields, uploaded media, session/CSRF/language cookies, Sentry error reports, Google Analytics traffic) and walks through the standard LGPD/GDPR sections. The page itself flags that legal review and team sign-off are still required, with placeholders for the contact email and effective date. What's left for the team: - Legal pass on wording. - Fill in section 9 (contact email) and section's effective date. - Translate the strings to pt-BR (everything is wrapped in `_()`). - Submit to the Meta Quest store. - Verify each VRC.Publishing.* and VRC.Quest.Privacy.* item. Routes: - core/views/static_views.py: privacy_policy view. - core/urls.py: GET /privacy/ → name="privacy-policy". Refs #634, #635 https://claude.ai/code/session_01XC1THLWgnGXGf5wgRhdyvB
This was referenced Apr 26, 2026
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
First-draft privacy policy served at
jandig.app/privacy/, as a prerequisite for the Meta Quest VRC.Publishing and VRC.Quest.Privacy items in #634 and the broader compliance work in #635.The wording is written from the engineering side: it inventories what the codebase actually collects (account fields, uploaded media, session/CSRF/language cookies, Sentry error reports, Google Analytics traffic) and walks through the standard LGPD/GDPR sections. The page itself flags that legal review and team sign-off are still required.
Files
src/core/jinja2/core/privacy.jinja2— the rendered page, all user-facing strings wrapped in{{ _("...") }}so a translator can pick them up viamakemessages.src/core/views/static_views.py—privacy_policyview.src/core/urls.py—GET /privacy/, namedprivacy-policy.What's left for the team (out of this PR)
VRC.Publishing.*andVRC.Quest.Privacy.*item against the rendered page./privacy/(deferred — touches a layout change that's out of scope here).Test plan
curl https://jandig.app/privacy/returns 200 with the policyreverse("privacy-policy")resolves to/privacy//community/and/documentation/routes unchangedcore/home.jinja2layoutRefs #634, #635
https://claude.ai/code/session_01XC1THLWgnGXGf5wgRhdyvB
Generated by Claude Code