docs: Data safety audit — Email Address (Play rejection vc142)#149
Merged
Conversation
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.
Summary
Audit of every off-device Email Address egress path in response to Google Play rejecting versionCode 142 for an undeclared Email Address in the Data safety form.
Note on vc142:
eas.jsonusesappVersionSource: remote, so EAS owns/auto-increments the Android versionCode — 142 appears nowhere in git (tags top out at vc39). Committed gradle/app.json values are stale. Email egress is a source property, so the audit was done at authoritativeorigin/main @ 6c103ac.Findings — exactly one real email egress
app/connection/add.tsx:217→src/lib/waitlist.ts:submitWaitlistSignup→POST https://opencode.agentlabs.cc/api/beta-signup→ Brevo (CRM). Optional, opt-in. Purpose: account management + developer communications. HTTPS.sendDefaultPii:false, scrubs URLs/tokens/username, no setUser), PostHog (anonymous ID, no identify/email), connection username (Basic-auth for user's own self-hosted server, not developer-collected). No RevenueCat/Firebase-auth/Amplitude/Segment/other email POSTs.Recommendation
DECLARE, don't remove. Fill Play Data safety for Email Address: Collected=yes, Shared=yes (Brevo), Optional, Purposes=Account management + Developer communications, Encrypted in transit=yes, deletion via support@agentlabs.cc. Prior PR #146 already aligned the privacy-policy/listing copy; this just needs the console form to match. Optional future hardening: drop the API POST and keep only the mailto fallback to answer Email=Not collected.
Full detail + exact form answers in
docs/data-safety-audit.md. Do not merge without review.