Your leave data isn't just personal. Some of it's sensitive.
Sickness and family leave carry a weight most leave trackers don't account for. Otium One treats them that way from the ground up.
Tenant isolation
Your data is isolated three ways: explicit scoping in every query, an application-level guard as a second line, and row-level security enforced at the database itself. Even if application code contains a bug, database-level row security provides a final barrier against one customer accessing another customer's data.
Authentication
Cookie-based sessions, optional or admin-required multi-factor authentication (TOTP), and breached-password checking on every password set. Repeated failed logins trigger exponential backoff. Deactivating a user ends every session of theirs within a minute, not just at cookie expiry.
Single sign-on
Microsoft Entra ID (formerly Azure AD) support with pre-provisioning and automatic account linking on first sign-in, plus SCIM 2.0 for automated user lifecycle management from your identity provider.
Audit & retention
An append-only audit log records every meaningful change — leave requests, approvals, entitlement changes and account changes — with a retention period you control. Database controls prevent audit records from being edited or deleted before their retention window ends.
Data protection
Sickness and family leave are treated as sensitive by default: they're excluded from external notifications and restricted in reporting to authorised administrators. GDPR-aligned erasure is built in for individual users, and full offboarding exports your data before removing it.
Support access
If our support team ever needs to look at your account to help you, that access is time-boxed, scoped to what's needed, and logged in full — never a standing, silent back door into your data.
Security concerns
Found something that doesn't look right? We'd rather hear about it. Report security issues privately to hello@example.com.