Repo sync for protected CLA branch

docs/ide/developer-community-privacy.md

@@ -1,8 +1,8 @@
 ---
-title: Private data for problem reports
-description: Learn how to keep your private data more secure when you create problem reports for the Developer Community to review.
+title: Developer Community data privacy
+description: Learn how to manage your private data when you create problem reports for the Developer Community to review.
 ms.custom: SEO-VS-2020
-ms.date: 06/21/2018
+ms.date: 11/07/2022
 ms.topic: conceptual
 helpviewer_keywords:
 - developer community privacy
@@ -18,7 +18,7 @@ ms.workload:
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-By default, all information in problem reports on [Developer Community](https://aka.ms/feedback/suggest?space=8), including any comments and replies, is publicly visible. This is beneficial because it allows the entire community to see the issues, solutions, and workarounds that other users have found. However, if you're concerned about the privacy of your data or identity, you have options.
+By default, all information in problem reports on [Developer Community](https://aka.ms/feedback/suggest?space=8), including any comments and replies, is publicly visible. This is beneficial because it allows the entire community to see the issues, solutions, and workarounds that other users have found. However, if you're concerned about the privacy of your data or identity, you have options. You can also View, Export, or Delete your feedback data.
 
 ## Identity privacy
 
@@ -46,45 +46,113 @@ To maintain your privacy and keep sensitive information out of public view, take
 
 ## Data we collect
 
+Microsoft collects data to help us reproduce and troubleshoot issues you report with Visual Studio Family products. This data includes **personal data** and **public feedback**.
+
+**Public feedback** includes: reported problems, comments, and solutions.
+
+**Personal data** includes:
+
+- Your [Developer Community](https://developercommunity.visualstudio.com/) profile information;
+- Preferences and notifications;
+- Attachments and system-generated logs you provided by [reporting a problem in Visual Studio](how-to-report-a-problem-with-visual-studio.md) or through [Developer Community](https://developercommunity.visualstudio.com/);
+- Your votes.
+
 If **Report a problem** is initiated from Visual Studio Installer, we collect the most recent setup log.
 
 If **Report a problem** is initiated from Visual Studio, we collect one or more of the following types of data:
 
 - Watson and .NET entries from the event log
-
 - Visual Studio in-memory activity log file
-
 - PerfWatson files, if Watson collection is enabled
-
 - LiveShare log files, if they exist
-
 - Xamarin log files, if they exist
-
-- Nuget log files, if they exist
-
+- NuGet log files, if they exist
 - Web debugger log files, if they exist
-
 - Service Hub logs and MEF error logs, if they exist
-
 - Python logs, if they exist
-
 - Razor LSP editor logs, if they exist
-
 - Windows Forms logs, if they exist
-
 - A screenshot, if you choose to include it
-
 - Recording data, if you choose to include a recording, which includes:
 
   - Steps to reproduce the problem
-
   - ETL trace file
-
   - Dump file
 
 > [!NOTE]
 > Log files, screenshots and recording data you send can significantly increase Microsoft's ability understand and respond to your issue.  So we recommend including them. To protect your privacy, any attached log files, screenshots and recording data are sent only to Microsoft when you provide permission by submitting the problem report with which they are included. You can see which files are included on the 'Summary' step of the 'Report a Problem' window before submitting the report. You can exclude system log files from the report by unchecking 'Attach system logs' in the 'Summary' step. For reference, see the following screenshot. 
-  > ![Report a Problem - Summary of logs collected](media/report-a-problem-logs-collected.png)
+  > ![Report a Problem * Summary of logs collected](media/report-a-problem-logs-collected.png)
+
+## GDPR Data Subject Request processing
+
+We support [General Data Protection Regulation (GDPR)](https://ec.europa.eu/justice/data-protection/reform/index_en.htm) and other data protection regulation requests through the [Developer Community](https://developercommunity.visualstudio.com/) website. You can View, Export, or Delete your feedback data.
+
+### View
+
+To View your feedback-related data, follow these steps:
+
+1. Sign into [Developer Community](https://developercommunity.visualstudio.com/). From the top-right corner, click on your **profile** and select **Profile and Preferences**.
+
+2. Click on any of the **Profile, Notifications, Activity,** and **Attachments** tabs to view the data submitted to the feedback systems.
+
+   - **Profile** refers to your Developer Community profile, including user name, email address, about, etc.
+   - **Notifications** are how you control the email notifications you receive.
+   - **Activity** will give you the feedback items you have been active on (posted, commented, etc.), and the activities performed.
+   - **Attachments** is a list of your attachment history in a format like `FileName was attached to the problem "ProblemName" Tue, Apr 10, 18 2:27 PM`.
+
+### Export
+
+You can export your feedback data as part of DSR. We will create one or more .zip archives that will include:
+
+- Your Developer Community **profile** information;
+- **Preferences** and **notification** settings;
+- **Attachments** you provided by reporting a problem in Visual Studio or through Developer Community.
+
+> [!NOTE]
+> We will exclude the following public feedback you have provided from your archive: comments, solutions, reported problems.
+
+To start an Export, follow these steps:
+
+1. Sign into [Developer Community](https://developercommunity.visualstudio.com/). From the top-right corner, click on your profile and select **Profile and Preferences**.
+2. Click the **Privacy** tab, and then click **Create an archive** to request exporting your data.
+3. The **Archive Status** will update to show that we are preparing the data. The length of time before the data is available depends on the amount of data we need to export.
+4. Once the data is ready, we will send you an email.
+5. Click **Download Archive** in the email, or go back to the **Privacy** tab to download your data.
+
+> [!NOTE]
+> - We will not send email if you chose not to receive notifications in the Notifications tab.
+> - If you request Export again, we will remove your old archive and create a new one.
+
+### Delete
+
+Deleting will remove the following information about you from Developer Community:
+
+- **Profile** information;
+- **Preferences** and **notification** settings;
+- **Attachments** you provided by reporting a problem in Visual Studio or through Developer Community.
+- Your **votes**
+
+> [!NOTE]
+> We will not delete, but will anonymize, the following public information: your comments, your solutions, problems that you reported.
+
+> [!IMPORTANT]
+> Delete of an Azure AD or MSA account triggers the Delete process for Developer Community.
+
+To initiate a Delete, follow these steps:
+
+1. Sign into [Developer Community](https://developercommunity.visualstudio.com/). From the top-right corner, click on your profile and select **Profile and Preferences**.
+2. Click the **Privacy** tab, and then click **Delete your data and account** to start deleting your data.
+3. A confirmation screen will appear.
+4. Type "delete" in the box, and then click **Delete my account**.
+
+Once you click **Delete my account**:
+
+- We will sign you out.
+- We will delete your Developer Community account, your personal data, and attachments.
+- We will anonymize your public feedback. Your public feedback will remain available on Developer Community, and will be indicated as reported by an Anonymous user.
+- We won't email you after we delete your account, because you will no longer be present in the system.
+- If you report a new problem or log into Developer Community, you will be identified as a new user.
+- If you delete your account from Developer Community, we will not delete it from other Microsoft services.
 
 ## See also
 

docs/ide/whats-new-visual-studio-2022.md

@@ -2,7 +2,7 @@
 title: "What's new in Visual Studio 2022"
 titleSuffix: ""
 description: "Learn about the new features in Visual Studio 2022."
-ms.date: 11/08/2022
+ms.date: 11/16/2022
 helpviewer_keywords:
   - "Visual Studio, what's new"
   - "what's new [Visual Studio]"
@@ -26,8 +26,12 @@ ms.workload:
 
 With [Visual Studio 2022](https://visualstudio.microsoft.com/vs/), you'll always get the best-in-class tools and services available for any developer, any app, and any platform. Whether you're using Visual Studio for the first time or you've been using it for years, there's a lot to like in our newest version!
 
+Want to see what's new in each updated release from within Visual Studio itself? Now you can! From the menu bar, select **Help** > **What's New** to view recent highlights.
+
+:::image type="content" source="media/vs-2022/whats-new-visual-studio.png" alt-text="Screenshot of the in-product notification of what's new in each updated release of Visual Studio.":::
+
 > [!TIP]
-> For more news + how-to's, check out our Visual Studio 2022 channels on [YouTube](https://www.youtube.com/visualstudio), [Twitch](https://www.twitch.tv/visualstudio), [Twitter](https://twitter.com/VisualStudio), and [TikTok](https://www.tiktok.com/@visualstudio).
+> For more news + how-to's, check out our Visual Studio 2022 channels on [YouTube](https://www.youtube.com/visualstudio), [Twitch](https://www.twitch.tv/visualstudio), [Twitter](https://twitter.com/VisualStudio), and [TikTok](https://www.tiktok.com/@visualstudio). And for the latest info on recent releases, current experiments, and what's in Preview, be sure to visit the Visual Studio [Blog](https://devblogs.microsoft.com/visualstudio/).
 
 ## Performance improvements