Getting in touch
Contact
There is no general contact form and no support inbox, and this page is not going to pretend otherwise. What exists instead is a set of specific routes, each attached to the thing it can actually change. Every one of them is faster than a form would be, because each goes directly to the queue that handles it.
Why no form? A contact form that posts nowhere is worse than no form at all: it takes a real problem, gives you the feeling of having reported it, and quietly discards it. The routes below are the ones with something on the other end.
Where to go
Something is wrong with a listing
Open the app's page and use the report action on it. Reports land in the moderation queue immediately, and a moderator can delist an app while it is investigated. You do not need an account and you do not need to be a rights holder.
Include the version, what you observed, and the SHA-256 of the file you downloaded if you still have it. That last detail is what separates a bad listing from a bad download, and without it the two look identical from our side.
Browse the catalogueA copyright or takedown matter
The DMCA page sets out the formal process, including the designated agent's address, what a valid notice has to contain, and the counter-notice procedure. If you are a publisher who simply wants your own app removed, that page covers the shorter path too.
For anything urgent — an app actively harming users, or an obvious impersonation of your brand — file the report on the listing as well. A moderator can act on that immediately while a formal notice is still in transit.
Read the DMCA processYou want to submit a build
Submissions go through the upload flow rather than through anyone's inbox. Sign in, describe the app and where the build came from, and confirm you have the right to distribute it. Nothing goes live on submission.
We compute the file's SHA-256 and check its signing certificate against earlier releases of the same package before a moderator reads the entry. A certificate mismatch blocks approval outright.
Submit an appYou want to see what is being reviewed
The moderation queue is visible rather than hidden behind a support address. It shows what has been submitted and what has been reported, which is usually a faster answer than asking would be.
If your submission or report is in the queue, that is where it is. Nothing is waiting in an inbox somewhere to be triaged separately.
View the review queueWhat makes a report useful
Most reports that arrive without enough detail are not wrong, they are just unactionable. "This app is fake" gives a moderator nothing to check. The version you installed, the SHA-256 of the file you actually downloaded, and a sentence about what you observed give them three things to check independently, and the difference between those two reports is whether anything happens.
The hash matters more than people expect. If the file you downloaded has a different SHA-256 than the one published on the listing, the problem is your download or the path it took, and the listing may be perfectly fine. If it matches, the problem is the listing, and that is a much more serious finding. Same symptom, opposite conclusions — and the hash is the only thing that separates them.
It is also worth knowing what a report cannot conclude. APKBrowse records hashes and signing certificates and links to official stores; we do not run malware scans. A report that an app behaves badly is still worth filing — it is exactly the kind of thing that provenance checks cannot detect — but the answer will come from a person looking at it, not from a scanner we do not have.
What we cannot help with
We do not provide support for the apps in the catalogue. If an app crashes, loses your data, or bills you for something you did not want, the developer is the only party who can do anything about it — we hold a file and a fingerprint, not their source code or their account system. The same goes for account recovery, refunds, and anything happening inside an app after it is installed.
We also cannot help you install a build that Android is refusing. When an install fails with a signature mismatch, that is the platform declining to let a file from one author replace an app from another, and it is doing the right thing. There is an article about why that error is not a problem to be worked around, and the answer is never for us to hand you a way past it.
Worth knowing
APKBrowse mirrors real, open-source apps from F-Droid and records the SHA-256 and signing certificate of every build it lists. The about page explains what this site is and why it is built this way.