Cookie Policy
Last updated: August 19, 2026
This Cookie Policy explains how Trading Risk Lab uses cookies and similar technologies on our website and our Service.
1. What cookies are
- • Cookies are small text files placed on your device when you visit a website or use an online service.
- • We also use similar technologies such as local storage and session storage. In this Cookie Policy, we refer to all of these together as “cookies” unless the context requires otherwise.
2. How we use cookies
We use cookies and similar technologies to:
- • Keep the website and tools working, including sign-in, session continuity, and core security-related functionality.
- • Store essential settings and your analytics consent preference.
- • Measure how visitors use the website and tools through Google Analytics, but only where required after you have given consent.
- • Support infrastructure, performance, and security services used to operate the website.
3. Types of cookies we use
Strictly necessary cookies and storage
These are required for the website and core product features to function properly. They may be used for authentication, login/session continuity, security, load balancing, consent state, and similar core operations. Because they are necessary for the Service, they do not rely on optional analytics consent.
Analytics cookies
These help us understand how visitors use the site and tools so we can improve performance, usability, and content. We currently use Google Analytics as our analytics provider. Where required by law, analytics cookies are used only after you have given consent through our cookie banner or preferences panel in Data & privacy in Account Settings.
Providers and technologies currently used
- • Trading Risk Lab / browser storage: used to store essential settings and your consent preference, including local storage entries created by our consent tool.
- • Supabase: used for authentication and account-related functionality that may require essential cookies or storage.
- • Cloudflare: used for hosting, content delivery, performance, and security. Cloudflare may process technical request information and may set cookies or similar technologies where needed for these purposes.
- • Google Analytics: used only for analytics purposes and only where required after consent.
- • Paddle: when you enter a checkout or payment flow, Paddle may use cookies or similar technologies required to provide billing, fraud prevention, tax, and payment services.
Current first-party and commonly encountered storage
- • trl_consent_v1 (local storage): records whether you made an analytics choice, the analytics setting, and the decision timestamp. It remains until you change the preference, clear site data, or the application replaces the stored version.
- • Theme, accessibility, and tool-preference storage: first-party local or session storage may remember choices such as theme, reduced-motion settings, tool state, or similar non-advertising preferences. Session storage normally ends with the browser session; local storage remains until cleared or replaced.
- • Supabase authentication storage: when you sign in, Supabase may store session information in browser storage so that authentication can continue and refresh securely. The exact storage key can include the Supabase project identifier and is tied to the authentication session.
- • Google Analytics cookies such as _ga and _ga_<container>: created only after analytics consent where required. Their duration is controlled by Google Analytics configuration and browser behavior. If you withdraw analytics consent, our consent tool disables analytics and makes a best-effort attempt to remove first-party Google Analytics cookies.
- • Cloudflare Turnstile/security storage: security checks may use technically necessary cookies or storage when required to distinguish legitimate requests from abuse.
- • Paddle checkout storage: Paddle may create payment, fraud-prevention, checkout, tax, and session technologies when you interact with Paddle-controlled payment or customer-portal flows. Their names and durations are controlled by Paddle.
Cookie and storage names can change when providers update their services or when browser behavior changes. We review this policy when material technologies or purposes change.
4. Managing your cookie preferences
- • When no prior analytics decision is recorded, our consent tool displays a cookie banner. Our current consent tool uses one optional category only: analytics.
- • You can accept analytics, reject analytics, or reopen the preferences panel later where that option is available.
- • You can also manage cookies through your browser settings, where you can delete existing cookies or block new ones, although doing so may affect core functionality.
- • If you withdraw analytics consent, we set analytics consent to denied, disable Google Analytics for the current page context, and make a best-effort attempt to remove first-party Google Analytics cookies. Withdrawal does not affect processing that lawfully took place before withdrawal.
5. Changes to this Cookie Policy
- • We may update this Cookie Policy from time to time to reflect changes in the Service, our providers, the technologies we use, or legal requirements.
- • We will post the updated version on this page and update the “Last updated” date.
6. Contact
- • If you have questions about our use of cookies or your analytics consent choices, you can contact us at .
- • For more information about how we process personal data, please see our Privacy Policy.
Need more information?
Read our other legal documents, or get in touch with questions about your data and privacy.