Cookie policy
Last updated 14 September 2026
This document is a plain-English starting point written for this product, not legal advice. Have a lawyer review it against your jurisdiction and your actual data practices before you rely on it.
SplitSimple uses very few cookies. Here is all of them.
On splitsimple.com (the app)
sb-*— Supabase authentication. Keeps you signed in. Strictly necessary, HTTP-only, secure.ss_ws— remembers which workspace you were last looking at. Strictly necessary for the app to work, and it is only ever a hint: your access is re-checked against the database on every request.ss_vid— set when you click an experiment link, so a returning visitor stays on the same page. A random string, nothing more.
We run no advertising cookies, no third-party analytics cookies and no cross-site trackers on this site.
On our customers’ pages
When a customer installs the SplitSimple pixel, it sets one first-party cookie on their domain:
ss_vid— a random 22-character string. Lifetime: 2 years. Purpose: keeping a visitor on the page they saw first, so the two sides of the test stay separate. It contains no personal data and is not readable across sites.
Cookie-free mode
Any experiment can run without cookies. Attribution then comes only from the parameter our redirect link appends, and it lasts for the pageview rather than across visits. Turn it on by adding data-cookieless="true" to the pixel tag.
If you are a SplitSimple customer
You are responsible for disclosing this cookie in your own cookie banner or privacy policy, and for collecting consent where your jurisdiction requires it. The privacy policy explains the split of responsibilities.