Skip to content

Face check-in is here: 1:1, liveness-checked, consent first

Security

Last updated 11 November 2026 · version 2026-11-11

How Musterwise keeps each organisation’s data separate, protected and accountable. Report a vulnerability to [email protected].

Isolation between organisations

Every organisation’s data is separated in the database itself with row-level security, and every query also filters by organisation. Tenant companies in a shared building see only their own people and visits. Automated tests check that one organisation cannot read another’s data.

Encryption

All traffic uses HTTPS with HSTS (one year, including subdomains), a strict Content Security Policy and framing blocked. Face references are encrypted with AES-256-GCM using a key derived per organisation. Passwords and kiosk PINs are hashed (argon2id for PINs); API keys are stored only as hashes and shown once.

Tamper-evident audit log

Every change and every override is written to an append-only audit log in the same transaction. Each entry is hash-chained to the previous one, so editing history breaks the chain; the integrity check is available to administrators. Personal details can be erased for GDPR without breaking the chain.

Access control

Roles decide what each person can do, and site-scoped roles see only their sites. Overrides at the security desk need a written reason. Two-factor authentication is available to every user. Webhooks are signed (HMAC-SHA256) and the API uses scoped keys.

Face check-in

Off by default, opt-in per person with recorded consent, 1:1 verification with liveness, never used to infer attributes, deleted on withdrawal. A non-biometric alternative is always available.

Operations

Daily encrypted database backups, restore tests, automatic roll-back of failed deploys, health checks and rate limits on public endpoints. Staff access to production is limited to what is needed to run the service.

Reporting a vulnerability

Please email [email protected] with details and give us reasonable time to fix the issue before disclosing it. We do not take action against good-faith research that avoids privacy violations and service disruption.

Questions: [email protected]