TTC is built with a privacy-first architecture. Private keys are encrypted client-side before reaching our servers — we cryptographically cannot access your funds.
The table below is generated directly from TTC's database schema. Only the fields listed here are stored on our servers.
One-way hash — original passkey is never stored
Encrypted by your passkey before reaching our servers. We cannot decrypt them.
Used only to enforce rate limits. Never written to a database.
Only collected if you choose to log in via Telegram.
All private keys (Solana, EVM, Orderly) are encrypted with your passkey or wallet signature before leaving your device. Our server stores only ciphertext blobs — we have no decryption key.
Your passkey is hashed with SHA-256 on the client before transmission. The server stores only the hash. We cannot reverse it to recover your passkey.
Auth tokens expire 24 hours after login; there is no silent refresh — re-login issues a new token. Challenges expire after 5 minutes.
IP addresses are read per-request for rate-limit enforcement only. They are never written to a database, log file, or analytics system.
In your browser, private keys are stored encrypted-at-rest via the Web Crypto API. The encryption key lives in sessionStorage — not localStorage — and is cleared on logout.
If you enable biometric login, your passkey is wrapped in a non-extractable AES-GCM key stored in IndexedDB. Decryption requires a WebAuthn assertion (Touch ID / Face ID).
We use a minimal set of sub-processors. We do not sell, rent, or share your personal data with advertisers.
Trade execution — Binance, Bybit, OKX, Bitget, and others
Your credentials are passed through in-session only, never stored server-side
Optional login via Telegram bot
Optional — only used if you choose Telegram login
If you are in the EU, EEA, or UK, you have the following rights under GDPR / UK GDPR. To exercise any right, email privacy@tetrac.xyz or use the self-service endpoint below.
POST /api/gdprSubmit an access, export, or deletion request programmatically. Requires a valid session token. Responses within 30 days.
Stores session token, public key, email, and public wallet addresses
Holds your in-memory encryption key — cleared on tab close and logout
Encrypted passkey blob for biometric login. Only present if you enable Touch/Face ID login
Anonymous page-view analytics. No cross-site tracking. No cookies set for analytics — uses privacy-preserving measurement
We will respond to all GDPR requests within 30 days. Where requests are complex or numerous, we may extend this to 90 days — we will notify you within the initial 30-day period if an extension is required. There is no charge for submitting a request.