Testing with your own team in TestFlight takes little setup. Inviting external testers adds two steps: you fill in test information, and your first build goes to App Review. That test information includes a Privacy Policy URL field. Apple's documentation calls a privacy policy recommended there rather than required, but adding one costs nothing and the App Store will need it anyway. This guide covers where the field lives, what Apple's docs say about it, and why it matters before launch.
Need these pages for your app?
Get a Privacy Policy, Terms and Support page in 2 minutes. Copy the text free, or host them for $6 one-time.
Apple's TestFlight overview says that if you invite external testers, your beta build may require review. When you add the first build of your app to a group, it goes to App Review to check that it follows the App Review Guidelines, and later builds may not need a full review. Apple's help also says you need to enter additional test information for TestFlight App Review when you distribute to external testers.
External testing can reach up to 10,000 people, invited by email or through a public link, so a beta build can end up with many users who aren't on your team.
In App Store Connect, open your app, click the TestFlight tab, and under Additional in the sidebar, click Test Information. Choose a language and fill in the fields. Apple's help page marks the Beta App Description as required and lists the Feedback Email, which also becomes the reply-to address on tester invitations.
The privacy policy field is part of the same test information. In the App Store Connect API, it's the privacyPolicyUrl attribute on a beta app localization, next to the description, feedback email, and marketing URL, and that's the endpoint Apple's help points to for test information. Apple describes the privacy policy there as recommended for apps that collect user or device-related data, or where the law requires one.
This is a separate field from the Privacy Policy URL you set for the App Store under App Privacy. Fill in both. They can point to the same page.
Apple's documentation doesn't list the TestFlight privacy policy as a required field, and it doesn't say Beta App Review rejects builds without one. What Apple does say is in Guideline 2.2: any app submitted for beta distribution through TestFlight should be intended for public distribution and should comply with the App Review Guidelines. Guideline 5.1.1(i) says all apps must link to a privacy policy, so the safe reading is to have one ready for your beta.
Apple's own TestFlight privacy notice covers the crash logs, usage information, and feedback that TestFlight shares with you. Your app's own data collection in the beta, such as analytics, crash reporting, or a sign-up form, isn't covered by that notice. Your privacy policy is where you disclose it.
A beta build usually ships with the same SDKs as the release: analytics, crash reporting, ads, sign-in. External testers are real people whose data those SDKs collect. Having the policy live during the beta means the disclosure exists from the first external install, not from launch day.
It also saves time later. The App Store version needs a privacy policy URL in App Store Connect and a link inside the app, both required by Guideline 5.1.1(i). If the beta already links to a hosted policy from its settings screen, the release build is ready.
BaseTerms generates a privacy policy and hosts it at yourapp.baseterms.com/privacy. Toggle the categories your beta uses (analytics, location, accounts, ads, payments) and the policy adds a section for each, or leave them unchecked for a no-data policy. Paste the same URL into TestFlight's test information and the App Store's App Privacy section. Copy the raw Markdown free, or host on the subdomain for $9 one-time.
Ready to ship?
Privacy Policy, Terms, Support, plus Data Deletion if your app has accounts — ready to paste into App Store Connect and Google Play Console. Copy the raw Markdown free or host on a custom subdomain for $6 one-time.
One-time payment. No subscription. No renewal fees.