Data security
Your emergency and health data is sensitive. This page describes the technical safeguards implemented in our application.
Controlled access to the emergency pass
- The public emergency pass can only be reached via a random access token (QR code) or the printed ID number.
- Unknown, deactivated, locked or hidden codes all return the same "not found" response, so it is not possible to tell whether a code exists.
- Public lookups are rate-limited per request source to make systematic guessing of codes harder.
- You decide per field which data is visible on the emergency pass. If you regenerate the QR code and link, all previous codes become invalid.
Sign-in and account
- Passwords are not stored in plain text but as bcrypt hashes.
- Sessions use signed tokens (JWT, HS256) stored in httpOnly cookies, so scripts in the browser cannot read them.
- You can optionally enable two-factor authentication (authenticator app or code by email). Authenticator secrets are stored encrypted with AES-GCM; recovery codes are stored only as bcrypt hashes.
- Sign-in attempts are rate-limited. For suspicious activity a Cloudflare Turnstile security check is additionally required.
Transmission and cookies
- In production, session cookies are set with the Secure flag and SameSite=Lax, i.e. they are only sent over encrypted connections.
- Details on the cookies in use can be found in our cookie policy.
Payments
- Payment processing for paid plans is handled by the payment provider Stripe.
Deletion
- You can delete your account yourself. Deletion is confirmed via a link sent to your email address. Orders and invoices are retained as required by tax law.
More information
Detailed information on the processing of personal data can be found in the privacy policy. Please direct security questions to info@sosid.net.