AppForShareStore

AppForShare store

How we review apps, in numbers

Every Android app in the AppForShare store is built by us from source code we reviewed, and checked again while it is live. This page explains each step and shows live counts. A review lowers risk; it is not a promise that an app is free of problems.

Live numbers

Counted 21 Nov 2026 15:20 UTC

0 apps listed, 0 versions live.

WhatLast 30 daysAll time
Releases reviewed00
Releases rejected00
Decided by the automatic review00
Live versions withdrawn as unsafe00
Listings taken down00
Live APKs scanned again00
Rescans that matched known malware00
Reports received00
Reports dismissed00
Reports that led to action00
Copyright and trademark notices00
Complete notices, listing disabled00
Developer responses to a notice00
Listings restored after a decision00
Notices upheld, listing kept down00

By month

MonthNoticesDisabledRestoredKept downMalware withdrawalsReport takedowns
2026-11000000
2026-10000000
2026-09000000
2026-08000000
2026-07000000
2026-06000000
2026-05000000
2026-04000000
2026-03000000
2026-02000000
2026-01000000
2025-12000000

How a release is reviewed

  1. Built from source. The APK is built from a pinned tag or commit by our own build workflow on a fresh GitHub hosted machine, with signed build provenance. We never take a finished APK from the developer.
  2. Checked. Our checks read the manifest and compare it with the last release, look for sensitive permissions and require a reason for each one, scan the APK for known malware (ClamAV and the MalwareBazaar hash list), find trackers, and look for code loaded at run time or hidden code files.
  3. Decided. Clear rules decide first: a malware match is rejected. Anything that needs judgement goes to an AI review with hard limits written in code. A clean minor update waits a short hold before it goes live. Nothing waits in a queue; our staff can review and reverse any decision later.
  4. Signed and published. We sign the reviewed APK for the store. The listing shows the permissions, trackers, source commit and signing certificate, so anyone can check what they install.

While an app is live

  • Rescans. Every live APK is scanned again every 7 days with the newest malware signatures. A match withdraws that version at once.
  • Withdrawing a version. A withdrawn version leaves the download button, the download address and our F-Droid compatible repository right away. For 90 days the repository still names it with a known vulnerability mark, so F-Droid, Droid-ify and similar apps warn the people who installed it. The listing page says which version and why, and the developer is told. Copies the developer sent to Google Play or the App Store are removed there by the developer.
  • Reports. Anyone can report a listing or one version of it for malware, impersonation, copyright or illegal content. An automatic review reads each report with the facts of the app. Reports that make no sense are dismissed. A malware report starts a new scan of that version at once with the newest signatures; only a match withdraws it, never the number of reports. When 2 (impersonation), 3 (copyright) or 2 (illegal content) different people report the same problem within 30 days and at least one report is clearly credible, the listing is taken down. The developer can dispute a takedown once.

Copyright and trademark notices

Rights holders send a notice with our takedown form, with evidence that they own the work or mark. A complete notice disables the listing as soon as it arrives; our target is a response within 24 hours. A notice without evidence changes nothing and gets an answer that says what is missing. The developer can send one response with evidence, and the sender can reply once within 10 business days. We then decide whether the listing comes back or stays down and tell both sides why; nothing comes back on a timer. Without a response within 30 days the notice counts as upheld, and 3 upheld notices in 12 months close the developer's store account. We decide only whether a listing stays on AppForShare, not who owns a right in law.

Contact for notices: AppForShare copyright and trademark team, [email protected].

The rules in full: Store Content Policy.