Cookie Policy

Cookies are small text files placed on your device by a website or service. They help the site recognize your browser, keep you signed in, and remember certain settings.

Similar technologies include browser storage such as localStorage and sessionStorage. These are not always cookies, but they can store information on your device for similar product purposes. This policy covers both.

TradePilot uses cookies and similar technologies to:

• Keep you securely signed in and protect account access
• Remember chart, toolbar, and replay preferences on your device
• Support create-session and onboarding flows within a browser session
• Enable payment checkout and billing portal on Stripe-hosted pages when you choose a paid plan

Based on the current TradePilot application code and dependencies, we do not use advertising cookies, marketing pixels, or third-party web analytics tracker SDKs that set browser cookies for advertising or audience measurement.

In-product “analytics” features (for example trade or playbook performance views) are product features that run on your journal data. They are not the same as third-party website analytics cookies.

These are required for TradePilot to authenticate you and run securely. Without them, sign-in and protected dashboard access will not work reliably.

Clerk (our identity provider) sets session and security-related cookies so you can create an account, sign in, stay signed in, and manage your account. Exact cookie names and lifetimes are managed by Clerk and may change with their configuration; they are not hardcoded in TradePilot source.

Disabling strictly necessary cookies will typically prevent signing in or remaining signed in.

TradePilot stores product preferences and temporary workflow state in first-party browser storage (primarily localStorage and sessionStorage). Examples include:

• Backtest toolbar favorites and recent tools
• Indicator favorites and recently used indicators
• In-progress replay draft state
• Pending create-session selections during a browser session
• Onboarding dismissal flags for the current tab session
• Charting library UI settings/favorites when the TradingView Advanced Charts widget is used (first-party storage on TradePilot)

These technologies improve usability. Clearing them may reset preferences or interrupt an in-progress replay draft, but core journaling and account features can still operate after you sign in again.

TradePilot does not currently include a third-party web analytics or product-telemetry SDK (such as Vercel Analytics, Google Analytics, or similar) that sets analytics cookies in the browser. If we add non-essential analytics cookies in the future, we will update this Cookie Policy and, where required, request consent before using them. See also our Privacy Policy.

TradePilot does not currently use marketing or advertising cookies, retargeting pixels, or similar advertising trackers.

Some providers process data to run TradePilot. Only the following are relevant to cookies or browser storage based on how the product is implemented today:

• Clerk — authentication and account session cookies / related client storage required to sign you in.
• Stripe — when you start checkout or open the billing portal, TradePilot redirects you to Stripe-hosted pages. Stripe may set its own cookies on Stripe's domains to process payment securely. TradePilot does not load Stripe.js trackers on TradePilot pages for advertising.
• TradingView Charting Library — embedded chart UI may store settings in first-party browser storage on TradePilot (not advertising cookies).
• Hosting (for example Vercel) — infrastructure that serves the site may use operational cookies for security or delivery. TradePilot does not configure Vercel Analytics or Speed Insights packages in the current application dependencies.

Supabase (database/storage), OpenAI (optional AI features), and market-data providers used on the server are not used in a way that sets TradePilot browser cookies based on current application code. Their processing of account or content data is described in the Privacy Policy.

TradePilot uses first-party localStorage and sessionStorage for functional preferences and temporary workflow state, as described above. We do not use IndexedDB in TradePilot application code based on the current repository audit.

These stores remain on your device until cleared by you, by the browser, or by the product when a flow completes or migrates data.

You can control cookies and site data through your browser settings (block, delete, or limit cookies and site storage for TradePilot).

Because TradePilot currently relies on strictly necessary authentication cookies and functional first-party storage—and does not load optional advertising or analytics trackers—we do not show a separate cookie preference banner at this time. If that changes, we will update this policy and provide an appropriate control.

If you block or delete authentication cookies, you may be unable to sign in, stay signed in, or use protected areas of TradePilot. Blocking functional browser storage may reset chart preferences or clear draft session state, but does not by itself cancel your account.

Most browsers let you view and delete cookies and site data, and block third-party cookies. Steps vary by browser and device. Refer to your browser's help documentation for current instructions. Private or incognito modes may limit persistence of local and session storage.

We may update this Cookie Policy when our practices or product change. When we do, we will revise the “Last Updated” date at the top of this page. Continued use of TradePilot after changes become effective constitutes acceptance of the updated policy, to the extent permitted by applicable law.

For questions about this Cookie Policy, contact us at jake@mytradepilot.ca. Related documents: Privacy Policy · Terms of Service.