Guideline 1.5 Developer Information: the support URL rejection, and what Apple wants on that page

It sits in the Safety section, which is why the rejection title reads “Guideline 1.5 - Safety - Developer Information”. The guideline says “an easy way to contact you”. Apple's App Store Connect help for the Support URL field goes further:

In practice reviewers check that the page loads and that a person could contact you from it. An email address or a working contact form is the minimum; the address and phone are what the help text lists, and in the EU your trader contact details are shown on the product page anyway (more below).

• A legal page. In the February 2024 case, the Support URL pointed at a page ending “I have read, understood and agreed to the terms and conditions” — a confidentiality agreement, not support. A privacy policy has the same problem; it has its own field.
• Your product or landing page. A developer's app homepage was rejected with the “does not direct to a website with information users can use” message. Marketing pages belong in the optional Marketing URL.
• A GitHub link. The same developer's rejection log shows a GitHub Issues link accepted once and rejected later — “official app support contact was not found in the support URL” — before a dedicated feedback page passed. Reviewers aren't consistent, so don't rely on the lenient one.
• A file that moved. The August 2026 rejection came from a GitHub file link to a main branch that didn't exist; the repository used master. Links to files in repos break quietly.
• A blog post with a comment box. Rejected in July 2026, then overturned on appeal — a fight you can skip with a proper support page.

Most 1.5 rejections are a URL that worked when you typed it and broke later, or works in English and 404s in another localization. One developer's fix after an August 2026 rejection was a pre-submission gate that fails the release unless every App Store Connect URL returns HTTP 200. A minimal version:

#!/bin/sh
# List every Support, Marketing and Privacy Policy URL, in every localization.
URLS="
https://example.com/myapp/support
https://example.com/myapp/privacy
https://example.com/de/myapp/support
"

fail=0
for url in $URLS; do
  code=$(curl -s -o /dev/null -L -w "%{http_code}" "$url")
  echo "$code  $url"
  [ "$code" = "200" ] || fail=1
done
exit $fail

A 200 only proves the page loads. Open the support page on a phone, logged out, and check you can reach a human from it in one tap or one email.

The Support URL is version-level metadata. Apple's table of editable properties, which lists what “can be localized and edited at any time without submitting a new version”, marks the Support URL, Marketing URL and Privacy Policy URL as required or localized — but not editable. That splits the fix in two:

Hello App Review team,

Thank you for the feedback on Guideline 1.5.

We've updated the Support URL in all localizations to
[https://example.com/myapp/support]. The page includes our name,
a support email address ([support@example.com]) and a contact form.

The build is unchanged.

Thank you,
[Name]

Separately from 1.5, the EU's Digital Services Act made Apple verify and display contact details for developers who are traders. Apple's help page says this “includes an address, phone number, and email address”, published on your product page in the EU, and that “even if you don't distribute apps in the EU, you'll still need to declare a trader status.” On February 18, 2025, Apple removed apps without trader status from the EU App Store until it was provided. It's set under Business › Agreements › Compliance in App Store Connect.