CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity Actions
storebound/skills/privacy-policy/SKILL.md

2.5 KiB
Raw Blame History

name description
privacy-policy Write and host one studio-wide privacy policy page for all of a developer's mobile apps and games - a per-app services table (analytics, ads, server, purchases), children, retention and contact sections, linked from both store listings and inside each app. Use when the user needs a privacy policy, privacy URL for Google Play / App Store, or must update the policy after adding an SDK.

Studio-wide privacy policy

Template: store/privacy-policy.html (from storebound init, or templates/privacy-policy.html in the toolchain). A single static page, light/dark, mobile friendly, English + a second language section.

Steps

  1. One page for the developer, one row per app and service. Columns: app, service (analytics, ad mediation + networks, your server or backend, sign-in provider, app stores), what data and why, the user's choice (in-app switch, ATT prompt, OS ad settings, "remove ads", deleting the account). Remove what you do not use; never list services you do not ship.
  2. Sections to keep: what we use (table), children (general audience, not directed at under 13 unless you really are a kids app), retention and rights (how to request a copy / deletion, response time; with accounts: how to delete the account, in the app and on the web, see the account-deletion skill), security (HTTPS), changes (date at the top), contact email.
  3. Host it at a stable URL on your developer website, the same domain that serves app-ads.txt and is named as website in both listings (e.g. https://example.com/privacy). Any static host works.
  4. Link it everywhere: app.privacyPolicyUrl in storebound.config.ts (pushed by storebound apple listing), Play Console > App content > Privacy policy, and inside the app (Settings > Privacy opens the URL): App Store guideline 5.1.1 requires the in-app link.
  5. Verify: the URL answers 200 over HTTPS without login or cookie wall, the table matches the Data safety / App Privacy answers (store-declarations skill), the date is current.

Gotchas

  • Update the policy first, then the store forms, whenever an app adds an SDK or starts storing something new.
  • The policy must not be a PDF or a Google Doc behind a login; a plain page is safest for review.
  • Do not put a personal address or private email in it; use a studio contact address.
  • If an app uses ads in the EU / EEA / UK / CH, say how consent works (CMP or non-personalized ads).
  • This template is a starting point, not legal advice.