User Opt-in Consent

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. Additionally, the 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. BOINC needs to be extended to support both.

User Experience

When 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 agreement to the terms of use is recorded in the project's database.

For account managers (AM), AMs can download a site's terms of use from get_project_config.php. Then present this text to a user. It will be the responsibility of an AM to present the text along with a checkbox for the user to agree to. (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.

For Web registration, the login page can provide the terms of use text. Users will have to accept the terms of use before creating an account. This agreement will be stored in the project's database.

For existing accounts: A project may decide that existing accounts should also agree to a terms of use. This is a separate feature from the user agreement to a terms of use when registering an account. Existing users will have tto agree to a terms of use via a checkbox, and then that agreement is stored in the project's database.

Existing code

As of April 2018, BOINC already contains a 'terms of use' mechanism for the BOINC client when creating a new account. If the file 'terms_of_use.txt' (filename is hardcod-ed) is in the root of the project directory, the contents of the file will be presented to the user when s/he creates an account. However, there is no persistent 'storing' of the datetime the user consented to the terms of use.

For Web registration, the code does not use the TermsOfUse text. But it can be modified to do so.

Additionally, it is not known whether account managers, such as BAM!, use this terms-of-use mechanism.

boinccmd command-line client does not use the TermsOfUse mechanism. Thus when a user creates an account, s/he does not see any terms of use, even if it exists.

Lastly, the terms of use text file must be text. HTML should be supported, although this may be added later.

Technical Implementation

Project config

A new project option will be included in config.xml for projects, enable_login_mustagree_termsofuse option. This flag will toggle whether or not the project requires existing users to agree to the terms of us of the site. Note, a site may toggle the feature where new accounts are required to agree to a terms of use in the OPS page. This config parameter is independent of the OPS page (see below).


Two new tables: consent and consent_type

  • consent
    • id - primary key of table - a unique id for each row. Not used for the consent functionality.
    • userid - the user id
    • consent_type_id - consent type id, corresponds to the 'id' in the consent_type table.
    • consent_time - datetime type attribute : unixtime of when user id gave consent to consent_id.
    • consent_flag - the boolean which explicitly stats that this user id has given consent to this consent id. If this is 0 (FALSE), the following boolean should be 1 (TRUE).
    • consent_not_required - a special boolean that indicates whether or not consent is not required. This feature may be used by certain special ...
    • source - text field containing the technology actor which the user gave consent. See below
  • consent_type
    • id - consent type id, also the primary key.
    • shortname - consent name, these should be short and in ALLCAPS, e.g., ENROLL, STATSEXPORTS, etc. There should be no spaces either.
    • description - text field describing the consent that user gives (or has given).
    • enabled - if true, this consent type is enabled. This is toggled in the OPS page for managing consent types.
    • protected - if true, this consent type is introduced by BOINC upstream. If false this consent type project-specific, and was added by the project via the ops pages.
    • privacypref - if true, (and enabled), this consent type will be shows in the preferences page in the privacy section. This allows projects to add consent types which deal with user privacy; and no additional coding is necessary.


Some discussion on source string.


  • If a user gives consent by registering for an account using the BOINC GUI client (BOINC manager), source would be set to 'client'.
  • If the account is created on a Web site registration page, source would be set to 'web'.
  • Account Managers should put their name in, e.g. source = 'BAM!' or source = 'GridRepublic?'.
  • command-line client uses 'boinccmd'.
  • In the case where source is not specified (but consent is being used) then a default source of 'URL' can be used.
    • 'URL' represents the fact that a user can create an account using the RPC by typing the correct parameters into the URL bar of a browser, or using a command line tool such as curl.

Re: consent_type table

At first there will be two records in consent_type: the main terms-of-use a user consents to when joining the project (ENROLL) and a stats-exports consent type (STATSEXPORT). In effect, these are distributed by BOINC upstream. This allows for flexibility - a project may decide to present a user with multiple items to consent to. Each can be recorded in the consent table with a different consent_type_id, which corresponds to the row in the consent_type table, which contains the name and description. The protected field indicated a consent type that is introduced by BOINC upstream for all projects.

The enabled flag is fairly important. By default no consent types are enabled. The project admins may toggle this in the Manage Consent Types OPS page. If the 'ENROLL' type is enabled, users will have to agree to a terms of use when creating an account. (The terms of use file must also exist). Independently, if 'ENROLL' is enabled, and parameter 'enable_login_mustagree_termsofuse' is equal to 1 (TRUE), existing users must agree to the site's terms of use.

If 'STATSEXPORTS' type is enabled, users will see a new privacy preference option about statistics exports. They may give consent to this consent type in the user preference pages.

Re: consent table

Entries to this table are to be inserted for a userid and consent_name. This way a single user may consent to multiple policies. If a user withdraws consent, a new entry should be added. Effectively, no rows should be deleted from this table, only added. There may be a situation where a user has dozens of rows since s/he has given and withdrawn consent multiple times. This acts as a record of the user's consent to policies. The latest row, that is the row with last datetime, represents the current consent status.

The exception is when a user deletes his/her account. Then all consent table entries for that user's id are deleted.


RPCs that will need to change:

  • create_account.php
  • am_set_info.php

The main RPC that needs to be changed is create_account.php, which needs to insert a record into the consent table when the user creates his/her account- assuming s/he consents to a site's terms of use.

Additional parameters for create_account.php RPC are

  • consent_flag = 0|1 - If true, sets the consent_flag to 1. If false the consent_flag is set to 0 and consent_not_required is set to 1. See discussion of anonymous accounts above.
  • source = 'string'
    • example: 'client', see above discussion about source for more details.

am_set_info.php needs to be modified in order to contain a consent parameter, which also modifies the consent table in the database.

Additional parameters are

  • consent_name = 'string' - This is the shortname of the consent_type to insert a new entry for.
  • consent_flag - '0|1' - sets the consent_flag to 0 or 1.
  • consent_not_required - '0|1' - sets the consent_not_required flag to 0 or 1.
  • consent_source - 'string'
    • example: 'client', see above discussion about source for more details.

am_set_info.php is used to insert a new record into the consent table, but only if all four of these additional parameters are present. If one is not present, the consent table will not be modified. However, the RPC will not return a failure. This is to ensure backwards compatibility. If all four parameters above are set, as below, then the RPC will insert a new entry into the consent table.



The RPC is attempting to set the consent information for a consent_name of ENROLL. It will check of consent_name ENROLL exists. If it does not an error message will be returned.

Web site

The Web site account registration page will have a new panel that includes the terms of use text. This will be the same text file as TermsOfUse. The text file is processed with PHP's nl2br() function in order to format the plain text into text that is readable in HTML. Admins should not put HTML tags into the plain text TermsOfUse file. (In the future, we hope to make this HTML compatible.)

The registration page will have an additional checkbox that requires a user agree to the terms of use. If this is not checked, the account will not be created, and an error shown to the user. Only when the checkbox is checked, will an account be created. A new record will be inserted into the consent table, in the same manner as the create_account RPC.

OPS pages

In the ops pages, there is a new 'Manage Consent types' page. Here the admins may add additional consent types, enable/disable them, and set whether or not the consent type should appear in the privacy preferences. Admins may only delete consent types which are not 'protected', meaning they are not created from the BOINC upstream source code. Effectively, non-protected consent types are local to this project.

Anonymous Accounts

(to be written)

Last modified 10 days ago Last modified on 06/15/18 14:18:37