Changes between Version 13 and Version 14 of UserOptInConsent


Ignore:
Timestamp:
May 31, 2018, 4:41:57 AM (6 years ago)
Author:
brevilo
Comment:

Fixed legally incorrect statement and typos

Legend:

Unmodified
Added
Removed
Modified

  • UserOptInConsent

    v13 v14  
    11= User Opt-in Consent =
    22
    3 The [https://en.wikipedia.org/wiki/General_Data_Protection_Regulation European GDPR law] requires users to opt-in to a terms of service. "Users who want to sign-up to a (BOINC) project need to give their informed explicit consent to how the project processes their data, before any personally identifiable information about that new user gets processed/stored by the project. This opt-in statement of consent then needs to tracked by the project as proof."
    4 
    5 Additionally, existing users will need to opt-in to the same terms of service, with their consent date saved.
     3The [https://en.wikipedia.org/wiki/General_Data_Protection_Regulation European GDPR law] requires projects to ask their users for consent before they are allowed to process personal information in certain ways, e.g. export user details to external statistic services. Additionally, projects may want to establish general terms of use their users have to explicitly accept during sign-up and potentially also for the continued of an existing accounts.
    64
    75== User Experience ==
    86
    9 When using the main BOINC manager to join a project (Add Project), the user is shown a Terms of Use / Porject policy text. S/he must accept the terms of use before the account is created. As part of the account creation process, the date-time of this consent is recorded in the project's database.
     7When using the main BOINC manager to join a project (Add Project), the user is shown a Terms of Use / Project policy text. S/he must accept the terms of use before the account is created. As part of the account creation process, the date-time of this consent is recorded in the project's database.
    108
    119For account managers, AM can download a site's terms of use from `get_project_config.php`. Then present this to a user. It will be the responsibility of an AM to present the text along with a checkbox for the user to opt-in. (It must not be passive.) The `create_account.php` RPC will be modified slightly for AM to set a consent flag. Additionally, the `am_set_info.php` RPC will be modified to allow AM to update the a user's consent information.