Privacy Policy

Last updated: October 18, 2026 · TradeShield

1. Who We Are

TradeShield ("we", "us", "our") operates the TradeShield web application (desktop and mobile browsers) (the "Service") — a connection monitoring and trade-safety tool for cryptocurrency traders. We are not a broker, exchange, or custodian. Questions: support@tradeshieldlabs.com.

2. What We Collect

Data You Provide

Email address (waitlist or account creation)
Alert preferences and latency threshold settings (stored locally in your browser)

Data We Collect Automatically

Connection health telemetry — latency samples (ms), exchange API reachability results, and shield-status transitions. Used exclusively to power Shield Status and improve latency models. Never sold or shared with advertisers.
Trade attempt metadata — symbol, side (buy/sell), size, connection status and latency at the moment of a trade submission attempt. We record intent only; TradeShield never submits orders to any exchange or blockchain.
Standard server logs — IP address, user-agent, HTTP method, path, and response time. Retained for up to 30 days for security and abuse prevention.

What We Never Collect

Private keys or seed phrases
Exchange API keys or secrets
Portfolio balances, P&L, or position data
On-chain transaction hashes or wallet activity
Biometric data

3. Crypto-Specific Data Handling

Because TradeShield operates in the cryptocurrency context, we apply heightened care:

No key or credential storage. We have no access to and do not store any private key, seed phrase, exchange API key, or signing credential. If you ever share such data with us by mistake, email us immediately.
No unattended on-chain activity. TradeShield never signs or broadcasts a blockchain transaction without your approval. If you connect a wallet while wallet features are enabled, we store the public wallet address you connect so we can show read-only activity and prepare a user-signed 0x quote. We never collect private keys or seed phrases.
Exchange API queries are read-only public endpoints. We query public exchange health/ping APIs (currently Binance REST API) without authentication. No user-specific account data passes through TradeShield's servers.
Trade metadata is anonymised. Trade attempt logs are not linked to exchange account identifiers, wallet addresses, or real-world identity unless you have created a TradeShield account.
Signal data is third-party sourced. Signal feeds are provided by external algorithmic services. We process signal metadata (symbol, direction, strength) but not the proprietary models behind them.

4. Cookies & Local Storage

We use localStorage (not cookies) to persist your settings: latency threshold, alert toggles, and theme preference. No cross-site tracking cookies are set. We may use a single first-party authentication session cookie if you create an account.

5. Third-Party Services

Binance Public API — queried for exchange latency checks. Your IP may be visible to Binance per their privacy policy.
No advertising networks, analytics SDKs, or tracking pixels are embedded in TradeShield.

6. Data Retention

Connection event logs: 90 days
Trade attempt metadata: 90 days (anonymised after 30 days for free tier)
Server access logs: 30 days
Account data: until deletion requested
localStorage settings: until you clear your browser or reset in app

7. Your Rights

Depending on your jurisdiction (GDPR, CCPA, etc.) you may have rights to access, correct, port, or delete your data, and to object to or restrict processing. Submit requests to support@tradeshieldlabs.com. We respond within 30 days. Crypto trading–related data that has been anonymised may be retained for model improvement even after account deletion.

8. Security & Compliance

We treat user data as a security-critical asset and design the Service to meet the substantive requirements of GDPR (EU/UK), the CCPA/CPRA (California), PIPEDA (Canada), and equivalent data-protection regimes. Concretely:

Encryption in transit. All client/server traffic is protected by TLS 1.2 or higher with modern cipher suites. HSTS is enforced on production domains.
Encryption at rest. Sensitive material — including any exchange API credentials supplied for opt-in automated features — is encrypted at rest using authenticated symmetric encryption (AES-GCM with per-record initialisation vectors) before being written to the database. The encryption key is held in a server-side secret store that is not accessible from the application bundle or from any client.
No client-side secret exposure. Stripe, Anthropic, database, webhook, and exchange-key encryption secrets exist only on the server. The shipped web/mobile bundle contains only public configuration (e.g. Stripe publishable key).
Least privilege & access control. Database access is restricted by network and role-based controls. Production access is limited to a small number of named operators using strong, unique credentials and (where supported) hardware-backed multi-factor authentication.
Webhook & request integrity. Stripe webhooks are signature-verified against the Stripe webhook secret before any state mutation. API inputs are validated server-side against typed schemas to prevent injection or tampering.
Bounded retention & purpose limitation. Data is collected only for the purposes described in this Policy and retained only as long as listed in Section 6, after which it is deleted or anonymised.
Vulnerability management. We run automated dependency, SAST, and secret-scanning checks against the codebase and remediate critical and high-severity findings on a prioritised schedule. Independent reviews are performed periodically.
Sub-processors. We engage a small number of reputable infrastructure and payment sub-processors (currently including the hosting platform, the managed PostgreSQL provider, Stripe, Anthropic, and Microsoft Graph for support email). Each is bound by their own enterprise security and data-protection commitments.
Breach notification. In the event of a confirmed personal-data breach, we will notify affected users and the relevant supervisory authority within the timeframe required by applicable law (within 72 hours where GDPR Article 33 applies).
International transfers. Where personal data is transferred outside your home jurisdiction, we rely on lawful transfer mechanisms (e.g. Standard Contractual Clauses or an adequacy decision) provided by our sub-processors.
Responsible disclosure. Suspected vulnerabilities should be reported to security@tradeshieldlabs.com. We will not pursue good-faith researchers who follow standard responsible-disclosure practice.

9. Children

TradeShield is not directed at anyone under 18. We do not knowingly collect data from minors. If you believe a minor has used the Service, contact us for immediate deletion.

10. Changes

Material changes will be announced in-app and by email (if registered) at least 14 days before taking effect. Continued use after the effective date constitutes acceptance.

Contact: support@tradeshieldlabs.com