Cookies

Last updated: 18 April 2026

Cookies are small pieces of text stored by your browser. Some are essential for a website to work. Others track you — we don't use any of those. This page tells you exactly what BuildRound does and does not set.

The short version

- We only set essential cookies (for keeping you signed in).
- No advertising cookies. No tracking cookies. No pixels.
- We use Plausible Analytics which does not use any cookies.
- You won't see a cookie consent banner because under UK PECR we don't need one for essential cookies, and we don't use any non-essential ones.

1. What we set

Cookie	Set by	Purpose	Lifetime
__session	Clerk (our auth provider)	Keeps you signed in	Session / 30 days
__client_uat	Clerk	Anti-CSRF protection for sign-in forms	1 year
__stripe_mid	Stripe (only on payment pages)	Fraud prevention for card payments	1 year

All of these are "strictly necessary" cookies under UK PECR — they are required for the service to function (authentication, payment fraud protection). Under PECR Regulation 6(4) these do not require prior consent.

2. What we do not set

- Advertising cookies (Google Ads, Facebook Pixel, etc.) — never.
- Analytics cookies — we use Plausible Analytics which is cookieless by design.
- Cross-site tracking cookies — we don't follow you around the web.
- Fingerprinting technologies — we don't try to identify your device beyond session auth.

3. Local storage

During the wizard (Steps 1-5) we use your browser's local storage to remember what you entered before you create an account. This stays on your device only. When you sign up at Step 6, the data transfers to our servers and is removed from local storage.

4. How to control cookies

All modern browsers let you view, clear, or block cookies in Settings. If you block essential cookies, BuildRound won't be able to keep you signed in — you'll be forced to sign in again every time.

5. Changes

If we ever add a non-essential cookie we would update this page, show a consent banner, and only set the cookie once you opt in. We have no current plans to do so.

6. More

See our Privacy Policy for the wider picture on how we handle personal data.