Private beta security
Practical protection without unnecessary friction.
Updated September 2, 2026
Account separation
Every saved AOL, schedule, and 168 Mode profile is tied to its signed-in owner. Requests for another account’s records are rejected.
Sign-in protection
Passwords must contain at least 12 characters. Repeated authentication attempts are limited. Verification emails, password recovery, optional authenticator-app protection, and one-use recovery codes are supported for the live beta.
Private-beta access
New registrations require the private invitation configured by the owner. Security-sensitive account actions are recorded without placing task names or plan contents in the security history.
Browser and transport protection
The published site is intended to use HTTPS. Browser security headers block framing, restrict loaded content, and prevent private API responses from being stored in shared caches.
Limits
No online service is risk-free. The private beta is not end-to-end encrypted, and the hosting account owner retains technical database access. Testers should report unexpected account activity to the person who invited them.