Sanitise a screenshot before asking for support

Decide what the helper needs

A useful screenshot shows the relevant error, application and enough context to reproduce the issue. It does not need your complete password vault, unrelated inbox, patient information or a token visible in the address bar. Decide which details are necessary before capturing the whole desktop.

Opaque removal is safer than lightly blurring text that might remain readable. Work on a separate copy so you can preserve the original privately when needed for an incident record.

Prepare the image deliberately

1. Close or move unrelated windows and crop to the smallest useful area. Include the actual error wording and relevant setting, but avoid revealing a broader customer or account list.
2. Look for passwords, API keys, recovery codes, session URLs, account identifiers and personal records. Inspect the address bar, side panels, notifications and reflected content as well as the main dialog.
3. Apply solid opaque redaction to details that are not needed. Flatten or export the result to an ordinary image so the recipient cannot remove an editable covering layer.
4. Open the exported file again, zoom in and inspect every area you intended to hide. Share that checked export through the approved support route rather than the editor's original layered project.

Verify the technical context remains

Read the screenshot as if you were the helper. Can you still identify the product, error and step? If not, include a short sanitised text description with version and expected behaviour. Redaction should remove sensitive information without making the problem impossible to diagnose.

Treat leaked secrets as exposed

If a working secret was already shared outside its approved audience, covering it in a later screenshot does not revoke it. Rotate or invalidate it through the genuine service and review relevant access according to the situation. Do not repost the secret while explaining that it should be changed.

Check the sharing channel

Public forums and social-media groups can distribute an image widely. Use dummy hostnames and account names where exact values are unnecessary. Business support portals also need appropriate access and retention; a private-looking upload is not automatically the approved location.

Keep a repeatable checklist

Review crop, secrets, personal information, export format and final readability. Good sanitisation improves support quality because the helper sees the relevant evidence without receiving a large unrelated collection of sensitive details.