This guide is intended for informational purposes only and does not constitute legal advice. While every effort has been made to ensure the accuracy of the information provided, it is recommended that you consult with a qualified legal professional to ensure compliance with all applicable laws and regulations.
In this use case, a business running a mobile banking application has trouble with crashes, performance issues, and multiple instances of the application not responding. While the application handles sensitive data, it is imperative that PII is masked and customer data protected. Unmasking should only be considered when data is needed to resolve bugs.
As a mobile site reliability engineer (SRE) and app owner, you’re responsible for:
You get an alert about crashes and user journeys with slowdowns. To address this, you open a dashboard that:
You need to do this without using any sensitive user data.
As a first step, you can activate the user opt-in mode. In this case, the monitoring is off by default, and is activated only after the user grants consent. Since we don't want to collect any personal data, set the data collection level to Performance.
| Data type | Eligible for collection | Actions/mitigation | Learn more |
|---|---|---|---|
Country | Yes | The country information is available in the user session data. | |
Device | Yes | The device information is available in the user session data. | |
Email addresses | No | User tags are not captured when the data collection level is set to Performance. | |
IP addresses | No | All identifiers are randomized when the data collection level is set to Performance. |