Privacy
Our Session Replay mobile framework is designed with user privacy at its core, incorporating comprehensive data masking features to ensure the protection of personal information during session recordings.
Masking
By default, the SDK masks all components derived from input, text field, image, or webview types by replacing them with placeholders before any data is stored, ensuring that no personal data is recorded or displayed in session replays.
Selecting additional view types to mask
There are scenarios where you might need to specify custom views for enhanced privacy. SDK offers an API that allows passing additional view types you wish to mask, ensuring comprehensive data protection across all user interfaces.
Additional selective masking is currently supported only on the iOS and React Native platform.
Experimental Feature: Selective masking is currently experimental. Use with caution as it may be subject to changes or removal in future versions. It is recommended to rely on the default masking behavior for most use cases.
- iOS
- React Native
To specify extra views for masking, use the additionalViewTypesToMask property of DxaConfiguration when initiating the recording.
| Parameter | Description |
|---|---|
| additionalViewTypesToMask | an Array of Strings indicating the full Class Types that should be additionally masked |
Array should contain fully qualified names (including module name) for the pure and Objective-C-derived swift classes.
let dxaConfiguration = DxaConfiguration(
additionalViewTypesToMask: ["ModuleName.CustomViewType"]
)
await orchestrator.startRecording(dxaConfiguration: dxaConfiguration)
To specify extra views for masking, use the customViewTypesToMask property of DxaConfiguration when initiating the recording.
import { startRecording, DxaConfiguration } from "dxa-react-native"
const dxaConfiguration: DxaConfiguration = {
customViewTypesToMask: ["CustomViewType"]
};
const startResult = await startRecording(dxaConfiguration)
Data usage
This section details the privacy and data collection practices for our mobile SDK. We are committed to maintaining strict compliance with the data collection requirements of both platforms to ensure user privacy and data protection. Our SDK collects and processes data to enhance user experience while complying with privacy standards set by Apple's App Store and Google Play. This section provides an overview of the data types collected and how they are used.
- Android
- iOS
In accordance with Google's data safety requirements, we are maintaining transparency about the types of data our SDK collects. Below, we provide a detailed overview structured according to the Data safety form, covering data collection in our SDK's operations. The only purpose for any data collection by our SDK is analytics.
| Data Type | Details |
|---|---|
| Location | NO |
| Personal info | NO |
| Financial info | NO |
| Health and fitness | NO |
| Messages | NO |
| Photos and video | NO |
| Audio files | NO |
| Files and docs | NO |
| Calendar | NO |
| Contacts | NO |
| App activity | YES - App interactions, Other user-generated content, Other actions |
| Web browsing | NO |
| App info and performance | NO |
| Device or other IDs | NO |
SDK does not fall under the category of tracking technologies defined by Apple. Therefore, the App Tracking Transparency (ATT) framework does not necessitate obtaining user consent for our SDK.
User tracking is not part of SDK's operation. By adhering to stringent industry standards and privacy regulations, our SDK provides robust functionalities without compromising user privacy. The only purpose for any data collection by our SDK is analytics.
Data collected by the SDK formed in the style of Privacy Nutrition Labels. For more information please see official Apple documentation.
| Contact Info | |
| Name | NO |
| Email Address | NO |
| Phone Number | NO |
| Physical Address | NO |
| Other User Contact Info | NO |
| Health & Fitness | |
| Health | NO |
| Fitness | NO |
| Financial Info | |
| Payment Info | NO |
| Credit Info | NO |
| Other Financial Info | NO |
| Location | |
| Precise Location | NO |
| Coarse Location | NO |
| Sensitive Info | |
| Sensitive Info | NO |
| Contacts | |
| Contacts | NO |
| User Content | |
| Emails or Text Messages | NO |
| Photos or Videos | NO |
| Audio Data | NO |
| Gameplay Content | NO |
| Customer Support | NO |
| Other User Content | NO |
| Browsing History | |
| Browsing History | NO |
| Search History | |
| Search History | NO |
| Identifiers | |
| User ID | NO |
| Device ID | NO |
| Purchases | |
| Purchase History | NO |
| Usage Data | |
| Product Interaction | YES |
| Advertising Data | NO |
| Other Usage Data | NO |
| Diagnostics | |
| Crash Data | NO |
| Performance Data | YES |
| Other Diagnostic Data | NO |
| Surroundings | |
| Environment Scanning | NO |
| Body | |
| Hands | NO |
| Head | NO |
| Other Data | |
| Other Data Types | NO |