App Store Reject

Guideline 1.5

Guideline 1.5 - Safety: Missing or Broken Developer Contact Information

Low SeverityEasy FixTypical Fix: 1-2 hours0 Reports
Also known as:Support URL does not include a functional contact methodApp does not include developer contact informationSupport URL returns a 404 or is a placeholder pageContact information is outdated or not monitoredEducational app lacks accessible support contact

Our Take

Apple is rejecting your app because it lacks accurate, accessible developer contact information. Users need to be able to reach you with questions and support issues. Both your app and its Support URL must include an easy way to contact you. This is a simple, checklist-style rejection that's easy to fix but commonly missed. The rejection can be triggered by: a broken support URL (404 page), a support page with no actual contact method (just a generic FAQ), missing contact information in the app itself, or outdated contact details. For educational apps (those used in classrooms), this is particularly important. Additionally, Wallet passes must include valid contact information from the issuer.

Resolution Guide

01

Fix the Support URL

Ensure the URL in App Store Connect points to a live page with a real contact method (email address, contact form, or support chat).

02

Add in-app contact

Add a 'Contact Us' or 'Support' option in your app's Settings or About screen with a working email link or form.

03

Verify URL accessibility

Open the Support URL in a private/incognito browser to confirm it loads without authentication and displays contact information.

04

Use a real email

Don't use noreply@ addresses. Use a monitored support email that you actually check.

Prevention

  • Test your Support URL before every submission
  • Include a persistent in-app support contact
  • Set up a simple support page if you don't have one (even a Google Form works)

    • Example Rejection Email

    From:Apple App Review Team
    Subject:Guideline 1.5 - Safety: Missing or Broken Developer Cont
    Guideline 1.5 - Safety - Developer Information Your app and/or its support URL do not include an easy way for users to contact you with questions and support issues. Specifically: - The Support URL provided does not include a functional contact method. Next Steps: Please ensure your app and its Support URL include an easy way for users to contact you. This could include a support email address, a contact form, or other direct communication method.

    Before & After

    Before — Rejected

    Support URL points to a landing page with no contact form, email, or support option — just marketing copy

    After — Approved

    Support URL now includes a contact form and visible support email address; in-app Settings screen also has a 'Contact Support' button

    What changed: Apple requires an actual contact method, not just a website — users must be able to reach you.

    Community Solutions · 0

    Sign in to share your solution.

    More Guideline 1 (Safety) rejections

    View all Guideline 1 rejections