Version 3.6 · Effective October 18, 2026
Privacy Policy
Supersedes version 3.5, effective October 17, 2026. Previous versions are archived at tradeainews.com/legal/archive. For accounts created before October 17, 2026, the changes that version 3.5 introduced apply from November 16, 2026, as we announced by email. Version 3.6 adds Portfolio Research (sections 2.1, 3 and 6), saved Research queries in the Journal (section 2.1) and states what we keep of the records of what you agreed to when you delete your account (section 6).
1. Who is responsible for your data
TradeAI News LLC, 30 N Gould St, Ste N, Sheridan, WY 82801, United States, is the controller of the personal data described here.
Contact for anything in this policy: support@tradeainews.com
2. What we collect
2.1 What you give us
- Email address — at signup and login, to authenticate you and to send one-time codes, receipts and service notices.
- If you sign in with Google — your email address, whether Google has verified it, and an identifier for your Google account. We use them only to sign you in and to recognise your account the next time you use Google sign-in. We do not receive your name, photo, contacts or anything else from your Google account.
- Name — optional. You can add it under My Account › Profile at any time. If you subscribe and haven't added one, we take the name you enter at checkout (see section 2.3). We use it only to address emails to you.
- Newsletter email — on separate opt-in, to send the newsletter you asked for.
- Market Brief email setting — if your plan includes the Market Brief: whether you turned its email on or off, when, from where (in the app), and the exact wording of the setting you saw, so the record shows what you agreed to.
- Telegram ID — if you connect Telegram, to deliver alerts to you there.
- Country and other optional profile details — voluntary, at any time, to understand in aggregate who uses the product. If you subscribe and your profile has no country, we take the billing country you enter at checkout.
- Journal entries — ticker, side, quantity, prices, timestamps, stop-loss and take-profit levels, and your notes, so we can show you your own journal with market context.
- Saved Research queries. If you save a query in the Journal's Research view, we store the name you give it and the filters and grouping you chose, linked to your account, so you can run it again. We do not store the results, which are recalculated from your own trades each time. You can delete a saved query at any time, and all of them are deleted when you delete your account. Saved queries are never combined with other users' data.
- Watchlists, portfolio entries, notification settings — when you set them, to operate the features you turned on.
- Portfolio Research holdings — if your plan includes Portfolio Research and you use it: the portfolios you enter or import (their names, the tickers, quantities or weights and, only if you add them, cost basis and purchase dates), to calculate the portfolio analytics you ask for. An imported CSV file is processed and discarded; only the rows you save are kept. We do not share these holdings, we do not use them for marketing, and we do not use them to train models.
- Research notice — if you use Allocation Models: that you accepted its notice (research and analysis only, not investment advice), when, from where (in the app), your plan at the time and the exact wording you saw, so the record shows what you agreed to.
- Watchlist alerts — the list of recorded changes we compute for the tickers on your watchlist after each close, to show them to you in the dashboard and, if you turned it on, by email.
- Watchlist alert email setting — if your plan includes the alert email: whether you turned it on or off, when, from where (in the app), and the exact wording of the setting you saw, so the record shows what you agreed to.
Broker export files. If you import trades from a broker export, the file itself is processed and discarded. We do not store the file. We extract only the trade fields listed above; account numbers, balances and commissions are not retained.
Two things about the import are kept, so that the next import works: the name of the broker the file came from, and how its columns map to our fields. Neither contains your trades, your balances, or anything about your account with that broker.
2.2 What we collect automatically
- Pages viewed, features used, in-product events — from our own first-party analytics, to understand what people use and what is broken.
- A first-party identifier, stored in the
tai_aidcookie for 12 months and set in your browser on your first visit, so we can recognise that several page views come from the same browser. - Where you arrived from — referring site, campaign parameters, the partner link if you used one, and the first page you opened (its address, without anything after a question mark) — stored in the
tai_srccookie for 12 months and set on your first visit, so we know which channel brought you here. - Your most recent campaign or partner visit — the same items for the last visit that arrived through a campaign or a partner link, stored in the
tai_ltcookie for 12 months. - IP address, browser and device info, timestamps — from our hosting providers' logs, for delivering the site, security and abuse prevention.
- Session recording — clicks, scrolling, mouse movement and page interactions, by Microsoft Clarity, on every page, to see where the product confuses people.
- Third-party web analytics — by Google Analytics, for aggregate traffic measurement.
About tai_aid, tai_src and tai_lt. These are our own cookies. They contain no name, no email and nothing you typed — only a random identifier and, in tai_src and tai_lt, where your first visit and your most recent campaign or partner visit came from. They are not necessary for the site to work; they exist so that we can measure it. In our database the same identifier appears as anon_id.
When you create an account, that identifier is linked to your account, so that the pages you viewed before signing up can be attributed to your signup. When you delete your account, we remove your account identifier from those analytics records. The records themselves are kept, still carrying the anonymous identifier, but no longer connected to you.
Deleting your account does not clear the tai_aid cookie from your browser. You can delete it yourself in your browser at any time, and a new visit would then start a new identifier.
Partner links and codes. If you arrive through a partner's link or page, or use a partner's code at checkout, we record which partner referred you. When you create an account, we store the items from tai_src and tai_lt with your account. We use them to pay that partner a commission on what you pay us, and to see which channels bring people to TradeAI News. Partners never receive your name, email address or payment details: they receive only monthly totals of referred customers and amounts. The partner code and the channel are also stored with your subscription at our payment processor.
If you are a TradeAI News partner, we keep your display name, your partner code and, to prevent self-referrals, a one-way hash of your email address. The details you give us to receive commissions are used only to pay you and are kept as financial records.
2.3 What we never collect
- We never see or store your full payment card number. Stripe handles payment details directly. We receive a customer reference, the last four digits and brand of the card, the outcome of each payment and, if your profile doesn't already have them, the name and billing country you enter at checkout. We never receive the full card number.
- We do not ask for, and do not want, your broker credentials.
- We do not collect government identifiers, and we do not knowingly collect data from anyone under 18.
3. Why we are allowed to use it (legal bases)
For users in the EU, the UK, and anywhere else with equivalent rules, this is the legal basis for each purpose.
- Creating and running your account, and authentication — performance of a contract.
- Delivering the Service you subscribed to, on the dashboard, by email or on Telegram — performance of a contract.
- Taking payment and keeping billing records — performance of a contract; legal obligation.
- Transactional emails — one-time codes, receipts and service notices — performance of a contract.
- Newsletter and marketing emails — consent, which you give by opting in and can withdraw at any time.
- The Market Brief email — consent, which you give by turning it on in your account, on the Brief page or under My Account › Notifications. It is off until you turn it on. You can turn it off there at any time, or use the unsubscribe link in any brief email.
- Watchlist alert emails — consent, which you give by turning them on under My Account › Notifications. They are off until you turn them on. You can turn them off there at any time, or use the unsubscribe link in any alert email.
- Product analytics, session recording and measuring which channel brought you here — consent, where the law requires it for non-essential cookies and similar technologies; otherwise legitimate interests. You may object or withdraw at any time.
- Paying partners a commission for the customers they refer, and preventing self-referrals — legitimate interests.
- Portfolio Research analytics on the holdings you enter or import — performance of a contract. You can edit or delete those holdings at any time.
- Keeping the record of what you agreed to — the terms, email consents and the research notice — legitimate interests: being able to show what you were told and when.
- Optional profile details — consent.
- Taking your name and billing country from checkout when your profile has none, to address emails to you — legitimate interests. You can change or remove them under My Account › Profile at any time.
- Security, fraud and abuse prevention — legitimate interests.
- Responding to legal requests and keeping records the law requires — legal obligation.
Withdrawing consent is as easy as giving it: unsubscribe from any marketing email, or write to support@tradeainews.com. Withdrawing does not affect what we did before you withdrew, and it does not stop transactional emails that are part of the Service.
We do not use your data for automated decisions that produce legal or similarly significant effects about you. Prices are the same for everyone, except for the discount that a published partner or promotion code gives to anyone who uses it. We do not profile individuals and we do not vary what we charge based on who you are.
4. Who we share it with
We do not sell your personal data, and we do not share it with advertisers or data brokers. We use the following processors:
- Stripe, Inc. (US) — payments and subscription billing. Receives your email, name, the payment details you enter directly with Stripe, a customer reference, our
anon_idand, if any, the partner code and the channel that brought you, for attribution. - Vercel Inc. (US) — website hosting and CDN, in the US East region. Receives request data including IP addresses.
- DigitalOcean, LLC (US) — application servers and database, in its New York region. Receives all account data listed in section 2.
- Telegram — alert delivery, if you connect it. Receives your Telegram ID and the alert content.
- Google sign-in (Google LLC, US) — only if you choose "Continue with Google". Google confirms who you are and sends us the items listed in section 2.1. Google learns that you are signing in to TradeAI News, under Google's own privacy policy.
- Google Analytics (Google LLC, US) — aggregate website analytics. Receives usage data, a truncated IP and a Google identifier.
- Microsoft Clarity (Microsoft Corp., US) — session recording: it records your clicks, scrolling, mouse movement and page interactions, on every page of the site. Receives interaction data and a Clarity identifier.
Note on Microsoft Clarity, stated plainly because version 2.0 did not: it runs on every visit, not "when enabled", and what it does is record your session. If you would rather it did not, see section 5.
We may also disclose data where the law requires it, to respond to a valid legal process, or to protect our rights, our users, or the public. Where we are permitted to tell you about such a request, we will.
If the company is ever sold or merged, your data may transfer as part of that, and we will tell you before it happens and before any new policy applies to you.
5. Cookies and similar technologies
- Essential — your login session (
tradeai_token) and your saved preferences. Necessary: without these you cannot log in or stay logged in. - Analytics and measurement — our own
tai_aid,tai_srcandtai_ltcookies, Google Analytics, and Microsoft Clarity session recording. Not necessary: the site works without them. They exist so we can measure it. - Google sign-in — Google's sign-in script loads only on the sign-in and sign-up pages (/login and /signup), when they open, so that the "Continue with Google" button can appear. Google may use its own cookies to show your Google accounts. Necessary for that way of signing in; it does not load on any other page of the site.
- Advertising — none. We run no advertising or cross-site tracking technology.
How to refuse the second category today. You can block or delete these cookies in your browser, and you can opt out of Google Analytics with Google's browser add-on and of Microsoft Clarity through Microsoft's own controls. Write to support@tradeainews.com and we will exclude you.
6. How long we keep it
- Account data — email, name, Telegram ID, Google account identifier, settings: while your account is open. Deleted immediately on account deletion.
- Journal entries, watchlists, portfolio, Portfolio Research holdings — while your account is open, or until you delete them. Deleted immediately and permanently.
- Records of what you agreed to — acceptance of the terms, email consents and the research notice: while your account is open. When you delete your account, your email address is removed from these records; we keep only a keyed hash of it (not the address), which agreement it was, the version of the text and the dates, so that we can still show what was agreed and when.
- Watchlist alerts — 365 days, or until you delete your account.
- Broker export files — not retained at all (section 2.1).
- Broker import settings — broker name and column mapping: while your account is open.
- Payment and billing records — for as long as applicable tax and accounting law requires us to keep them. Card numbers are never held by us.
- Suppression list — the record that you unsubscribed or bounced: kept indefinitely, because its only purpose is to make sure we do not email you again. It holds a minimal record and nothing else. The exceptions are your own requests for the Market Brief email and for the watchlist alert email: if you later turn either of them on while signed in to your account, we send you that email again, and your unsubscribe still applies to every other product email. We keep a record of when you did this. Turning that email off, or unsubscribing again, ends its exception.
- Where your account came from (section 2.2) — while your account is open. Deleted immediately on account deletion.
- Partner commission records — for as long as accounting law requires. They hold only payment-processor references and amounts, never your name or email address.
- Server and security logs — no longer than necessary for security and operational purposes.
- Product analytics records with the account identifier removed — indefinitely.
Deleting your account removes your email, name, Telegram ID, Google account identifier, subscription record, the record of where your account came from, journal, watchlist, watchlist alerts, portfolio, Portfolio Research holdings, API keys, webhooks and notification settings in a single operation, immediately — not on a schedule.
What survives, and why:
- Payment records held for accounting and tax. Never card numbers.
- Your entry on the suppression list, so that deletion does not accidentally make you emailable again.
- Product analytics records, with your account identifier removed, as described in section 2.2.
- A minimal record of what you agreed to: a keyed hash of your email address instead of the address, which agreement, which version of its text and when.
- Records held by Stripe under Stripe's own policy, which we do not control.
7. Where your data is processed
We are based in the United States. The website is served from Vercel's US East region, and our application servers and database run on DigitalOcean in its New York region. If you are in the EU, the UK, or another country with data transfer rules, your data is transferred to the United States to provide the Service.
For those transfers we rely on the European Commission's Standard Contractual Clauses, together with the UK Addendum where UK data is involved, and on encryption in transit. Our payment, hosting and analytics processors each publish data protection terms that incorporate those clauses.
You can ask us about the transfer safeguards that apply to any particular processor at support@tradeainews.com.
8. Your rights
Wherever you are, you can access, correct, export or delete your data, and most of it you can do yourself from the dashboard. For anything else, write to support@tradeainews.com and we will respond within 30 days.
If you are in the EU or the UK, you also have the right to: restrict how we process your data; object to processing based on legitimate interests, including profiling; receive your data in a portable format; withdraw consent at any time; and lodge a complaint with your national data protection authority — you do not have to come to us first, though we would rather you did.
If you are in California, you have the right to know what we collect and why, to delete it, to correct it, and to opt out of "sale" or "sharing". We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are defined under the CCPA/CPRA — we run no advertising technology at all. We will not discriminate against you for exercising any right.
We ask for no fee and we will not make you create an account to exercise a right.
9. Security
We do not store passwords at all. Login is by a one-time code sent to your email, so there is no password of yours for anyone to steal from us.
Traffic to and from the site is encrypted in transit, and the site is served over HTTPS only, with HTTP Strict Transport Security enabled. Payment card details never reach our servers — they go directly to Stripe.
No system is perfectly secure. If a breach affects your personal data and is likely to put you at risk, we will notify you and the relevant authority without undue delay, and, where required, within 72 hours of becoming aware of it.
10. Children
The Service is for adults. We do not knowingly collect data from anyone under 18. If you believe a child has given us data, write to support@tradeainews.com and we will delete it.
11. Changes to this policy
Every version carries a version number and an effective date, and previous versions stay available at tradeainews.com/legal/archive.
If we make a change that materially affects how we use your data, we will tell people who already have an account by email at least 30 days before the change applies to them. For people who create an account after a version is published, and for visitors without an account, that version applies from its effective date. For other changes, the updated version applies from its effective date.
TradeAI News LLC
30 N Gould St, Ste N, Sheridan, WY 82801, United States
support@tradeainews.com · legal@tradeainews.com
Version 3.6 · Effective October 18, 2026 · Previous versions