Cookie Policy
The two cookies The Bidding Floor sets, both of them for signing you in — and the analytics and tracking we do not run.
Last updated: 24 August 2026
Summary
This summary is for convenience only. It does not form part of the policy, and the numbered clauses below take precedence if there is any inconsistency.
- Two cookies, both for signing in.
- They keep you logged in between pages and protect the link in a confirmation email. That is the entire list.
- None at all if you do not sign in.
- Searching, filtering and reading a catalogue leave nothing on your device.
- No analytics, no advertising, no tracking.
- We run no measurement product, set no advertising cookies, and load no third-party script. Nobody else is watching you through us.
- That is why there is no banner.
- Cookies that are strictly necessary to provide the service you asked for do not need consent. If we ever set one that is not, we will ask first.
- You can block them.
- Your browser can refuse or delete them. Doing so signs you out.
1. What this policy covers
1.1
This Cookie Policy explains the cookies and similar technologies used on https://thebiddingfloor.com and any other site operated by Digital Auction Solutions Limited that links to it. It should be read with our Privacy Policy and our Website Terms of Use.
1.2
A cookie is a small text file a website asks your browser to store and send back on later visits. Related technologies — local storage, session storage and similar — do the same job in a different place, and this policy covers them too.
1.3
Auction houses listing on The Bidding Floor operate their own websites, which are not covered by this policy. If you follow a link to a saleroom’s own site, its cookie policy applies there.
2. The cookies we set
All of them are strictly necessary, and they exist for one purpose: keeping you signed in. They are set by Supabase, the authentication and database service behind The Bidding Floor, and are first-party cookies on this domain.
| Cookie | What it does | How long it lasts |
|---|---|---|
sb-<project>-auth-token | Holds your session so you stay signed in between pages. Without it you would have to sign in again on every click, and your watchlist and registrations would be unreachable. It may be split across several numbered cookies (….0, .1) when it is too large for one. | Until you sign out, or the session expires. Refreshed on each visit while you stay signed in. |
sb-<project>-auth-token-code-verifier | Set for a few minutes while you confirm an email address or reset a password. It proves the browser finishing the process is the one that started it, which is what stops somebody else completing a sign-in with a link intended for you. | Deleted as soon as the link is used. |
2.1
<project> is an identifier for our Supabase project, so the exact name differs between our live site and our test environments.
2.2
If you browse without signing in, no cookie is set at all. Searching, filtering and reading a catalogue need no account and leave nothing on your device.
3. Why there is no cookie banner
3.1
The Privacy and Electronic Communications Regulations require consent before a site may store information on your device, with an exemption for storage that is strictly necessary to provide a service you have asked for. Keeping you signed in is that, and it is all we do.
3.2
So there is nothing to consent to, and asking would be a banner offering a choice that does not exist. If we ever add a cookie that is not strictly necessary, we will ask first — properly, with refusing as easy as accepting — and this policy will change before it is set.
4. What we do not do
Stated positively, because “we may use analytics cookies” is what most policies say and it is not true here:
4.1
No analytics. We run no analytics or measurement product of any kind — no Google Analytics, no tag manager, no heatmap or session-recording tool. We do not build a profile of what you look at.
4.2
No advertising or tracking. We set no advertising cookies, run no retargeting or conversion pixels, and take part in no cross-site tracking or ad network. We do not sell or share browsing data with anybody for advertising.
4.3
No third-party scripts. No page on The Bidding Floor loads script, styling or media from a third-party domain, so no third party is in a position to set a cookie through us. Our typeface is served from our own site rather than from a font service, and every photograph is served from our own storage.
4.4
No social media buttons. There are no embedded share, like or follow widgets, which are a common way for a third party to observe visitors on sites they do not own.
5. Managing cookies
5.1
Every browser lets you see the cookies a site has set, delete them, and refuse them. Look for Privacy or Site Settings in your browser’s preferences, and for a padlock or similar control beside the address bar for controls covering this site alone.
5.2
Because our cookies are the ones that keep you signed in, blocking or deleting them signs you out. Browsing, searching and reading catalogues will still work; signing in, your watchlist, and registering to bid will not.
5.3
We honour a browser’s Do Not Track and Global Privacy Control signals by having nothing for them to switch off. There is no tracking here to disable.
6. Changes, and how to contact us
6.1
We will update this policy if the cookies we use change, and the “Last updated” date at the top will say when. A change that introduces a cookie which is not strictly necessary will be accompanied by a request for your consent, as clause 3.2 says.
6.2
Questions about this policy, or about anything else to do with your personal data, go to [support email]. Our Privacy Policy explains what we do with the information behind the sign-in these cookies maintain.
6.3
Digital Auction Solutions Limitedis registered with the Information Commissioner’s Office under registration number [ICO registration number]. You can complain to the ICO at ico.org.uk if you believe we have handled your data improperly, though we would rather you told us first.