Forex Trading App Ads Policy: What Google, Meta and the App Stores Require (2026)

A forex trading app can be promoted, but only inside four separate rulebooks. Google Ads treats rolling spot forex and CFDs as complex speculative financial products: eligible locations only, a licensed provider, and a certified account. Meta lists contract for difference trading as prohibited. Google Play needs a declaration; Apple needs the financial institution itself to submit the app.

The forex trading app ads policy is four rulebooks, not one

There is no single "forex trading app ads policy". An app that lets people trade foreign exchange touches four sets of rules at once, and each one can stop a launch on its own:

• The ad platform decides whether your ads may run at all, in which countries, and after which certification.
• The app store decides whether the listing itself is allowed, who may publish it, and what you must declare.
• The financial regulator in each market decides whether you may offer the product there in the first place. Both Google and Apple push this question back to you.
• Local advertising law adds disclosures on top, which the platforms expect you to know.

The practical consequence is that approval is per market, not global. A product that is advertisable in one country may be unadvertisable in the next one, with the same app, the same creative and the same account.

Google Ads: forex sits in "complex speculative financial products"

Google's Financial products and services policy defines financial products and services as "products and services related to the management or investment of money and cryptocurrencies, including personalized advice". Inside that policy, forex has its own section: complex speculative financial products, which Google describes as contracts for difference (CFD), rolling spot forex — "often referred to as 'Forex' or 'FX'" — and related forms of speculative products.

According to that policy, ads for these products are allowed only when all of the following are true:

1. "The advertiser is a licensed provider or aggregator."
2. "The products and ads comply with local laws and industry standards."
3. "The targeted location is eligible to be targeted and the account is certified by Google."

Two details in that list are easy to miss. First, eligibility is a property of the targeted location, and Google publishes the approved locations in a selector on the policy page — if your target market is not on that list, the product cannot be advertised there, certification or not. Second, certification is applied for per location or location group, so a business that expanded into three markets may need three applications.

What gets disapproved even with a licence

The same policy names destinations that are not allowed regardless of your licence: ad destinations that provide signals for the trading of complex speculative financial products. Google's examples include trading signals, tips or speculative trading information, and affiliate sites that carry related content or broker reviews. This is the single most common surprise for growth teams: the broker's own app may be perfectly certifiable while the affiliate funnel pointed at it is not.

Destination disclosures

Google's general financial services requirements apply on top of the category rules. The destination must prominently show the physical address of the business offering the product or service, all associated fees, and links to third-party accreditation or endorsement where an affiliation is asserted or implied. Google also states plainly that advertisers "are expected to do their own research on the local regulations for any location their ads target".

Note that the policy applies to the ad and its destination, whether that destination is a website, an app store listing or a progressive web app. The distribution format you choose does not change the category your product falls into — the same point we made in our guide to Google Ads restricted categories.

Where you apply in 2026

Google is moving these applications into the product. In Google Ads you apply under Admin, then Policy, then Account, then Apply for certification; Google lists complex speculative financial products there alongside the three cryptocurrency certifications. Google's own note on the change says applications "will no longer be supported via the Google Ads Help Center and will need to be submitted through your Google Ads account starting June 2026", that the rollout is incremental, and that existing certifications and pending applications are not affected. Separately, Google may require financial services verification in certain locations, and a separate verification may be needed for each targeted location.

If your product is crypto rather than currency pairs, the certification track is a different one — we covered it in the crypto app Google Ads policy guide.

Meta: CFD trading is on the prohibited list

Meta's rules run the other way, and this is the difference that most often breaks a cross-platform launch plan. Meta's Prohibited Financial Products and Services standard lists contract for difference trading — defined there as "a financial contract that pays the differences in the settlement price between the open and closing trades" — and binary options, "a financial product where the payoff is either a fixed monetary amount or nothing at all". The standard states these as prohibitions, without a certification path of the kind Google offers for the same instruments.

Meta's separate Financial and Insurance Products and Services standard governs the financial products that are allowed but restricted. Under it, advertisers "may be required to verify their business and/or individual identity and demonstrate they are authorized by the relevant regulatory authorities", and they are "required to comply with disclosure requirements set by law". Ads promoting credit cards, loans or insurance services must be targeted to people 18 years or older.

So the realistic reading for a forex app in 2026: plan Google as the paid-acquisition channel where a compliant, licensed broker has a documented route, and treat Meta as a channel where the specific instrument you sell may not be advertisable at all. Check the current standard before building a budget around it — Meta revises these pages, and the burden of checking sits with the advertiser.

Google Play: the declaration is the gate

