Define the purpose of the image
If you are showing navigation, capture the relevant navigation area. If you are reporting an error, include the error and the minimum surrounding controls needed to explain it.
Do not publish a complete dashboard merely because it looks more convincing. Customer names, account identifiers, balances, activation history and access links can be irrelevant to the public explanation.
Remove private data from the derivative
Create a separate public copy and review every visible area, including page titles, sidebars and notification panels. Opaque redaction or a suitable crop can be more dependable than a superficial blur.
Check exported files for private metadata or filenames where relevant. An editable design project can retain the original customer screenshot even when a redaction shape covers it in the visible composition.
Use demonstrations honestly
A navigation-only screenshot can illustrate the interface without implying customer volumes, earnings or current account capabilities. Do not add fictional balances or customer totals to make a demonstration look successful.
Keep the source image privately controlled and label what the public derivative actually shows. If a real customer credential was exposed, removing the screenshot may not be sufficient; follow the relevant provider’s process for replacing or revoking it.
Questions about this guide
Can I publish a panel screenshot after hiding only the username?
Review the entire image. Other identifiers, balances, URLs, QR codes or repeated fields may remain.
Does a large dashboard balance prove reseller success?
No. A screenshot is not reliable evidence of earnings, customer volume or an approved business claim.
