Privacy Policy · Updated July 26, 2026

How TensorTrader collects, uses, stores, and shares your data.

Applies to the TensorTrader web application and to the TensorTrader — TradingView Alerts browser extension for Chrome and Edge.

No data saleNo advertisersNo remote codeExtension scope: TensorTrader + TradingView only

Section 1

Scope and Summary

This policy explains what data TensorTrader collects, how we use it, how we store and protect it, how long we keep it, and every party we share it with. It covers both the TensorTrader web application at tensortrader.agent-swarm.net and the "TensorTrader — TradingView Alerts" browser extension distributed on the Chrome Web Store and Microsoft Edge Add-ons.

TensorTrader is a trading-workflow tool. The browser extension has a single purpose: helping you build and manage TradingView alerts that route to your own TensorTrader webhook. Every category of data described below is collected in direct support of that purpose or of operating your TensorTrader account.

We do not sell user data. We do not share user data with advertisers or data brokers. We do not use user data for creditworthiness or lending decisions. We do not use user data for any purpose unrelated to the features described here.

Section 2

What We Collect

The web application collects the following, all of it either provided by you or generated by features you use.

CategoryWhat it includesSource
Account identityEmail address, hashed password, email-verification state, and (if you choose social sign-in) the email and name returned by Google or Apple.You provide it at registration or sign-in
Subscription dataPlan tier, subscription status, and billing period. Card numbers are entered on Stripe-hosted checkout and never reach TensorTrader servers.You provide it at checkout
Exchange configurationExchange API keys and secrets you choose to connect, venue selection, testnet/live flag, leverage and sizing preferences.You provide it in account settings
Trading activityOrders, positions, fills, and performance metrics generated by workflows you run.Generated by your use of the product
Alert routing dataYour personal TradingView webhook secret, alert payloads delivered to it, and the source IP of each webhook delivery.Generated when your alerts fire
Support and diagnosticsBug reports you submit, error diagnostics, server logs including request routes, timestamps, and IP addresses.Generated automatically or submitted by you
Abuse preventionA reCAPTCHA token and your IP address on registration, login, and verification-resend attempts.Generated at those specific actions
Optional Discord linkYour Discord user ID and username, plus message content in conversations with our bot, only if you connect Discord.You provide it by linking Discord

Browser extension

The extension runs only on tensortrader.agent-swarm.net and tradingview.com. It reads the following, and the last column states whether that data leaves your browser.

CategoryWhat it includesLeaves the browser?
Authentication tokenA short-lived TensorTrader access token and the email address of the signed-in account, obtained by asking our API to mint a token using the session cookie already set in your browser.Sent to TensorTrader
TradingView session stateYour TradingView username and plan tier, read from the TradingView page you already have open.Plan tier only is sent to TensorTrader
TradingView alertsAlert IDs, names, symbols, timeframes, active state, stop reasons, and alert message bodies.Alert metadata is sent to TensorTrader; message bodies are not re-uploaded
Indicator and script metadataNames, IDs, inputs, plots, and alert conditions of Pine studies and favorites in your TradingView account.Sent to TensorTrader when you sync or use AI template alignment
Workflow selectionsSymbols, venues, timeframes, and actions you choose, including lists you paste or import from CSV.Derived selections are sent to TensorTrader; the CSV file itself is never uploaded
Account balancesThe account value in USD of each exchange you connected, and available funds for Interactive Brokers, retrieved from your TensorTrader account so the wizard can size margin per alert. The extension never sees the API keys behind those accounts.Retrieved from TensorTrader; displayed in the panel
Tab presenceWhether a TradingView or TensorTrader tab is open, matched against those two domains only.Stays in your browser
Extension preferencesAlert-sentinel state, autotune state, update-check cache, and dismissed notices.Stays in your browser
Administrator TradingView cookiesOnly for operator accounts: the sessionid and sessionid_sign cookies, read on explicit click, to refresh our server-side TradingView session. Never read for ordinary users.Sent to TensorTrader, never stored in the extension

What the extension never collects

  • Your browsing history, or the content of any site other than tensortrader.agent-swarm.net and tradingview.com.
  • Your TradingView password, or any TradingView cookie belonging to an ordinary (non-operator) user.
  • Your exchange API keys or secrets — the extension never reads them. It sees only which venues you connected and their account value, so it can size margin.
  • Card numbers, bank details, or payment history. Payments are handled entirely by Stripe on the web app, never in the extension.
  • Keystrokes, clipboard contents, form data on unrelated sites, or any content outside the two permitted domains.

Section 3

How We Use It

PurposeData usedWhat we do with it
Operate the serviceAccount identity, subscription data, exchange configurationAuthenticate you, enforce plan limits, and run the workflows you configure.
Execute your instructionsExchange configuration, trading activity, alert routing dataPlace, size, and reconcile orders on the venues you connected, using the credentials you supplied.
Build and maintain alertsAuth token, TradingView alerts, indicator metadata, workflow selectionsCreate, list, restart, and audit TradingView alerts that point at your TensorTrader webhook.
Keep the product workingSupport and diagnostics, extension preferencesDiagnose failures, restore stopped alerts, and notify you about extension updates.
Protect accountsAbuse prevention, server logsDetect automated abuse, rate-limit, and investigate suspicious access.
Communicate with youAccount identity, optional Discord linkSend verification and service email, and reply through Discord if you linked it.

