Introduction

This document outlines the event, critical dates, and service changes to enable a smooth rollout of the new terms of service (ToS) and managed plans.

Critical Dates

• ToS-Notifiation-Date - The date the new ToS will be emailed to ALL Synapse user. → Oct 15, 2024

• ToS-Available-Date - The date the new ToS will be available to be signed by Synapse users. → 1 Nov, 2024

• ToS-Enforcment-Date - The date when the Synapse API will reject any authenticated request from a user that as not agreed to the new ToS. → Nov 15, 2024

• New-Project-Automatic-Limit-Date - From this date forward any new project that uses the default Synapse will automatically limited to 100 GB by the Synapse back-end servers.

Requirements

ToS

1. Synapse will provide a new API that will allow all clients (both UI & command line) to register that a user has agreed to a specific version of the ToS. The version of the ToS shown to the user and the date/time of the agreement will be permanently saved for that user.

2. The version of the ToS must be a Semantic Version.

3. The client is responsible to correctly identify the semantic version of the ToS that was shown to the user before making the agreement API call. The server will not attempt to infer the version based on the date/time when the user agrees.

4. All existing users that have agreed to the original ToS will have an entry that shows they agreed to version ‘0.0.0’ of the ToS on the date that their account was created. Note: We did not capture the date when users agreed to the original ToS, so we will use the date their account was created as a proxy for this date.

5. If the user later agrees to a newer version of the ToS a new entry will be made to capture the newer ToS version number and date of agreement. The full history of previous agreements must be maintained.

6. The Synapse back-end will provide a new API that will allow any member of the Access and Compliance Team (ACT) or Admin, to set the date when a specific version of the ToS is required by all users.

   1. This service will accept a semantic version and an enforcement date.

      1. The semantic version is the minimum version number of the ToS that the users will be expected agree to.

      2. The provided date is the date when Synapse API will enforce the new ToS.

   2. The Synapse back-end will reject any authenticated request from any user that has not agreed to the set minimum semantic version starting on the set date.

Limit Synapse Storage

1. The Synapse back-end will add a new API that will provide the sum of the number of bytes consumed by files stored in the default Synapse storage location for each project. This sum will only be available for users with the UserEntityPermissions.hasUpload=true.

2. The Synapse back-end will maintain a record of the maximum number of bytes of files in the default Synapse storage location for each project, both old and new.

3. The Synapse back-end will add a new API that will provide the limit for each project. This limit will only be available to users with the UserEntityPermissions.hasUpload=true.

4. Once a project has exceed its limit on the number of bytes in the default Synapse storage location, the Synapse API will block any attempt to add new files to that storage location within that project.

5. Initially all existing project will automatically have a limit set to “unlimited”.

6. Starting on the New-Project-Automatic-Limit-Date, any newly created project will automatically be assigned a limit of 100 GB.

7. The Synapse back-end will add a new API that will allow any user belonging to the “data managers” team to set the limit on the default storage location for any project.

8. The “data managers” team is responsible for overriding all default storage limits on all projects.

9. The Synapse UI will show a “progress” bar on each project page to any user with the “create” permission on the project. The progress bar shows how close a project is to its limit.