Legal
Android Store Developer Distribution Agreement
Last updated November 20, 2026
These terms apply to every developer who lists an Android app in the AppForShare store. Apps must also follow the Store Content Policy.
1. Who this agreement is between
This agreement is between you (the developer, or the company you list apps for) and ZenTalk LLC, Houston, Texas, United States ("we", "us"), which runs AppForShare and the AppForShare Android store. It applies when you set up an app on a project's Store tab. It adds to our Terms of Service and Privacy Policy; where they differ for the store, this agreement wins.
Your app must also follow the Store Content Policy.
2. How the store works
Every app in the store is built from reviewed source. You choose the repository, the tag or commit, the Gradle module and the variant. The build runs either in your own GitHub Actions through our published build workflow, or on our own build servers. We never accept a signed binary that we did not build or could not reproduce from your source.
Each release is then reviewed automatically: permission changes against your last release, malware and tracker scans, code rules, and an AI review of the first release, of any new sensitive permission and of anything the checks flag. Our staff can review any decision later. "Built from reviewed source" describes this process. It is not a promise that an app has no bugs or security issues, and it does not mean Google or anyone else has approved the app.
3. Your app and your package name
You keep every right to your app, its code, its name and its package name. AppForShare is never the registered developer of your app with Google, and listing an app with us does not move your Google developer account or your package name to us.
Before a package name is listed for the first time you prove you control it: with an APK of the app that carries your claim token and is signed with your release key, which proves you hold that key, or with a claim file committed to the repository. A copy of the app from another store does not count. If two workspaces claim the same package name, fixed evidence rules decide at once: proof of the signing key beats a repository claim file, and otherwise the workspace that proved it first keeps the name. Our staff can review that decision later and may ask both workspaces for more proof. We may remove a listing if a claim turns out to be false.
4. What you allow us to do
For each app you list, you allow us, for as long as it is listed and for the wind down described below, to:
- read the source at the tags and commits you choose, build it, scan it and review it;
- sign the APK we built with the key held for your app, and host and distribute it to anyone, free of charge;
- show your app's name, description, icon, screenshots and other listing details on store pages, in our store app and in a repository index that F-Droid compatible apps can read;
- keep build records (the recipe, logs and hashes) so anyone can rebuild a release and compare it with ours.
We list your app in other stores only if you agree to it for that store.
5. Private repositories
For apps built from a private repository we read it through the AppForShare Builds GitHub app with the access you grant. We read only what a build and its review need, we do not publish your source, and build logs of private apps are visible only to your workspace and our staff. Our hosting and build providers handle the source only to run the build for us. Releases from private repositories always get the full automatic review, including the AI review, because their source is not public.
6. What you promise
- You have the right to distribute the app and everything in it, including third party code, fonts, images and media, under their licenses.
- The listing is accurate: description, screenshots, content rating answers, anti features and the privacy policy describe the app as it is.
- The app has a privacy policy at a public address, and it handles personal data as that policy says.
- The app does not contain malware or hidden functions, and does not download code at run time to change what it does after review.
- You answer reports about your app sent to your account email within 7 days, and within 24 hours for security issues.
- You follow the export, sanctions and consumer laws that apply to you and your app.
7. Review and our decisions
We may delay, decline or remove a release or a whole listing when it breaks this agreement or the Store Content Policy, when we receive a valid legal notice, or when a release puts users at risk. Release decisions are made automatically by our checks and an AI review (Google Gemini), within fixed rules in our code; the AI review sees the facts our checks found and the text you wrote for the listing, never treated as instructions. We tell you why and what to change, unless the law does not allow it. You can ask once per release for an automatic re-review with an explanation in the Store tab, our staff can review and reverse any decision, and you can always ask for a person to look at a decision by writing to [email protected]. Decisions to remove a whole listing or to act on a legal notice are made by a person.
8. Signing keys
By default we create a signing key for your app in Google Cloud Key Management Service; the private key never leaves it and we use it only to sign releases built from your source. You can instead sign our build yourself, or have your own key held for your app, where your plan includes it. Copies installed from Google Play cannot be updated by our store, because Google holds that signing key.
9. Sending a release to Google Play or the App Store
If you ask us to, we send a reviewed release to Google Play or to App Store Connect with the store connection your workspace set up, after an Admin of your workspace confirms each send. You stay the developer on those stores and remain responsible for your listing there; their own review and rules still apply, and we do not submit anything on our own. For Google Play we send the app bundle built with the reviewed release, signed with the key you chose here as your upload key. We never sign iOS builds; the iOS build you send is the one you signed.
10. Plans and fees
Apps built from a public repository are listed on every plan with an AppForShare account. Apps built from a private repository, and several apps or maintainers per workspace, need the plans shown on the pricing page. The store does not sell apps or process payments for you in this version.
11. Removing your app
You can remove an app from the store at any time. We stop offering new downloads within 7 days and keep a short notice in the repository index so apps that installed it can tell their users. Copies already on devices stay there. We keep build records and review history for 2 years to handle reports and legal requests, then delete them.
12. Warranties and liability
The store is provided as described in our Terms of Service, including its limits of liability. You are responsible for your app and for the claims of your users about it, and you will cover our reasonable costs if a third party brings a claim against us because your app broke their rights or the law.
When a third party complains about your app, our usual step is to hold or remove the release or listing while the matter is open. If the person who complained proves the claim, for example with a court order or evidence we find clear, you may also face a penalty. That can include paying the costs and damages that follow from the claim and losing access to the store.
13. Changes and contact
We may update this agreement. For significant changes we email account holders with listed apps at least 30 days before they apply. Questions: [email protected].