What stains... permanently.

Privacy Policy

Last updated: 9/10/2026 (mm/dd/y)

What blood.bid keeps

We keep only what the service needs to run, and we can state it plainly: your internal account identifier, the usernames you hold, the page configuration attached to each name, your posts, the sealed messages in your inbox, and the auction bids and transfer history behind each name. We don't keep other categories of personal data unless this policy says otherwise.

Quality of life

A few small things improve the experience: theme and layout preferences, your settings, and the music bar state (like the track already playing on your page). These are stored so the site looks the way you left it.

What we don't do

• We don't sell or rent your data. There are no ads.
• We don't track you across the rest of the web.
• We don't build profiles of who you are beyond your own account.

Private messages

Messages are encrypted end to end. Every account holds its own PGP key pair, separate from any handle, and messages are sealed to that key before they reach us. We only see what's needed to route them: who a message is between, when it was sent, and the handle it rode in on — never the contents.

Because the key belongs to the account and not the name, nothing changes when a handle changes owners. The new holder receives the handle and its page, but the account that encrypted the conversation still holds the private key — previous messages stay unreadable to the new owner.

You can reset or burn your key at any time. Burning it makes the old message contents unreadable from anything we hold — including to us, even on a legal request.

Technical logs

We may keep short-lived technical logs — the endpoint, status and timestamp of a request — to stop abuse and keep the auction floor fair. These logs don't include your full IP address by default; where a rate limit or a specific problem needs one, it's held briefly and only as long as the problem is open. Logs are not used to build profiles of you. These are blood.bid's application logs; infrastructure providers such as Cloudflare process connection information as necessary to provide their services, subject to their own policy.

Auction records are permanent

Auction and transfer records are retained as long-term provenance records — who held a name, when, and at what bid. Where an account is deleted, identifying account information may be removed or detached while the name's historical record remains. A name's provenance should outlive its former owner, not drag their identity along behind it.

Deletion

Remove a page and its configuration and contents go with it. Remove an account and its data is erased: posts, messages, settings and the account identifier itself. Auction records for names that already changed hands are kept, as noted above.

Payments

Card details are handled by the payment processor (Stripe) rather than stored by blood.bid; our servers never receive them. We retain payment information such as transaction status, amount and relevant transaction identifiers as needed to operate the service and maintain financial records.

Third-party services

There are no ad networks and no tracking scripts built in. The services we rely on are named here: Cloudflare (content delivery and protection) and Stripe (payments). If we add or change a third-party service, this list is updated, with a link to its own policy.

Legal requests

We may disclose data where the law requires it — on a valid court order or equivalent process. Message contents aren't among the data we can hand over: they're sealed to your key, and we don't hold the private half. Legal requests can reach the metadata we already have, not the conversations themselves.

Cookies and local storage

We use your browser's local storage for small quality-of-life state: the theme you chose, the track on your music bar. No tracking cookies, no advertising cookies, nothing from third parties.

Age

blood.bid isn't aimed at children. You need to be old enough to enter into these Terms where you live.

Contact

Questions about what's stored: open a request from Support and a human (not a script) will answer.