Privacy

Privacy policy

A draft pending legal review, describing what the software does today.

What we collect when you bid. Your email address, your company name, your bid amounts and their timestamps, and the fact that you accepted these terms and when. Your email address comes from the account you create; we do not ask for anything else.

Card details. We never see them. Stripe collects your card in an iframe on their infrastructure and gives us back identifiers. We store a Stripe customer id and a payment method id, and nothing that could be used to charge a card anywhere else.

Who processes your data. Clerk handles accounts and sign-in. Stripe handles payments. Supabase hosts our database. Resend sends transactional email. Vercel hosts the application. Each of these sees only what it needs to do its job.

Your bid is sealed. Bid amounts are visible to you and to us. They are never shown to other bidders, and no page, response, or email discloses another bidder’s amount or the number of bidders beyond a published summary of an auction that has already closed.

What we keep and why. Bids, auctions, and the audit trail are retained so that any auction outcome can be reconstructed if it is ever disputed. That is the point of keeping them, and it is why bids are never edited or deleted once placed.

What we do not do. We do not sell your data, and we do not use your bid amounts for anything other than running the auction.

How long we keep it. Bids, auctions, email records, and the audit trail are kept for as long as we operate the auction. They are what makes a disputed outcome answerable, so we do not delete them on request while a payment relationship exists. Your account itself is Clerk’s to delete, and deleting it does not erase the record that a bid was placed.

Operator access to your bid. We can see bid amounts in an open auction from an internal admin surface. Every one of those views is recorded with who looked and when, and that recording cannot be skipped: if it fails, the amounts are not shown.

Email. We email you when you win, when you lose, if a card is declined at clearing, and if a later renewal fails. Every send is recorded so a re-run can never send the same message twice. These are transactional; there is no marketing list here and nothing to unsubscribe from.

International transfer. Our processors are US-based. If you are bidding from outside the US, your data is processed there.

Open questions for review. Places where this draft describes what the software does but does not settle what it should promise.

Deletion requests against a retained record. We say we keep bids for as long as we operate, because that record is what answers a dispute. Which jurisdictions that is actually compatible with, and what a lawful deletion request should produce here, needs review.

Entity, controller, and contact address. Not stated on this page yet. A privacy policy needs a named controller and a way to reach them.

International transfer basis. We say processing happens in the US. Whether that needs a stated legal basis for bidders outside the US is a question for review.