Guideline 1.2 rejection: user-generated content, decoded

Short answer: your app has user-generated content but is missing one of Apple's four required safety mechanisms — filtering, reporting, blocking, and published contact information — or a credible commitment to act on reports within 24 hours. The requirement list is fully specified in the guideline, which makes 1.2 one of the most mechanical rejections to fix: implement all four, document the paths, and hand the reviewer a demo account that can exercise each one.

One warning the guideline is explicit about: apps whose user-generated content is primarily objectionable — anonymous chat roulette patterns are the named risk — don't get a fix list, they get removed. If that's your app's center of gravity, moderation features won't save it.

Got the actual message? Paste it into the free rejection decoder — it matches your rejection against documented store rules and returns the fix steps, the resubmission checklist, and a reply draft. Three free decodes, no account.

1.2 — User-Generated Content Safety Requirements

Your app includes user-generated content (posts, comments, profiles, chat, shared media) but lacks one or more of Apple's four required safety mechanisms: (1) a method for filtering objectionable material, (2) a mechanism for users to flag offensive content, (3) the ability to block abusive users, and (4) published contact information — plus acting on reports, generally within 24 hours.

Severity: blocker · Decoder confidence for this class: A (see the honesty note below)

The fix

  1. Implement content filtering that prevents objectionable material from being posted (keyword/media screening proportionate to your app).
  2. Add an in-app flag/report action on every piece of user content and user profile.
  3. Add block-user functionality that immediately removes the blocked user's content from the blocker's view.
  4. Publish contact information in the app and App Store metadata, and commit to acting on reports within 24 hours — then document all four paths in the review notes with a demo account.

Resubmission checklist

  • Filtering method in place and described
  • Report mechanism on all UGC surfaces
  • Block mechanism implemented
  • Contact info published; 24-hour response process in place
  • All paths documented for the reviewer

Reply draft

Hello App Review Team,

Thank you for the feedback. Build [X] implements all four user-safety mechanisms: (1) filtering — [METHOD]; (2) reporting — [PATH]; (3) blocking — [PATH], which immediately hides the blocked user's content; (4) contact information — published at [LOCATION]. Reports are actioned within 24 hours. Each mechanism is documented in the review notes and testable with the provided demo account.

Thank you for your time.

[NAME]

What the decoder can diagnose here: Which of the four mechanisms Apple named as missing — the fix list is mechanical and fully specified by the guideline. What it cannot: Whether your moderation operation (response times, enforcement) will satisfy a follow-up — anonymous chat apps and apps with an objectionable-content history get extra scrutiny (and apps whose UGC is primarily objectionable get removed, not rejected).

Rule text: “Apps with user-generated content present particular challenges... must include: a method for filtering objectionable material from being posted to the app; a mechanism to report offensive content and timely responses to concerns; the ability to block abusive users from the service; and published contact information for users to easily reach you.” — App Review Guidelines §1.2, retrieved 2026-10-23

Related guides

Sources

  • App Review Guidelines §1.2, retrieved 2026-10-23

Last updated October 23, 2026. Rules change; the retrieval dates above say when this page was last checked against the store's published text.

Decode your rejection — free

The decoder covers 41 documented rejection patterns across the App Store and Google Play, grounded in the stores' own published rules. Three free decodes; the $29 Pre-Flight Founding pre-sale unlocks unlimited decoding plus a full pre-flight check credit when the checker ships.

Open the free decoder

The decoder classifies and guides from the message you paste. It cannot see your app or your binary, and it never promises an approval outcome — that decision is always the store's.