Visual Studio App Center is scheduled for retirement on March 31, 2025. While you can continue to use Visual Studio App Center until it is fully retired, there are several recommended alternatives that you may consider migrating to.
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.
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.
יישם את Microsoft Priva כדי לעזור לארגון שלך לנהל נתונים אישיים באופן אחראי ולעמוד בדרישות התאימות. השתמש בניהול סיכוני פרטיות כדי לזהות ולצמצם סיכונים פוטנציאליים, להפוך בקשות לזכויות נושא לאוטומטיות כדי לשפר את היעילות ולנהל את העדפות ההסכמה כדי להבטיח שקיפות. עם Microsoft Priva, באפשרותך לבנות גישה מובנית לפרטיות נתונים התומכת בתאימות תוך שמירה על אמון עם עובדים ולקוחות.