CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity Actions

play data-safety: PSL_SUPPORT_DATA_DELETION_BY_USER as Play's single choice (partialDeletion true | false | 'auto90'), drop the removed PSL_DATA_COLLECTION_USER_REQUEST_DELETE (deletionRequest deprecated, check notes it); ship Google's empty form (cli/data/play-data-safety-form.csv, exported 2026-10-12), take every Answer requirement from it and report pairs not in it (formPairIssues) in check, declarations and play data-safety. Pitfall 21

Browse source
This commit is contained in:
CRTkafa 2026-10-12 09:33:56 +08:00
parent dfc28c15f8
commit b5b8f2da9d
35 changed files with 1824 additions and 859 deletions
Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -1003,8 +1003,9 @@ Checked against each tool's own docs in October 2026:
offer tag, the ISO 8601 strings for Play billing periods (Google lists them only in words), the Play subscription
benefit length (40, from Play Console), the Data safety sign-up method ids (`PSL_ACM_*`, Google publishes none:
compare with a Console export) and the data deletion question ids (`PSL_ACCOUNT_DELETION_URL` is confirmed by a
Play 400; `PSL_SUPPORT_DATA_DELETION_BY_USER` and `PSL_DATA_DELETION_URL` come from reported Play answers, override
with `dataSafety.extra` if an export differs). From the store
Play 400; `PSL_SUPPORT_DATA_DELETION_BY_USER` with its three options and `PSL_DATA_DELETION_URL` are in Google's
empty form exported 2026-10-12, `cli/data/play-data-safety-form.csv`, which every generated pair is checked
against). From the store
operations (built from the App Store Connect API 4.5.1 OpenAPI spec and the cited Help pages, tested with recorded
answers, not yet run live): the first IAP of a type sent through `reviewSubmissionItems` next to the app version
(`--no-submit` leaves the draft for the UI if Apple refuses it), free IAP offer code and win-back prices without a