What Gavel stores, why it is used, and what you can control.

1. Information Gavel uses

• Account information: account ID, email, public handle, authentication provider information and sign-in metadata supplied through the authentication system.
• Product activity: verdicts, original and revised verdict state, arguments, Case submissions, Jury decisions, Daily activity, streaks, badges, onboarding state and other record data.
• Social/community activity: Rivals, Challenges, notifications, reports and moderation-related records.
• Operational/security information: roles, staff actions, internal audit records and other data needed to operate or secure supported features.

2. Why the data is used

Gavel uses this information to authenticate accounts, enforce one-player-one-vote and sealed-result rules, build your record, operate community features, moderate content, investigate abuse, deliver account features and maintain the service.

3. What can be public

Your handle and supported public profile/record information can be visible to other players. Approved arguments, published community Cases and other intentionally public contributions may also be shown. Gavel's sealed-result rules are designed to prevent room results and arguments from being revealed through protected flows before the required vote.

4. Authentication and infrastructure providers

Gavel currently relies on Supabase for authentication, database/storage and server-side product functions, and Cloudflare for hosting/delivery. If you choose Google or Discord sign-in, that provider participates in the authentication flow. Their own services are governed by their respective terms and privacy practices.

5. Browser storage

The authentication client persists a session in your browser so you can stay signed in. Do not use a shared device without signing out when you are finished. Gavel also provides a separate action for signing out other Gavel sessions.

6. Export and deletion

Signed-in users can use Gavel's Data & Privacy controls to download the supported account-data export. The export intentionally does not include passwords or authentication tokens.

Gavel also provides a guarded account-deletion flow. It requires explicit confirmation and blocks deletion of the final active OWNER account. Published Cases and approved arguments may remain as an anonymous public record after deletion; private account activity is removed according to the implemented database deletion/cascade behavior.

7. Retention

Gavel does not publish one blanket retention duration for every data type. Data is retained as needed for the active product, account security, moderation/audit history and community-record behavior described here. The self-service deletion flow applies the implemented deletion rules when an account is eligible to be deleted.

8. Recovery privacy

Password-recovery requests use generic messaging so the page does not confirm whether a particular email address belongs to a Gavel account. A recovery session is treated separately from a normal signed-in product session until the password reset is completed.

9. Your controls

You can update supported profile information, use password recovery, sign out the current device, sign out other devices, export supported account data, and request account deletion from the product's account controls. Content problems can be reported through Gavel's Community Reports flow where available.

10. Policy changes

If Gavel's data behavior materially changes, this page should be updated with the product. The date at the top identifies this version of the notice.