privacy

CrowdRank uses the normal Laravel session cookie to keep the site working. Guest voting also uses a signed cookie named crowdrank_guest so votes can be tied to the same anonymous browser session.

These cookies help prevent duplicate voting, keep play progress coherent, and support abuse controls.

Public pages load GoatCounter and Ahrefs analytics scripts. CrowdRank also uses server-side PostHog events for product analytics such as registration, login, debate views, play starts, votes, result views, completions, streaks, and achievements.

PostHog credentials are configured through environment variables. CrowdRank does not add tracking parameters to canonical URLs.

If you create an account, CrowdRank stores your email address for login, verification, password reset, and account security. New accounts receive generated display names.

Account data is kept while the account exists. Signed-in users can delete their account from the profile page.

Votes store the debate, contenders, selected winner, account or guest session, vote weight, risk score, and hashed IP and user-agent metadata. This is used to produce rankings and defend voting integrity.