DeathCam

Privacy Policy

Effective Date: October 2026

1. Discord sign-in

When you sign in, Discord shares your user ID, username, display name, email and email verification status, and basic information about the servers you belong to. Sign-in also requests permission to join you to the DeathCam support server. We use this information to identify your account, recognize owner access and complete the support-server join.

2. Sessions and credentials

Your sign-in profile and server count are stored in an encrypted, HttpOnly session cookie for up to 12 hours. The cookie does not contain your Discord access token, refresh token or full server list. OAuth tokens are used during sign-in and a revocation request is sent to Discord afterward. Signing out removes this browser’s session cookie; an already copied session remains valid until it expires. Rotating the session secret invalidates existing sessions.

3. Combat data and recordings

A connected collector sends kill records to its authenticated workspace, including character identifiers and names, player usernames, kill IDs, event times, weapon hashes, distances, routing buckets and attribution methods. Authorized workspace members can view those records. Cloud kill records expire 30 days after the event; database deletion runs asynchronously. Local server retention is separate. Shot and hit aggregates include character identifiers, weapon hashes, routing buckets, 15-minute windows, counts and hit-region indices. These aggregates expire 30 days after their window. Fight traces are not synced yet. Video-only POV recordings upload directly to private Cloudflare R2 storage. Authorized workspace members can play clips using temporary signed URLs. Clip access expires seven days after the event; object deletion runs asynchronously through the bucket lifecycle rule.

4. Account storage and third-party services

The website is hosted on Vercel and uses Discord for authentication and support-server membership. MongoDB Atlas stores your Discord ID, username, display name, email and verification status, server count, support screening status, and account creation, login and activity timestamps. We do not store Discord OAuth tokens or your full server list. Account records remain until deleted; signing out removes the browser session but does not delete your account record. These providers process requests under their own privacy policies. Hosting providers may retain request logs under their service settings.

5. Workspace access

MongoDB Atlas stores workspace names, owner and staff Discord IDs, access roles and creation/update timestamps. Collector keys are stored as hashes with creation and revocation metadata. A newly generated key is shown once to the authorized user; it is not saved in browser storage by the application. Workspace owners control staff access, and Owners and Admins can rotate or revoke collector keys.

6. Access and deletion

Sign out to remove the session from your browser. For questions, corrections or deletion requests concerning test combat data, contact us through the DeathCam support server. We do not sell your account or combat data.