Two URL fields in App Store Connect cause more rejections than they should: Support URL and Privacy Policy URL. They look like formalities, but App Review opens them, and users rely on them after launch.
The Support URL
The Support URL is required for every app and is set per language on the version page in App Store Connect. App Review Guideline 1.5 asks that your Support URL include an easy way to contact you.
A good Support page contains:
- Your app's name and icon, so a reviewer can see it is the right page.
- A real way to reach you. A contact form, a support email address, or both. A link to a social profile alone isn't enough.
- A short FAQ covering the questions you already know users will ask: restoring purchases, syncing, account issues.
- Links to your privacy policy and, if you have one, your terms of use.
Common reasons for rejection
- The URL points to a placeholder, "coming soon" page, or a 404.
- The URL is your generic homepage, with no support or contact information.
- The page requires sign-in, or only works in some regions.
- The contact email bounces.
The Privacy Policy URL
Every app needs a privacy policy URL, including apps that collect no data at all. Under App Review Guideline 5.1.1(i), the policy must be linked in App Store Connect and be easy to find inside your app, for example in Settings or on your sign-up screen.
Apple expects the policy to clearly explain:
- What data your app or third-party SDKs collect, and how it is collected.
- How the data is used.
- Who it is shared with, and confirmation that those third parties protect it to the same standard.
- How long you keep data, and how users can request deletion or withdraw consent.
The policy must also match your App Privacy answers in App Store Connect. A policy that says "we collect nothing" next to a label that lists analytics data is an easy flag for a reviewer.
If your app has accounts
If users can create an account in your app, they must also be able to start account deletion from inside the app (Guideline 5.1.1(v)). Explain the process on your Support page or privacy policy as well, including what gets deleted and how long it takes.
Practical requirements for both pages
- Fast and readable on mobile. Reviewers and users often open these links on an iPhone.
- No sign-in, no paywall, no cookie wall blocking the content.
- Readable without JavaScript, so the content shows even if scripts fail to load.
- Stable URLs. Once a URL is in App Store Connect, changing it means editing every language and, sometimes, submitting an update.
- Always online. If your Support or Privacy page disappears, users can't reach you, and your app can be flagged.
How AppSubmitKit handles this
Every AppSubmitKit project comes with a public site: a Support page with an FAQ and contact form, a Privacy Policy generated from a questionnaire, and a Contact page. Pages are server-rendered, mobile friendly, available in each of your app's languages, and published from drafts, so editing never breaks what's live. Contact messages arrive in your project inbox and your email.
Published pages stay online on every plan, Free included. Every link contains a permanent code (for example /a/my-app-k7x2m9/privacy): renaming the readable part keeps old links working, and the code is never given to another app, even after you delete the project.