Wallet keys are generated and encrypted in your browser before they reach our servers. We store only ciphertext.
The exception: if you sign in with Telegram, your wallet key is derived on our server so you can recover it on any device, which means TTC could decrypt those wallets.
Tetrac (“TTC”, “we”) operates www.tetrac.xyz and is responsible for the personal data described here. Reach us through the contact channel at the end of this page.
This table lists every category of personal data our servers keep.
Encrypted in your browser before upload. Exception: for Telegram sign-in accounts the key is derived on our server, so TTC could decrypt those wallets.
Never linked to your account. The sign-in service's own limiter still counts your raw IP for 60 seconds.
Your Telegram name is shown in the app but not stored.
Wallet keys are generated and encrypted in your browser before they reach our servers. The key that encrypts them comes from your sign-in: your passkey phrase (email accounts), a signature from your wallet (Web3 accounts), or your device passkey (passkey accounts). We store only ciphertext.
Your browser stretches your passkey phrase with PBKDF2-SHA256 (600,000 iterations). Our server stores only a verification public key derived from it, so it never receives your passkey phrase or a hash of it.
The unlocked key lives only in browser memory. The vault locks 60 seconds after you unlock it (some signing steps restart that timer), switching tabs does not lock it, and reloading the page drops it.
If you turn on biometric unlock, an encrypted copy of your vault key is kept in this browser's IndexedDB. The key that wraps it is derived from your device passkey each time and is never stored.
Sessions expire 24 hours after sign-in, with no silent refresh. Sign-in challenges expire after 5 minutes.
IP addresses are used to rate-limit requests. Our counters store a keyed hash, never the IP, and delete themselves within 2 hours. Our host (Vercel) also processes IPs to serve the site.
Exchange API keys are stored only in your browser, encrypted under your vault key. In Pro mode, a venue's key and secret (for some decentralised venues, its trading key) travel to our server with each request so it can sign it; they are never stored there. Lite mode signs in your browser.
If you sign in with Telegram, your wallet key is derived on our server so you can recover it on any device. That means TTC could decrypt those wallets. Email, wallet and device-passkey accounts do not have this exception.
These services receive personal data, either from our servers or from your browser. We do not sell or rent your data, and we share none with advertisers.
Hosting and serverless functions, so every request and its IP address; cookieless page-view analytics (paths only)
Sent by: Our servers and your browser
Every server-side record in the table above: our database runs on Upstash Redis
Sent by: Our servers
Your orders and account requests. In Pro mode, a venue's API key and secret (for some decentralised venues, its trading key) pass through our server on each request so it can sign them; they are never stored there
Sent by: Our servers (Pro mode) or your browser (Lite mode)
Wallet addresses and signed transactions, relayed through our RPC proxy
Sent by: Our servers
Deposit and withdrawal addresses and amounts, when you bridge funds
Sent by: Our servers and your browser
Your live video and the stream title, while you stream; a stream is deleted when you end it
Sent by: Our servers and your browser
AI prompts you run, which can include positions shown on screen, sent with your own OpenRouter key
Sent by: Your browser
Your TTC EVM wallet address, your challenge orders and the API key pair it issues, only if you buy or claim a challenge
Sent by: Our servers
Telegram sign-in (only if you use it); feedback you send, without your account or IP; alerts you send to your own bot
Sent by: Our servers (sign-in, feedback) and your browser (alerts)
If you are in the EU, EEA or UK, you have these rights under GDPR / UK GDPR. Access, export and deletion work in the app (below); for the others, contact us at t.me/tetracChat. Please don't post personal data in the group: ask an admin, who will continue in a private chat.
POST /api/v1/gdpr {"type": "access" | "export" | "delete" }Send it with your session headers (ttc-auth-token and ttc-public-key); it answers immediately. Signed in? The buttons below do the same.
Sign in to download or delete your data here.
We set no cookies. This site keeps the following in your browser.
Your session token, public key, email and key-derivation settings, so you stay signed in
Exchange API keys, your OpenRouter key and Telegram bot credentials, each encrypted under your vault key; plus a plain list of which exchanges you connected
The wrapped vault key, only if you turn biometric unlock on
Preferences, layouts, market caches and pending-payment records, with no secrets
Always on and cookieless: counts page views by path. Query strings are dropped and the wallet in a /user/… share link is replaced before anything is sent
We respond to requests within 30 days. Where requests are complex or numerous we may extend this to 90 days, and we will tell you within the first 30 days if we need to. There is no charge for a request.