The Play compliance groundwork is done (#17, merged): privacy policy (PRIVACY.md), data-safety mapping (docs/play-data-safety.md), permissions justification (docs/play-permissions.md), and a console-step checklist with drafted answers (docs/play-compliance.md). This ticket tracks the remaining human Play Console steps that can't be automated.
Steps (human)
Register a Google Play Developer account ($25 one-time); complete the developer profile + identity verification.
Create the app in Play Console (default language; type = App; Free).
Signing: complete the keystore + Play App Signing (see the "Release signing keystore + CI publishing secrets" ticket).
Data safety form — fill from docs/play-data-safety.md (recommended answer: "No data collected / No data shared", backed by the evidence table there).
Permissions declarations — READ_CONTACTS, POST_NOTIFICATIONS, and the FOREGROUND_SERVICE_DATA_SYNC declaration; record the demo video per the script in docs/play-permissions.md.
Content rating (IARC questionnaire) — use the drafted answers in docs/play-compliance.md (expect Everyone / "Users Interact").
Store listing — title, short (<=80 chars) + full description (drafts in docs/play-compliance.md and fastlane/metadata/), 512x512 icon, 1024x500 feature graphic, 2-8 screenshots, category, contact info.
Privacy policy URL — host PRIVACY.md at a public URL and enter it (Play requires a reachable URL).
Target audience & content; Ads = No; app access (provide a test mailbox/credentials for the reviewer); account-deletion statement (data is device-local — see docs/play-compliance.md).
Upload the signed AAB to Internal testing; verify the pre-launch report and the App-bundle-explorer 16 KB page-size verdict (empirically confirmed passing in #17); then promote to Production / staged rollout.
(Optional automation) Create a Play Publisher API service account and add its JSON to CI secrets so #19's workflow can publish on tag.
Dependencies
Groundwork #17 (done); the signing/secrets ticket; #19 (automated publish).
The Play **compliance groundwork is done** (#17, merged): privacy policy (`PRIVACY.md`), data-safety mapping (`docs/play-data-safety.md`), permissions justification (`docs/play-permissions.md`), and a console-step checklist with drafted answers (`docs/play-compliance.md`). This ticket tracks the remaining **human** Play Console steps that can't be automated.
## Steps (human)
- [ ] Register a **Google Play Developer** account ($25 one-time); complete the developer profile + identity verification.
- [ ] Create the app in Play Console (default language; type = App; Free).
- [ ] Signing: complete the keystore + Play App Signing (see the "Release signing keystore + CI publishing secrets" ticket).
- [ ] **Data safety form** — fill from `docs/play-data-safety.md` (recommended answer: "No data collected / No data shared", backed by the evidence table there).
- [ ] **Permissions declarations** — `READ_CONTACTS`, `POST_NOTIFICATIONS`, and the **`FOREGROUND_SERVICE_DATA_SYNC`** declaration; record the demo video per the script in `docs/play-permissions.md`.
- [ ] **Content rating** (IARC questionnaire) — use the drafted answers in `docs/play-compliance.md` (expect Everyone / "Users Interact").
- [ ] **Store listing** — title, short (<=80 chars) + full description (drafts in `docs/play-compliance.md` and `fastlane/metadata/`), 512x512 icon, 1024x500 feature graphic, 2-8 screenshots, category, contact info.
- [ ] **Privacy policy URL** — host `PRIVACY.md` at a public URL and enter it (Play requires a reachable URL).
- [ ] Target audience & content; **Ads = No**; app access (provide a test mailbox/credentials for the reviewer); account-deletion statement (data is device-local — see `docs/play-compliance.md`).
- [ ] Upload the signed **AAB** to **Internal testing**; verify the pre-launch report and the App-bundle-explorer **16 KB page-size** verdict (empirically confirmed passing in #17); then promote to Production / staged rollout.
- [ ] (Optional automation) Create a **Play Publisher API** service account and add its JSON to CI secrets so #19's workflow can publish on tag.
## Dependencies
Groundwork #17 (done); the signing/secrets ticket; #19 (automated publish).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The Play compliance groundwork is done (#17, merged): privacy policy (
PRIVACY.md), data-safety mapping (docs/play-data-safety.md), permissions justification (docs/play-permissions.md), and a console-step checklist with drafted answers (docs/play-compliance.md). This ticket tracks the remaining human Play Console steps that can't be automated.Steps (human)
docs/play-data-safety.md(recommended answer: "No data collected / No data shared", backed by the evidence table there).READ_CONTACTS,POST_NOTIFICATIONS, and theFOREGROUND_SERVICE_DATA_SYNCdeclaration; record the demo video per the script indocs/play-permissions.md.docs/play-compliance.md(expect Everyone / "Users Interact").docs/play-compliance.mdandfastlane/metadata/), 512x512 icon, 1024x500 feature graphic, 2-8 screenshots, category, contact info.PRIVACY.mdat a public URL and enter it (Play requires a reachable URL).docs/play-compliance.md).Dependencies
Groundwork #17 (done); the signing/secrets ticket; #19 (automated publish).