Check protection, encrypted checkpoints and owner access. These controls apply to your mailbox application.
Checking owner session…
Create and save a private recovery key on this device. Then choose that saved file to prove it can decrypt a challenge. Only the public key and challenge proof go to the server. Keep older recovery keys for older checkpoints.
The Worker uses a public encryption key. The recovery private key stays with the operator. Independent owner custody and a production recovery cutover still require separate acceptance. Checkpoints have no automatic expiry in this release.
Pausing fences native and personal AI and automatic replies. It does not stop an already submitted email or disable explicit owner sends, account sync or mailbox access. Personal accounts remain disconnected until you connect them.
Revoke a session to stop its signed cookie from accessing the mailbox. Revoke all refreshes this browser and invalidates older sessions. Your owner access key remains a separate trusted credential.
This is owner access management. Individual staff accounts and MFA are not established by these controls. Never share the owner key with staff or products.
Known executable, script and macro attachments, disguised executable signatures and unsafe filename controls are held in Junk. Originals are retained for review. Archives and other files are not certified malware-free. This is not a complete antivirus, phishing or authenticated-sender service.
A current snapshot does not guarantee uptime or recipient delivery. Uncertain sends need reconciliation before any retry.
These are minimal access-control records, not a complete independent or tamper-proof audit. A named human must review alerts and incidents.