Quick answer
Share the smallest useful error, code excerpt, and reproduction steps. Remove passwords, tokens, private keys, cookies, personal customer records, and payment information. Many configuration files and verbose logs contain secrets even when the visible problem seems harmless.
Before you start
Know where the error came from, the approximate time and time zone, the affected URL, and the software version. Work on a copy of the evidence so the original remains available for a trusted support investigation.
What to do
- Copy only the relevant lines and surrounding context, not an entire configuration, mailbox, database dump, or request archive.
- Replace secret values with descriptive placeholders while preserving names and syntax needed to understand the issue.
- Check headers, query strings, screenshots, terminal history, and stack traces for session tokens, credentials, private paths, and customer details.
- Tell the assistant what was redacted and ask for a diagnosis or next read-only check. Use a secure support channel if the investigation actually requires sensitive access.
Check the result
Review the final material before sending it and confirm that redactions did not change the meaning of the error. Keep any shared diagnostic file out of public website folders.
If something does not work
If a credential was exposed, rotate or revoke it through its real account interface. Editing the message or deleting the file does not prove that all copies are gone.
Related help
- Keep credentials and private files out of your public website
- Collect useful evidence when an email message is missing
- Send a website support request with useful troubleshooting details
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
