Privacy Policy
How BidLOL collects and uses account, payment, and leaderboard data.
Last updated: 2026-11-18
What we collect
BidLOL stores the name, email address, profile image, and account identifiers provided through Google sign-in. We also store submitted public destinations, bid targets, payment status, timestamps, aggregate outbound clicks, moderation records, IP-derived security signals, and basic request logs.
Stripe processes payment details. BidLOL does not receive or store complete card numbers. Cloudflare provides hosting, security, database, and email-routing infrastructure.
How we use data
We use data to authenticate accounts, create Stripe Checkout sessions, verify payments, rank listings, prevent abuse, provide transaction history, moderate public content, and answer support or legal requests. We do not sell personal data.
Public information
Active listing names, descriptions, destinations, cumulative paid totals, rank, and aggregate click counts are public. The identity of an individual supporter is not shown on the public board.
Retention and rights
Payment and moderation records may be retained where required for fraud, accounting, dispute, or legal purposes. To request access, correction, or deletion, email privacy@outbid-lol.io.
Contact
Privacy questions can be sent to privacy@outbid-lol.io.
Optional DataAny analytics
DataAny is a separate, optional analytics provider. Only after you allow it in Analytics settings, eligible public-page visits can send the canonical BidLOL page path, screen width, and an allowlisted search or AI referral origin to dataany.ai. Query strings, fragments, account identifiers, email, payment details and submitted destination URLs are not included. Other referrals are suppressed, so reports cannot reliably distinguish direct visits from unknown sources. Like any recipient of a network request, the provider may receive connection metadata such as an IP address.
Your versioned choice is stored in this browser. Analytics settings remain available on every page; rejecting or withdrawing stops new DataAny pageviews. If saving fails, DataAny stays paused on the current page and a retry is shown. This choice does not grant permission for another analytics provider. Internal/QA traffic and browser privacy signals are excluded. We use a local exclusion flag and a two-hour QA deadline to avoid counting internal visits; these are not sent to DataAny. See the provider’s privacy information at https://dataany.ai/privacy-policy.