Short answer
Good support context explains the problem without exposing secrets, private billing data, access tokens, or unrelated user data.
When to use this
Use this article before sharing screenshots, logs, AI prompts, payment context, or workspace details.
Requirements
Hide sensitive values before sending a screenshot. Keep full payment identifiers and private credentials out of public channels.
What to include
Include the route, product surface, approximate time, account state, safe error message, and what you expected.
Common problems
Screenshots often contain emails, customer names, private links, or billing details. Crop or redact before sharing.
Related articles
Read Get help for the full support package.
Escalation guidance
If you already shared sensitive data by mistake, say so in a trusted support channel and rotate any exposed secrets.
Related articles
Was this article helpful?
Your feedback helps Probe improve articles, search synonyms, and support triage.