Privacy

Public browsing

RuleRoster can be read without an account. The site does not offer public signup. Standard hosting and security infrastructure may process request metadata such as an IP address, user agent, requested URL, and timestamp for delivery, abuse prevention, and incident investigation.

RuleRoster uses free Cloudflare Web Analytics on approved public entry pages to report aggregate visits, page views, referrers, countries, device and browser types, and loading performance. Cloudflare states that this service does not use cookies, local storage, or fingerprinting to identify visitors and does not log query strings. Administrative and API paths are excluded, and automatic single-page navigation tracking is disabled. We do not join visitor identities across products.

The operator views aggregate traffic in a private portfolio dashboard. This does not collect correction content or administrative activity. Advertising remains disabled unless its separate configuration and consent requirements are completed and disclosed here.

If error monitoring is configured, RuleRoster may send a scrubbed technical error event to Sentry. Query strings, request headers and bodies, cookies, and user identity fields are removed; session replay and performance tracing are disabled.

Correction submissions

A correction may include the page URL, challenged claim, supporting evidence URL, and an optional contact email. An abuse-prevention check and a one-way IP-derived value may be stored. The public page never displays the submitter's email or network information.

Correction data is used to triage and document factual review. Do not include sensitive personal information in a correction.

Protected administration

Editorial access is allowlisted and requires multi-factor authentication. Administrative actions create security and audit records needed to attribute approvals, protect integrity, and investigate failures.

Retention and requests

Source evidence and publication audit records may be retained to preserve provenance and explain historical answers. Personal correction contact details should be removed when they are no longer needed for the review or a legal obligation.

Controller, privacy contact, correction retention period, and data-request instructions have not yet been published. Correction intake remains disabled until all four are published, its privacy and abuse-prevention controls are configured, and an operator explicitly sets the server-side activation flag.