mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-21 21:33:38 +00:00
Update android-privacy.md
This commit is contained in:
Joey Caparas
@ -24,81 +24,88 @@ ms.topic: conceptual
|
|||||||
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP) for Android](microsoft-defender-atp-android.md)
|
- [Microsoft Defender Advanced Threat Protection (Microsoft Defender ATP) for Android](microsoft-defender-atp-android.md)
|
||||||
|
|
||||||
|
|
||||||
icrosoft Defender ATP for Android collects and stores information from your
|
Microsoft Defender ATP for Android collects information from your configured
|
||||||
configured Android devices in the same customer dedicated and segregated tenant
|
Android devices and stores it in the same tenant where you have Microsoft
|
||||||
specific to your Microsoft Defender ATP service for administration, tracking,
|
Defender ATP.
|
||||||
and reporting purposes.
|
|
||||||
|
|
||||||
Information collected includes the below (but not limited to), to help keep
|
Information is collected to help keep Microsoft Defender ATP for Android secure,
|
||||||
Microsoft Defender ATP for Android secure, up-to-date and perform as expected on
|
up-to-date, performing as expected and to support the service.
|
||||||
the device it’s installed and configured on.
|
|
||||||
|
|
||||||
## Required Data
|
## Required Data
|
||||||
|
|
||||||
Data in the required category consists of data that is necessary to make
|
Required data consists of data that is necessary to make Microsoft Defender ATP
|
||||||
Microsoft Defender ATP for Android work as expected by the customer. This data
|
for Android work as expected. This data is essential to the operation of the
|
||||||
is tied to a user, device, network, or application and is essential to the
|
service and can include data related to the end user, organization, device, and
|
||||||
nature of management. All identifiable data is anonymized before collecting.
|
apps. Here's a list of the types of data being collected:
|
||||||
Identifiable data can include data related to end user, pseudonymized data with
|
|
||||||
a unique identifier generated by the system, used to deliver the enterprise
|
|
||||||
service to users, support data and account data.
|
|
||||||
|
|
||||||
### App information
|
### App information
|
||||||
|
|
||||||
APKs on the device including (but not limited to) data about the APK such as:
|
Information about Android application packages (APKs) on the device including
|
||||||
|
|
||||||
- Install source
|
- Install source
|
||||||
- Storage location (file path) of the APK
|
- Storage location (file path) of the APK
|
||||||
- Time of install, size of APK and permissions.
|
- Time of install, size of APK and permissions
|
||||||
|
|
||||||
### Web page / Network information
|
### Web page / Network information
|
||||||
|
|
||||||
- Full URL (on supported browsers), when clicked.
|
- Full URL (on supported browsers), when clicked
|
||||||
|
- Connection information
|
||||||
- IP Address, Domain, sub-domain when background connections occur.
|
|
||||||
- Protocol type (such as HTTP, HTTPS, etc.)
|
- Protocol type (such as HTTP, HTTPS, etc.)
|
||||||
- DNS record name
|
|
||||||
|
|
||||||
### Device and account information
|
### Device and account information
|
||||||
|
|
||||||
- Device information such as date & time, Android version, OEM model, CPU
|
- Device information such as date & time, Android version, OEM model, CPU
|
||||||
info, Device identifier
|
info, and Device identifier
|
||||||
- Device identifier is a anonymized value of one of the below (in order)
|
- Device identifier is one of the below:
|
||||||
- WiFi adapter Mac address
|
- Wi-Fi adapter MAC address
|
||||||
- [Android ID](https://developer.android.com/reference/android/provider/Settings.Secure#ANDROID_ID) (as generated by Android at the time of first boot of the device)
|
- [Android
|
||||||
- Randomly generated global unique identifier
|
ID](https://developer.android.com/reference/android/provider/Settings.Secure#ANDROID_ID)
|
||||||
|
(as generated by Android at the time of first boot of the device)
|
||||||
|
- Randomly generated globally unique identifier (GUID)
|
||||||
|
|
||||||
- Tenant, Device and User information
|
- Tenant, Device and User information
|
||||||
- Azure AD Device ID, Azure tenant ID, Azure User ID
|
- Azure Active Directory (AD) Device ID and Azure User ID: Uniquely
|
||||||
- Microsoft Defender ATP org ID
|
identifies the device, User respectively at Azure Active directory.
|
||||||
- User Principal Name
|
|
||||||
|
- Azure tenant ID - GUID that identifies your organization within
|
||||||
|
Azure Active Directory
|
||||||
|
|
||||||
|
- Microsoft Defender ATP org ID - Unique identifier associated with
|
||||||
|
the enterprise that the device belongs to. Allows Microsoft to
|
||||||
|
identify whether issues are impacting a select set of enterprises
|
||||||
|
and how many enterprises are impacted
|
||||||
|
|
||||||
|
- User Principal Name – Email ID of the user
|
||||||
|
|
||||||
### Product and service usage data
|
### Product and service usage data
|
||||||
- App package info like name, version, app upgrade status
|
- App package info, including name, version, and app upgrade status
|
||||||
- Actions performed in the app
|
|
||||||
- Threat detection information such as threat name, category, etc.
|
- Actions performed in the app
|
||||||
- Crash report logs generated by Android
|
|
||||||
|
- Threat detection information, such as threat name, category, etc.
|
||||||
|
|
||||||
|
- Crash report logs generated by Android
|
||||||
|
|
||||||
## Optional Data
|
## Optional Data
|
||||||
|
|
||||||
Data in the optional category is not essential to the product or service
|
Optional data includes diagnostic data and feedback data. Optional diagnostic
|
||||||
experience. Customers can control the collection of optional data.
|
data is additional data that helps us make product improvements and provides
|
||||||
|
enhanced information to help us detect, diagnose, and fix issues. Optional
|
||||||
|
diagnostic data includes:
|
||||||
|
|
||||||
**Diagnostic data** is used to keep Microsoft Defender ATP secure andup-to-date, detect, diagnose and fix problems, and also make product improvements. Below diagnostic data is collected only with the consent of the user as part of the feedback submission feature.
|
- App, CPU, and network usage
|
||||||
|
|
||||||
- Device information such as Build Information, date & time, Android version,
|
- State of the device from the app perspective, including scan status, scan
|
||||||
OEM model, CPU info, Device identifier
|
timings, app permissions granted, and upgrade status
|
||||||
|
|
||||||
- App usage, CPU and network usage
|
|
||||||
|
|
||||||
- State of the device from the app perspective like scan status, scan timings,
|
|
||||||
app permissions granted, Upgrade status
|
|
||||||
|
|
||||||
- Features configured by the admin
|
- Features configured by the admin
|
||||||
|
|
||||||
- Basic information about the browsers on device
|
- Basic information about the browsers on the device
|
||||||
|
|
||||||
**Feedback Data** is collected thru in-app feedback provided user
|
**Feedback Data** is collected through in-app feedback provided by the user
|
||||||
|
|
||||||
- User email address is optional to provide.
|
- The user’s email address, if they choose to provide it
|
||||||
- Feedback type (smile, frown, idea), Feedback comments submitted by user
|
|
||||||
|
- Feedback type (smile, frown, idea) and any feedback comments submitted by
|
||||||
|
the user
|
||||||
|
|||||||
Reference in New Issue
Block a user