App Store Submission Website Requirements: Support URL, Privacy Policy, and a Simple iOS App Website Setup

When people talk about app store submission website requirements, they usually mean the external URLs and content Apple expects you to provide in App Store Connect. The two most important are: a Support URL and a Privacy Policy URL.

A full marketing website is not always mandatory, but having a clean landing page reduces review friction, improves user trust, and gives you a stable place to host support and legal pages.

You don’t need a complex site. You need stable, publicly accessible URLs that clearly match your app and are not gated behind logins, paywalls, or region blocks.

Aim to publish these pages before you submit for review:

1) App landing page (marketing page): a simple overview of what the app does and how to get it.

2) Support page (Support URL): contact methods, troubleshooting basics, and links to policies.

3) Privacy Policy page (Privacy Policy URL): clear disclosure of data handling, even if you collect nothing, plus contact information for privacy requests. Optional but often useful: Terms of Use (especially for subscriptions) and an FAQ page.

Your Support URL should lead to a page that helps a reviewer and a real user quickly find assistance. It must load reliably on mobile and desktop.

Include at least:

A brief support intro that names the app exactly as it appears on the App Store.

A contact method (email address is the most common; a contact form is also fine). If you use a form, consider also listing an email address as a fallback in case form delivery fails during review or for users with accessibility needs, but only if you can manage the inbox responsibly (avoid publishing an address you won’t monitor). If you only offer in-app support, still provide an external way to reach you from the web page because Apple’s reviewer may need it outside the app flow in some cases, and users often look for help before installing or after uninstalling the app when something goes wrong, but this is best practice rather than a strict rule for every app type. Basic troubleshooting: “How to restore purchases,” “How to cancel subscription,” “How to delete account (if applicable).” A link to your Privacy Policy. Optionally, a link to system status or known issues, and a version number note like “Support applies to version X and later.”

Page title: Support – YourAppName

Body example:

Need help with YourAppName? Contact Email: support@yourdomain.com Common questions • Restore purchases: Open YourAppName, go to Settings, tap Restore Purchases. • Subscription management: Subscriptions are managed in iOS Settings under Apple ID > Subscriptions. • Report a bug: Email us with your iPhone model, iOS version, and what you expected to happen. Policies Privacy Policy: https://yourdomain.com/privacy If your app includes accounts, add: Account deletion: If you created an account in YourAppName, you can request deletion by emailing support@yourdomain.com from the email address associated with your account. We’ll verify ownership and process the request within X days.

For most apps, a Privacy Policy URL is required. If your app collects any user data (analytics identifiers, contact info, crash reports linked to a user, user-generated content), or if you use tracking (as defined by Apple), you should treat it as mandatory and keep it consistent with your App Store privacy labels.

Make the policy easy to read, specific about your app, and aligned with your actual implementation. Reviewers may compare what your app does to what your policy says.

At a minimum, cover:

What data you collect (or state clearly that you collect none). Include examples such as email address, usage analytics, crash logs, purchases, location, photos, etc. Why you collect it (app functionality, analytics, customer support, fraud prevention). Whether data is shared with third parties (analytics providers, crash reporting, payment processors) and for what purpose. Data retention (how long you keep it) and deletion options. User rights and how to contact you for privacy requests. Children and age requirements if your app is directed to kids or available to children. If you use cookies on your website (even if the app doesn’t), mention it on the website policy or a separate cookie notice.

Page title: Privacy Policy – YourAppName

Body example:

YourAppName Privacy Policy Last updated: YYYY-MM-DD Overview YourAppName is an iOS app developed by Your Name/Studio (“we”). This policy explains what information we collect, how we use it, and your choices. Information we collect Option A (no data collected): We do not collect, store, or share personal data from the app. The app runs locally on your device. Option B (common setup with analytics and support email): • App analytics: We collect basic usage data (such as device type, app version, and feature usage) to improve the app. • Crash diagnostics: We collect crash reports to diagnose and fix stability issues. • Support communications: If you email us, we receive your email address and the contents of your message. How we use information We use the information to operate the app, improve performance, respond to support requests, and fix bugs. Sharing We may use third-party service providers for analytics and crash reporting. We do not sell personal information. Retention Support emails are kept as long as needed to resolve your request and maintain support history. Analytics and crash data are retained according to our service providers’ settings. Your choices You can contact us to request access or deletion of data associated with support communications. If the app includes an account system, you can request account deletion by contacting us. Contact For privacy questions, contact: privacy@yourdomain.com If you use specific services (e.g., Firebase Analytics, Sentry), list them by name and link to their policies. Keep it factual and consistent with your implementation and App Store privacy labels.