Developer Policy

Every build is checked before it reaches a single reader.

Technical requirements

• The package must be signed. Unsigned builds are rejected automatically.
• Debug builds are rejected. Ship a release build signed with your release key.
• The package name in the manifest must match the listing.
• Each release must have a higher versionCode than the last.
• An update must be signed with the same certificate as the previous release.

Listing requirements

• A real icon, at least two screenshots and a description that says what the

app does.

• A privacy policy URL if your build requests sensitive permissions.
• A support email address for paid apps.

Permissions

Request only the permissions you use. A build requesting SMS, call log or background location access needs a clear justification in the listing — we read these carefully because readers do too.

What gets a listing pulled

Malware or unwanted behaviour, undisclosed data collection, impersonating another product, ratings manipulation, or a listing that materially misdescribes the app. Serious cases are suspended immediately rather than sent back for changes.

Payouts

Earnings clear after a short holding period, which protects against refunds and chargebacks. Once cleared they can be withdrawn to a saved payout method. Payout requests are reviewed by our finance team before the money moves.