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 is the general 'can users request deletion?' question; a delete-account URL answers yes (with PSL_DATA_DELETION_URL), dataSafety.dataDeletion for apps without one; check flags a no next to a delete-account URL

Browse source
This commit is contained in:
CRTkafa 2026-10-12 09:46:58 +08:00
parent e01a27d7b7
commit dbd9f2973c
15 changed files with 95 additions and 66 deletions
Download patch file Download diff file Expand all files Collapse all files

7
templates/storebound.config.ts
View file

@ -102,10 +102,9 @@ const config: ShipConfig = {
// No accounts: PSL_ACM_NONE. A guest account with a name picked on the device and a server token (no password, no
// email): accounts { enabled: true, signUp: ['username'], ... } and ['PSL_ACM_USER_ID_OTHER_AUTH'] here (Play's
// "Username and other authentication"; `storebound scan` proposes it). With accounts Play also requires the
// delete-account URL (from accounts.deletionUrl) and partialDeletion: true | false | 'auto90' (people can request
// that data is deleted without deleting the account / they cannot / it is deleted automatically within 90 days; ask
// the owner), plus partialDeletionUrl when true (default accounts.deletionUrl). Play removed the old "users can request
// deletion" question, so there is no deletionRequest any more. `storebound check` compares every row with Play's
// delete-account URL (from accounts.deletionUrl). That page also answers "can users request that their data is
// deleted?" with yes (dataDeletion: 'yes' | 'no' | 'auto90' only for apps without one). partialDeletion: true +
// partialDeletionUrl when a page deletes data without deleting the account. `storebound check` compares every row with Play's
// current form (cli/data/play-data-safety-form.csv).
accountCreation: ['PSL_ACM_NONE'],
data: {