We do not use any of this data for advertising, profiling unrelated to your own trading workflows, or training general-purpose machine-learning models on your personal data.

Section 4

How We Store and Protect It

All transmission is over HTTPS/TLS. The extension makes no plaintext HTTP requests, and credentials are never placed in URLs or query strings.

Exchange API keys and secrets are encrypted at rest with Fernet symmetric encryption before being written to the database, and are decrypted only in memory at the moment an order or balance request is made. Passwords are stored only as salted hashes. Card details are never stored by TensorTrader.

Inside the extension, your TensorTrader token and email are held in chrome.storage.session, which the browser clears when the browsing session ends. Extension preferences and caches are held in chrome.storage.local and are removed when you uninstall the extension. Your TradingView webhook secret is held in memory only and is never written to extension storage. TradingView cookies are never written to extension storage in any case.

Server data is stored in a MySQL database on infrastructure we operate and administer directly. Access is limited to authorized operators, and administrative access to user records is logged.

Retention

DataWhere it livesHow long
Extension token and emailchrome.storage.session in your browserCleared automatically when the browser session ends
Extension preferences and cacheschrome.storage.local in your browserUntil you clear them or uninstall the extension
Account, exchange keys, trading recordsTensorTrader databaseWhile your account is active; deleted when you delete your account
Webhook delivery logsTensorTrader databaseRetained for reliability and abuse investigation; unlinked from your account on deletion
Server and application logsTensorTrader infrastructureShort-lived operational retention, rotated as part of normal operations
Billing recordsStripeRetained by Stripe as required by financial and tax law, independent of account deletion
Error diagnosticsSentryPer Sentry retention; sent with email, IP, username, headers, and request bodies scrubbed

Section 5

Who We Share It With

The following is the complete list of parties that receive user data from TensorTrader. Several of them receive data only if you opt into the relevant feature, as noted. Each acts as a service provider or as a destination you explicitly chose.

RecipientWhat they receiveWhy
TradingViewAlert definitions, alert message bodies containing your webhook URL and secret, symbols, timeframes, and study lookups. These requests run under your own TradingView login.To create and manage the alerts you asked for
Your chosen exchanges (Binance, Bybit, Hyperliquid, dYdX and other supported venues)The API credentials you supplied for that venue and the order instructions your workflow generates.To execute your trades on the venue you selected
Interactive BrokersYour IBKR OAuth credentials and order or contract requests, only if you connect IBKR.To execute your trades on IBKR
StripeEmail address, an internal user identifier, and plan metadata. Card details go directly from your browser to Stripe.To process subscription payments
GoogleA reCAPTCHA token and your IP address on registration and sign-in; your email and name if you use Google Sign-In.Abuse prevention and optional social sign-in
AppleYour email and name, only if you use Sign in with Apple.Optional social sign-in
DiscordYour Discord user ID, username, and message content, only if you link a Discord account.Optional notifications and support channel
SentryError and performance diagnostics, scrubbed of email, IP, username, headers, and request bodies.To detect and fix crashes
OpenRouterIndicator names, inputs, plots, and alert-condition metadata, only when you use the optional AI template-alignment feature. No credentials or personal identifiers are included.To map an unfamiliar indicator onto an alert template
GitHubThe contents of bug reports you submit, with email addresses redacted, plus route, browser user agent, and app version.To track reported bugs
Our email provider (SMTP)Your email address and the contents of service email such as verification links.To deliver transactional email

TensorTrader runs on infrastructure we operate and administer directly, with a MySQL database. We may also disclose data if required by law, to enforce our terms, or to protect the rights and safety of users. If ownership of the service changes, we will notify users before their data becomes subject to a different policy.

Section 6

Your Choices and Deletion

You can delete your account at any time from Settings in the TensorTrader web app. Deletion removes your account record, your stored exchange credentials, and your trading records, and unlinks your webhook delivery logs. Records held by Stripe for legal and tax purposes, and diagnostics already sent to Sentry, are governed by those providers’ retention terms.

You can disconnect any exchange or remove any stored API key individually from account settings without deleting your account.

You can stop all extension data collection at once by removing the extension from Chrome or Edge, which also deletes its local storage. Signing out of TensorTrader immediately invalidates the token the extension uses. Optional features — AI template alignment, the alert sentinel, autotune, and the Discord link — are off unless you turn them on, and can be turned back off at any time.

To request access to or deletion of your data, or to ask any privacy question, email support@agent-swarm.net or contact support from inside your account.

Sale of user data
No
Shared with advertisers or data brokers
No
Used for credit or lending decisions
No
Used for purposes unrelated to these features
No
Remote-hosted code execution in the extension
No
Browsing history or non-permitted site content collected
No

Section 7

Changes and Contact

If we change how we collect, use, store, or share data, we will update this page and revise the date at the top. Material changes affecting the browser extension will also be surfaced in the extension itself.

Privacy questions and data requests: support@agent-swarm.net