Support Attachments & Log Redaction
Detailed support evidence guidance for screenshots, logs, project files, API keys, brokerage data, and deletion requests.
Page sections
Purpose
This page gives users a safer checklist for sending screenshots, logs, project files, crash reports, or reproduction steps to support.
It is designed to reduce accidental disclosure of brokerage credentials, private API keys, personal financial details, or unrelated personal information.
Redact before sending
Before sending an attachment, remove or mask broker account numbers, passwords, API keys, tokens, secret keys, full payment-card details, tax identifiers, private addresses, unrelated emails, and personal information not needed to solve the issue.
Screenshots should crop unrelated browser tabs, chats, account pages, and personal documents.
What useful evidence can include
Helpful support evidence can include app version, Windows version, installation source, Microsoft Store installation/update context, error message, approximate time, steps to reproduce, affected module, expected behavior, actual behavior, and non-sensitive sample data.
Logs may contain paths, timestamps, configuration values, provider names, and error traces. Review logs before sharing.
Retention and deletion
Support attachments may be retained while needed for troubleshooting, security, dispute handling, audit, or product-quality purposes.
Users may request deletion of support attachments, subject to legal, security, platform, and dispute-preservation limits.