Skip to content

The fine print

Security

The court keeps its records under lock and key. Here's how we protect your account and your data, and how to tell us if you find a weakness.

Last updated November 15, 2026

  1. How we protect your account and data

    • Encrypted connections: Gavel Drop is served only over HTTPS, and browsers are told to always use it.
    • Checked on our servers: every request that reads or changes data is checked on the server for who you are and what you’re allowed to touch. Hiding a button is never the only protection.
    • Two-step sign-in: you can add an authenticator app or a text code to your account in Settings → Security.
    • Staff access is limited and logged: only court officials can open the back office, and their actions there (settings, refunds, moderation, viewing a case for a report) are recorded in an audit log.
    • Backups: we back up the service every night. Backups are encrypted before they are stored, and older copies are removed on a fixed schedule.
    • Payments: card details are handled by Stripe or the app stores. We never see or store your full card number.
    • Your control: you can download a copy of your data (Settings → Your data) or delete your account (Settings → Delete account) at any time.
  2. Report a vulnerability

    If you believe you’ve found a security problem in Gavel Drop, email security@gaveldrop.app. Tell us what you found, the page or feature, and the steps to reproduce it. We’ll confirm we received it within 3 business days and keep you posted while we fix it.

    Please act in good faith while you look:

    • Only use accounts you own or have permission to test, and never access, change or delete other members’ data.
    • Don’t run tests that slow down or break the service (no denial-of-service, spam or automated mass sign-ups).
    • Give us a reasonable time to fix the problem before you tell anyone else about it.

    We won’t pursue or support legal action against anyone who reports a problem this way. We don’t run a paid bug bounty at the moment. Our machine-readable contact file is at /.well-known/security.txt.

  3. Something else?

    For a hacked account, a lost password or a privacy request, use Help or contact support instead, so the right person picks it up quickly. Abuse and safety reports go through the Report button on the post or profile.