Cookies, and the short list of them.
A cookie is a small note a website leaves in your browser so the next page knows something the last one did. Here is every one Piggles uses, which of our three sites uses it, and what it is for.
The ones that make it work
Without these, signing in does not stay signed in. There is no version of Piggles that works without them, which is why there is no switch for them.
| Cookie | Where | What it is for | How long |
|---|---|---|---|
| better-auth.session_token | getpiggles.com and mypiggles.com | Keeps you signed in. Each of the two sites sets its own copy on its own address — they cannot share one — and both point at the same single sign-in, so signing out of either ends both. | Until the session expires or you sign out |
| sparx_active_property | mypiggles.com | Remembers which of your sites you were last working on, so the workspace opens where you left it. It holds an identifier for one of your own sites and nothing about you. | One year |
The ones that tell us what to fix
These live inside the workspace at mypiggles.com — the place you do the work — and nowhere else. They are how we find out that a screen is confusing or that something failed quietly.
| Cookie | Where | What it is for | How long |
|---|---|---|---|
| PostHog (several, all beginning ph_) | mypiggles.com | Product analytics inside the workspace: which screens get used and where something broke. It tells us that a screen is confusing. It is not advertising, it is not sold on, and it is not running on the site you are reading now. | Up to one year |
| sparx_attr_first | Read on mypiggles.com | Records which page first brought somebody to a WizeWorks product, so we can tell what is working. Piggles’ own marketing site does not set it — this is read only if you arrived by way of a sparx site. | Up to one year, if present |
Four things worth knowing
None of them are advertising cookies
There is no ad network on any Piggles site, nothing is sold or passed to a data broker, and nothing here follows you to somebody else’s website.
The site you are on right now sets nothing
meetpiggles.com has no tags at all. Which page you clicked "start free" from travels in the link itself rather than in a cookie — the three Piggles addresses are separate domains and could not share one anyway.
Signing in with Google is your choice
If you sign in with Google rather than a password, Google sets its own cookies as part of that and knows you signed in to Piggles. A password involves nobody else. Either way Piggles ends up with the same one session cookie.
Connecting an outside account does not add cookies here
Linking Instagram, Amazon or a carrier lets Piggles talk to them from our servers — it does not put their tracking on any page you look at. What information travels to them is on the privacy page.
Your own visitors are your business, not ours
The website you build with Piggles is yours. If you add something to it that sets cookies — a chat widget, an ad pixel, a video embed — that is your decision to make and yours to tell your visitors about.
Turning them off
Every browser can block or clear cookies, and you can use Piggles’ public pages with them off entirely. Signing in is the one thing that genuinely needs one: without the session cookie there is no way for the next page to know it is still you.
More on how your information is handled is on the privacy page, and how it is kept safe is on trust.