Last updated: October 23, 2026
Short version: we collect the minimum needed to run your account and your bots, we don't sell your data, and your broker API keys are encrypted and never shown back to your browser.
utm_source, utm_medium, utm_campaign, utm_term, utm_content), and basic device and browser details (browser and version, operating system, device type, screen size, language and time zone). PostHog receives your IP address with each request because that's how the internet works, but we've set it to discard the IP address, so it isn't stored, and we don't use it to work out your location. We don't record what you type, we don't record your screen, and we don't use this on the signed-in app.We use a few first-party cookies and on-device storage, and no advertising or cross-site tracking cookies: a sign-in cookie that keeps you logged in; a cookie and on-device note (tx_ref, 30 days) that remembers which of our links or videos brought you to the site; and, when you open an active invite or partner link, a cookie (tx_aff, 30 days) that remembers the code so the right person gets credit if you sign up. A first-touch campaign tag (tx_first_source) records the first valid source or utm_source tag from a link, so we can understand which campaign led to a signup. It is saved in a 30-day cookie, in browser storage until cleared, and with a new checkout order. It is a short tag, not your browsing history or the full referring URL. The app also keeps display preferences on your device. We don't share any of these with anyone, except as described next for website analytics.
Website analytics (PostHog). On our public pages, PostHog sets a first-party cookie and matching browser storage named ph_[project]_posthog (90 days). It holds a random visitor ID, the first campaign tag that brought you here, and your current visit, so repeat page views aren't counted as new visitors. It doesn't contain your name, email or account details. A short session note (tx_conv_[page]) in browser storage, cleared when you close the tab, makes sure a button click is counted once per visit. When you tap an App Store link we add a short campaign tag to it (for example ct=ig_campus_campus) so Apple can tell us, in aggregate, which campaign led to a download. We honor Do Not Track and Global Privacy Control: if either is on, PostHog doesn't load and no analytics cookie is set.
iPhone signup comparison. When you open account creation in the iPhone app, we may assign one of two designs using a first-party cookie (tx_ios_signup_v1, 30 days). It holds a random identifier and version, not your email or password. We count signup-screen views and subscription-screen opens, and attach the assignment to a confirmed Apple signup to measure activations and profile completion. The trial offer and Apple payment process are the same in both designs. No third-party pixel is used. We honor Do Not Track and Global Privacy Control. Browser measurement records are removed after 90 days when this service next runs; aggregate counts and account-attribution records remain with the business records. Clearing app cookies or using another device may assign a new version.
Link-page comparison. The comparison is currently stopped: visitors see the original design, and new experiment assignments are disabled. During the comparison, we tested two versions of our link page using a first-party cookie (tx_links_v1, 30 days). It contains a random browser identifier and assigned version. We count page views, download-link clicks and web signups; a new web checkout can store that assignment so we can count later subscription activations. Preview mode uses a short-lived cookie to exclude test visits. The experiment stores no raw IP address, user-agent string or browsing history, uses no third-party tracking pixel, and honors Do Not Track and Global Privacy Control requests. Browser-level measurement records become eligible for deletion after 90 days and are removed when the measurement service next runs; aggregate totals and order-attribution records remain with the corresponding business records. Clearing cookies or using another device can create a new assignment.
Website experiments. On our public website pages we may show one of two versions of a headline, an introduction or a button label, using a first-party cookie (tx_ab, 90 days). It holds a random browser identifier, the version shown for each comparison, and a one-word source such as TikTok, Instagram, X, a partner link, search or direct, not the referring address or your email. We record page views, clicks on trial or App Store buttons, starting and finishing the spike check (never your answers or score), starting checkout, and whether that checkout became a trial and a first payment. A new web checkout stores the identifier with the order so we can count those later steps. We don't store your IP address or your browser's full user-agent string (only whether the browser looks like a phone), and these experiment records are not shared with any third party. The prices, trial terms and checkout are the same in every version. Signed-in members, the iPhone app and browsers that send Do Not Track or Global Privacy Control are not included and always see the standard page. Experiment records are kept for up to one year, then deleted.
To create and secure your account, run the features you use (including sending orders to your connected broker when you enable a bot), process payments, send you account and receipt emails, provide support, and improve reliability and safety. On our public website, analytics helps us see which pages and campaigns are useful, which pages lead people to download the app or start a trial, and which questions people open, so we can improve the site and test page designs.
Only the service providers needed to operate: payment processors (Stripe/PayPal), our email provider (for receipts, resets, and support), market/broker data providers you use (e.g., Alpaca, and public market-data sources), and our website analytics provider, PostHog Inc., which processes website analytics on our behalf on its US cloud (data stored in the United States). We may disclose information if required by law or to protect the platform and its members.
Referrals. If you join with a member's invite link or code, that member sees counts only (for example, “2 friends joined, 1 paid”) and the free months they got, never your name, email or payment details. If you were the only person to use their link, they may be able to tell it was you. Partners in our affiliate program see the same kind of anonymous counts and commission amounts.
Connected brokerages (SnapTrade). If you choose to connect a brokerage account through the "Other brokerages" option, the connection is made by SnapTrade, an independent third-party service, under its own terms and privacy policy. You sign in on your broker's page or SnapTrade's secure form; Tradexa AI never receives or stores your brokerage password. Through that connection Tradexa AI receives your account name and masked account number, balances, positions (what you hold and what you paid) and recent orders, and stores them on our server to show them to you in the app. We do not sell this data or share it with anyone else, and we do not store the broker's price data. You can disconnect at any time from Settings; disconnecting removes the connection at SnapTrade and deletes the stored account data from Tradexa AI. Connecting an account does not place any trade.
Passwords are hashed with PBKDF2; broker secrets, two-factor secrets, and dates of birth in consent records are encrypted at rest. Access to the site is over HTTPS. No system is perfectly secure, but we work to protect your data and limit what's stored. Enabling two-factor authentication in Settings adds a strong layer to your login.
The signup quiz uses your experience, learning focus, trading pace and practice preferences to prepare a simulated agent. Answers are sent to our server to preview your practice settings. Your chosen name and answers are saved with your order when you continue to checkout, and with your account after profile setup, so the plan can be restored after payment. No brokerage connection or real-money trade is created by the quiz. Email is used for your account; completing the quiz does not opt you into marketing.
We keep account and order records while your account is active and as needed for legal, tax, and security purposes. You can ask us to delete your account data — email [email protected] and we'll remove what we're not required to keep. Referral records tied to an order are kept as long as the order record. For members, only the last five network hashes are kept. Website analytics events are kept by PostHog for up to one year on our current plan, then deleted; the analytics cookie expires after 90 days. The 90-day removal described above for the iPhone signup and link-page comparisons still applies to those comparisons. Website experiment records (tx_ab) are kept for up to one year, then deleted; that cookie expires after 90 days.
Privacy questions? Email [email protected].