Skip to content

Transparency

We believe the people who use a platform deserve to understand how it operates. Adieuu is built on a commitment to radical transparency — in our code, our finances, and our decision-making. If we ask for your trust, you should be able to verify it.

Open Source

Our codebase is openly auditable. Anyone can read (or locally clone) the code that powers Adieuu, audit how we handle data, and suggest improvements. If our codebase is compromised, or vulnerable in any way, it's publicly visible and verifiable by you, your tech friends, or others.

View our repositories

Public Financials

We're working toward making our financials fully public. Revenue, costs, how money flows through the company — all of it. We think you should know exactly where your money goes and how we sustain the platform. This is coming soon, and when it's ready you'll find everything here.

Content Reports

We plan to make all platform-level content reports public, except in cases where doing so could affect a user's privacy. You deserve to see how we enforce our policies and what actions we take. Users can file content reports directly in the app or by emailing abuse@adieuu.com. Our Privacy Policy explains how we handle reports and the information that comes with them.

When we are allowed to say so, we publish government and law enforcement requests we have received and whether we complied with them, any legally compelled removals or restrictions, and DMCA notices we process.

We will not publish anything that would identify a person. Secret orders we are forbidden from disclosing will not appear here, but depending on your jurisdiction, our warrant canaries may apply.

The chart and table use the same four monthly totals, grouped here the way we think about them:

  • Government & Law Enforcement Requests: how many arrived, and how many we completed (when compliance is required). Those are separate totals; a request we declined (or haven't yet completed) still counts as received.
  • Compelled Removals: content, aliases, or accounts a court or other legal process required us to remove or limit. This is notably separate from content reports, which are user-initiated actions.
  • DMCA Notices: DMCA and/or takedown notices we processed. These come from copyright and other intellectual property holders.

We will add or split categories if the product or the law around it needs more honest detail. If we change how a number is defined, we will note it here so you can still compare reports without guessing.

Year to date, as of

Export CSV
01JanFebMarAprMayJunJulAug
  • 0 LEO Requests Received
  • 0 LEO Requested Completed
  • 0 Compelled Removals
  • 0 DMCA Notices

No requests recorded in 2026 through August 25, 2026.

Warrant Canary

Some government orders come with a gag or sealing order: we would be legally forbidden from telling you they exist. A warrant canary is a regularly updated public statement that we have not received such orders in a given jurisdiction. As long as a canary is current, that statement still holds there. If we stop updating it, treat the silence as a warning.

View warrant canaries