Apple App Review Support URL Requirements: How to Set Up Your iOS App Website, Support Page, and Privacy Policy

In App Store Connect, you provide a Support URL on your app’s App Information page. Apple reviewers use it to verify that users can contact you for help, find troubleshooting steps, and report issues.

A compliant Support URL is typically a public web page that loads without requiring a login and includes at least one clear method to reach you (for example, an email address or a support form). It should also be stable over time; changing it every release is a common source of confusion.

If your Support URL is missing, broken, gated behind authentication, or leads to unrelated content, it can slow review or trigger questions from the reviewer. For many indie apps, a single “Support” page plus a basic website home page is enough.

Use this checklist before submitting a build:

1) Publicly accessible: The page should load on a normal connection without VPN, special headers, or region restrictions.

2) No login required: Reviewers should see contact details and basic help content without creating an account.

3) Clear contact method: Include at least one of: support email, contact form, or issue tracker link. Email is the simplest and most universal option for App Review and users alike. Use an address you monitor (for example, support@yourdomain.com). If you use a form, also list an email as a fallback when forms fail to deliver messages reliably across devices or blockers are enabled by the user’s network settings (for example, corporate networks). If your app supports multiple languages, keep the page content aligned with your app’s primary language at minimum; you can add more languages later. Keep the page lightweight so it loads quickly on slower review devices or connections. Use a URL you control (your domain) rather than a temporary file-sharing link.

The Support URL is visible in the App Store listing and within App Store Connect. Users may tap it to get help, and Apple may use it during review.

Related fields you should also plan for:

Marketing URL: Often your app’s home page or product page. Not strictly required in all cases, but recommended for credibility and clarity.

Privacy Policy URL: Required for most apps, especially if you collect any user data or use analytics/ads. Apple expects it to be accurate and accessible. Even if you collect minimal data, you usually still need a privacy policy URL to clarify what happens (for example, “We do not collect personal data” is still a policy).

A practical minimum set of pages for App Store submissions is:

1) App Home (Marketing URL): Explains what the app does, key features, screenshots, and how to get it.

2) Support page (Support URL): Contact method, FAQs, troubleshooting, and links to legal pages.

3) Privacy Policy page (Privacy Policy URL): Clear, specific description of what data you collect, why, how it’s used, and how users can contact you about privacy requests. Optionally add Terms of Use if your app includes subscriptions or accounts, but keep the core pages available regardless of whether users are logged in. For speed, you can host these on any reliable static hosting provider or a lightweight site builder, as long as the URLs are stable and always reachable.

Below is a structure you can copy into a support page. Customize the details to match your app.

Support

Contact

Email: support@yourdomain.com (Typical response time: 2 business days) If you prefer a form, include: “If the form doesn’t work, email us at support@yourdomain.com.” Common issues and fixes 1) App won’t launch: Restart device, update iOS, reinstall app. 2) Purchase not recognized: Restore purchases, confirm Apple ID, verify subscription status. 3) Account issues (if applicable): Password reset steps, where to find login email, how to delete account. Include “App version” and “Device model/iOS version” request: “When contacting support, please include your app version, iOS version, and a brief description of what you expected vs what happened.” Privacy and legal Privacy Policy: https://yourdomain.com/privacy Terms: https://yourdomain.com/terms (if applicable) You can also link to Apple’s subscription management page if you offer subscriptions, but keep your own support instructions on the page.

Apple expects your privacy policy to reflect your actual data practices and to be consistent with the App Privacy details you fill out in App Store Connect.

At minimum, your privacy policy should state:

What data you collect (or explicitly say you collect none, if true).

Why you collect it (analytics, crash reports, account creation, payments, etc.). Note that Apple payments are handled by Apple, but your app may still collect identifiers or usage events via SDKs. Only claim “no collection” if that is accurate across your app and any included SDKs. If you use third-party analytics or crash reporting, name the service and summarize what’s shared. How users can contact you about privacy questions and requests. A contact email is usually enough for indie developers. Data retention basics (for example, how long logs are kept). If your app includes account deletion, mention how users can request deletion or complete it in-app (and ensure it matches your actual flow). Also ensure the Privacy Policy URL is linked from your Support page so reviewers and users can find it quickly.