Skip to content

Trust · Transparency report

Every request we can tell you about.

Each quarter we publish how many requests we received and what came of them. Once a report is out, it is never edited: each one is sealed to the one before it, so changing any past number breaks the chain for everyone to see.

What we count

Secret orders are not counted here. An order that comes with a gag would forbid us from reporting it, even as a number. That is the job of our warrant canary: if one arrives, the canary goes quiet instead.

  1. Automated DMCA requests

    Copyright takedown notices, almost always sent by automated scanners. We count every one, including those we reject.

  2. Inquiries from government institutions

    Any request for information from police, courts, regulators or other public bodies, in any country, whether or not it was legally binding.

  3. Requests that led to disclosing user data

    How many of those requests ended with us handing over anything about a customer. We hold only the account and licence details that billing and support need.

Reports

Newest first. Each report lists its own hash and the hash of the report before it. Check the whole chain yourself, right here in your browser.

Each report is sealed with a SHA-256 hash that includes the hash of the report before it. Change a single number in an old report and every hash after it stops matching.

Every report here is sealed by the hash 20815657…cc695d, signed into our warrant canary statement of 3 November 2026. Rewriting history would need our signing key.

  1. First report

    No requests
    Automated DMCA requests
    0
    Inquiries from government institutions
    0
    Requests that led to disclosing user data
    0

    Nothing to report. Since Deniable began, we have received no automated DMCA requests and no inquiries from any government institution, and we have disclosed no user data.

    Hash 20815657…cc695dPrevious genesis