Privacy notice

Read this first. Bidding Floor is a demonstration website. It has no server, no database, no account system and no analytics. Nothing you type into it is transmitted anywhere. The sections below describe what the page itself does in your browser, and then what a real deployment of this site would have to disclose.

What this site stores, and where

The storage notice at the foot of the page asks before any of this is written, and offers This tab only as plainly as it offers Keep on this device. Choosing tab-only writes nothing to localStorage at all, deletes anything already there, and keeps your settings in sessionStorage instead — so they survive clicking a link and vanish when the tab closes. The settings themselves work identically either way.

With storage accepted, four things are kept — all of them in your own browser, none of them sent to us or to anybody else:

• Your palette and ground (bf.skin.v1, localStorage). The palette and the dark / light / system choice you made in the Paint panel, so the site looks the same on your next page. Cleared by the panel's Reset button or by clearing site data.
• Your access settings (bf.access.v1, localStorage). Text size, high contrast, reduced motion and link underlining. Reduced motion defaults to whatever your operating system asks for and only records a value here if you override it.
• Your answer to the storage notice (bf.consent.v1, localStorage). Written only if you chose to keep preferences; declining writes nothing, including this.
• Your demo session (bf.market.v1 and bf.mybids.v1, sessionStorage). The simulated bid movements and any maximum bids you placed in the demo, so a lot you were winning on one page is still a lot you are winning on the next. Deleted when you close the tab.
• The session clock (bf.epoch.v1, sessionStorage). The moment you first loaded the site, which is what the countdowns are measured from. Deleted when you close the tab.

There are no cookies on this site at all, no analytics, no tag manager, no third-party scripts, no tracking pixels, no fingerprinting and no advertising identifiers. The fonts and images are served from the same origin as the page. That is why the storage notice asks about preferences rather than performing a consent ritual over tracking that does not exist.

Forms

The contact form and the demo bid controls validate in your browser and then tell you plainly that nothing was sent. There is no endpoint behind them. If you type your real phone number into the contact form, it goes nowhere — but there is also no reason to.

What a real deployment would collect

A live auction platform of this shape would need to collect and disclose considerably more, including at minimum:

• Account details for registered bidders: name, email, phone, billing address, and a payment method held by a PCI-compliant processor.
• Identity and approval records, including any resale certificate on file.
• Bid records tied to an account, retained for the period required by state auction law.
• Invoice, payment and collection records, retained for tax purposes.
• Server logs including IP address, for fraud prevention and for resolving bidding disputes.

It would also need a lawful basis for each of those, a retention schedule, a process for access and deletion requests, and a named contact. None of that applies here, because none of it exists here.

Your choices on this page

You can change your answer at any time from Change what is stored at the foot of any page. Choosing not to store anything deletes every key listed above immediately. Clearing site data for this origin does the same thing. The site works identically afterwards; it will simply have forgotten your palette, your access settings and your demo session.

Contact

Questions about this demonstration can go to [email protected]. That address is fictional, as is everything else on this site — the lots, the prices, the results, the phone number and the street addresses. No coordinates are published anywhere on this site.