Privacy

• submitted media URLs, action amounts, ranking entries, Screen events, click counts, and content reports;
• a random first-party browser visitor identifier used for aggregate visitor counts, realtime connection continuity, and deduplicated entry reach;
• per-entry pseudonymous hashes used to count how many browsers saw an entry and how many distinct browsers visited its content, without storing the browser identifier in each entry's analytics record;
• historical best rank and accumulated time in the Top 3 and controlling the Screen, measured from the date tracking began;
• locally stored entry-control tokens, theme preference, and temporary in-progress action data;
• payment intent and provider identifiers, requested and received amounts, asset/network fields, provider statuses, timestamps, and verified callback data;
• IP-derived hashes used for abuse prevention and rate limiting, plus ordinary hosting and Worker request logs that may contain IP address and user-agent information;
• limited first-party product events such as Screen views, embed outcomes, reconnects, and sharing actions.

The repository does not currently integrate PostHog or another third-party browser analytics SDK. Embedded media and payment services have their own privacy practices.

Browser local storage and a first-party cookie keep the same random visitor ID. Local storage also keeps the theme and entry-control tokens. Session storage may keep an in-progress action so it can recover after a reload. These values can be cleared through browser settings, but doing so may remove entry controls or recovery context.

The visitor cookie is not an account or advertising cookie and is not shared across sites. The private operator area uses a signed, HttpOnly administration session cookie. Third-party embeds may apply their own storage or cookies.

Information is used to operate the shared Screen, preserve deterministic ranking, verify and reconcile payments, prevent duplicate execution, measure aggregate audience activity, rate-limit abuse, investigate exceptions, provide private entry performance summaries to the holder of its control token, moderate content, and maintain service security.

Payment information is shared with the configured payment provider; media URLs are shared with the relevant media platform. Hosting and Cloudflare infrastructure process requests and operational logs. Support messages are handled through the configured email provider.

Ranking history, payment audit evidence, execution receipts, moderation records, and security logs may be retained as needed for product operation, dispute investigation, fraud prevention, and legal obligations. Raw visit-event IDs used for retry deduplication expire after 30 days. Per-entry reach and unique-visitor hashes are retained with the entry's aggregate analytics so exact totals do not decrease. No shorter deletion period is promised by the current implementation.

Use Support for privacy questions, content reports, or takedown requests. Do not send a seed phrase, private key, or wallet recovery phrase.