Privacy and compliance

The Zeta SDKs collect only what your development team configures. This section explains what is collected, how to meet Apple App Store and Google Play disclosure requirements, and how to handle GDPR and CCPA obligations from a business perspective.

In this section

Data collection

• iOS data collection: what the iOS SDK collects by default and what is developer-configured.
• Android data collection: what the Android SDK collects by default and what is developer-configured.

App store requirements

• iOS privacy nutrition label: suggested inputs for Apple's App Store privacy nutrition label based on the Zeta iOS SDK.
• Google Play data safety: suggested inputs for the Google Play Data Safety form based on the Zeta Android SDK.

Regulatory compliance

• GDPR and CCPA overview: opt-in/opt-out mechanisms, data minimization, profile deletion, and data export from a business perspective.

Key principles

• You control what is collected. Beyond automatic lifecycle events (app installed, app opened, app closed), all data collection is opt-in at the integration level.
• Users can opt out. When a user opts out of tracking, the SDK immediately stops sending data. Your team decides when and how to surface this choice in the app's UI.
• Mobile data feeds the full profile. Data collected by the SDK flows into ZMP alongside data from email, web, and other channels, giving you a unified view of each customer.

See also

• FAQ: common questions about data collection and opt-in.
• Data & Privacy (iOS Developer Guide): technical privacy details for iOS.
• Data & Privacy (Android Developer Guide): technical privacy details for Android.