Cookie Policy
alpely.com uses very few cookies, and none of them track you without your permission. This page explains what we set, why we set it, and how you stay in control.
What cookies are
Cookies are small text files that a website stores in your browser. They let a site remember things between pages and visits, like a preference you picked or a session you started. Some sites also rely on similar browser storage, such as localStorage, which works much the same way. When we say "cookies" in this policy, we mean both.
How we use cookies
Everything we set falls into one of two categories: strictly necessary, or analytics that runs only with your consent. We do not use advertising cookies, marketing pixels, or third-party trackers of any kind.
Strictly necessary
These make the site work and remember the privacy choices you make. They do not track you across sites, and they do not require consent:
- alpely_consent stores the choice you make in our consent banner as a small JSON value with your analytics preference. Without it, we would have to ask you again on every visit.
- Supabase session cookies, with names that start with sb-, exist only for members of the Alpely team who sign in to our internal portal at /founders. They are host-only, which means they are never shared across subdomains. If you are a regular visitor, these cookies are never created in your browser.
Analytics, only with your consent
We use PostHog to understand how people use alpely.com: which pages get read, where visitors arrive from, what works and what needs improving. PostHog sets a cookie whose name starts with ph_ and also uses localStorage.
Here is the part that matters: analytics loads only after you accept in the consent banner. Until you accept, or if you decline, the PostHog script never loads and your browser makes no request to PostHog. Not one.
Cookie inventory
This is the complete list of cookies on alpely.com. There are no others.
| Name | Purpose | Duration | Provider |
|---|---|---|---|
| alpely_consent | Remembers your consent choice from the banner (a small JSON value with your analytics preference) | About 180 days | Alpely |
| Supabase session cookies (names starting with sb-) | Keep an Alpely team member signed in to the internal portal at /founders; host-only, never shared across subdomains, never set for regular visitors | About 32 days | Supabase (on behalf of Alpely) |
| PostHog analytics (a cookie starting with ph_, plus localStorage) | Measures how the site is used so we can improve it; set only after you accept in the consent banner | About 12 months | PostHog |
The consent banner
On your first visit, a banner asks whether you accept analytics. Accept and Decline carry the same weight: same size, same style, one tap each. Declining is exactly as easy as accepting.
Whatever you choose is saved in the alpely_consent cookie, and the banner stays out of your way after that. You can change your mind at any time: the "Cookie preferences" link in the footer of every page reopens the banner so you can switch your choice.
Browser privacy signals
We honor Do Not Track and Global Privacy Control (GPC). If either signal is active in your browser, we treat it as a decline: analytics never loads, no matter what. You do not need to configure anything else.
Your data and the privacy notice
Cookies are only one part of how a site handles data. For the full picture, including what personal data we collect, why we collect it, who processes it on our behalf, and the rights you can exercise, read our privacy notice.
Changes to this policy
If we change how we use cookies, for example if we ever add a new one, we will update this page, and the change will be reflected in the effective date shown at the top of this page. If a change involves a new non-essential cookie, we will ask for your consent again before setting it.