Guideline 1.2 User-Generated Content: filtering, reporting, blocking — and the 2026 changes for chat and AI apps

Guideline 1.2 says apps with user-generated content or social networking services “must include”:

The same guideline adds that apps “used primarily for pornographic content, Chatroulette-style experiences, random or anonymous chat, objectification of real people… making physical threats, or bullying do not belong on the App Store and may be removed without notice.”

Rejection messages under 1.2 list concrete precautions, and two of them go beyond the guideline's own text. One developer posted the full list:

So build for the rejection, not just the guideline: terms with a zero-tolerance clause that users accept before they can post, and a process to act on reports within 24 hours. Reviewers check each item — one app with pre-approval moderation and a report button was still rejected because it had no in-app block.

PostRow(post: post)
    .contextMenu {
        Button("Report", systemImage: "flag") {
            Task { await moderation.report(post) }   // goes to your review queue
        }
        Button("Block \(post.author.displayName)", systemImage: "hand.raised") {
            Task { await moderation.block(post.author) } // hide their posts and messages now
        }
    }

The age rating side is less scary than it sounds: in Apple's age rating definitions, user-generated content, messaging and chat, and advertising are listed as capabilities even at 4+. What changes the rating is how often sensitive content can appear — and for social feeds, whether under-13s are kept out. Apple's definition for that option says that “at a minimum, the Declared Age Range API is called to check users' age ranges before enabling social media features.”

• Chatbots inside your app are your responsibility. Guideline 4.7 covers software not embedded in the binary — including “chatbots” — and 4.7.1 requires the same filtering, reporting and blocking tools as 1.2.
• AI affects your age rating. Apple's July 2025 note says to consider “how all app features, including AI assistants and chatbot functionality, impact the frequency of sensitive content appearing within your app.”
• Sending user data to an AI provider needs consent. Since November 2025, Guideline 5.1.2(i) requires you to disclose sharing personal data “with third-party AI” and get explicit permission — see our 5.1.2 page.
• Let people report AI output. A Report action on generated replies and images covers the 1.2 requirement and gives you the data to tune your filters.

1. 01

   Add terms users must accept

   A clear zero-tolerance clause for objectionable content and abusive users, accepted before anyone can post or message.

2. 02

   Filter before content goes public

   Text filtering at minimum; image moderation if users upload photos.

3. 03

   Report and block everywhere

   On posts, comments, profiles, messages and AI output — reachable in one or two taps.

4. 04

   Commit to 24-hour action

   Set up a queue and alerts so reports are reviewed, content removed and users ejected within a day.

5. 05

   Show contact information

   A support email or form inside the app and on your Support URL.

6. 06

   Reply with where each one lives

   App Review checks every item; tell them exactly how to find each one.

Hello App Review team,

Thank you for the feedback on Guideline 1.2.

Build [number] includes:
- Terms (EULA): users must accept them at sign-up before posting. They
  state zero tolerance for objectionable content and abusive users.
- Filtering: posts and usernames are filtered before publishing.
- Report: long-press any post, comment or profile > Report.
- Block: long-press any post or open a profile > Block.
- Reports are reviewed within 24 hours; violating content is removed
  and the user is removed from the service.
- Contact: Settings > Contact Support ([email]).

Thank you,
[Name]