The app is signed, the build passes review, the crash rate is fine, and then a policy notice arrives asking for evidence that the entity behind the listing is authorised to offer contracts for difference in the countries where the app is available. That is the moment most brokers discover that mobile distribution is a licensing question rather than an engineering one.
Google Play publishes a financial services policy that covers, among other categories, trading in complex speculative products. The published shape of it is consistent: developers offering regulated financial products must declare what they offer, restrict availability to countries where they are permitted to offer it, and provide evidence of authorisation where the local regime requires one. The declaration is not a formality. It is the record the review team compares against your listing text, your screenshots and your website when a complaint or an automated sweep flags the app later.
What actually gets checked
Three things sit at the centre of nearly every financial app review. First, the identity of the developer account holder and whether it matches the licensed entity. A group that holds its authorisation in one company and publishes the app from a different holding company creates a mismatch that a reviewer cannot resolve without correspondence, and correspondence is where timelines die. Second, country targeting. An app available worldwide is, by definition, available in markets where the developer has no permission to solicit, and that is the single easiest policy breach to prove. Third, the marketing surface: the store listing, the screenshots and the first screen after install. Language promising returns, or images of profit figures without risk context, is judged against advertising standards even though it sits inside a product listing rather than an ad.
The country targeting point deserves a blunt statement. If your only authorisation is an offshore registration and your app is switched on across the European Union, you are relying on nobody noticing. That is not a strategy, and the consequence when it fails is not a warning but a removal, sometimes with the developer account attached. The same logic that drives marketing restrictions on CFDs in regulated markets drives store enforcement, because the store is looking at the same national rules.
The licence evidence problem
Where a review asks for authorisation evidence, what is wanted is a verifiable public record: a register entry with a firm reference number, a legal name and a permission set that plainly covers the activity in the app. A certificate PDF from a jurisdiction with no searchable public register is weak evidence, and reviewers are entitled to treat it that way. This is one of the quiet costs of an offshore route that founders underprice when they compare setup expense. Our piece on offshore broker licences covers the tradeoff in more detail, and the practical test in how to check a broker licence is the same test a reviewer applies.
Prop firms sit in an awkward position here because the product is an evaluation of simulated trading rather than a live market offering. The honest answer is that the classification depends on how the app describes itself. An app that presents simulated accounts, states plainly that no client money is traded and does not offer a route to real-market execution is a different object from one that walks a user from a challenge into a live account. Firms that blur the two in their copy invite the harder review.
App store policies change, are enforced unevenly across markets, and are interpreted by the reviewer in front of your case. Nothing here is legal advice. Take advice from counsel qualified in each market you distribute in before you rely on a classification.
When the answer is no
Removal has a shape that is worth understanding before it happens. Existing installs keep working until they break on an OS update, but you lose new acquisition on that platform, you lose the update channel for security fixes, and you lose the ratings history that took a year to build. Firms that treat the store as their only Android channel find that a single enforcement decision cuts a meaningful share of new accounts overnight.
The alternative for Android is a signed package distributed from your own domain. It is a real option and plenty of firms use it, including for products that were removed rather than never listed. It also carries real friction: users must permit installation from an unknown source, updates run through your own mechanism rather than the store, and some corporate device policies block it entirely. On iOS there is no equivalent, which makes the licence question on that platform binary.
Building for the review rather than around it
The listing should read like a description of a regulated service. Name the legal entity and the licence in the listing text. Restrict distribution to the countries the licence covers, and do it in the console rather than through a geo-block inside the app, because a reviewer in an excluded country will see the app as available. Keep risk disclosure on the first screen a new user reaches, not buried in a settings menu. Put account deletion where the policy expects it, reachable from inside the app and from a web page, since data policies are enforced independently of financial ones.
Platform choice matters too. A white-label terminal published under a vendor's own developer account puts your distribution inside someone else's policy record, and their enforcement history becomes yours. A broker publishing its own build under its own licensed entity controls the correspondence. That control is part of why firms move from a shared vendor app to a branded one, a decision covered in choosing a trading platform. Whichever route you take, the store's view of you is only as good as the licence you can evidence, and no amount of engineering fixes a permission you do not hold.
"Treat the app store as a second regulator. It reads your licence, your website and your ad copy, and it can switch off your distribution in a morning without a hearing."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- App stores enforce national financial rules, so distribution follows your licence rather than your build quality.
- Country targeting is the easiest breach to prove: an app switched on where you hold no permission is a removal waiting to happen.
- Reviewers want a searchable public register entry, which is where thin offshore registrations cost you real distribution.
- A signed Android package on your own domain is a genuine fallback, with install friction and no equivalent on iOS.
Frequently Asked Questions
Does a prop firm app need a financial services licence to be listed?
It depends on how the app presents itself. An app offering only simulated evaluation accounts, with no route into live-market execution, is classified differently from one that leads a user into real trading. Firms that mix both in the same listing invite the stricter review. Take local legal advice on the classification before you publish.
What happens to existing users if the app is removed?
Installed copies keep running until an operating system update breaks them, but new downloads stop, the update channel closes, and the ratings history is lost. The immediate business effect is on new account acquisition on that platform.
Is distributing an Android package from our own website a workable alternative?
It works and firms do use it. Users must allow installation from a source outside the store, updates run through a mechanism you build and maintain, and some managed corporate devices block it. There is no comparable route on iOS.
About the Author
Roman Onta is an Executive Director at SINGUARD. He builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals side by side with his brother Alex Onta, and he helped on the design of eTrader, the division Alex built and leads. His ground is worldwide payment processing, AML compliance and the corporate structures brokers are built on, work the two of them carry together, shaped by executive roles in the UAE and international corporates. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.