Cookie Policy.
Last updated: September 2, 2026
- Signing in, remembering your consent, and crediting the link that brought you here all use cookies we set on every visit.
- PostHog and the Meta Pixel do not load until you accept them.
- Your account's Usage analytics choice controls browser analytics startup. Cookie preferences also apply to PostHog, Meta and Google. Notifications and error reporting have separate purposes.
- Change your answer any time with the button below.
Cookies we set
These come from tradingwizard.ai itself, and the site needs them.
| Cookie | Purpose | Lasts |
|---|---|---|
| next-auth.session-token | Keeps you signed in. Set when you sign in. | Session / 30 days |
| next-auth.csrf-token | Protects the sign-in form against cross-site request forgery. | Session |
| next-auth.callback-url | Remembers the page you were on so you land back there after signing in. | Session |
| tw_consent | Remembers your answer to this banner, and when you gave it. | 180 days |
| wiz_anon | Counts the free questions asked from this browser before you have an account. | 48 hours |
The cookie that records how you got here
This one is set on your first visit whether or not you answer the banner, because it is how an affiliate gets credited for sending you.
| Cookie | Purpose | Lasts |
|---|---|---|
| tradingwizard_ref | Records how you arrived: the referral code, any campaign parameters on the link, the page you landed on and the site you came from. It credits the person or the campaign that referred you. It cannot be read by scripts in your browser. | 30 days |
Tools that wait for your consent
Neither of these loads at all until you accept the matching category in the banner. Accept nothing and their scripts are never fetched.
- PostHog, under Analytics. Product analytics and session recording, so we can see which features get used and watch back what happened around an error. What you type into a field is masked before it leaves your browser. Signed in, it is tied to your account and carries your email address.
- Meta Pixel, under Marketing. Tells us which Facebook and Instagram ads led to a sign-up.
Other tools and your account choice
Google, datafa.st and Vercel analytics can start before you answer the banner, after we resolve your saved Usage analytics preference. They stay off when that preference or this browser's analytics choice is off.
- Google Tag Manager, Google Analytics and Google Ads. The scripts load, but they start in Google's consent mode with everything denied, so they set no cookies and send no identifiers until you accept. Before that they send anonymous pings that let us count visits without knowing who you are.
- datafa.st. Traffic counting. It sets its own first-party cookies to recognise a returning visit. It does not wait for the cookie-banner choice; your Usage analytics preference still applies.
- Vercel Web Analytics and Speed Insights. Page views and load times, with no cookies and no identifier.
- OneSignal. The tool that delivers push notifications. It loads on every page so it can register your device if you turn notifications on.
- Sentry. Error reporting. When something breaks it sends us the fault together with your account id, your IP address and a replay of your screen around the moment it happened, with anything you typed masked.
In Settings → Account, Usage analytics controls browser product tracking across your signed-in devices. The same control is available under Data and Privacy in the older terminal. Turning it off stops browser events from PostHog, datafa.st, Meta and Vercel, disables GA4 measurement and denies Google storage and advertising consent. It does not disable sign-in, billing, notifications or error reporting. Requests already sent cannot be recalled.
Changing your mind
Use the button above, or the Cookie Settings link in the footer. Rejecting on arrival means the consent-gated tools are never loaded. Withdrawing after you have accepted tells PostHog and the Meta Pixel to stop at once: a script that has already loaded stays on the page until you leave it, but it sends nothing more. Clearing the tw_consent cookie makes the banner ask again.
Your browser can also block or delete cookies itself. Blocking the sign-in cookies means you will not be able to sign in.
Contact
Questions about any of this, write to hi@tradingwizard.ai. The Privacy Policy covers what happens to the data these tools collect.
See what the market is doing. Right now.
Deploy my free botFree. No card.
Trading involves risk. Every bot starts in paper mode: no real money.