Last updated: August 2026
This page explains, plainly, what PlotForge actually uses cookies for. Short version: not much, and nothing that tracks you.
One strictly necessary session cookie, set when you log in. It's what keeps you logged in as you move around the app instead of asking you to sign in on every page. It's set by our authentication provider, Supabase, and it's deleted when you log out.
Cookieless analytics — we use Vercel Analytics to understand overall traffic to the site (how many people visit, which pages), which works without setting any cookie or identifying individual visitors.
Local storage (not a cookie, but similar in spirit) — your browser preferences, like light/dark theme and sound settings, are saved locally on your device so they persist between visits. This data never leaves your browser.
No advertising cookies. No cross-site tracking. No third-party marketing pixels. PlotForge doesn't run ads and has no ad-network integrations, so there's nothing here to opt out of beyond what's already absent.
Under most cookie regulations, strictly necessary cookies — like the login session cookie described above — are specifically exempt from requiring a consent banner, since the site can't function without them. That's the only cookie PlotForge sets, so you won't see a cookie consent popup here.
When you subscribe to Pro, checkout happens on a page hosted by Dodo Payments, our payment processor — any cookies set during that checkout process are set by Dodo, not by PlotForge directly, and are used only for processing your payment securely.
If our cookie usage ever changes — for example, if we add analytics that require consent — we'll update this page and add a consent mechanism if one becomes necessary.
Questions? Reach us at hello@plotforge.site.