Security and data protection

At PULSE, security has been part of the architecture from the start. This page lists what we actually do to keep study data protected.

Data protection

Participants stay pseudonymous. They enroll with a study code, without name or email, and grant each sensing module individually.

  • Pseudonymous participation via study code
  • Consent per sensor, visible beforehand
  • Servers and backups in Germany

Access

Only your project team accesses study data. Every sign-in needs a second factor, every action is logged.

  • Mandatory two-factor in the admin panel (TOTP)
  • Roles and rights per project team
  • Audit log of all actions, including failed sign-ins

Technology and operations

Data is encrypted in transit and, at critical points, in the database. The infrastructure is isolated and monitored.

  • TLS for all connections, HTTPS with HSTS
  • Sensitive fields encrypted with AES-256-GCM
  • Passwords stored with bcrypt

Documents

Everything your data protection officers and ethics committee need, before you sign.

  • Data processing agreement (DPA)
  • Technical and organizational measures (TOM)
  • Template for the participant privacy notice
Request documents