Security
A summary of how Wardeye is designed to protect your data. We are an early-stage company and say plainly what we have and have not done.
Design principles
- Keep biometrics local. Face and voice templates are made and stored on the organisation’s Mac, not in our cloud. Remote enrolment media is encrypted on the phone to the Mac’s key (X25519, HKDF-SHA256, ChaCha20-Poly1305) so our servers only hold ciphertext.
- Do not record calls. Call detection checks whether the mic or camera is in use. Nothing is recorded or uploaded.
- Least privilege email access. The optional Microsoft 365 connector asks for read-only mail access to the connecting person’s own mailbox. It cannot send or change mail. Message bodies are not stored. Refresh tokens are encrypted, and disconnecting removes them.
- Out-of-band confirmation. Approvals are answered on the principal’s own phone with Face ID or passcode, so a compromised call or email channel cannot approve itself.
Platform controls
- TLS for all traffic; HSTS and a strict Content-Security-Policy on this site.
- Per-row access control (Postgres row-level security) so users see only their organisation’s data; service-role keys never ship to browsers or apps.
- Passwordless sign-in (email one-time code or Microsoft), so there are no passwords for us to lose.
- Signed and Apple-notarised Mac app with signed automatic updates (Sparkle).
- Stripe handles card data; we never see card numbers.
What we have not done yet
Wardeye has not completed a SOC 2 or ISO 27001 audit or an independent penetration test. If your procurement process requires one, tell us; it informs our roadmap. We can answer security questionnaires and sign a DPA on request.
Report a vulnerability
Email wardeye@odysseydevelopments.dev with details and steps to reproduce. We will acknowledge within 3 business days. Please give us reasonable time to fix before public disclosure, do not access other people’s data beyond what is needed to show the issue, and do not degrade the service. We will not pursue legal action against good-faith research that follows these rules. See also security.txt.
Incidents
If an incident affects your data we will tell affected customers without undue delay and in line with applicable law.