MarketPilotMarketPilot legal
Cookie Policy
The cookies and browser storage MarketPilot currently uses and why.
Effective: July 25, 2026
Current use
MarketPilot currently uses cookies and local browser storage that are needed for authentication, security, navigation, integrations, and saved preferences. The codebase does not currently install third-party advertising or audience-analytics cookies.
Cookies
Authentication and security: Auth.js session, CSRF, and callback cookies keep you signed in, defend forms and sign-in flows, and return you to the correct page. Secure production variants may use names beginning with __Host- or __Secure-.
Region preference: marketpilot-active-region remembers the active market available to the account.
Broker connection state: short-lived robinhood_oauth cookies validate broker authorization redirects and are removed or expire after the connection flow.
Local storage
The browser stores theme choices and workspace preferences for charts, opportunity matrices, scanners, and heatmaps. This information stays in that browser unless a feature explicitly syncs it to the account.
Stripe and other sites
Stripe-hosted checkout and the Stripe customer portal, connected brokers, and other linked sites may set their own cookies under their policies. MarketPilot does not control cookies on those separate domains.
Your controls
You can clear or block storage in browser settings, but essential authentication, security, broker connection, and preference features may stop working. Because MarketPilot currently uses only necessary or user-requested storage on its own domain, no optional-cookie banner is presently shown.
If optional analytics, advertising, or similar tracking is added, we will update this policy and introduce consent controls where required before enabling it.