Guideline 1.1.6
Guideline 1.1.6 - Safety: False Information or Fake Features
Our Take
Apple is rejecting your app because it presents false information, fake device capabilities, or trick/joke functionality. This covers apps like fake lie detectors, fake X-ray scanners, fake metal detectors, or prank call/SMS apps. Adding an 'entertainment purposes only' disclaimer does NOT overcome this guideline. This rejection is common for novelty apps that claim device capabilities that don't exist. Even if your intent is humorous, Apple takes the position that users shouldn't be misled about what their device can do. The same applies to apps that send anonymous or prank phone calls or SMS messages. The guideline also covers apps with inaccurate device data — for example, showing fake battery levels, fake storage information, or fake location data. If your app displays any device information, it must be accurate.
Resolution Guide
Remove fake capability claims
If your app claims to detect metals, measure blood pressure, take X-rays, or any other impossible function using only the phone's sensors, remove that feature entirely.
Reframe as educational or entertainment
If the core concept has value, reframe it honestly. For example, instead of 'Metal Detector,' an app could be 'Magnetometer Viewer' showing actual compass/magnetometer readings.
Ensure device data accuracy
If your app displays battery, storage, network, or location information, verify it's pulling real data from system APIs.
Remove prank functionality
Remove any anonymous calling, prank SMS, or spoofed messaging features entirely. There is no compliant version of this.
Update marketing materials
Ensure screenshots, descriptions, and preview videos don't make any false claims about the app's capabilities.
Prevention
Example Rejection Email
Before & After
App marketed as 'Ghost Detector' claiming to use phone sensors to detect supernatural activity
App reframed as 'EMF Meter' showing actual magnetometer data with creative visualization, no supernatural claims
What changed: Using real sensor data honestly rather than claiming impossible capabilities satisfies the guideline.
Community Solutions · 0
Sign in to share your solution.
More Guideline 1 (Safety) rejections
- Guideline 1.1 - Safety: Objectionable Content in App Marketing
- Guideline 1.1.1 - Safety: Defamatory or Discriminatory Content
- Guideline 1.1.2 - Safety: Realistic Violence or Encouragement of Violence
- Guideline 1.1.3 - Safety: Weapons and Firearms Content
- Guideline 1.1.4 - Safety: Sexual or Pornographic Content
- Guideline 1.1.7 - Safety: Exploiting Recent Events or Tragedies