Privacy at Ranksen

Updated 5 October 2026. Ranksen is an entertainment application. Guests can play without an account. Creating and submitting a tournament requires an account.

Account and creator data

Supabase Auth stores your email address, account ID, sign-in provider identity and authentication records. Google sign-in requests basic profile and email scopes; Ranksen does not request Google Drive or contacts. Your editor data, submitted versions, uploaded images, rights acknowledgement, timestamps, review and publication state are stored in Supabase. Draft content and private images are limited to the owner and authorized moderation services. After an explicit moderator publication, the approved tournament and images become public; your email is not shown with them.

Guest activity and reports

A guest may report a published tournament without an account. The application stores the target, reason, optional details and moderation decision. It does not store the reporter's email, raw IP address or browser fingerprint in report records. Short-lived keyed data limits abuse. Hosting, authentication, email and network providers may separately process request addresses and technical logs under their own policies.

If you explicitly share a saved result, its link and game summary are readable for 720 hours (30 days) from creation. After expiry, only minimal route/status information remains. Local browser storage can hold your language, game progress, session and editor recovery data, and analytics choice. Signing out does not delete an account or its submitted content.

Analytics choice

On Production, Google Analytics is loaded only after you choose Accept. It measures site and game use with the existing event set; Ranksen does not send account identity, email, raw search text or private UGC text as custom events. Rejecting keeps gameplay and essential sign-in storage working. You can change or withdraw your choice using Analytics choices in the game-page footer; withdrawal reloads the page to stop the loaded tag.

Retention and requests

New unfinished creator staging expires after 48 hours without activity. A never-published rejection blocks access and removes its content and images through the cleanup process; a limited owner-only record of the tournament title, status, rejection date and reason remains for 30 days. Submitted, published, hidden and removed records, reports and moderation evidence are not automatically erased at that deadline. Report rate-control data expires after 25 hours. Physical cleanup and provider logs can have separate timing.

There is no automatic delete-account button. Account or data requests require a manual identity check and review of linked publications, reports and necessary audit records. The operator uses supported Supabase Auth, moderation and storage tools to act on a verified request; an action may hide public content before eligible bytes are removed. For support, privacy, account or data requests, email support@ranksen.com. Do not send passwords or sign-in codes.

Support correspondence is handled through Zoho Mail and includes your email address, message and any details you choose to send. It is used to respond to and resolve your request; necessary request and decision records may be retained alongside the relevant account or moderation records.

Providers

Supabase provides Auth, database, Storage and Edge Functions; Vercel hosts the site; Resend delivers authentication email through Supabase; Zoho Mail handles support correspondence; Google provides optional sign-in and consented analytics. Their service logs and retention are distinct from Ranksen's application records.