Redact a SignalBet support screenshot without losing the useful evidence

Define the support question before capturing a screen

A long gallery of unlabelled screenshots may expose private information while failing to explain a missing balance or account warning. Write the exact question first: which event, on what date, and what response is requested? A minimal image then has a purpose, a version and a safe channel.

CISA's phishing guidance emphasizes recognizing suspicious requests and reporting them through independently verified channels, rather than trusting a message that asks for sensitive data. The public source establishes this starting point; its date and scope belong beside the specific decision in the support-evidence manifest.

Preserve one untouched original

A crop or annotation can remove context needed to distinguish a transaction from an unrelated entry. Save the full image privately with capture date, timezone, device and page name. Give the original image a capture time, page label and private storage location. A later working copy can then be traced to the precise view it came from.

Do not place the original in a shared folder whose access you have not reviewed. Do not annotate the original in place. If support questions whether a crop removed a status label, you need the untouched record to review that context.

Mark the minimum relevant region

An account identifier, transaction status and timestamp may matter while other balances or messages do not. Make a separate working copy and crop only after noting the source of each visible field. For a missing credit, include the relevant transfer row, amount, asset or payment rail, and status time. Crop out unrelated conversations and other people's transactions.

A cropped image should not imply that a pending event is final or that a partial address is complete. Explain in a short caption which visible field answers the support question. A pile of broad account screenshots often obscures the actual discrepancy.

Redact secrets irreversibly in the shared copy

Blur and translucent drawing tools may preserve readable pixels or metadata in some workflows. Use opaque replacement for passwords, one-time codes, full card numbers and unrelated identity details, then reopen the exported file to verify. Export a copy with solid opaque replacements over secrets and unrelated identity data. Zoom into the result and inspect metadata or thumbnails where the tool retains them.

Never send a wallet seed phrase or private key even if a person claims to be support. A soft blur can leave text recognizable, especially after sharpening. Keep the full original private and send only the verified redacted export.

Label the event chronology

Wallet, account and support screens can use different timezones and state labels. Attach a short legend with displayed time, timezone, exact status and where it appeared. Put wallet broadcast, network confirmation and account-credit screens in chronological order, with the timezone each displayed. Label a status as a quotation from that screen.

Do not turn a blockchain confirmation into a claim of account credit without the account record. Do not relabel a confirmed chain transaction as a completed account deposit. The receiving system may still have a separate review or unsupported-route question.

Control where the evidence goes

A direct message can imitate a support representative and request the same screenshots. Open a verified support route independently, note the ticket number and retain what was sent. Submit through a route you opened from the authenticated account or verified site, then note its acknowledgement and ticket. Limit the attachments to the bounded question.

Do not upload an identity document unless the authenticated process specifically requires it. An unsolicited social-media helper may know a transaction identifier without representing support. Do not move the evidence to that person's upload link.

Apply phishing caution to the support handoff

CISA's advice supports independent verification and limited exposure when a support-themed message asks for data. Reopen the named HTTPS page when applying the support-evidence manifest; an internal SignalBet guide is context, not the authority for a changing fact.

It cannot judge a specific account event, establish legal document-retention duties or identify which images an operator requires. Do not extend that source into a conclusion about an individual case it does not cover.

Make the evidence usable without making it public

A recipient should see the precise event and question, while the private original remains available for an authorized follow-up. Recheck the disputed item in the support-evidence manifest before a consequential action and retain the dated answer.

For a concrete support packet, use a one-page cover note followed by only the images that answer its question. State the event date, payment rail, reference and precise discrepancy, such as confirmed on the network but not credited in the account. Number the screenshots in chronological order and identify their original page names. Keep full originals offline or in private storage, while the submitted copies mask unrelated transactions and identity fields. Check each exported image at full resolution; some editors leave a readable thumbnail or semitransparent blur. Send through the account's authenticated support route and record the receipt. If support later asks for another document, evaluate that new request separately rather than sending an entire archive. Better labels usually help more than more data.

• An untouched original lets a later reviewer inspect labels removed by a working crop.
• A delayed-payment question rarely needs unrelated balances or conversations in the shared image.
• Reopen the export to ensure an opaque mask actually covers sensitive pixels.
• Pending in a wallet is not the same status as pending in an operator account.
• A ticket number preserves continuity; a private-message profile does not authenticate support.

A pending support case should not prompt another deposit or a longer gambling session. Adults 18+ must also meet local legal-age rules. Gambling is optional entertainment, not income or debt recovery. Protect essential money, set time and spending limits, never borrow or chase losses, and use the responsible-play centre for a break, blocking, exclusion or support.