Merge pull request #49565 from eross-msft/legal-update

Updating what data we collect, per legal

Author: PRMerger16

articles/active-directory/user-help/microsoft-authenticator-app-faq.md

@@ -24,7 +24,7 @@ The Microsoft Authenticator app replaced the Azure Authenticator app, and is the
 ## Frequently asked questions
 |Question|Solution|
 |--------|--------|
-|What data does the Authenticator store on my behalf and how can I delete it?| The Microsoft Authenticator app stores the account information you provide when you add an account. When you use the app, a diagnostic log is created for debugging purposes and only stores data that's useful to help Microsoft diagnose unforeseen issues. You can review the log data by opening the app, selecting **Help**, selecting **Send logs**, and then selecting the **View logs** button.<br><br>You can delete your all of your data, including your log files, by deleting the account tile on the **Accounts** screen. For more information about how Microsoft uses your data, see the [Service Trust Portal](https://servicetrust.microsoft.com/ViewPage/HomePage.)|
+|What data does the Authenticator store on my behalf and how can I delete it?|The Microsoft Authenticator app collects three types of information:<ul><li>Account info you provide when you add your account. This data can be removed by removing your account.</li><li>Diagnostic log data, which resides only in the app until you choose to **Send Logs** to Microsoft through the app's **Help** menu. These log files contain personal data, like your email addresses (such as, [email protected]), server/IP addresses, and device data (such as, device name and operating system version), with the personal data limited to info necessary to help troubleshoot app issues. You can view these log files in the app at any time to see the info being gathered. If you send the log files, the Authentication app engineers can use it to troubleshoot customer-reported issues.</li><li>Non-personally identifiable usage data, such “started add account flow/successfully added account,” or “notification approved.” This data is an integral part of our engineering decisions and helps us determine what features are important to you, and where improvements need to be made in the form of updates to the apps. You, as an app user, see a notification of this data collection on first launch of the app, and are informed that it can be turned off on the app’s **Settings** page. You can enable or disable this setting at any time.</li></ul>|
 |What are the codes in the app for?|When you open the Microsoft Authenticator app, you'll see your added accounts as tiles with a six- or eight-digit number for each.<br><br>You'll use these codes as verification that you are who you say you are. After you sign in with your username and password, you'll type in the verification code that's in the same tile as your account. For example, if you're Alain signing in to your Contoso account, you'd use the verification code, 427303.<br><br>![Accounts screen in the app](./media/microsoft-authenticator-app-faq/auth-app-accounts.png)|
 |Why does the number next to the code keep counting down?|You might see a 30-second timer counting down next to your active verification code. This timer is so that you never sign in using the same code twice. Unlike a password, we don't want you to remember this number. The idea is that only someone with access to your phone knows your code.|
 |Why is my account tile gray?|Some organizations require the Microsoft Authenticator app to work with single sign-on and to protect organizational resources. In this situation, the account isn't used for two-step verification and shows up as gray or inactive. This type of account is frequently called a "broker" account.|