Privacy

RoboDebut stores the homepage URL, name, tagline, description and category sent with a listing request, plus the contact email sent with it. Approved listing details are public. The contact email is never published; only the operator sees it, on the operator page and in the operator's private Telegram notice about each new submission. Unapproved proposals, badge-check outcomes and moderation records are kept in the operator's private database.

The server uses the connection's IP address to enforce request and homepage-fetch limits. Rate-limit records store keyed hashes instead of raw IP addresses. Expired counters are cleared on later submissions. The application logs a request's outcome, without its listing details or IP address.

Badge checks load the submitted public HTTPS homepage. The homepage's server can see the check and its RoboDebutBot user agent. Submitting needs a contact email but no account. RoboDebut sends no email, including approval or rejection notices.

The theme button saves your light or dark preference in your browser's local storage. RoboDebut's only application cookie is the operator's sign-in session on the private operator page. Fonts load from Google Fonts, so your browser sends font requests to Google.

Public pages send page views to Clicky and PostHog, both set up without tracking cookies, and Copy prompt clicks to PostHog. The operator page loads neither. The server sends PostHog the outcome and category of listing requests and each approval change, without listing details. RoboDebut adds no advertising scripts.

There is no set retention period yet. Listings, contact emails and moderation records stay in the database until the operator deletes them by hand. Unapproving or removing a listing stops its public display but keeps a private record to prevent anonymous replacement. There is no self-service edit or deletion flow yet.