On the store side, Google Play's Financial Services policy uses the same definition of financial products and services as the ads policy. Its headline requirement is compliance rather than certification: "If your app contains or promotes financial products and services, you must comply with state and local regulations for any region or country that your app targets — for example, include specific disclosures required by local law." One instrument is banned outright: "We do not allow apps that provide users with the ability to trade binary options."

Every developer with a published app must complete the Financial features declaration in Play Console, including apps in testing tracks, and developers whose apps have no financial features must still complete it to certify that. The declaration's trading group covers stock trading and portfolio management, cryptocurrency exchanges and wallets, tokenised digital asset sales, and crowdfunding; a trading app declares there and the answers are reviewed as part of app review.

Worth knowing precisely: Play's country-specific licence uploads — India's RBI registration, Indonesia's OJK licence, the Philippines' SEC registration and Certificate of Authority, Nigeria's FCCPC approval letter, Kenya's CBK digital credit provider licence, Pakistan's SECP approval, Thailand's Bank of Thailand or Ministry of Finance licence — are written for lending features, not for currency trading. A forex app is therefore governed by the general rule plus the declaration, which means the burden of proving local authorisation falls on the review of your declaration and your own market research. If the review goes against you, the reason string is the thing to read first; our guide to Google Play app rejections covers how to work that back to the specific policy.

Apple: the institution submits, not the marketer

Apple's App Store Review Guidelines are short and direct on this point. Guideline 3.2.1(viii) states: "Apps used for financial trading, investing, or money management should be submitted by the financial institution performing such services and must have necessary licensing and permissions in the locations where you make them available." Guideline 5.1.1 adds that apps providing services in highly regulated fields, financial services among them, should be submitted by a legal entity that provides the services and not by an individual developer.

For a white-label or agency-built trading app this is a structural requirement, not a paperwork detail: the developer account under which the app ships has to be the regulated entity. Discovering that after the build is finished is expensive.

A pre-launch checklist

1. List your target markets first. Everything else — ad eligibility, certification applications, store licences — is decided per market.
2. Confirm the licence held by the entity that will appear as the advertiser and as the app publisher, in each of those markets.
3. Check the Google Ads eligible-location selector for complex speculative financial products before you plan spend, and apply for certification per location or location group.
4. Fix the destination before applying: physical address, all fees, and accreditation links where affiliation is claimed.
5. Complete the Play Financial features declaration honestly, and expect the answers to be part of app review.
6. Ship the app under the regulated entity's account on the App Store.
7. Re-read the Meta standards rather than assuming parity with Google; the same instrument is treated differently.
8. Keep the creative claim-free. Performance or income claims attract scrutiny under the deceptive-content standards on every platform.

What not to try

There is a category of "solutions" circulating for restricted verticals that amounts to showing review a different destination from the one users get. On Google's side this is squarely against policy: its rules on abusing the ad network prohibit techniques that hide the true destination or manipulate settings to circumvent policy review, and that is a prohibited-practice violation, which puts the whole account at risk rather than a single ad. Google's enforcement ladder runs from disapproval to warnings and strikes, with immediate suspension for egregious violations and the possibility that related accounts are suspended too.

The comparison is worth stating plainly, because the two paths have opposite risk profiles. The licensing route is slow, market-by-market and survivable. The other route ends the account, and usually the accounts next to it.

FAQ

Can you run Google Ads for a forex trading app?

Yes, in eligible locations, if the advertiser is a licensed provider or aggregator, the product and ads comply with local law, and the account holds Google's complex speculative financial products certification for that location. Apply in the Google Ads account under Admin, then Policy, then Account.

Does Meta allow forex or CFD app ads?

Meta's prohibited financial products standard names contract for difference trading and binary options. Its restricted financial services standard covers the allowed products and can require identity or business verification and proof of regulatory authorisation. Check the current standards before planning a Meta budget.

What does Google Play require from a forex trading app?

Completion of the Financial features declaration in Play Console, compliance with local regulation in every targeted country, and the disclosures local law requires. Apps that let users trade binary options are not allowed.

Who should submit a trading app to the App Store?

The financial institution performing the service. Apple's Guideline 3.2.1(viii) requires the submitting entity to hold the necessary licensing and permissions in the locations where the app is available, and Guideline 5.1.1 rules out individual developer accounts for highly regulated fields.

Sources and versions

Policies move. The statements above reflect Google's Financial products and services and complex speculative financial products policies, Google's certification application notes, Google Play's Financial Services policy and Financial features declaration help, Meta's Prohibited Financial Products and Services and Financial and Insurance Products and Services standards, and Apple's App Store Review Guidelines as published in September 2026. Before a launch, open each source page for your specific market rather than relying on any summary, including this one.