What your browser remembers.

biw-visitor is a first-party cookie containing a random browser ID. It helps avoid counting the same browser as a new visitor on every page and identifies recent activity for the online counter. It lasts up to one year and is refreshed during activity.

The browser sends an activity request approximately every 30 seconds while the page is visible. “Online” means activity within the last 90 seconds. These counts refer to browser identifiers, not verified people. Clearing the cookie or using another browser can create another visitor record.

This is audience measurement, not a login or proof of identity. It is set by activity or listing measurement requests. Our application does not use it to join your browsing history to a Stripe customer or crown-alert email.

On the home page, we also measure a listing when at least half its card stays visible for one continuous second in a visible tab, and when its website link is used. A daily hashed key combines the browser ID, reign, placement and event type to avoid repeated counts. We store the key, reign, placement, event type, day and timestamp. Counts, not browser identifiers, are shown to that reign’s private receipt holder. They are estimates, not audited visitors or sales. These records are retained for historical receipt reporting; there is currently no automatic expiry. Contact us for a data request.

biw-theme · local storage

Remembers whether you selected light or dark mode. It remains until cleared or changed.

biw:locations · local storage

Remembers recent location selections so you can choose them again. It remains until cleared or updated. “Use my location” requires your browser’s permission; you can instead choose a place manually.

crown-checkout:… entries in session storage hold your private purchase token so the current tab can restore access when returning from Stripe. Session storage normally ends when the tab or browser session is closed, subject to browser restoration settings.

Private receipt links also contain access information in the part of the URL after #. Share the public crown page instead. Deleting your local access information can make it harder to return to a receipt without your saved private link.

Stripe’s checkout and infrastructure providers may use their own cookies or storage for payment processing, fraud prevention and security. Their practices are covered in the provider notices linked from our privacy notice.

You can block cookies or clear this site’s cookies, local storage and session storage in your browser’s site-data settings. Removing preferences resets your theme and recent places. Blocking the visitor cookie prevents that browser from being confirmed as a visitor, but the site can still receive network and security information.

Clearing local data does not delete historical listings, purchase records or an email-alert subscription. Use your receipt’s notification preference or unsubscribe link to stop an alert, and contact us for a data request.