SafeZone keeps your company's 2FA secrets in one locked-down place and only ever hands out the live code, to the right person, for the 30 seconds it's valid.
The bank code lives on the finance manager's phone. The social accounts are on the phone of whoever set them up two years ago. And somewhere there's a spreadsheet of "backup" secrets.
The person with the phone is away, and payroll has to go out today.
Nobody is quite sure which accounts they can still get into.
A customer, auditor or insurer wants to know who has access to what. The answer is "let us get back to you".
The people using the codes never hold the secret itself. There's nothing to copy, nothing left on a phone when they leave, and nothing to leak from a laptop. Remove someone's access and they're done, on the spot. Need a secret out again? An export takes a second person's approval.
SafeZone isn't in production yet. We built the hard part first: how secrets are stored, who can reach them, how that's enforced, and how every change is recorded.
| Secrets encrypted at rest, never in normal API responses | Built |
| Live codes streamed over authenticated WebSockets | Built |
| Access enforced by the database itself (row-level security) | Built |
| Companies, nested teams, custom roles and invitations | Built |
| Team vaults shared with team members | Built |
| Instant session revocation and one-click offboarding | Built |
| Consent-based, time-boxed support access | Built |
| Four-eyes secret export (Google Authenticator, otpauth) | Built |
| Database-written change history, exportable by admins | Built |
| TOTP and HOTP, Google Authenticator import | Built |
| Offline codes for approved phones | Built |
| Code-view logging and auditor-ready reports | Built |
| Native Android app | Built |
| EU hosting and data residency | Roadmap |
| Native iOS app | Roadmap |
We're looking for a small group of companies with a real shared-2FA problem.
A 30-minute call: how your team shares 2FA today, and whether SafeZone fits.
demo@safe-zone.nl