Settle legal
Cookie Policy
Settle does not use advertising cookies, cross-site trackers, or third-party analytics scripts. The only cookies we set are the ones required to keep you signed in. This page lists every one of them.
Last updated: September 12, 2026
1. The short version
We set no cookies at all until you log in, and the ones we then set exist solely to maintain your session. There is no advertising network, no social pixel, no session-replay tool, and no third-party analytics script on this site — including on hosted checkout pages, where your customers’ privacy is not ours to trade away.
Because we set only strictly necessary cookies, no consent banner is required under the ePrivacy Directive or the UK PECR. We consider that a feature rather than a loophole.
2. Cookies we set
| Cookie | Purpose | Category | Lifetime |
|---|---|---|---|
| sb-<project>-auth-token | Keeps a merchant signed in to the dashboard. Set by our authentication provider when you log in. | Strictly necessary | Session, refreshed on use |
| sb-<project>-auth-token-code-verifier | Short-lived value used to complete a secure sign-in exchange (PKCE) and prevent interception of the login flow. | Strictly necessary | Minutes, during login only |
3. Browser storage that is not a cookie
Wallet connection libraries on the checkout page use your browser’s local storage to remember a connected wallet. This data stays in the browser and is never transmitted to Settle.
- wagmi.* / walletconnect.* — Remembers which wallet a customer connected so the checkout page does not prompt again on reload. Stored in the browser, never sent to us.
4. How we count page visits without tracking you
Merchants can see how many times a payment link was viewed. To produce that number we store a salted, irreversible hash of the visitor’s IP address together with the date — never the IP address itself — and deduplicate on it. The hash cannot be reversed to recover an address, it is not shared, and it is not used to build a profile or to follow anyone between sites.
5. Controlling cookies
You can block or delete cookies in your browser settings. Blocking the authentication cookies listed above will prevent you from logging in to the dashboard, because the session cannot be maintained without them. Customers paying through a checkout link are not required to accept any cookie.
6. Changes and questions
If we ever introduce a cookie that is not strictly necessary, we will update this page and request consent before setting it. Questions can go to [email protected].