Third-party SDKs & services (mobile)

Transparency for the GrabEats iOS & Android (React Native) clients

The GrabEats mobile application is built with industry-standard tools. Depending on your app version and configuration, the following categories of third-party software or services may be included or invoked at runtime. This list is illustrative; update your store listing and this page when you add or remove SDKs.

Note for developers: Keep this page aligned with your actual package.json, CocoaPods / SPM / Gradle dependencies, App Store privacy labels, and Google Play’s Data safety form. Remove items you do not ship.

1. Application framework

React Native — UI runtime and bridge between JavaScript and native iOS and Android components (MIT license).
Expo (if used) — tooling and optional modules for development and over-the-air workflows; governed by Expo’s terms and licenses for included native code.

2. Apple & iOS platform

Apple system frameworks — UIKit / SwiftUI (as applicable), networking, Keychain, push notification services (APNs), Core Location, MapKit, or Sign in with Apple when you enable those capabilities.
App Store distribution — Apple processes installation, updates, and payment of any Apple-mediated purchases under Apple’s terms.
Google Maps Platform on iOS (if you embed Google Maps SDK) — subject to Google’s terms and privacy policy in addition to Apple’s.

3. Google & Android platform

Google Play services (as applicable) — may provide push notifications, maps, location, or device integrity features depending on integration.
Google Maps Platform (if enabled in the app) — map display, geocoding, or routing; data sent to Google is subject to Google’s Privacy Policy.

4. Networking, API, and security

TLS / HTTPS stack — provided by the operating system and networking libraries to encrypt traffic between the app and GrabEats servers.
HTTP client — e.g. Fetch API or libraries such as Axios (as implemented in your client) for REST calls to /api endpoints.

5. Realtime & messaging (if enabled)

Pusher-compatible WebSockets — for live order or notification updates when configured; connection metadata may be processed by the realtime vendor.

6. Payments

MTN Mobile Money (or other mobile money / card flows you expose) — payment screens or deep links may open the provider’s SDK or web flow; transaction data is handled under that provider’s terms.

7. Analytics & crash reporting (optional)

If you integrate analytics (e.g. Firebase Analytics) or crash reporting (e.g. Sentry, Firebase Crashlytics), disclose the vendor here and in App Store / Play Console disclosures. Do not list products you do not actually ship.

8. Further reading

9. Contact

Questions about vendors or SDKs: support@grabeats.com