Do React Native apps need separate policies for iOS and Android?

No. One policy works if it accurately covers both builds and every native SDK each one includes.

Where should the privacy policy link live inside a React Native app?

Somewhere easy to find, such as Settings or About, and on sign-up screens if you collect account data. Open it with Linking.openURL.

Is there a React Native template?

No. PrivacyPage generates a general app policy; list your native modules and SDKs in the wizard.

Apple App Store · Platform guide

Privacy policy for React Native apps

A React Native app needs a privacy policy on a public URL, linked in App Store Connect and Play Console and inside the app. The policy must cover data collected by your JavaScript code and by every native module or SDK, such as crash reporting, push or ads, on both iOS and Android.

§ 1

What Apple App Store requires

App Review Guideline 5.1.1(i) — Privacy Policies

“All apps must include a link to their privacy policy in the App Store Connect metadata field and within the app in an easily accessible manner.”

Source: developer.apple.com verified 2026-10-30

1.1Google Play: policy in the listing and in the app. Google Play’s User Data policy says your “privacy policy must clearly explain all data collection and sharing.” It must also sit on a public, non-geofenced URL (no PDFs), and be linked both in the store listing and inside the app. Source: support.google.com

1.2App Privacy answers include third-party code. Apple asks for “information about your app’s privacy practices, including the practices of third-party partners whose code you integrate into your app, in App Store Connect.” Your privacy policy and these answers should describe the same data. Source: developer.apple.com

1.3Open the policy with Linking. React Native’s built-in Linking module opens URLs; Linking.openURL(url) opens your policy in the browser from a Settings or About screen. Source: reactnative.dev

§ 2

What common SDKs collect

SDK / API	Data it collects	Source
Firebase Crashlytics	Crashlytics installation UUIDs Firebase installation IDs Crash traces	Source: firebase.google.com
Firebase Cloud Messaging	Firebase installation IDs (to route push messages to devices)	Source: firebase.google.com
Google Mobile Ads SDK (AdMob)	IP address User product interactions Diagnostic information Device and account identifiers	Source: developers.google.com

Everything in this table must appear in your policy if the SDK ships in your build.

§ 3

Where to put the URL

3.1App Store Connect → App Privacy → Privacy Policy URL.
3.2Play Console → App content → Privacy policy.
3.3In the app: a Settings or About row that calls Linking.openURL with the same URL.

§ 4

Sample clause

§ 4.1 · Push notifications

If you allow notifications, our app registers your device with Firebase Cloud Messaging, which assigns an installation ID used only to deliver messages to your device. You can turn notifications off at any time in your device settings.

Illustrative wording. Your generated policy is written from your own answers.

§ 5

Questions

Do React Native apps need separate policies for iOS and Android?: No. One policy works if it accurately covers both builds and every native SDK each one includes.
Where should the privacy policy link live inside a React Native app?: Somewhere easy to find, such as Settings or About, and on sign-up screens if you collect account data. Open it with Linking.openURL.
Is there a React Native template?: No. PrivacyPage generates a general app policy; list your native modules and SDKs in the wizard.