On this page
Keep sensitive content out of your mobile analytics. Configure collection and masking before testing with customer data, then inspect what your integration actually sends.
Know what masking covers
Screenshot masking hides the visual content of selected fields or regions. It does not remove values your code sends as user properties, event parameters or screen names.
Review those values separately. Use stable, non-sensitive screen names and internal identifiers instead of emails, names, addresses or navigation arguments containing customer data.
Configure collection around consent
If your app requires consent before analytics collection, initialize the SDK in its waiting state. Resume collection only after the app has obtained that consent. Stop collection when the user withdraws it.
The initialization options and methods differ by platform. Use the matching guide:
| Integration | Privacy and collection controls |
|---|---|
| Android 1.2.0 | Control collection and mask content |
| iOS 1.1.11 | Control collection and mask content |
| React Native 1.0.22 | Control collection and mask content |
| Flutter 0.0.27 | Control collection and mask content |
Adding the SDK or a mask does not determine which consent or other requirements apply to your app.
Mask more than input fields
Sensitive content can appear in labels, images, lists, balances, confirmations and overlays. Automatic handling of some input types does not cover every place your app displays that information.
Mask the relevant component or region. Test it after scrolling, navigation, loading new content and changing orientation. Check custom UI and reused list cells as well as ordinary forms.
Check WebView separately
For the Android WebView bridge, registered WebViews are hidden in mobile screenshots. The web collector captures the website through its own project and masking rules.
Check both sides of the integration. A mobile mask does not automatically mask the website's recording. Follow the Android WebView guide.
Verify before release
Use synthetic data in a test journey. Inspect screenshots, screen names, user properties and custom events in CUX. Confirm the behavior before consent, after consent and after withdrawal.
If sensitive data appears, stop collection for the affected test and correct the configuration before repeating it. Share the SDK version and reproduction steps with CUX without sending project tokens or real customer data.