← SeqDesk Lab

HZI collaboration service

A shared space for your lab.

Chat, tasks, projects, people, and a shared notepad for research groups. The HZI-hosted service connects invited colleagues in separate lab workspaces through SeqDesk Lab.

Hosted by HZILab membership requiredSSO in preparation

01 / The service

One service. Separate labs.

The Helmholtz Centre for Infection Research (HZI) operates this collaboration instance. Each lab has its own workspace, members, administrators, and access permissions. Joining one lab does not grant access to another lab on the same server.

Application
SeqDesk Lab for macOS
Service address
seqdesk-mail.bifo.helmholtz-hzi.de
Operator
Helmholtz Centre for Infection Research · Germany

This page describes the HZI instance. A lab running its own server manages its own access, hosting, and privacy arrangements.

02 / Joining a lab

Access comes from your lab membership.

To join a lab from the Mac app:

  1. Ask your lab administrator for a personal invitation.
  2. Open SeqDesk Lab and go to Settings → Collaboration.
  3. Paste the invitation, review the lab and role, and confirm joining.
  4. Choose which available collaboration features to synchronize.

For shared chat and tasks in your browser, open in browser. Sign-in is handled by the HZI server. Once SSO is configured and your identity is assigned to a lab, you return to the app and choose your workspace.

The invitation is your joining credential: keep it private. Collaboration is optional, and joining does not upload your mailbox. The Mac app currently connects each mail account to one lab at a time.

03 / Privacy notice

What collaboration shares and keeps.

Scope and purpose

This notice concerns collaboration on the HZI service, including membership, sharing, synchronization, and administration. These functions use personal data to identify contributors, control access, deliver shared work, and investigate service problems. Mail connections and optional AI features have their own configured destinations and are outside this notice.

Visiting this information page is covered separately by the website privacy policy. The website and the HZI collaboration server are separate services.

Data processed by the service

  • Membership: display name, work email address, lab membership, role, permissions, and invitation records.
  • Shared work: messages, replies, files, tasks, notepad contributions, lab directory profiles and groups, and project information. Profiles can include work contact details and positions; projects can include funding and timelines.
  • Synchronization: author and device identifiers, device labels, timestamps, and records of shared changes. Access credentials authenticate requests; the server stores credential hashes.
  • Administration and diagnostics: audit records of administrative and membership actions, including the action, actor, target, time, and client IP address, plus operational logs. Online and away presence is temporary and held in memory.

Collaboration does not synchronize your mailbox, mailbox password, private notes or tasks, private contacts, or private personnel and salary records. Information you copy into a shared message, file, or record becomes shared content, including copied email text.

Who can access shared data

Authorized lab members can access shared features according to their permissions. The membership directory identifies colleagues in the lab. Assigning a shared task to one person does not make the task private. Lab administrators manage access and can inspect their lab’s audit trail.

Collaboration is not end-to-end encrypted. Operators with access to the server or its backups can access stored data. HZI must confirm the operational access arrangements, hosting and backup locations, and any service providers as part of finalizing this notice.

History, deletion, and local copies

Revoking a membership on the server stops future access for that member. Leaving a lab or revoking access does not erase earlier contributions, audit records, or downloaded copies, including copies on a former member’s devices.

Shared edits and deletions are recorded in the synchronization history, so earlier text and file metadata can remain there. Deleting a message or channel removes its attached file bytes from active storage; backups and downloaded copies may retain them. Unsent file uploads expire after seven days. That period does not apply to messages, memberships, audit records, or backups.

The service’s overall retention periods and deletion process have not yet been specified for this notice.

Using the browser app

Vercel serves the browser interface. The interface communicates directly with the HZI server for authentication and collaboration; shared data is not proxied through the website. The interface code runs in your browser and can access the shared content it displays.

The browser retains downloaded collaboration content, drafts, and pending changes in local site storage. Signing out does not erase that storage. Clearing this site’s browser data removes those local copies, including unsent changes.

In the SSO implementation, the application session lasts at most eight hours and its token stays in memory. Reloading requires sign-in again. The temporary sign-in proof lasts at most ten minutes; identity-provider tokens and the client secret stay out of the browser interface.

Planned SSO identity processing

The planned LS Login integration will use identity information to connect a sign-in to an approved lab membership. The exact attributes received, session handling, and retention must be documented here before SSO is enabled. The current invitation flow does not use LS Login.

Questions and data protection rights

Contact the project or HZI’s Data Protection Officer below about your data. Depending on the applicable conditions, GDPR rights include access, correction, erasure, restriction, portability, and objection. You may also complain to a data protection supervisory authority. See HZI’s data protection information.

Decisions needed before finalization

  • Confirm the controller arrangements and legal basis for each processing purpose.
  • Set retention and deletion rules for collaboration history, identities, audit records, operational logs, and backups.
  • Confirm hosting, backup locations, operator access, service providers, and any international transfers.
  • Define how access, correction, and deletion requests are handled.
  • Document the deployed SSO attributes and session lifecycle before enabling sign-in.

04 / Contacts

Talk to the people responsible.

Service operator

Helmholtz-Zentrum für Infektionsforschung GmbH
Inhoffenstraße 7
38124 Braunschweig, Germany

Legal information

Project contact

Philipp Münch
Bioinformatics of Infection Research

pmu15@helmholtz-hzi.de

Data Protection Officer

Helmholtz Centre for Infection Research

datenschutz@helmholtz-hzi.de

Draft updated .