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

play data-safety: write the conditional required rows (PSL_ACCOUNT_DELETION_URL from accounts.deletionUrl, PSL_SUPPORT_DATA_DELETION_BY_USER from dataSafety.partialDeletion, PSL_DATA_DELETION_URL); a rule table checks every conditional row in check, declarations and --dry before Play answers 400

Browse source
This commit is contained in:
CRTkafa 2026-10-12 08:25:14 +08:00
parent c9a7f095c4
commit 97ab76e9c8
14 changed files with 295 additions and 24 deletions
Download patch file Download diff file Expand all files Collapse all files

4
templates/storebound.config.ts
View file

@ -102,7 +102,9 @@ const config: ShipConfig = {
deletionRequest: true, // e.g. "email us"; no accounts, so no account deletion URL needed
// 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).
// "Username and other authentication"; `storebound scan` proposes it). With accounts Play also requires the
// delete-account URL (from accounts.deletionUrl) and partialDeletion: true | false (delete data without deleting the
// account; ask the owner), plus partialDeletionUrl when true (default accounts.deletionUrl).
accountCreation: ['PSL_ACM_NONE'],
data: {
PSL_APPROX_LOCATION: { shared: true, collect: ['analytics', 'advertising', 'fraud'], share: ['analytics', 'advertising', 'fraud'] },