1. What are cookies and local storage?
Cookies are small text files that a website places in your browser. Local storage is a similar mechanism that lets a web app save data directly on your device. Both let BuildTracker remember things between visits — for example, that you're signed in.
2. Our approach
BuildTracker only uses cookies and local storage that are strictly necessary to run the service. We do not use advertising cookies, third-party tracking pixels, or cross-site analytics that follow you around the web.
Because everything we store is strictly necessary, we do not show a cookie consent banner — necessary cookies are exempt from consent under GDPR / ePrivacy and UK regulations. If we ever add analytics or marketing cookies, we will add a consent banner first and update this page.
3. What we store
The table below lists every cookie and local-storage key BuildTracker may set.
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
sb-*-auth-token |
Local storage (Supabase) | Keeps you signed in. Stores the access and refresh tokens for your session. | Until you sign out or the refresh token expires |
bt_theme |
Local storage | Remembers your light / dark theme preference. | Persistent |
bt_currency |
Local storage | Remembers the currency you use for quotes and invoices. | Persistent |
bt_notif_seen_at |
Local storage | Tracks when you last opened the notifications panel so we only mark new activity as unread. | Persistent |
bt_last_tab |
Local storage | Remembers which tab you were on so we can return you there on your next visit. | Persistent |
| Paddle checkout cookies | Third-party (Paddle) | Set only during checkout to process your subscription payment. Governed by Paddle's privacy policy. | Session |
4. Third-party services
BuildTracker relies on a small number of third parties to run the service. Where they set cookies of their own, the lifetime and scope are governed by their own policies:
- Supabase — authentication and data storage. Sets the
sb-*-auth-tokenentry in local storage. - Paddle — payment processing. Sets its own cookies only during a checkout flow.
- Vercel — hosting. May set a first-party cookie used for load balancing.
5. How to clear or block cookies
You can clear all cookies and local storage for BuildTracker at any time from your browser's settings — look for "Site settings" or "Clear browsing data". You can also block cookies entirely, but if you block the Supabase auth cookie you won't be able to stay signed in.
6. Changes to this policy
If we change how we use cookies we will update this page and, for anything beyond strictly-necessary cookies, ask for your consent first.
7. Contact
Questions about cookies? Email support@buildtracker.tech.
Last updated: April 2026