How is my account protected?

Which layers protect the account?

• Passkeys: the strongest way to sign in. The private key stays on your device and only works at the service's real address.
• Phone approval with a number: the phone only approves if you type the number shown in the browser, which stops requests sent by others.
• Access policy: the organization decides which methods each application, network, time and device posture require.
• Recent confirmations: sensitive actions (changing security, removing a phone, erasing data) ask for a passkey confirmation from a few minutes ago.
• Dual control: critical changes can require a second administrator's approval.

Which secrets does the service keep?

None that would let someone sign in as you:

• passwords: only an Argon2id verifier;
• passkeys and phones: only public keys;
• recovery codes: only digests;
• code seeds and privileged credentials: sealed with separately managed keys.

How do I know what happened on my account?

The organization has a chained, verifiable audit log: each event depends on the previous one, so deleting or changing an event is detectable. Important decisions get signed receipts.

What do I do if I suspect an account takeover?

1. Decline any request you did not make, with "it wasn't me".
2. Sign in with your passkey and change your password.
3. Review your trusted devices and sessions, and end the ones you do not recognise.
4. Tell your organization's security team at once.

A suspected account takeover is always handled by a person, never only by an automated assistant.

Who can see my data?

Your organization's administrators, within the roles they were given. The service provider only accesses it for support and operation, and that access is recorded.