Cookie policy
This policy lists the cookies and browser storage used on spurn.io and by the Spurn tag on our customers' websites.
1. About this policy#
Cookies are small files a website stores in your browser. Local storage and session storage do a similar job. This policy covers both, on spurn.io (the marketing site and the dashboard at spurn.io/app) and on our customers' websites, where the Spurn tag runs (section 5).
2. What spurn.io does not use#
We run no advertising cookies and no third-party analytics on the spurn.io marketing site. There are no ad network pixels or social media trackers, and we do not share cookie data with ad networks.
3. Cookies and storage on spurn.io#
| Name | Type | Purpose | Lasts |
|---|---|---|---|
__Secure-spurn.session_token | First-party cookie, HTTP-only | Keeps you signed in | 30 days, renewed while you use Spurn |
__Secure-spurn.session_data | First-party cookie, HTTP-only | A signed, short-lived copy of your session, so pages load without a database check every time | 5 minutes |
__Secure-spurn.state | First-party cookie, HTTP-only | Protects sign-in with Google or GitHub against forged requests | 5 minutes |
spurn_appsumo_redeem | First-party cookie, HTTP-only | Carries a one-time token while you activate an AppSumo licence | 30 minutes |
spurn_touch | First-party cookie | Records how you found us (see below) | 90 days |
spurn-theme | localStorage | Your light, dark or auto theme, saved only when you pick one | Until you clear it |
| Sonny chat storage | Browser storage | Dashboard only: a chat visitor id and your conversation, so the chat carries on between pages | Until you sign out |
The __Secure- prefix tells your browser to send a cookie only over HTTPS. All our cookies use SameSite=Lax.
The sign-in cookies, the AppSumo cookie and the theme setting are needed for the features you use, and the site does not work as expected without them.
spurn_touch is our own marketing attribution. It is only set when you arrive at spurn.io from a link with campaign tags or an ad click id. It keeps the campaign tags, click id, landing page, time and referring site of your first and latest tagged visits. When you sign up, we read it once and save it to your account so we know which of our marketing brings customers. It is not shared with ad platforms or anyone else. Blocking or deleting it does not affect how the site works.
4. Cookies set by others#
- Stripe. Checkout and the billing portal are on Stripe's own pages, where Stripe sets its own cookies for payments and fraud prevention. See Stripe's cookie policy.
- Google and GitHub. If you sign in with them, their sign-in pages set their own cookies.
- Cloudflare. Cloudflare protects spurn.io and may set a
cf_clearancecookie if it shows you a security challenge.
Sentry, which we use for error monitoring, sets no cookies.
5. Storage the Spurn tag uses on customer sites#
When a website uses Spurn, the tag stores these items in the visitor's browser, on that website's own domain:
| Name | Type | Purpose | Lasts |
|---|---|---|---|
_spc | First-party cookie, SameSite=Lax | Pageview id and ad click id, so an order can be matched to the paid click | 30 days |
_sp_v | localStorage | Random visitor id, to spot repeat clicks from the same device | Until cleared |
_sp_s | sessionStorage | Marks a paid session, so later pages count as part of it | 30 minutes without activity, or when the tab closes |
The tag only runs on visits that arrive from a paid ad and on the later pages of that paid session. On organic visits it stores nothing and sends nothing. The Shopify app's web pixel and the WordPress and WooCommerce plugin read _spc to match orders to clicks.
This storage is used only for fraud prevention. The website owner is the controller of the data and decides whether its visitors must consent first. It can load the tag through its consent tool or tag manager, or use a server integration alone, which stores nothing in the browser.
If the website has its own Meta pixel or Microsoft UET tag, the Spurn tag may send an event through it for flagged visitors. Those pixels and their cookies belong to the website owner and to Meta or Microsoft.
For questions about a site that uses Spurn, contact its owner. Our privacy policy explains what the tag collects.
6. Managing cookies#
You can block or delete cookies and browser storage in your browser settings. If you block the sign-in cookies, you cannot sign in to the dashboard. Signing out clears the Sonny chat storage.
7. Changes and contact#
We update this page when we add or change a cookie. Questions go to legal@spurn.io.