Send enough information to explain the problem without exposing credentials or unrelated customer data.
What is useful
- A screenshot showing the error and the relevant settings.
- A short log extract around the time the problem occurred.
- The affected URL, service, timestamp and timezone.
- Steps we can use to reproduce the issue.
Remove sensitive information
Before attaching files or pasting text, remove passwords, API keys, authorization headers, session cookies, private keys, recovery codes, payment card details and unrelated personal information. Log files, browser network exports and configuration files can contain secrets even when they look like ordinary technical text.
Keep the error code and relevant context visible. If redacting a screenshot, use a solid opaque block rather than a transparent highlight. Do not upload an entire database or website backup unless support specifically requests it and explains an appropriate transfer method.
If access is necessary
Ask support how to provide access safely. Where practical, use a separate temporary account with only the permissions needed and remove it when the work is complete. Do not disable two-factor authentication or grant full administrator access just to submit a question.
If you have already exposed a secret
Revoke or rotate the affected credential and tell support what type of credential was exposed, without repeating its value. Removing an attachment alone does not make an exposed password or token safe again.
