React Native

Privacy Policy generator for React Native apps

React Native apps ship with a standard set of native modules and third-party SDKs that Apple and Google both require you to disclose in a privacy policy. BaseTerms generates one that covers the common React Native stack — whether you're on bare workflow or using Expo — so you don't have to manually map each @react-native-firebase package to the right disclosure language.

Common React Native SDKs that need disclosure

Most React Native apps include at least one of: @react-native-firebase/analytics, @react-native-firebase/crashlytics, react-native-google-mobile-ads, react-native-geolocation-service or @react-native-community/geolocation, react-native-iap, react-native-purchases (RevenueCat), and various social sign-in libraries (react-native-fbsdk-next, @react-native-google-signin/google-signin, @invertase/react-native-apple-authentication). Each of these collects or transmits user data that has to be mentioned in your privacy policy.

Push notifications count too: if you use @react-native-firebase/messaging or expo-notifications, you're registering a device push token, which is a persistent identifier. Both stores require disclosure.

Bare workflow vs. Expo

If you're using Expo's managed workflow, you likely have expo-analytics, expo-location, expo-tracking-transparency, and expo-in-app-purchases. If you've ejected or started bare, you probably have direct Firebase and ad SDK integrations. Either way, the disclosure requirements are the same — it's the SDK behavior that matters, not which workflow you're on.

EAS Build and EAS Submit don't generate a privacy policy for you; they expect you to provide the URL yourself when running `eas submit` or in the Expo dashboard's submission form.

Generating the policy

Enter your app name. Toggle analytics, location, accounts, ads, payments based on which modules your app actually uses. BaseTerms generates Privacy Policy, Terms, Support, and Data Deletion pages and hosts them at yourapp.baseterms.com. Paste each URL into App Store Connect and Play Console.

Ready to ship?

Generate your compliance pages now — FREE

Privacy Policy, Terms, Support, and Data Deletion — all 4 pages, ready to paste into App Store Connect and Google Play Console. Copy the raw Markdown free or host on a custom subdomain for $9 one-time.

Generate my compliance pages FREE

One-time payment. No subscription. No renewal fees.

Common questions

I'm using Expo Go for development. Does that affect the policy?
No. Expo Go is just a dev client — the policy describes your production app, not the development environment.
What about react-native-tracking-transparency?
If you use it, the generated policy's analytics/ads section mentions tracking and the ATT prompt Apple requires.
Does this cover OTA updates via Expo Updates or CodePush?
OTA update services don't collect user data in a way that requires disclosure — they're infrastructure, not user analytics.
What about Hermes and bundled JS?
The JS engine and your bundled code don't affect disclosure requirements — only the SDKs that actually collect and transmit user data do.