Privacy on VERSUS
Guest voting
Firebase Authentication creates a private browser identity so votes can be saved without a public username. Clearing browser storage or using another browser may create a different guest identity.
Accounts and public contributions
Your username, display name, profile, published debates and comments are public. Public debates can be indexed by search engines and included in social link previews. Vote records are readable by their owner and authorized administrators; debate totals are public data.
PINs and security
PIN verifiers are stored in a server-only collection, not in public profiles. Firebase services store account, debate, comment, vote and image data. App Check helps protect backend requests from abuse.
Browser storage and external services
The browser remembers your authentication session and interface language. Images, fonts, icons and Tailwind may be loaded from external providers. Those providers receive the normal network information needed to serve a request.
Audience measurement
Google Tag Manager is loaded only if you accept optional audience measurement. You can decline and keep using VERSUS, or change your choice using the audience measurement settings on this page. Our page-view events do not include your username, PIN, comment text or voting choice.
View counts
Visible debate cards can add one view per private identity and debate each UTC day. These are daily impressions, not a count of unique people. Deduplication records expire after 48 hours; combined counters are retained.
Retention and requests
Votes and contributions remain stored unless removed through moderation or by the platform operator. Contact the platform operator for account or data-removal requests. Do not publish sensitive personal information in a debate or comment.