Trust
Security
Janus holds records of who enters your buildings. This page sets out how that information is protected.
Where your data lives
Janus runs from New Zealand infrastructure. Each workspace's data is isolated by tenant at the database layer. Every query is scoped to the workspace it belongs to, enforced in the data-access layer rather than in application code.
Encryption
All traffic is encrypted with TLS: the kiosk, the QR sign-in pages, the dashboard and the API. Passwords are hashed with bcrypt; API keys are stored only as SHA-256 digests, shown once at creation; webhook deliveries are HMAC-signed so receivers can verify them.
Backups
The database is dumped nightly with rolling daily, weekly and monthly retention, and a copy is shipped off the server every night to separate object storage. Restore procedures are tested, not assumed.
Monitoring
Public services are monitored continuously. A failed check alerts the operator and opens a tracked incident, and the status page shows current status at any time.
Access and privacy controls
Role-based permissions govern every dashboard action. Workspaces can anonymise a visitor on request, or set a retention policy that anonymises inactive visitors automatically, removing names, contact details, photos and signatures while preserving visit statistics. Every anonymisation is recorded in the audit log.
Access boundaries
Kiosks are paired devices with revocable tokens. Public QR pages cannot enumerate your people: host search requires a typed match and email addresses are masked. Rate limits apply to every public endpoint, and outbound texts are guarded against duplicate sends.
Questions or reports
For security reports, or if you need this information in more detail for procurement, contact [email protected]. Security reports receive a prompt reply from a person.