VERSUS

Beta policy

Privacy Policy

Last updated: October 8, 2026

1. Information we process

VERSUS processes account information such as name, username, email, authentication data, date of birth when the age gate is enabled, profile information, uploaded media, Challenges, Responses, comments, messages, follows, votes, notifications and moderation activity.

2. Technical and usage data

We process technical and usage signals needed to operate and secure the service, including IP address, user agent, session activity, view and watch-time events, exposure counts and timestamps.

3. How we use data

We use data to create and secure accounts, operate social features, process media, rank and recommend content, provide analytics, detect fraud and abuse, enforce rules, deliver notices and improve reliability.

4. Age and teen safety

Date of birth is intended to remain private and is used to apply age-appropriate product rules. The ordinary account baseline is 13+, subject to local law. Teen accounts may receive stronger privacy and recommendation protections.

5. Sharing and service providers

VERSUS relies on infrastructure and service providers for hosting, media delivery, sign-in and email. Providers process data only as needed for those services and subject to the applicable agreements.

6. Your controls

Depending on your location, you may have rights to access, correct, delete, export, object to or restrict processing of personal data. VERSUS currently provides in-product data export and account deletion controls.

7. Account deletion

When you schedule account deletion, VERSUS provides a 30-day recovery period. Signing in during that period cancels the request. After the grace period, the account is eligible for permanent deletion, subject to lawful security, dispute or legal-retention requirements.

8. Security

VERSUS uses authentication, access controls, session protections and security monitoring intended to protect accounts and data. No online service can guarantee absolute security.

9. Changes

Privacy changes will be versioned and communicated where required. Separate consent will be requested where the law requires it.

Beta notice: the final public policy still requires the legal operator identity, privacy contact, processor inventory, transfer details and finalized retention schedule before general public launch.