Redact an account screenshot for support

Choose the smallest useful view

Keep the app name, screen heading and exact error wording where they help explain the case. Exclude unrelated chats, notification previews, payment cards and other accounts. If a typed transcription communicates the same observation, use that instead. A support request can describe field labels without displaying the field values.

Remove sensitive values in a separate copy

Make a redacted copy while retaining the original privately only if it is needed for the case. Cover sensitive values fully with an opaque block or crop them out. Do not rely on a translucent highlight, blur of uncertain strength or a tiny mark over only part of a password. Include the complete token or link in the redaction, including any repeated value elsewhere in the image.

1. Inspect the full screen before capturing.
2. Crop to the relevant panel.
3. Remove every credential and unrelated personal value.
4. Export and reopen the exact file you intend to send.

Check the actual attachment

Zoom in on the exported copy. Check image edges, notification overlays and filenames for information you did not intend to disclose. Ensure the error remains readable. A conversation preview may show an earlier image, so verify that the selected attachment is the redacted version before sending it through the established private support route.

Add a short caption

State the app, relevant device, observation time and question. For example, say that the displayed end date differs from the order confirmation, without treating the screenshot as proof of ownership. Keep account verification in the provider’s proper process. If you accidentally sent a secret, follow the exposure-response procedure; editing your local copy does not remove the recipient’s earlier copy.

Questions about this guide