Cookie policy
Last updated 2026-08-16
1.What this page covers
Cookies and browser storage that Saasworld ([Company legal name]) uses when you visit [https://your-domain]. There are no advertising cookies, no third-party analytics scripts and no social-media pixels on the site. Everything below is set by us or by our authentication provider on our behalf.
Because everything we set is either strictly necessary or a first-party preference, we don't show a cookie banner. If that ever changes we'll ask before setting anything non-essential.
2.The cookies and storage keys we use
| Name | Type | Set by | Purpose | Duration | Category |
|---|---|---|---|---|---|
| sb-<project>-auth-token (and .0/.1 chunks) | Cookie (HttpOnly-equivalent via server) | Supabase Auth, via our server | Your session — keeps you signed in and lets the server load your account and progress. | Session; refreshed while you use the site, expires after inactivity | Essential |
| gw_free | Cookie | Saasworld server | Signed-out visitors get one free task. This remembers which one, so a second task asks you to sign up. | About 1 year | Essential |
| gw-theme | localStorage | Saasworld (your browser) | Remembers light or dark theme so the first paint is right. | Until you clear site data | Essential (preference) |
| groundwork.progress.v6 | localStorage | Saasworld (your browser) | Your progress, XP, streak and settings while signed out. Never sent to us until you sign up. | Until you clear site data | Essential |
| groundwork.merged.v1 | localStorage | Saasworld (your browser) | A flag that the signed-out progress above has been merged into your account, so it isn't merged twice. | Until you clear site data | Essential |
| groundwork.anon.v1 | localStorage | Saasworld (your browser) | A random id (UUID) attached to analytics events while you're signed out, so a funnel can be seen end-to-end. Contains nothing about you. | Until you clear site data | Analytics (first-party) |
3.How our analytics work
We record product events — “started onboarding”, “finished a task in course X”, “opened pricing” — in an events table in our own database. Each event carries the event name, a few small properties (like a course slug), and either your user id (signed in) or the random anonymous id from groundwork.anon.v1 (signed out). We use them to see where people get stuck and what gets finished. They aren't shared with anyone and aren't used for advertising.
You can object to this processing at any time (email [privacy email]); clearing your browser's site data resets the anonymous id.
4.Controlling cookies
Your browser lets you view, block and delete cookies and site data for any site — look under Privacy or Site settings. If you block the essential ones, signing in and keeping progress won't work.
Third parties we use may set their own cookies on their domains when you interact with them directly — Google during OAuth login, for example. Those are governed by their policies. See the Privacy policy for the full list of processors.
5.Changes
We'll update this table whenever the app starts or stops using a key. The date at the top is the current version. Questions: [privacy email].