Cookies Policy
This page explains what cookies and similar technologies CodeFoundry uses, and how you can control them.
Last updated: July 26, 2026
1. What Are Cookies
Cookies are small text files placed on your device by your browser. They let a site remember information about your visit, such as your session, so you don't have to re-enter it every time you load a page. Because CodeFoundry is a multi-page application without a single-page "app" framework, cookies and browser storage are essential to keeping you signed in as you move between Training, Dashboard, and Checkout pages.
2. Cookies We Use
We intentionally keep our cookie footprint small and first-party only. We do not use third-party advertising or cross-site tracking cookies.
- Strictly necessary — session and CSRF-protection cookies required for login, checkout, and form security. The Platform cannot function without these.
- Preference — remembers small UI choices such as whether you've already seen the welcome splash screen in your current browser tab.
- Local progress markers — some quiz-level completion state is stored in your browser's local storage (not a cookie, but a related browser technology) so level-selection screens can show checkmarks instantly without a server round trip.
3. Cookie Reference Table
- Session cookie — Purpose: keeps you signed in across pages. Duration: expires when you close your browser or sign out.
- CSRF token — Purpose: protects forms (login, checkout, profile updates) from cross-site request forgery. Duration: per session.
- Splash-seen flag — Purpose: prevents the welcome animation from replaying on every page. Duration: per browser tab session.
4. Managing Cookies
Most browsers let you view, delete, and block cookies through their settings menu. Because our "strictly necessary" cookies are required to keep you logged in and to protect forms from forgery, blocking them will prevent sign-in and checkout from working correctly. You are always free to browse public pages, such as course descriptions, without accepting any cookies at all.
5. Third-Party Cookies
Where a payment provider is used at checkout, that provider may set its own cookies as part of processing your payment securely; those are governed by the provider's own privacy and cookie practices, not this policy.
6. Changes to This Policy
We may revise this Cookies Policy as our use of cookies evolves. The "Last updated" date above will reflect any changes.
7. Contact
Questions about cookies can be sent via Support or to privacy@codefoundry.org. See also our Privacy Policy.