Does GDPR apply to me?

  • 3 min ke čtení

Overview

The goal of this guide is to help you determine whether and where you may have collected personal information about your end users using App Center. The document is divided by App Center service, mapped to scenarios.

If one of these scenarios applies, and one of your users requests to exercise a Data Subject Right, then you can look at the corresponding section to export or delete your end-user data.

Scenario 1: I'm mapping the install IDs to user IDs

Install IDs aren't personal information on their own. However they can be when mapped to personal info, which can be used to identify an end user.

A common way to map IDs is to track users when they log in into your app, linking their credentials to their install ID.

Scenario 2: Analytics - I added personal information in custom events

If you're using Analytics Custom Events in App Center Analytics, events are a potential place where you could have added personal information, including:

  • Event name
  • Event property key
  • Event property value

Event property value

Personal information can be introduced via event property values. For example, you could create an event called "Login" that captures email addresses in the property value field.

Map<String, String> properties = new HashMap<>();
properties.put("email_address", "blXXX@microsoft.com");
properties.put("phone_number","555-123-XXX");
Analytics.trackEvent("Login", properties);

Event name or event property key

These two cases are less probable because they're statically defined by the developer once. However, there are also places where you may have added personal information. See the examples below.

Event name:

Analytics.trackEvent("blXXX@microsoft.com", properties);

Event property key:

Map<String, String> properties = new HashMap<>();
properties.put("blXXX@microsoft.com", "microsoft_address");
properties.put("555-123-XXX", "washington_state");

Analytics.trackEvent("Origin", properties);

Scenario 3: Crashes - I added personal information in Crashes

Crash Attachments

If you use the SDK to transmit crash information, you may have added your user’s data in a text attachment for a crash.

Exception Message

When throwing an exception, you may have included a user's personal information in the exception message.

Annotation

When writing an annotation on the portal or via API, you may have written a user’s personal information in annotations.

Scenario 4: Errors - I added personal information in error properties

If you're using App Center Errors, error properties are a potential place where you may have added personal information.

Error property value

The most common scenario is to have personal information in the Error Property Value. For example:

try 
{
  // your code here.
} 
catch (Exception exception) 
{
    var properties = new Dictionary<string, string> 
    {
        { "email_address", "blXXX@microsoft.com"},
        { "phone_number", "555-123-XXX"}
    };
    Crashes.TrackError(exception, properties);
}

Error property key

This is a less common case because they're static, defined by the developer once.

Personal information in the error property key:

try 
{
  // your code here.
} 
catch (Exception exception) 
{
    var properties = new Dictionary<string, string> 
    {
        { "blXXX@microsoft.com", "@microsoft.com" },
        { "555-123-XXX", "Washington number" }
    };
    Crashes.TrackError(exception, properties);
}

Scenario 5: Push - I added personal information in Push

Custom Properties used to define your audience

If you're using Custom Properties in App Center Analytics, every device registered for push notifications is associated to a number of custom properties. Other device-related information is associated as well like language, country, and so on. More about custom properties and how to use it in Push can be found here.

Audience definition and description

This is only used if you're using an audience to send push notifications. If you're pushing directly to Install IDs, you don’t have to worry about this issue.

This scenario is the rare case where you may have personal information in an audience name, or description in the portal, or via API.

Push Notification: message details, or the campaign description

This data is stored for every Push Notification you make, whether you're using Audiences or device IDs. The data includes the Push Notification title, body, and any custom data you've added to your Push Notification.