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
This commit is contained in:
parent
e01a27d7b7
commit
dbd9f2973c
15 changed files with 95 additions and 66 deletions
|
|
@ -83,9 +83,8 @@ const config: ShipConfig = {
|
|||
// Export to CSV before the first import. The delete-account URL (PSL_ACCOUNT_DELETION_URL) comes from
|
||||
// accounts.deletionUrl; `storebound check` names any other row Play requires.
|
||||
accountCreation: ['PSL_ACM_USER_ID_PASSWORD'],
|
||||
// Play asks this once there are accounts (PSL_SUPPORT_DATA_DELETION_BY_USER, one choice): can people request that some
|
||||
// or all of their data is deleted without deleting the account? true | false | 'auto90' (no, but it is deleted
|
||||
// automatically within 90 days). Ask the owner. true also needs a page: partialDeletionUrl (default accounts.deletionUrl).
|
||||
// Can people delete their data without deleting the account (a data-only page)? true needs partialDeletionUrl.
|
||||
// Play's "can users request deletion?" is answered yes by accounts.deletionUrl. Ask the owner.
|
||||
partialDeletion: false,
|
||||
data: {
|
||||
PSL_EMAIL: { shared: false, collect: ['functionality', 'account'] },
|
||||
|
|
|
|||
|
|
@ -111,9 +111,8 @@ const config: ShipConfig = {
|
|||
// Export to CSV before the first import. The delete-account URL (PSL_ACCOUNT_DELETION_URL) comes from
|
||||
// accounts.deletionUrl; `storebound check` names any other row Play requires.
|
||||
accountCreation: ['PSL_ACM_USER_ID_PASSWORD'],
|
||||
// Play asks this once there are accounts (PSL_SUPPORT_DATA_DELETION_BY_USER, one choice): can people request that some
|
||||
// or all of their data is deleted without deleting the account? true | false | 'auto90' (no, but it is deleted
|
||||
// automatically within 90 days). Ask the owner. true also needs a page: partialDeletionUrl (default accounts.deletionUrl).
|
||||
// Can people delete their data without deleting the account (a data-only page)? true needs partialDeletionUrl.
|
||||
// Play's "can users request deletion?" is answered yes by accounts.deletionUrl. Ask the owner.
|
||||
partialDeletion: false,
|
||||
data: {
|
||||
PSL_EMAIL: { shared: false, collect: ['functionality', 'account'] },
|
||||
|
|
|
|||
|
|
@ -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: {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue