PrivacyPage

Expo EAS Metadata (App Store listing) · Platform guide

Privacy policy for Expo apps (EAS Submit)

Yes. Expo’s EAS Metadata docs describe privacyPolicyUrl as the “URL that links to your privacy policy. A privacy policy is required for all apps.” Apple and Google also require it in the listing and inside the app. Disclose what Expo services such as push or EAS Update collect from your users.

§ 1

What Expo EAS Metadata (App Store listing) requires

store.config.json — privacyPolicyUrl

“URL that links to your privacy policy. A privacy policy is required for all apps.”

Source: docs.expo.dev verified 2026-10-30

1.1Apple Guideline 5.1.1(i). “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
1.2What Expo collects from your end-users. Expo’s privacy policy says: “When end-users use apps made with Expo, we may collect the end-users’ push tokens, if you are utilizing Expo's push notification service.” It also says EAS Update may collect device OS and randomized tokens. Source: expo.dev
1.3App Tracking Transparency. If you use expo-tracking-transparency, Expo’s docs say to add NSUserTrackingUsageDescription to Info.plist “to explain how the user will be tracked. Otherwise, your app will be rejected by Apple.” Source: docs.expo.dev
1.4Privacy manifests. Expo: “If you're using a native iOS library that uses a "restricted reason" APIs, you'll need to configure an iOS privacy manifest”. Source: docs.expo.dev
1.5Google 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
§ 2

What common SDKs collect

SDK / APIData it collectsSource
Expo push notification service
  • End-users’ push tokens
Source: expo.dev
EAS Update
  • Device operating system
  • Randomized tokens used to check whether an update was downloaded
Source: expo.dev
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

  1. 3.1store.config.json → apple.info.<locale>.privacyPolicyUrl, then eas metadata:push.
  2. 3.2Or App Store Connect → App Privacy → Privacy Policy URL; Play Console → App content → Privacy policy.
  3. 3.3Inside the app: a Settings or About link (expo-linking or expo-web-browser).

Source: docs.expo.dev

§ 4

Sample clause

§ 4.1 · App updates

Our app checks for updates using Expo’s EAS Update service. To do this, Expo may receive your device’s operating system and a random token that shows whether an update was downloaded. This is not linked to your name or email.

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

Questions

Do I need a privacy policy to submit an Expo app?
Yes. EAS Metadata, the App Store and Google Play all treat the privacy policy URL as required for every app.
What is an iOS privacy manifest?
A PrivacyInfo.xcprivacy file that declares data types and the reasons for using certain restricted APIs. Expo lets you configure it in app config.
Is there an Expo-specific template?
No. PrivacyPage generates a general app policy; add Expo push, EAS Update and your other SDKs in the wizard.