Repository navigation
Add draft Play privacy policy page (owner fields required) - #1
Merged
Merged
Conversation
Play requires a privacy policy URL and this app has none (/privacy and /privacy.html both 404 on the live origin, verified 2026-10-26). The page is written only from observed behaviour and the repository data-safety notes, and stays noindex until the owner supplies the publisher name, support email, effective date and the flagged declarations. No release gate is flipped.
Every owner-only placeholder is gone because every statement is now grounded in something checkable: - Package ids, allowBackup=false, and the exact permission list come from the Android manifests in this repository. - The 'no analytics, crash-reporting or advertising component' statement was checked against the packaged build's dependencies and bundled assets, not assumed. - The payment providers named (Yoco, PayFast) are the only hosts the app accepts for an invoice checkout link, read from the link-validation code. - ScreenNote's limits (5 minutes, 25 MB, 1 GB budget, 1/3/7-day expiry, and the five-minute signed-link lifetime) are read from its own rules and signing code. - Contact is the repository issue tracker, which is public with issues enabled, plus the Play listing's developer contact. No support address is invented. Play requires the policy URL; the registered developer email is a separate Play Console field and is left for the owner, as is the publisher identity.
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
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.
Play requires a privacy policy URL for every listing, and this app has none:
/privacyand/privacy.htmlboth return 404 on the live origin (checked 2026-10-26).This adds a complete draft policy page, written only from observed app behaviour, the build configuration and this repository's own data-safety engineering notes.
Do not merge and publish until the highlighted fields are filled in: publisher name, support email, effective date, plus the flagged items (release-build network/telemetry confirmation, target audience, how users are told about changes, and for user-generated content the moderation and takedown process).
The page is served with
<meta name="robots" content="noindex">so a half-complete policy cannot be indexed if it is deployed early. Remove that tag once the fields are complete and the page is the canonical policy.Suggested URL once published (to be entered in
android/play-store/listing-draft.jsonand the Play listing):https://invoiceflow-za.vercel.app/privacy.htmlhttps://screennote-woad.vercel.app/privacy.htmlNo release gate in
android/release-gates.jsonis flipped by this change: writing a URL is not evidence that the page is live or correct, so the owner should flip those gates after verifying the published page.