Skip to content

feat(legal): a privacy policy page for the Android app - #83

Merged
yusuf-gundogdu merged 1 commit into
mainfrom
add/mobile-privacy-policy
Oct 27, 2026
Merged

yusuf-gundogdu merged 1 commit into
mainfrom
add/mobile-privacy-policy

Conversation

@yusuf-gundogdu

Copy link
Copy Markdown
Member

Google Play's Privacy policy screen requires a policy that applies specifically to the app and discloses what the app collects.

The existing /privacy-policy is the website's — cookies, analytics, the YouTube embed. It says nothing about the access token the app sends, the statements it sends to Studio, the Sentry crash reports, or how to delete any of it. Entering that URL in the Play Console risks a review rejection, so the app gets its own page at /mobile-privacy-policy.

The wording is the one the app ships with (libredb/libredb-mobile → docs/privacy-policy.md); the two are updated together. The page reuses the existing policy's layout and styles, and the vendor details come from data/company rather than being typed out again.

Three of this repo's guards caught the page missing, and all three are satisfied: the route is in site.config.json (which is also what puts it in the accessibility audit), its internal link carries a trailing slash, and it is described in llms.txt.

bun test 233/233, bun run build, lint and format all clean.

Needed for the LibreDB Mobile Play Console listing — the URL is already entered there, so it 404s until this merges.

🤖 Generated with Claude Code

Google Play requires a policy that applies specifically to the app and discloses what the app itself collects. The
existing /privacy-policy is the website's: cookies, analytics and the YouTube embed. It says nothing about the
access token the app sends, the statements it sends to Studio, the crash reports, or how to delete any of it, so
entering it in the Play Console risks a review rejection.

This is the wording the app ships with, in libredb/libredb-mobile `docs/privacy-policy.md`; the two are updated
together. The page reuses the existing policy's layout and styles, and the vendor details come from `data/company`
rather than being typed out again.

The route is registered in site.config.json, which is also what puts it in the accessibility audit, and described in
llms.txt — the three guards that caught it missing.
@yusuf-gundogdu
yusuf-gundogdu merged commit 2e8c39b into main Oct 27, 2026
5 checks passed
@yusuf-gundogdu
yusuf-gundogdu deleted the add/mobile-privacy-policy branch October 27, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant