Privacy Policy

Account and requested-action data

ATI uses Supabase for account authentication and protected owner/security records. When you sign up, sign in, recover a password, submit beta feedback, or use a protected action, ATI processes the information needed to complete that request and secure the account.

Conversations and browser-local memory

In this beta release, ATI conversation history is saved in local storage in your browser under an account-specific key. It is not yet synchronized to ATI's central database. Browser-local conversations remain on that browser until you delete them, clear site storage, or the browser removes them. Do not use a shared browser profile for private ATI conversations.

Guardian security and operational telemetry

When operational telemetry is enabled, ATI Guardian may record the page path or protected route involved, a keyed one-way actor/client hash when the dedicated security salt is configured, request identifiers supplied by the hosting platform, coarse country information supplied by the hosting platform, browser/automation client type, timestamps, response status, duration, severity, and security outcome. Guardian is designed not to store raw IP addresses, submitted passwords, authentication tokens, or raw ATI prompt/response content in security events.

Guardian security events are currently retained until they are deleted as part of ATI's beta security and operational process. ATI will replace this with a defined automated retention schedule before broader public release.

Loading telemetry preference…

Service providers

ATI uses Vercel for hosting and, when telemetry is enabled, Analytics and Speed Insights; Supabase for authentication and database services; Resend for configured Guardian owner alert emails; and Alpaca for live market-data and paper-trading requests. Those services receive only the information required for the feature being used and operate under their own terms and privacy practices.

Data separation and access

Server-side Guardian records use owner-only authorization and database row-level security. Member conversation history in this release is browser-local and separated by account-specific storage keys rather than Supabase rows. ATI does not claim that browser-local storage provides the same protection as a private server database.

Your choices

You can turn optional operational telemetry off for this browser above, and ATI also respects the browser's Do Not Track signal for that telemetry. You can delete browser-local conversations from ATI or clear the site's local storage. Beta members may request access to or deletion of centrally held account information through the ATI beta support/owner channel. Security and agreement records may be retained where reasonably necessary to protect the service or document required agreements.