Verified email + separate user boundary.
Beta sign-in stores display name, email, age confirmation, consent time, and sign-in timestamps. The one-time email code expires after 10 minutes and is never shown in the operator dashboard.
ATLAS://PRIVACY // R68
TRACK ENOUGH TO
IMPROVE. NOT ENOUGH TO SPY.
The protected beta uses verified accounts and records security/product events so failures can be diagnosed. It does not silently record every keystroke, and raw chat content is not retained for operator review unless the tester explicitly opts in.
Events, not covert surveillance.
Public website analytics are first-party: basic page counts and CTA categories are anonymous at the application layer. Scroll depth, active time and section dwell are collected only after a visitor allows performance analytics. ATLAS does not record keystrokes, form-field text or full-screen session replay. Sign-in/security records may include normal browser/device information, IP address and coarse network geography supplied by Netlify.
Goals and explicit memories persist.
Goals and memory notes you deliberately save are stored under your authenticated beta account so future sessions can continue with context. Do not store passwords, payment data, medical records, recovery codes or private customer information.
Provider calls happen only for requested features.
When you send a beta chat or request neural voice, the relevant text is sent through the site’s serverless function to the configured AI provider. The beta does not send Shaun’s PRIVATE FULL corpus into tester accounts.
Raw beta chat retention is opt-in.
If you enable “content review” in Settings, ATLAS may retain your beta chat question/answer content for operator product review. Turning the option off deletes previously retained opt-in chat content from the beta store. Usage/security event metadata continues either way.
Dashboard + daily digest.
The owner console can show verified beta users, usage/security events and deliberately submitted feedback. A scheduled digest can email aggregate beta counts to the configured operator address. The digest does not include raw chat content.
Comments are deliberate + moderated.
Approved comments are public. Submitting one requires a verified beta session, is rate-limited, and enters a pending queue. The owner can approve or reject it. Do not post private information in a public comment.
A 4-digit PIN is not the whole lock.
Owner/delegate console access uses the PIN only as one factor. The first deliberately enrolled browser creates a non-exportable cryptographic device key; future console sessions require that device key as well. Mr. Hampton’s binding can be reset only from Shaun’s authenticated owner console.
RETENTION
Automatic cleanup is part of the build.
R68 schedules cleanup of abandoned verification/rate-limit records, opt-in chat content after 30 days, user-scoped usage events after 90 days, and aggregate access/security events after 180 days. Goals, account profile and explicit memories remain until you remove them or delete the beta account.
You can delete your beta data.
The Settings tab includes an account-data deletion control. It deletes the beta profile, goals, explicit memories, user-scoped events, feedback and retained opt-in chat content, then clears the beta session. Security systems may still have infrastructure logs outside the application-level stores according to the hosting/provider’s own operation.
Public/beta access is not Shaun PRIVATE FULL.
Opening the website or signing into the beta does not authorize access to Shaun’s private files, email, finances, health information, credentials, customer records, device control, or full private memory. Those boundaries remain separate.