Document telemetry collection and opt-out steps

[Copilot]

Addresses user request for transparency around Windows Terminal's telemetry practices and how to disable data collection.

Changes

• README.md: Added "Data Collection and Telemetry" section

  • Specifies what data is collected (feature usage, crashes, aggregated settings)
  • Clarifies data is anonymized and excludes terminal session content
  • Step-by-step opt-out via Windows diagnostic data settings
  • Links to Microsoft Privacy Statement

• TerminalDocs/faq.yml: Added FAQ entry "How do I disable telemetry collection on Windows Terminal?"

  • Quick reference for disabling telemetry
  • Cross-references detailed README section

• TerminalDocs/troubleshooting.md: Added telemetry section linking to both README and FAQ

Creates multiple discovery paths for users seeking telemetry information.

Original prompt

---

This section details on the original issue you should resolve

<issue_title> Document our telemetry collection and opt-out steps</issue_title>
<issue_description>microsoft/terminal#6118</issue_description>

Comments on the Issue (you are @copilot in this section)

@mattwojo Kayla will write up a data collection / telemetry statement, that also links to the privacy statement, and add it to the Terminal product repo readme, along with linking to this section of the readme from the terminal troubleshooting doc. @mattwojo Add a FAQ: "How do I disable telemetry collection on Windows Terminal?" > Basic telemetry statement with instructions on how to disable telemetry all together on Windows (likely covered somewhere already that can be linked to)

• Fixes Document our telemetry collection and opt-out steps #139

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[learn-build-service-prod]

Learn Build status updates of commit d00eb95:

✅ Validation status: passed

For more details, please refer to the build report.

[learn-build-service-prod]

Learn Build status updates of commit 8d12551:

✅ Validation status: passed

File	Status	Preview URL	Details
README.md	✅Succeeded
TerminalDocs/faq.yml	✅Succeeded	View
TerminalDocs/troubleshooting.md	✅Succeeded	View

For more details, please refer to the build report.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit d762c36:

✅ Validation status: passed

File	Status	Preview URL	Details
README.md	✅Succeeded
TerminalDocs/faq.yml	✅Succeeded	View
TerminalDocs/troubleshooting.md	✅Succeeded	View

For more details, please refer to the build report.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.