...

The use of JupyterHub in DSS as described in these Terms of Use is hereinafter referred to as ‘DSS JupyterHub Service’ or ‘Service’.

Registration

DSS JupyterHub Service is available to all DSS users registered with the respective data store, serviced by DSS. No additional registration is needed.

...

with the following environment.yml file described in the Pre-installed software section of the complete technical description of the DSS JupyterHub Service.

DSS users can install additional packages from the  condaconda-forge channel (`conda install PACKAGE-NAME`), or from PyPi (`pip install PACKAGE-NAME`). These packages will be installed in the DSS user’s private storage Private Storage and will be available next time the DSS user creates a session. For such packages and other software, additionally installed by the DSS user Article Articles 5.3-5.4 5 below shall apply.

User Storage

DSS JupyterHub Service is provided with two forms of storage: Private and Scratch, as described below. 

Private Storage

Each DSS user has Private Storage allocation, which is accessible only to the given DSS user. For the size of this private storage alllocation, please refer to the technical description of the DSS JupyterHub Service.

If a Private Storage is not accessed (i.e., by spawning a session) for a period of thirty-one (31) consecutive days, this Private Storage together with its contents may be deleted in its entirety.

...

Each DSS user will have a temporary Scratch Storage , which represents 100Gb with a maximum quota per each DSS user on a temporary scratch disk. For the size of the the maximum quota, please refer to the technical description of the DSS JupyterHub Service. If the individual quota is exceeded, automated scripts will delete the oldest files (in terms of file modification time) until the quota is no longer exceeded.

Should the individual DSS user circumvent the quota, in addition to any other rights available under these Terms of Use, ECMWF reserves the right to delete any files stored in the Scratch Storage of the DSS user.

...

DSS users are responsible for ensuring that the use of the DSS JupyterHub Service, as well as any data, content and information stored on DSS infrastructure is aligned with the purposes, objectives and activities of ECMWF and the Copernicus services (C3S, CAMS and CEMS) and is in compliance with the applicable laws.

...

Use of third-party software either pre-installed on the DSS infrastructure or installed by the DSS user shall be in line with the applicable third- party software license.

...

ECMWF may at its sole discretion, under any circumstances, for any or no reason and with or without prior notice to the DSS users, suspend, terminate or restrict any DSS user’s access to the DSS JupyterHub Service, particularly in cases of violation of these Terms of Use or any of the applicable license terms .

Exclusion of Liability and Warranties

or if a Private Storage is not accessed (i.e., by spawning a session) for a certain period of time beyond thirty-one (31) consecutive days.

Exclusion of Liability and Warranties

Other than Other than in cases of intentional or grossly negligent breaches of duty by its staff or representatives or claims resting on an injury to life, body or health, neither ECMWF nor the respective data provider, nor any other third-party copyright holder/contributor of the data or the software used ) shall be responsible or liable to any user of the DSS and/or the DSS JupyterHub Service for any loss or damage of any sort incurred in connection with the use of the DSS JupyterHub Service.

ECMWF and/or the respective data provider and/or any other third-party copyright holder of the data or the software used ( shall not be responsible or liable for the accuracy, usefulness or availability of the DSS JupyterHub Service.

...

ECMWF and the respective data provider and any other third-party copyright holder/contributor of the data or the software used disclaim all warranties related to the provision of DSS JupyterHub Service.

The DSS user are is liable for the consequences of any violation of these Terms of Use. 

...

Nothing in or relating to these Terms of Use shall be deemed a waiver of any of the privileges and immunities of ECMWF in conformity with their respective Protocols its Protocol on the Privileges and Immunities.

...

ECMWF Data Protection and Privacy Statement applies to all personal data provided by the DSS user in order to use the DSS JupyterHub Service.

Severability

Categories of Personal Data Processed

The personal data processed when using DSS JupyterHub Service is the personal data contained in either or both of these two types of data:

User Data

User Data, such as: (i) data provided to ECMWF by the DSS user through DSS JupyterHub Service in the DSS user’s account, environments and/or storage, and data that the DSS user derives from that data through their use of DSS JupyterHub Service; or (ii) data submitted, stored, sent or received by or on behalf of the DSS user via the DSS JupyterHub Service under the account of the DSS user and/or DSS user’s environments and/or storage.

The DSS user acknowledges that given the nature of the DSS JupyterHub Service, ECMWF will not able to verify the types of personal data that may be contained in the respective DSS user’s account, environments and/or storage. In order to maintain an accurate record, the DSS user will notify ECMWF if any of the personal data types listed below are not processed in the DSS user’s account, environments and/or storage.

The following types of personal data are generally contained in a DSS user’s account, environments and/or storage and/or can be processed within the DSS JupyterHub Service: basic personal information about the identity of an individual (such as name, address, phone number, email) and personal data contained in credentials for access to data stores and/or other services.

Service data

Data that ECMWF collects or generates during the provision and administration of the DSS JupyterHub Service and related technical support, excluding the User Data. The Service Data consists of: (i) account information (username, names, contact details and job titles); (ii) any data that may be contained or provided by the DSS user with respect to the DSS JupyterHub Service settings and configurations, including resource identifiers and attributes, and service and security settings for data and other resources; (iii) technical and operational details of the usage of the DSS JupyterHub Service by the DSS user (usage, operational status, software errors and crash reports, authentication details, quality and performance metrics, and other technical details necessary to operate and maintain cloud services and related software, incl. device identifiers, identifiers from cookies or tokens, and IP addresses); (iv) direct communications of the DSS user with ECMWF and its partners (user feedback, questions, request for technical support).

Purpose(s) of the Processing

ECMWF collects and processes the personal data under Article 13.1 above for the provision, administration, security and improvement of the DSS JupyterHub Service and related technical support in line with these Terms of Use, as well as according to DSS user’s use of the features of the DSS JupyterHub Service.

Obligations of the DSS user

The DSS user shall comply with the respective obligations under the applicable data protection laws and shall not use DSS JupyterHub Service in a manner that would violate such applicable data protection laws. The DSS user is responsible for not including any personal data that is not designed to be processed by ECMWF or the DSS user for the provisioning or use of the DSS JupyterHub Service. The DSS user shall not include personal data in text fields that are not intended for or do not request personal data. The DSS user is responsible to decide if the DSS JupyterHub Service, including its security features, functions and certifications, is appropriate for personal data and other regulated content.

ECMWF Data Protection and Privacy Statement

ECMWF Data Protection and Privacy Statement applies supplementary to the above-listed provisions of this Article 13.

Severability

If any provision of these Terms of Use If any provision of these Terms of Use is for any reason held to be invalid, illegal or otherwise unenforceable, such unforceability unenforceability does not affect any other provision; the Terms of Use are then to be construed as if they had never contained the provision(s) in question and are to be interpreted, in so far as possible, in such a way as to maintain their original intent.

Version 1.0 2 (November 2024March 2025)