tetrac.xyz / privacy

Privacy
Policy

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.

Last updated: 2026-10-11Contact: t.me/tetracChat
Private keys
Encrypted in your browser
Sign-in secret
Never leaves your device
IP addresses
Rate-limit only

Who We Are

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.

Data We Collect

This table lists every category of personal data our servers keep.

Account profile
Purpose:Your account: wallet public key, email (an internal address for Telegram and device-passkey accounts), sign-in method, the verification key your browser derived, key-derivation settings, creation date, sharing settings and arena handle
Basis:Contract
Retention:Until you delete your account
Who can see it:You
Encrypted wallets encrypted

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.

Purpose:Wallet key custody: Solana and EVM private keys, as ciphertext
Basis:Contract
Retention:Until you delete your account
Who can see it:You (decrypted only in your browser)
Subscription and payments
Purpose:Your plan and its expiry, the payment transaction, the payment rail and paying wallet, an MPP session channel, and who referred you
Basis:Contract
Retention:Until you delete your account
Who can see it:You
Session
Purpose:Keeping you signed in: a hash of your session token
Basis:Contract
Retention:24 hours
Who can see it:No one
Token-gate result
Purpose:Whether your wallet held $TTCP / $TTCS at sign-in (yes or no)
Basis:Contract
Retention:24 hours
Who can see it:No one
Arena records
Purpose:Battles and rumbles you join: wallet, handle, stake, deposit transaction and result
Basis:Contract
Retention:Kept as the record of each settled battle; your handle is removed when you delete your account
Who can see it:Signed-in users (the arena)
Shared trade history
Purpose:The snapshot you choose to publish as a share page
Basis:Consent
Retention:30 days, or until you delete your account
Who can see it:Anyone with the link
Live streams
Purpose:Which account owns a stream you start
Basis:Contract
Retention:Until you end the stream (it is deleted) or delete your account
Who can see it:Viewers of the stream
Payment receipts
Purpose:Replay protection for pay-per-call payments (paying wallet, amount, endpoint), and which account an MPP session channel activated
Basis:Legitimate interest
Retention:24 hours (pay-per-call); 10 years (MPP channel claims)
Who can see it:No one
Referral totals
Purpose:If someone you referred pays: the count and amount owed to your wallet
Basis:Contract
Retention:Kept for referral payouts
Who can see it:You
Rate-limit counters

Never linked to your account. The sign-in service's own limiter still counts your raw IP for 60 seconds.

Purpose:Abuse prevention: a keyed hash of your IP address (or account or paying wallet) per limit
Basis:Legitimate interest
Retention:60 seconds to 2 hours
Who can see it:No one
Daily active-user count
Purpose:Aggregate usage statistics, not linked to your account
Basis:Legitimate interest
Retention:32 days
Who can see it:No one
Telegram sign-in

Your Telegram name is shown in the app but not stored.

Purpose:A pseudonymous account id derived from your Telegram id (optional sign-in)
Basis:Consent
Retention:Until you delete your account
Who can see it:You

How We Protect Your Data

Client-side encryption

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.

No passkey on our servers

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.

Short-lived unlock

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.

Optional device unlock

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.

Short-lived sessions

Sessions expire 24 hours after sign-in, with no silent refresh. Sign-in challenges expire after 5 minutes.

IP addresses for rate limits only

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

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.

Telegram accounts

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.

Third-Party Services

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.

Vercel

Hosting and serverless functions, so every request and its IP address; cookieless page-view analytics (paths only)

Sent by: Our servers and your browser

USA / global edge
Privacy policy ↗
Upstash

Every server-side record in the table above: our database runs on Upstash Redis

Sent by: Our servers

Region of our Upstash Redis database
Privacy policy ↗
Crypto exchanges and DEXs

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)

Varies by venue
Solana RPC providers

Wallet addresses and signed transactions, relayed through our RPC proxy

Sent by: Our servers

Varies by provider
NEAR Intents (1Click) and Mayan

Deposit and withdrawal addresses and amounts, when you bridge funds

Sent by: Our servers and your browser

Global
Livepeer

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

OpenRouter

AI prompts you run, which can include positions shown on screen, sent with your own OpenRouter key

Sent by: Your browser

DojiFunded

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

Global
Telegram

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)

Your Rights

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.

Right to access
Download a copy of the data above with the button below, or call the endpoint.
Right to portability
The same download is a machine-readable JSON export.
Right to erasure
Delete your account with the button below. It removes your profile, wallets, session, share page, streams and handle. Arena battle records, payment receipts, MPP channel claims and referral totals are kept.
Right to rectification
Your email salts your wallet-key derivation, so it cannot be changed in place: delete and re-register, or contact us for other corrections.
Right to withdraw consent
A share page ends after 30 days, or when you delete your account.
Right to object or restrict
Contact us to object to processing based on legitimate interest, or to restrict it while a dispute is resolved.
Right to complain
You can complain to the data-protection authority where you live or work.
Self-service GDPR endpoint
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.

Cookies & Browser Storage

We set no cookies. This site keeps the following in your browser.

Session and account (localStorage)always on

Your session token, public key, email and key-derivation settings, so you stay signed in

Encrypted credentials (localStorage)always on

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

Biometric unlock (IndexedDB)optional

The wrapped vault key, only if you turn biometric unlock on

Settings and caches (localStorage)always on

Preferences, layouts, market caches and pending-payment records, with no secrets

Vercel Analyticsalways on

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

Contact

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.