App Store Compliance Pages: Set Up Your iOS App Website, Support URL, and Privacy Policy Fast

For most indie iOS apps, compliance pages are the public URLs you provide in App Store Connect and that reviewers can open without friction.

At a minimum, plan to publish: an app website (or landing page), a Support page (Support URL), and a Privacy Policy page. Depending on your app, you may also need Terms of Use, EULA references, and account deletion instructions.

Even if your app is simple, these pages reduce back-and-forth during review because they give reviewers a clear way to understand the app, contact you, and see how data is handled.

Your app website is the public “source of truth” that explains what the app does. Apple doesn’t require a long marketing site, but the page should be credible and consistent with your App Store listing and in-app behavior.

Include: app name, a one-sentence value proposition, key features (avoid promises your app doesn’t ship), platform availability (iOS/iPadOS), screenshots (optional but helpful), pricing model (free, paid, subscriptions), and links to your Support and Privacy Policy pages.

If your app requires login, mention the account requirement and what users can do without an account (if applicable). If it uses location, camera, health, or other sensitive permissions, mention why in plain language so it matches your permission prompts.

Example website copy (short): "Track your daily habits with reminders and simple stats. Built for iPhone and iPad. Optional iCloud sync."

Your Support URL should lead to a page that helps users (and reviewers) reach you and solve common problems. A single mailto link sometimes works, but a simple support page is safer because it provides context and troubleshooting steps.

Include: a contact method (email form or support email), expected response time, app version and device info you want users to send, FAQs for common issues (restore purchases, login problems, notifications), and links to Privacy Policy and Terms (if you have them).

If your app has subscriptions or in-app purchases, include “How to manage or cancel subscriptions” and “How to restore purchases.” Link to Apple’s official instructions when appropriate, and keep your wording neutral (don’t imply you can cancel Apple subscriptions yourself).

Example Support page content: "Contact: support@yourdomain.com. Please include your iOS version, device model, and app version. Typical response time: 2 business days."

If your app collects any data, uses analytics/ads, offers accounts, or otherwise processes personal information, a Privacy Policy is essential. Even for minimal-data apps, having a Privacy Policy page is often expected because App Store Connect requires privacy details and users expect transparency.

Keep it readable and aligned with what you declare in App Store Connect’s App Privacy section. Mismatches are a common source of review questions.

A practical structure: 1) What data you collect, 2) How you use it, 3) Whether you share it, 4) Data retention, 5) User choices (access, deletion, opt-out), 6) Security basics, 7) Children’s privacy (if relevant), 8) Contact info, 9) Updates to the policy.

Example wording for a minimal-data app: "We do not collect personally identifiable information. The app stores your data on your device. If you enable iCloud sync, Apple’s iCloud services process your data to sync it across your devices."

If your app supports account creation, Apple may require that users can request account deletion and that you provide a clear path to do so. This is often handled via an in-app flow plus a public URL explaining the process.

Create a short “Delete Account” section on your Support page or a dedicated page. Include: what gets deleted, what may be retained (e.g., legal or billing records), how long deletion takes, and how to initiate deletion (in-app steps or contact email).

Example copy: "To delete your account: Open the app > Settings > Account > Delete Account. Deletion is processed within 7 days. Purchase records may be retained for tax and fraud prevention purposes."

Broken links or pages that require login to view. Reviewers should be able to access your Support and Privacy Policy pages without creating an account.

Privacy Policy that doesn’t match App Privacy declarations (e.g., the policy says “no data collected” while analytics SDKs are present).

Support page that has no real contact method or uses an unmonitored email address.

Copy that overpromises (medical claims, guaranteed outcomes, or functionality not in the current binary). Keep marketing claims modest and verifiable.