The fine print
Cookies Policy
Last updated: October 18, 2026
What This Page Covers
Cookies are small files a site stores in your browser so it can remember things between visits, like whether you're logged in. This page lists exactly which cookies we use and why.
Cookies We Use
wider_session is our own cookie, used for admin login. Alongside it, Supabase sets its own session cookies, the ones with names starting sb-, which keep you signed in when you log in with Google or with an email and password. Together, these cookies exist to keep you logged in and your account secure.
Once Google Analytics is live, which is landing soon, it will set cookies named _ga and _ga_ followed by an ID. Those help us understand how visitors use the site.
PostHog, the analytics tool we use to see where visitors get stuck between landing on the site and getting in touch or signing up, sets cookies whose names start with ph_. They hold your PostHog identifier and the state it needs from one page to the next, and they last up to a year. It runs alongside Google Analytics rather than instead of it, and it also runs in the course area. If you withdraw analytics consent, the ph_ cookies and the stored identifier are deleted. What it collects, and what it doesn't, is in the Privacy Policy.
wider_ref is our own cookie, set only when you open an active partner link or enter a partner code at checkout. It carries the link or code you came with, when it was set and how (link or code), and a signature that prevents tampering, so the discount stays applied until you pay and we can credit the purchase to the partner. It holds no name, email or other personal detail. It lasts 30 days, browser scripts cannot read it, and we don't use it for analytics, advertising or building a profile. The cookie is set when the link opens. Checkout shows a notice about it, and you can remove the code or continue at the regular price. What we do with the partner record is in the Privacy Policy.
wider_invite is set only for someone who opens an invitation to join the partner program. It holds the invitation token for an hour at most, so the token doesn't stay in the page address.
Your Choice
On your first visit a banner offers two choices: accept all cookies, or necessary only. Both take one click and carry the same weight. Refusing shouldn't be harder than agreeing. Until you choose, neither Google Analytics nor PostHog loads at all, and their scripts never run. PostHog goes a step further. Its library isn't even downloaded, so there's no ph_ cookie and no data. Pick necessary only and both stay off. If you withdraw consent later, PostHog stops capturing.
The essential cookies above are set without asking, because without them the site can't log you in, run your account, or keep the discount from a partner's link or code applied until you pay. They stay active even if you chose necessary only. The choice itself is stored in a cookie too, wider_consent, so we don't ask again on every page.
It's kept for a year. To change it, delete wider_consent through your browser settings and the banner comes back.
Managing Cookies Yourself
Chrome, Firefox, Safari, and Edge all let you view, block, or delete cookies through their settings. Feel free to use those controls. Just know that blocking the essential cookies above will break login, account features and a partner discount at checkout on this site.
Third-Party Cookies
If you accepted all cookies, the Google Analytics ones are set and controlled by Google rather than by us. The ph_ cookies belong to PostHog, and the data collected with them goes to its servers in the United States, outside Israel and the EEA. For how Google and PostHog handle that data, see each one's own privacy and cookie information. Without that acceptance, none of them are ever set.
Changes to This Policy
We may update this policy as the cookies we use change. The date at the top of the page shows the version currently in effect.
Contact
Questions about the cookies we use go to shahar@wider-group.com.