nanoColab · Personally operated pilot
Privacy notice
Last updated:
Information we use
- Account details, password hashes and sessions provide competition access.
- Notebooks, files and outputs support your work and recovery.
- Activity and security logs, which may include IP addresses, support security and troubleshooting.
- Administrator Google sign-in uses your account identifier, verified email and authentication information. We do not receive your Google password or access Gmail messages or Google Drive files.
Who can access information
Authorized administrators can access retained work for support and recovery. Authorized committee members may also use it for grading under the event instructions. A saved notebook is not automatically an official submission.
We use Google Cloud for hosting and storage, and Google Identity Services for administrator sign-in. Do not store unrelated private information or personal credentials in notebooks.
Retention and deletion
Competitor accounts are scheduled for deletion within one calendar year of the event’s end; unassigned/draft accounts use creation time and retired multi-event accounts use their earliest event end.
Metadata, deletion receipts, provider logs and backups are separate. Provider logs currently include 30-day general and 400-day infrastructure-audit retention. These rules do not mean all data disappear together.
Sign-in and browser storage
The portal stores sign-in details in browser session storage. JupyterHub and Google use their own authentication mechanisms, including cookies. Portal sign-out does not stop notebooks or end every session; use separate browser profiles for different accounts.
Questions and requests
Email aleksisdatseris@gmail.com about access, correction, deletion or other applicable data rights. Identity verification may be needed. You may complain to Bulgaria’s Commission for Personal Data Protection. Never send passwords or tokens.
See the platform terms and your event instructions.