App rejected: minimum functionality

An app that is a wrapper around a website, or that does very little, is rejected under 4.2 regardless of how good the legal pages are.

Updated 2026-09-18 · Written from the same rules terms.gg uses to generate documents

What the rejection means

An app that is a wrapper around a website, or that does very little, is rejected under 4.2 regardless of how good the legal pages are.

The usual causes

• The app is a web view of an existing site.
• The only features are links.
• There is nothing a browser could not do.

What to change

This is a product problem rather than a paperwork one. Add something that needs the device: notifications, offline use, a sensor, a share sheet.

Before you resubmit

• Open every URL you entered in a private window.
• Read the reviewer's message again and answer the specific point, not the general topic.
• Reply in Resolution Center saying what you changed and where to see it.

Keeping it true after launch

A legal page stops being true the moment the product moves past it, usually by adding a payment provider, an analytics SDK or a sign-in. No store re-checks your pages against your build, so the drift is yours to notice.

• Re-read it whenever you add a dependency that sees user data.
• Re-check what loads on the page after any change: the cookie notice and the policy have to agree.
• Keep the URL stable. Changing where a policy lives breaks every listing that points at it.