How to separate private support evidence from a public creative example

Identify the audience before selecting evidence

A support recipient needs to understand a particular observed issue. A public reader needs to understand a general principle. These purposes call for different detail. A screenshot that helps support locate a selected task may expose an email address, unreleased product name or client information when republished in a guide. Choose the audience first instead of sharing the same capture everywhere.

In an illustrative custom-jewelry case, the product photo contains an engraved customer name. The defect concerns an extra clasp, not the engraving. An internal record can identify the relevant task and clasp position. A public lesson can use a separately permitted example with a neutral engraving, rather than publishing the customer’s personal detail to prove that the defect occurred.

Use the current feedback channel accurately

Itemlume’s current feedback channel accepts a subject, description, category, feature and optional task reference. It keeps diagnostic task information separate from the private generation instructions. It is not currently an image-attachment collection. Describe the visible problem and reference the relevant task where available; do not assume the form uploads the source photograph simply because you mention it.

Exclude passwords, API credentials and full payment details from the text. If an investigation later requires media through an explicitly agreed route, select only the necessary material and confirm how it will be used. A pasted link can expose information beyond the screenshot itself, so review the access granted by the link as well as its apparent preview.

Separate originals, annotations and public examples

Do not overwrite the original when making annotations. A redacted derivative should remain distinguishable from untouched evidence. If the public replacement depicts a hypothetical event, say so; it must not become a fabricated customer case study or a claimed paid test.

Redact without destroying the relevant observation

Remove unrelated browser tabs, account labels, addresses and private order details from an interface capture. For a visual defect, keep enough product and timing context to explain the issue. A crop that removes the entire contact point may protect privacy but also make the defect impossible to understand. Choose a separate illustrative example when those purposes cannot be reconciled.

Inspect the exported redaction as a flattened image or video, including thumbnails and surrounding metadata when relevant. Do not assume a temporary overlay in an editable project permanently removes underlying information from every delivered artifact. Avoid making a public location or identity guess from model imagery; focus the explanation on the observable creative issue.

Obtain a new decision for public use

Before publishing, confirm who owns the product material and who can approve the proposed use. Model references, customer contributions and unreleased designs may involve different permissions. An administrator’s ability to investigate a feedback record does not automatically grant marketing rights. Frame.io’s sharing documentation similarly treats access as an explicit sharing decision, although its controls are not Itemlume features. Frame.io’s external sharing reference.

For the jewelry example, support can work from a precise private task report while the public guide uses an approved fictional product. Label the example and retain the investigation record separately. This keeps the educational value without turning support access into a public media collection or suggesting that customers must expose sensitive images to report a problem.