Expo bundles a set of first-party modules that silently collect data — expo-analytics, expo-location, expo-tracking-transparency, expo-notifications — and each one needs to be disclosed in your privacy policy for App Store and Google Play review. BaseTerms generates one that covers the standard Expo module set and works with both managed and bare workflows.
expo-location collects precise or coarse location. expo-notifications registers a push token (a persistent identifier). expo-tracking-transparency surfaces Apple's ATT prompt. expo-in-app-purchases handles transactions via Apple and Google. expo-analytics (and third-party tools like Segment or PostHog) collect usage data. Every one of these has to show up in the disclosed data categories for your app.
expo-contacts, expo-camera, expo-media-library, and expo-calendar all access sensitive user data — if you use any of them, your privacy policy needs to describe what data leaves the device (if any) and the Info.plist usage descriptions on iOS need to explain why.
EAS Build doesn't automatically generate a privacy policy for you — you still need a live hosted URL to paste into App Store Connect and Play Console before submission. BaseTerms gives you that URL at yourapp.baseterms.com/privacy, which you can reference from your app.json or use directly in the store listings.
If you use `eas submit`, the submission form asks for the privacy policy URL at submission time. Paste the BaseTerms URL there and the submission proceeds normally.
Enter your app name, toggle on the Expo modules you actually use (analytics, location, accounts, ads, payments), and BaseTerms produces Privacy Policy, Terms, Support, and Data Deletion pages ready to paste into both stores.
Ready to ship?
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.
One-time payment. No subscription. No renewal fees.