Privacy Policy

Effective August 28, 2026. Last updated August 28, 2026.

This Privacy Policy explains how bidboard.lol (https://bidboard.lol) collects, uses, and shares information when you visit the site, plant a billboard, or pay for a ranking. It sits alongside our Terms of Service.

Who is responsible

The controller for personal data processed through the Service is Billel Tighidet. Contact: @billel_tighidet on X.

What we collect

We keep the Service small. We collect only what we need to run the road, take payment, and stop abuse:

Presence identifier. A random ID generated in your browser for the length of your visit, used only to power the live “N on the road” counter. It is not a cookie, is not stored on our servers, and disappears when you close the tab.
Checkout and listing data. The domain, category, and amount you submit; the page title, meta description, favicon, and theme color we read off that domain's public homepage at the time of payment; and the Stripe checkout session ID tied to the payment.
Payment data. Card details and billing identity are collected by Stripe, not by us. Stripe sends us confirmation of what you paid and the amount. See Stripe's own privacy notice.

Technical data

Standard request data, such as IP address and user agent, may be processed by our hosting provider to serve pages, keep the Service running, and prevent abuse. We do not run a separate analytics tool, and we do not set advertising or tracking cookies.

Messages you send us

If you send us a notice, a category correction, or a privacy request, we keep that correspondence as needed to respond to it and to keep a record where the law requires one.

Cookies

bidboard.lol does not set first-party tracking or analytics cookies. Stripe sets its own cookies during checkout under its own privacy policy, which we don't control.

Why we use this data

Contract. To take payment, create or grow your billboard, show your rank, and provide the Service you asked for.
Legitimate interests. To keep the ranking fair (avoid double-crediting a payment), measure usage, and debug outages.
Legal obligation. To keep tax, accounting, and complaint records where the law requires it.

Public billboards

Rank, amount paid, domain, and the scraped title, description, and icon shown on a billboard are public — anyone can see them, including search engines. We fetch this public metadata because you submitted the domain to us; that fetch discloses to the destination domain that bidboard.lol requested its page, the same way any visitor would.

Who we share data with

Stripe — checkout and payment confirmation.
Supabase — stores the billboard, payment, and cycle records described above.
Our hosting provider — standard request logs for serving pages and securing the Service.
Google's public favicon service — used as a fallback when a domain doesn't serve a readable icon of its own; only the domain you submitted is sent to it.

We do not sell your personal data, and we don't share it beyond what running the Service requires.

How long we keep it

Presence identifiers are never stored on our servers — they exist only for the length of your visit.
Public billboard entries stay live while their cycle is current, and remain afterward in the hall of fame.
Payment identifiers and amounts are kept as long as needed for accounting, tax, fraud, and dispute handling.

Your rights

If GDPR or a similar law applies to you, you can ask us to access, correct, delete, or export the personal data we hold about you, and to restrict or object to processing. Contact us via @billel_tighidet — we need enough information to find your data. A billboard's public content that is also on your own website isn't made private just because it appears on bidboard.lol, but you can ask us to remove the billboard.

Children

The Service is for adults. We don't knowingly collect personal data from children — if you believe a child has used the Service, contact us and we will delete the data we can identify.

Changes

We may update this policy when the Service or the law changes. The date at the top of this page is the current version; if a change is material, we will post the updated policy here.