Rejection Decoder
Home / Guidelines / 4.7

Guideline 4.7 rejection: Mini apps, mini games, chatbots, plug-ins, and emulators

What it means, why it happens, and how developers get through it.

Subject line you may see: Guideline 4.7

In one line: Your app offers software that is not in the binary, such as HTML5 mini apps, mini games, streaming games, chatbots, plug-ins, or emulator games, and it misses one of the 4.7.1 to 4.7.5 rules.
Usual next move: Fix, new build, then replySomething in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify.Based on how this guideline is usually resolved, not a prediction for your app.
Paste your rejection to check
On this page: Apple's textCausesFixReplyReal casesQuestions

What Apple's guideline says

You are responsible for all such software offered in your app, including ensuring that such software complies with these Guidelines and all applicable laws.

From App Review Guidelines, 4.7, as revised October 16, 2026.

Common causes

How to fix it

  1. Check each of 4.7.1 to 4.7.5 against your app
  2. Add filtering, reporting, and blocking
  3. Route digital purchases through Guideline 3.1 rules
  4. Ask for consent each time data or permissions are shared with a mini app
  5. Publish an index with universal links, and add age labels and an age restriction mechanism
  6. Reply listing each 4.7 rule and where the app meets it

What to put in your reply

A sample reply note. Replace the brackets with your facts and remove anything that does not apply.

Hello,

Thank you for the review. Regarding Guideline 4.7, build [number] adds: 4.7.1 report and block at [screen]; 4.7.3 a consent prompt each time a mini app asks for [data]; 4.7.4 an index at [URL]; 4.7.5 age labels and an age restriction at [screen].

Thank you.

Real cases: others who got 4.7

No public cases logged yet.

Questions developers ask about 4.7

What does a Guideline 4.7 rejection mean?

Your app offers software that is not in the binary, such as HTML5 mini apps, mini games, streaming games, chatbots, plug-ins, or emulator games, and it misses one of the 4.7.1 to 4.7.5 rules.

Why do apps get rejected under Guideline 4.7?

Common causes, based on Apple's guideline text: no filtering, reporting, or blocking for content in the mini apps (4.7.1); digital goods sold in mini apps without following Guideline 3.1 (4.7.1); native APIs exposed to the software without Apple's permission (4.7.2); data or permissions shared with a mini app without consent each time (4.7.3); no index of the software with universal links (4.7.4); no way to identify software above the app's age rating and restrict it by age (4.7.5).

How do I fix a Guideline 4.7 rejection?

1. Check each of 4.7.1 to 4.7.5 against your app. 2. Add filtering, reporting, and blocking. 3. Route digital purchases through Guideline 3.1 rules. 4. Ask for consent each time data or permissions are shared with a mini app. 5. Publish an index with universal links, and add age labels and an age restriction mechanism. 6. Reply listing each 4.7 rule and where the app meets it.

Do I need a new build for Guideline 4.7?

Fix, new build, then reply. Something in the binary has to change. Fix it, bump the build, resubmit, and reply with what changed and how to verify. This is how the guideline is usually resolved, not a prediction for your app.

How should I reply to App Review about Guideline 4.7?

Reply in App Store Connect. Thank the reviewer and name Guideline 4.7, say exactly what changed and in which version and build, give a numbered path the reviewer can follow, and attach proof such as screenshots or a screen recording.

Stuck on 4.7?

Do it yourself, faster

App Store Rejection Rescue Kit: the full decoder, 12 reply templates, Notes for Review templates, and a 60-point preflight checklist.

Get the kit, $12

Have it written for you

Send your rejection, get a reply drafted for your exact case. Kit buyers get $10 off.

AI-assisted, built on Apple's App Review Guidelines. Not a guarantee of approval. If we do not deliver within 24 hours, you get a full refund.

Reply service, $29

Related rejections

2.1(a) App Completeness2.1(b) In-app purchases not found2.5.2 Downloading or executing code2.5.19 Hidden or undocumented features

See also: 1.2 user-generated content · 2.5.2 executing code · 3.1.1 in-app purchase

Source: Apple's App Review Guidelines, section 4.7, as revised October 16, 2026. Last checked . Always read the current official text. How we write these guides.