Birds Beware stays public. ATLAS app, OS, memory, chat, voice and system pages require a signed-in beta session. Public testers verify an email address; owner/delegate consoles still require their separate private admin credentials.
BETA TESTERVERIFIED ACCESS
TRY THE WORKING ATLAS BETA.
Create a separate beta account boundary. Choose email now; phone/SMS is the next provider lane and will not pretend to send a code until a verified SMS provider is configured. Security and feature-usage events are logged so the system can be debugged. Your actual chat content is not retained for product review unless you separately opt in.
EMAIL SIGN-IN // CHECKING AVAILABILITY
BETA SIGN-IN TEMPORARILY OFFLINEEmail codes will appear here automatically after the mail provider is connected. Owner PIN access below is still available.
SESSION DEVICEDetecting this browser…
PRIVATE CONSOLEPIN + THIS DEVICE
TAP YOUR NAME. ENTER 4 DIGITS.
That’s it. On the first approved phone, ATLAS seals a private device key automatically. After that, the PIN only unlocks from that enrolled device.
FIRST TIME ON A PHONE?
Shaun opens a short setup window. Enter the PIN once and ATLAS binds that browser automatically. After setup, no phone number, name, or extra form is needed.
INVESTOR / STRATEGIC PARTNERSEPARATE ROOM
SEPARATE ACCESS. SEPARATE SCOPE.
The investor room uses its own access key and intentionally does not inherit owner, delegate, or beta-user authority.
NO COVERT “TRACK EVERYTHING” MODE. ATLAS records security/session and product-usage events needed to operate the beta. Message content is stored for operator review only when the tester explicitly opts in. Passwords, one-time codes and admin keys are never written to telemetry.