This is the umbrella rule under which Apple's more specific content restrictions sit — content in your app, whether you wrote it, licensed it, or users posted it, can't cross into being genuinely offensive, obscene, or in bad taste in a way most people would find upsetting.
Why apps actually get flagged
Broad or ambiguous submissions that include crude humor, shock content, or edgy meme-style material aimed at a general-audience rating often get caught here even when no single specific sub-rule clearly applies.
A real example
"Your app contains content that is offensive, insensitive, or in poor taste, per guideline 1.1. Please remove or revise the flagged content and resubmit."
The short version, in more detail
Guideline 1.1 is the umbrella rule for content in an app. It says that material which is offensive, insensitive, upsetting or in poor taste does not belong on the App Store, regardless of who created it. The more specific sub-rules under 1.1 cover individual cases such as discrimination, violence and sexual material, but reviewers also use 1.1 itself when something feels clearly out of bounds without matching a narrower rule.
What this guideline covers
Content the developer wrote, licensed or generated, as well as content posted by users.
Material that is obscene, defamatory or designed to demean or upset people.
Shock content, crude humour and meme-style material shown to a general audience.
The listing itself, including screenshots and descriptions, not only the in-app experience.
What usually triggers this rejection
A joke, soundboard or meme app that leans on crude or shocking material presented to a general-audience rating.
Imagery or text that a reasonable reviewer would find upsetting even though no single specific rule is clearly broken.
User-contributed content that is not filtered and includes offensive posts that the reviewer sees during testing.
Marketing images or descriptions with edgy language that reads as inappropriate on a public storefront.
An app whose main appeal is mocking or humiliating real people or groups.
How reviewers evaluate it
Reviewers spend time inside the app and look at what a typical user would encounter in the first minutes.
They apply a common-sense standard of what most people would find offensive, so judgement plays a role.
They check the age rating against the content actually shown.
Content that is borderline can be treated more strictly when the app targets a broad audience.
Common misunderstandings
An age rating does not make any content acceptable. Some material is not allowed at any rating.
Content created by users is not exempt. The developer is responsible for what the app shows.
A clear "just a joke" intent does not change how a reviewer reads the content.
Common questions
Is 1.1 the same as the more specific content guidelines?
It is the general rule that the specific ones sit under. Reviewers may cite 1.1 when the issue is broad or does not match one narrow sub-rule.
Does AI-generated content count?
Yes. Output generated by a model inside the app is treated as content the app presents.
Can a mature app avoid 1.1 with an age gate?
Age gates help with ratings but do not permit content that is prohibited outright.
Platform rules change often. This page is a plain-language explanation written by AppReviewFix, not official guidance. Check the current App Store Review Guidelines for the exact wording.
Got this exact rejection?Paste it in and get a diagnosis specific to your app, free.