Cookies and local storage

This page describes the cookies and similar storage this website and app actually use, based on a review of the current codebase. Because only essential storage is used on this site, we do not show a cookie consent banner.

Controller: [TODO: legal name of the eenmanszaak]. Contact: [TODO: privacy contact email].

Essential authentication cookies

Sign-in is provided by Supabase. After you log in, the app stores a session in first-party cookies whose names include -auth-token (Supabase SSR / Auth helpers). These cookies are required to keep you signed in and to protect authenticated pages. They are not used for advertising.

If you only visit the public marketing pages and never sign in, these authentication cookies are not needed for the page to work.

Essential local and session storage (signed-in app)

The following browser storage is used inside the logged-in product, not for marketing:

• funding_firms in localStorage — remembers prop-firm names you have used in the funding tracker.
• tj.journal-cache.v1 in sessionStorage — a short-lived cache of journal data so the app feels faster while you navigate.
• last-seen-ping in sessionStorage — throttles a “last seen” update so the app does not ping the server on every page view.

There is no theme or colour-scheme preference stored in the browser. The interface is always the dark theme defined in the product.

Vercel Analytics

The site uses Vercel Analytics (already enabled once in the root layout). Vercel documents this as cookieless, privacy-friendly analytics (no advertising cookies, no cross-site tracking identifiers from this script). It is used to understand aggregated traffic and performance, not to profile you for ads.

Payments (Stripe), only if you upgrade

Paid plans are started from the in-app billing page. Checkout and the customer portal run on Stripe’s domain. Stripe may set its own cookies there. We do not load Stripe.js on the public landing page.

Intro video (YouTube), when enabled

The landing page is prepared to embed an intro video from youtube-nocookie.com. While the video ID is still a placeholder, no YouTube iframe is loaded. When the video is published, playing it will load Google/YouTube resources, which can set cookies on YouTube’s domain. That embed is not loaded today.

What we do not use

We do not use advertising cookies, a consent-management platform, or marketing pixels on this site in the current codebase. We also do not store a cookie for cookie-consent, because we are not setting non-essential cookies ourselves.

Managing storage

You can clear cookies and site data in your browser settings. Signing out clears the authentication session. Deleting site data will sign you out and remove local caches listed above.