Closed jensneuhaus closed 4 years ago
Here is an update on the Account info:
account_info_link
/ last_account_info_created
to the User modelACCOUNT_INFO_AUTOMATED=True
(True is default) - if False, only the email is sentPOST /users/me/account_data
ACCOUNT_INFO_ASKED_FOR_EMAIL
, default GDPR_ADMINISTRATOR_EMAIL
- send an email send_account_info_asked_for_email
if it is not Noneaccount_info_link
hash (64 chars or longer)account_info_is_ready
to the Usersend_account_info
handling as part of daily_tasks
commandaccount_info_link != None
and no last_account_info_created
datetime > ACCOUNT_INFO_LINK_AVAILABILITY_IN_DAYS
, delete the account_info_link
GET /users/me/account_data/<account_info_link>
account_info_link
hash like thisACCOUNT_INFO_HANDLER
for collect the data, default is our handler
'gdpr.utils.account_info_handler'
user
data (name, email, username, last login, etc.)Hello Jens,
thanks for your interest in the data . You can access your report here:
<PUBLIC_URL>/account-data/<account_info_link>/
For security reasons it will be deleted after <ACCOUNT_INFO_LINK_AVAILABILITY_IN_DAYS>.
Fore more infos and any questions related to your privacy please write to <GDPR_SUPPORT_EMAIL >
@jensneuhaus I didn't find anything about bcc in a Saasy documentation. May I ask you to tell how it works in the Saasy? At the moment I'm just sending two letters: one to the user, and the second to the admin
Can you please create an Issue for this in saasy (if access) and also one on the Boilerplate repo with a link to the Code lines which need to change, if we have BCC working?Am 13.02.2020 15:30 schrieb Vladislav Borisov notifications@github.com:@jensneuhaus I didn't find anything about bcc in a Saasy documentation. May I ask you to tell how it works in the Saasy? At the moment I'm just sending two letters: one to the user, and the second to the admin
—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or unsubscribe.
☝️What is it? Why do we need it?
Inactive account handling
Delete an account with some informations to him, when the user was inactive for too long
User deletes his account
The user decides to delete his account, we keep it for a few days
Send all existing user informations to email
The user can ask to send all data
📋 Todos
gdpr
GDPR_ADMINISTRATOR_EMAIL
, defaultNone
GDPR_SUPPORT_EMAIL
, default isGDPR_ADMINISTRATOR_EMAIL
daily_tasks
commandINACTIVE_ACCOUNT_DELETION_IN_WEEKS
, default52
INACTIVE_ACCOUNT_DELETION_IN_WEEKS
can beNone
- then there is no such logicINACTIVE_ACCOUNT_WARNING_IN_WEEKS
, default =1,4
(it means, we remind 1 week and 4 week before it ends)INACTIVE_ACCOUNT_DELETION_BCC_EMAIL
, defaultGDPR_ADMINISTRATOR_EMAIL
, do not send an BCC email ifNone
INACTIVE_ACCOUNT_WARNING_BCC_EMAIL
, defaultGDPR_ADMINISTRATOR_EMAIL
, do not send an BCC email ifNone
52
+ Warning54
makes no sense.. or if it is set to Nonesend_warning_about_upcoming_account_deletion
Email (use BCC!)send_warning_about_upcoming_account_deletion
handling as part ofdaily_tasks
command; use BCC mailsend_inactive_account_was_deleted_email
Email (use BCC!)send_inactive_account_was_deleted_email
handling as part ofdaily_tasks
command; use BCC mailDELETE /users/me
?is_deleted
ACCOUNT_DELETION_RETENTION_IN_DAYS
, default7
; if set to0
the Account is deleted right awayACCOUNT_SCHEDULED_FOR_DELETION_BCC_EMAIL
, defaultGDPR_ADMINISTRATOR_EMAIL
, do not send an BCC email if NoneACCOUNT_DELETED_BCC_EMAIL
, defaultGDPR_ADMINISTRATOR_EMAIL
, do not send an BCC email if Nonesend_account_scheduled_for_deletion_email
Email (if not0
days of retention)send_account_scheduled_for_deletion_email
handling as part ofdaily_tasks
command; use BCC mailsend_account_was_deleted_email
Emailsend_account_was_deleted_email
handling as part ofdaily_tasks
command; use BCC mailsend_account_was_recovered_email
Email then