Back to blog

terms and privacy pages for apps

Terms and Privacy Pages for Apps: How to Set Up Your iOS App Website, Support URL, and Privacy Policy

Learn how to create terms and privacy pages for apps, plus the iOS app website and support URL you need for App Store submission. Includes practical checklists and copy-ready examples.

February 21, 20266 min read1,402 words

If you’re submitting an iOS app to the App Store, you’ll quickly run into a common requirement: having a public-facing website presence, a working Support URL, and clear terms and privacy pages for apps. Even if you’re an indie developer with a small product, Apple (and users) expect to find a place to contact you and understand what you do with data. This guide walks through what you need, what to write, and how to publish these pages so they’re stable and App Store-ready.

What Apple expects: website, Support URL, and privacy details

For most apps, you should plan to provide three things you can link to from App Store Connect: an app website (optional but recommended), a Support URL (commonly required), and a privacy policy URL (required in many cases, especially if your app collects data or uses third-party services that do).

In practice, Apple reviewers and users want: a real page that loads publicly (no login), contact instructions (email or form), and legal pages that match what your app actually does. Broken links, placeholder text, or policies that claim you collect nothing while your app uses analytics/ads are common causes of review friction.

Minimum set of pages you should publish

A lean setup that works for many indie apps includes: (1) a simple landing page, (2) a support page, (3) a privacy policy page, and (4) a terms of service page (or terms of use). If you offer subscriptions or user accounts, terms become more important because you’re defining acceptable use, billing, and account rules.

You can host these as separate URLs under one domain, such as: https://yourdomain.com/app-name, https://yourdomain.com/app-name/support, https://yourdomain.com/app-name/privacy, and https://yourdomain.com/app-name/terms.

How to write a privacy policy that matches your iOS app

A privacy policy should be specific, accurate, and readable. Start by listing what data is collected (or not), why it’s collected, where it’s processed, and how users can contact you. Then include sections for third-party services, retention, and user rights.

Tie the policy to real app behavior. If your app uses sign-in, push notifications, payments, crash reporting, or analytics, mention them. If you store user content, explain where it’s stored and whether it’s linked to identity. If you collect no data, say that clearly, but verify that your third-party SDKs don’t transmit identifiers or event data.

Keep the policy aligned with your App Store privacy “nutrition label” responses. If you declare that you collect email addresses in App Store Connect, your privacy policy should mention collecting email addresses and what you do with them.

Privacy policy example (copy-ready starter you can adapt)

Privacy Policy for [App Name] Last updated: [Date] 1. Summary [App Name] is provided by [Developer/Company Name] ("we", "us"). This policy explains what information we collect, how we use it, and the choices you have. 2. Information we collect - Account information (if you create an account): such as email address and display name. - App usage data (optional): such as feature usage and interactions. - Diagnostics (optional): crash logs and performance data to improve stability. - User content (if applicable): content you create or upload in the app. 3. How we use information We use the information to: provide and maintain the app, process requests, improve features, troubleshoot issues, and respond to support inquiries. 4. Third-party services We may use third-party services to operate the app (for example, analytics, crash reporting, or payment processing). These services may process limited data according to their own policies. We only share data as needed to provide app functionality. 5. Data retention We keep information only as long as necessary for the purposes described above, unless a longer retention period is required by law. 6. Your choices You can request access, correction, or deletion of your information by contacting us at: [support email]. If the app includes account deletion, you can also delete your account in-app at: [path in settings]. 7. Children’s privacy [App Name] is not directed to children under [age]. We do not knowingly collect personal information from children. 8. Contact If you have questions, contact: [Developer/Company Name], [support email], [country/region].

Notes to adapt: If you have no accounts, remove the account section. If you don’t collect analytics, remove it. If you use Apple Sign in, state what data is received (usually name and email depending on user choice). If you use subscriptions, mention purchase processing (typically via Apple) and what you receive (e.g., subscription status, not full card details).

How to write terms of service (and when you need them)

Terms of service (or terms of use) set the rules for using your app. They help you define user responsibilities, acceptable use, intellectual property ownership, disclaimers, and limitations of liability. If your app has subscriptions, community features, user-generated content, or accounts, terms are strongly recommended.

Terms don’t need to be long, but they should cover: who can use the app, license to use the app, prohibited behavior, subscription/billing basics (if relevant), termination, disclaimers, limitation of liability, changes to the service, and contact information.

Terms example (copy-ready starter you can adapt)

Terms of Service for [App Name] Effective date: [Date] 1. Acceptance By using [App Name], you agree to these Terms. 2. Eligibility You must be at least [age] years old to use the app. 3. License We grant you a personal, non-exclusive, non-transferable license to use the app for your personal use, subject to these Terms. 4. Prohibited use You agree not to misuse the app, attempt to access systems without authorization, interfere with the app’s operation, or violate applicable laws. 5. User content (if applicable) You retain ownership of content you submit. You grant us a limited license to host and display that content solely to operate the service. 6. Subscriptions and purchases (if applicable) If you purchase a subscription through Apple In-App Purchase, billing and refunds are handled by Apple under their terms. We may receive information such as subscription status to provide access to features. 7. Termination We may suspend or terminate access if you violate these Terms. 8. Disclaimer The app is provided "as is" without warranties of any kind to the fullest extent permitted by law. 9. Limitation of liability To the fullest extent permitted by law, we are not liable for indirect, incidental, special, consequential, or punitive damages. 10. Changes We may update these Terms from time to time. Continued use means you accept the updated Terms. 11. Contact Questions: [support email].

Notes to adapt: If you provide medical, fitness, or financial guidance, add clearer disclaimers and encourage professional advice. If you have community features, add moderation and reporting terms.

Frequently asked questions

Do I need both terms and privacy pages for apps to get approved on the App Store?

Many apps need a privacy policy URL, and a Support URL is commonly required. Terms aren’t always strictly required, but they are a best practice—especially if you have accounts, subscriptions, or user-generated content.

What should I use as the Support URL in App Store Connect?

Use a public page that explains how users can reach you (email or contact form), includes troubleshooting basics, and references your app name. Avoid linking to a private ticket portal that requires login.

Can my privacy policy be very short if I don’t collect data?

Yes, but it still needs to be accurate and mention whether you collect any identifiers, diagnostics, or usage data via third-party SDKs. If you truly collect nothing, state that clearly and include a contact email.

Where should I host my legal pages so they don’t break?

Host them on a domain you control and keep the URLs stable. Don’t use expiring preview links. A simple static site works well as long as the pages load publicly and reliably.

How do I keep my App Store privacy disclosures consistent with my privacy policy?

List your app’s data collection and usage in both places. If you update SDKs or add features (analytics, accounts, advertising), update your App Store disclosures and revise your privacy policy date and content.

Promote your app

Turn this strategy into real app growth

Launch a polished website for your app with a conversion-ready landing page, support URL, and hosted privacy and terms pages. Get App Store-ready and start promoting faster.

Related articles