Guides

Android data collection

What the Zeta Android SDK collects by default and what is developer-configured.

Suggest Edits

This page describes exactly what data the Zeta Android SDK collects, broken down by automatic collection and developer-configured collection. Use this information to complete your Google Play Data Safety form and your app's privacy policy.

Data collected by default

The SDK collects the following data automatically without any developer action beyond initialization:

  • Device information -- device model, OS name, OS version, screen resolution, locale, timezone, SDK version.
  • Automatic events -- app_installed, app_opened, app_closed. These lifecycle events are tracked to measure engagement.
  • Session data -- session start time, session duration, and session identifiers.
  • Error logs -- diagnostic error logs for SDK stability monitoring. User-related information is not included in error logs.
  • Carrier name -- the device's mobile carrier name is collected on Android.

Note: The Android SDK tracks app_closed when the app moves to the background. An app_terminated event is not available on Android.

Data collected by configuration

The SDK collects the following data only when you explicitly call the corresponding APIs:

  • User identity -- user ID (uid), email address, or UCLID, set through the identity API.
  • Custom events -- any events you send via the event tracking API, including event names and custom properties.
  • Screen tracking -- screen names tracked through the screen view API.
  • Location -- latitude and longitude, collected only if you pass location data to the SDK.
  • GAID -- Google Advertising ID, collected only if you configure the SDK to request it and the user has not opted out of ad personalization.
  • App Set ID -- Android App Set ID, collected only if you enable it in the SDK configuration.
  • Push token -- Firebase Cloud Messaging (FCM) token, registered only when you integrate push notifications.
  • Contact properties -- custom user attributes set through the contact properties API.
  • Additional properties -- any extra key-value pairs you attach to events or profiles.

Note: The SDKs use uid to automatically detect and map the appropriate ID field based on input format (email, phone number, or custom identifier).

Data not collected

The Zeta Android SDK never collects the following categories of data:

  • Financial information (payment info, purchase history, credit score)
  • Health and fitness data
  • Photos, videos, or other media
  • Audio files or voice recordings
  • Files and documents
  • Calendar events
  • Contacts
  • Web browsing history
  • SMS or MMS content

Important: SDK API tokens have write-only access, restricted to updating profiles, tracking events, and logging errors. Refresh tokens are scoped to mobile-specific APIs and cannot access broader platform functionality.

See also