Rejected under Guideline 1.1.1 (Objectionable Content) — car notification app, looking for advice

Hi everyone, I recently got rejected under Guideline 1.1.1 - Safety - Objectionable Content and I'm struggling to understand how my app falls under this category. Looking for advice from anyone who's dealt with similar rejections.

What the app does:

AutoSignal is a vehicle notification app designed for the Bulgarian market. It solves a very common real-world problem - needing to contact a car owner when their vehicle is double-parked, blocking you in, has its lights left on, or has been hit/damaged while parked.

The core flow is:

A user scans a license plate using their phone camera

If the car owner is registered in the app, they receive an anonymous push notification (e.g., "Your car with plate XX 1234 XX is blocking someone" or "Your lights are on")

The car owner can then take action

Users can also report vehicle damage cases with temporary witness notes that auto-expire after 7 days.

Why I believe it doesn't violate 1.1.1:

  • The app does not expose any personal information. Notifications are fully anonymous - the sender never sees the car owner's identity, phone number, or any personal details.

  • License plates are public information - they are visible on every car on every street. The app doesn't scrape or store plate databases.

  • The use cases are entirely constructive: notifing someone their car is being towed, blocked in, damaged or has lights on.

  • There is no messaging or direct contact between users - only predefined notification templates.

  • Damage case witness notes are temporary (7-day expiry) and designed to help with insurance claims, not harassment (everything is opt-in model).

What Apple said:

"Issue Description

The app includes content that could be considered defamatory or mean-spirited.

Specifically, your app allows users to collect license plate information and send activity associated with the license plate. Content that is likely to humiliate, intimidate, or harm a targeted individual or group is not appropriate for the App Store."

What I've tried/considered:

  • Adding content moderation and reporting features

  • Limiting notification frequency (rate limiting on the backend)

  • Requiring car owners to opt-in by registering their own plates before they can receive any notifications

Has anyone successfully appealed a 1.1.1 rejection for a similar use case? Should I request a call with the App Review Board? Any suggestions on what additional safeguards I could highlight or implement to address their concerns?

Thanks in advance for any guidance.

If your app has been rejected and you need help resolving the issue, consider taking advantage of one of the following support options available from App Review:

  • Reply to the message from App Review in App Store Connect and request clarification.
  • Request a call with an Apple representative to discuss the outcome of the review.
  • Submit an appeal to the App Review Board if you believe your app follows the App Review Guidelines.

Visit the Contact Us page on Apple Developer and select the App Review tile to learn more.

Rejected under Guideline 1.1.1 (Objectionable Content) — car notification app, looking for advice
 
 
Q