Privacy Policy

• Account information: email address and authentication credentials provided at registration.
• Trade & journal data: trades, imports, screenshots, journal entries, trading rules and settings that you voluntarily save into your account.
• Technical logs: minimal, anonymized request logs used strictly for uptime, abuse prevention and performance. These never include the contents of your trades or journals.

We use your data strictly to provide and maintain your private trading journal. We do not sell, rent, share or trade your personal data, trade executions, journal entries or screenshots with third parties, advertisers, brokers, or analytics networks. There are no ad trackers. There is no data marketplace.

• TLS in flight. All traffic between your browser and TerminalX is encrypted with HTTPS/TLS 1.2+.
• AES-256 at rest. The managed Postgres database and object storage that back TerminalX encrypt every byte at rest with AES-256 using provider-managed keys. Backups are encrypted with the same standard.
• Row-Level Security (RLS). Every user table — trades, journals, screenshots, imports, rules, settings — has Postgres RLS policies that scope every query to auth.uid(). One user cannot see, touch, or infer another user's rows. The database itself refuses the read.
• Private storage. Uploaded screenshots live in private object-storage buckets. Access is granted only through short-lived signed URLs issued to your authenticated session.
• CSVs never leave your browser. Broker exports are parsed in-memory on your device via FileReader. Only the resulting normalized trade rows are persisted. The raw CSV file is never uploaded to our servers or storage.
• No content admin console. Operator tooling covers CMS publishing, uptime and billing — not browsing other users' trades, journals or screenshots. Database access for emergencies uses service-role credentials under access control and logging.

Your trading and portfolio rows are readable by your authenticated session via Row Level Security. Other users cannot read them. TerminalX staff do not have a product UI to browse your journal or holdings. Service-role access exists only for account deletion, shared market caches, and operational emergencies — not for advertising or resale. AI Coach sends journal/portfolio context to the provider you configure (your key) or the managed Premium provider when enabled.

You retain ownership of your account and its contents. From Settings → Danger Zone you can permanently delete your account, which purges owned application data (journal, portfolio, knowledge, coach memory, screenshots) and the auth user. Deletions are irreversible; encrypted infrastructure backups may retain residual copies for a limited retention window (typically up to 30 days).

TerminalX uses a single authentication cookie / local-storage token required to keep you signed in. There are no advertising cookies, no session replay, no third-party analytics on authenticated surfaces.

Privacy questions, data-access requests and deletion requests can be sent to the address published on our contact page.