Skip to content
AppFoyer
Start free

Guides

Publishing beyond Google Play: the other Android stores

Huawei, Amazon and Samsung each want a privacy policy URL in their own console with their own form. What is the same everywhere, what is not, and what we have not verified.

Huawei AppGallery, Amazon Appstore, Samsung Galaxy Store and the rest each ask for a privacy policy URL in their own console, with their own questionnaire. The pages themselves can be the same ones you already publish — what differs is where the URL goes and which form you fill in.

Checked 19 September 2026. Store policies change, sometimes without notice. Everything below links to the official documentation, and that page — not this one — is the authority. If the two disagree, the store is right.

Shipping the same APK to a second Android store is mostly a distribution question. The compliance part is smaller than people expect — and larger than “nothing”, which is what most guides imply by ignoring it.

The one thing that is the same everywhere

Your pages do not change. A privacy policy is a privacy policy; a support page is a support page. If yours are honest and cover what your app and its SDKs actually do, the same URLs work for every store that asks for one.

What differs is where the URL goes and which questionnaire sits next to it. So the work per additional store is: find the field, paste the URL, fill in that store’s form.

Huawei AppGallery

AppGallery Connect asks for a privacy policy URL in the privacy statement area of app submission, and Huawei expects both an easy-to-find in-app link to the policy and the URL submitted in AppGallery Connect so it can be shown in the app’s information on AppGallery.

On content, Huawei’s requirement mirrors the others: the policy has to cover the purpose, method and scope of personal data collection and use — including data handled by third-party code and plug-ins embedded in your app.

If your Play listing is already in order, the same policy satisfies this. The in-app link is the part iOS-first developers sometimes have not built.

Amazon Appstore

Amazon runs a privacy questionnaire rather than only a URL field. If your app collects data associated with an individual user, you must supply a privacy policy.

The part worth knowing before you plan a release: the questionnaire is not optional any more. Amazon states that all new apps and app updates are required to have a completed privacy questionnaire, and that you can no longer publish a new app or update an existing one if the questionnaire is incomplete or has unaddressed issues. For a live app with missing information, the Submit button is disabled.

So on Amazon, an unfinished privacy form blocks shipping — not just your first submission.

Samsung Galaxy Store

Galaxy Store keeps a Privacy Policy URL in the app registration, and Samsung’s guidance is explicit that when your privacy policy URL changes, the URL in the app registration must be updated.

That is the one operational rule to carry with you across every store: a URL change is not one edit. See changing a URL in a live listing — with three or four stores, the case for keeping the old address redirecting gets much stronger.

The ones we have not verified

Xiaomi GetApps, RuStore, OPPO App Market, vivo App Store and F-Droid all take Android apps, and several are the practical route into markets Google Play does not serve. We have not checked their current submission requirements, and this page will not guess at them — a made-up requirement is worse than an absent one.

Open each console’s own documentation before you submit. The pattern above holds in every store we have checked, so expect a privacy policy URL field and some form of data-collection declaration, and confirm the details rather than assuming them.

F-Droid is a different animal from the rest: it builds from source and has its own inclusion policy, so read that rather than mapping a commercial store’s expectations onto it.

A practical order for a multi-store release

  1. Get Play right first. Its requirements are the strictest of the mainstream stores and the best documented; everything else is then mostly paperwork.
  2. Publish your pages on one hostname and use the same URLs everywhere. Four stores pointing at four different hosts is four things to keep alive.
  3. Keep one dependency list and fill every store’s data form from it, never from each other.
  4. Write down which store has which URL in which field, because the day you move the pages you will need that list.

What AppFoyer does here

The store URL field accepts listings from the well-known Android stores — Google Play, Huawei AppGallery, Samsung Galaxy Store, Amazon Appstore, Xiaomi GetApps, F-Droid, RuStore, OPPO and vivo — not only Play, so an app distributed outside Google’s store is a first-class case rather than something the form refuses. APK mirror sites are refused, deliberately.

Your pages live at one address and the same URLs go into every console. Each app gets both a .page and a .site address serving identical content, which matters here more than anywhere else: some countries and networks block whole top-level domains, and a store you are publishing to precisely because Google Play does not serve that market is a bad place to have an unreachable privacy policy.

The authoritative sources

Do this in a few minutes instead

AppFoyer hosts the pages this guide is about — privacy policy, terms, support, account deletion and app-ads.txt — on their own subdomain, with no domain or server of your own. One app is free, and nothing a store requires is ever behind a paywall.

Start free See a live example