Guideline 3.2.2 trips up a lot of free apps, because the business models that seem clever, watch ads to earn rewards, get paid to refer friends, a feed promoting other apps, are exactly the ones Apple lists as unacceptable. The rule is not against free apps or ads; it is against an app whose primary purpose is to drive ad-watching, marketing tasks, or referrals rather than to provide real value. Here is what 3.2.2 actually prohibits, the traps free apps fall into, and how to build a model that passes.
Short answer
Guideline 3.2.2, Unacceptable Business Model practices, prohibits apps whose primary purpose is to encourage watching ads or performing marketing-oriented tasks, that reward users for downloading other apps, that exist mainly to promote third-party apps, or that monetize built-in device or operating system capabilities. Per Apple's business guidelines, this commonly hits free apps built around "watch ads to earn" or referral payouts. Free apps and advertising are fine; what is not fine is an app where the ad-watching or marketing is the product. To pass, make genuine utility or entertainment the core purpose, and treat ads as support, not the point.
What you should know
- It targets the business model, not free apps: free apps are fine.
- Ad-watching cannot be the purpose: an app to watch ads for rewards is rejected.
- Referral payouts are restricted: rewarding the recipient for downloading is not allowed.
- Promoting other apps is off-limits: a feed of third-party apps is unacceptable.
- Do not monetize OS features: built-in capabilities are not yours to charge for.
What does Guideline 3.2.2 prohibit?
A set of business practices Apple considers unacceptable, regardless of price. The core one is an app whose primary purpose is to get users to watch advertisements or complete marketing tasks, which is not what the App Store is for. It also covers incentivizing downloads, where rewarding the person who receives an invitation for downloading or registering is not allowed, though rewarding the sender for inviting can be acceptable. It prohibits apps that mainly display or promote third-party apps, such as a news feed of other apps, and monetizing built-in capabilities provided by the hardware or operating system, like Push Notifications, the camera, or Apple services such as iCloud. The thread is that the app must offer its own value, not repackage ads, referrals, or system features as the product.
What are the common 3.2.2 traps in free apps?
The popular "earn rewards" models are where free apps go wrong. The table lists them.
| Model | Problem under 3.2.2 |
|---|---|
| Watch ads to earn points or cash | Ad-watching is the primary purpose |
| Pay users to download other apps | Rewards the recipient for downloading |
| Feed that promotes third-party apps | App mainly promotes other apps |
| Charging for a built-in OS capability | Monetizing system or hardware features |
| Complete marketing tasks for rewards | Marketing tasks are the product |
These share a pattern: the app's reason to exist is the ad, the referral, or the promotion, not a feature users value for itself. So a rewards app where the point is watching ads, or a referral scheme that pays people to install apps, is the classic 3.2.2 rejection, even though both are free.
How do you build an acceptable free-app model?
Put real value first and let monetization support it. Build an app that does something genuinely useful or entertaining, then fund it with ads or in-app purchases that support that core, rather than making the ads or tasks the experience. Advertising is allowed as a way to monetize a free app, so a free app with ads is fine when the app itself is the draw. For referrals, you can reward the sender for inviting, but do not reward the recipient for downloading or registering. And do not build your model on charging for capabilities the OS already provides. The question to ask is whether users would value the app with the ads and referrals stripped away; if the answer is no, the model needs rethinking.
What to watch out for
The first trap is assuming a free app is automatically fine, when 3.2.2 is about the model, not the price. The second is a referral feature that rewards the downloader, which is the specific incentivized-download pattern Apple calls out; reward the sender instead. The third is dressing up an ad-watching or task-completion app as a utility when the rewards are the real product. Business model is a product and policy matter rather than a security one, so it sits apart from a pre-submission scan such as PTKD.com (https://ptkd.com), which reads the binary against OWASP MASVS for the security side; the 3.2.2 fix is a change to what your app fundamentally offers.
What to take away
- Guideline 3.2.2 prohibits apps whose primary purpose is watching ads, doing marketing tasks, paying users to download other apps, promoting third-party apps, or monetizing OS features.
- It targets the business model, not free apps, so a free app with ads is fine when the app itself is the value.
- Reward the sender of a referral, not the recipient for downloading, and do not charge for built-in system capabilities.
- Build genuine utility as the core and let ads or in-app purchases support it, since 3.2.2 is fixed by changing what the app offers, not its security.
