SetTern.io · Legal · Strictly-necessary only

Cookie Notice

The cookies we set, the ones we don't, and how to clear them. No advertising, no cross-site tracking, no third-party profiling pixels.

Last updated · 1 May 2026 Effective · 1 May 2026 Version · v1.4
★ The short version

We use only the cookies that are strictly necessary to keep you signed in, remember your consent, and protect the service from abuse. We do not use advertising or cross-site tracking cookies.

What we set
Strictly-necessary

Four cookie types. None of them follow you off the site.

Authentication session session
Keeps you signed in after Google sign-in. Set when you sign in, cleared when you sign out.
Consent record consent.v1
Remembers that you have accepted our terms and consent so we don't prompt you again on every visit.
Anti-abuse signals rl.*
Short-lived rate-limit counters to keep free-tier quotas honest.
Payment session __stripe_*
Set by Stripe during checkout to complete your purchase securely. Stripe is our payment processor.
× What we don't set
Never

No matter how clever the marketing case, we don't ship these.

Advertising cookies
No third-party ad-network IDs, no remarketing lists, no Facebook Pixel, no Google Ads tags.
Cross-site tracking pixels
We don't drop a 1×1 image to follow you to another site. We don't have one to share.
Cross-site profiling analytics
No analytics that profile you across other websites. Server logs only, anonymised by /24 prefix.
"Anonymised" data brokers
We don't sell first-party data to brokers, "anonymised" or otherwise. We never have. We never will.

How to control them

You can clear cookies in your browser at any time. Doing so will sign you out of SetTern.io and ask you to reconfirm consent on your next visit, but the rest of the service will keep working.

Browser instructions: Chrome · Firefox · Safari · Edge.

Why we don't use a cookie banner

Under UK PECR / EU ePrivacy, consent banners are required for non-essential cookies. We don't set any non-essential cookies, so a banner would be a confusing piece of theatre. We disclose what we set in this document, and you can clear them at any time. If we ever start using anything beyond strictly-necessary cookies, we'll add a proper consent flow before that change ships and we'll notify you in-app.

Sub-processor cookies

The Stripe payment-session cookies are set on Stripe's domain when you start checkout — they're how Stripe maintains a secure session while you enter card details. They are first-party to Stripe (not to SetTern.io) and are governed by Stripe's own cookie policy. Card details never touch our servers; we receive only a token and the outcome of the transaction.