Send Crypto Support Documents Safely: Channels and Redaction

Before sending documents to crypto support, verify the recipient and establish which edits the specific review permits. Redaction suitable for a diagnostic screenshot may make an identity image or financial statement unacceptable. When edits are allowed, remove the selected information from the disclosure copy and inspect that saved file; a dark rectangle on a page is not enough evidence that the underlying content has gone.

Start with the request, before opening an editor

Write down the case reference, the document requested and the question it should answer. A transfer investigation might require evidence of a particular withdrawal, while an identity check has a different purpose. Sending an entire document archive because the message says ‘verification’ creates unnecessary disclosure without necessarily answering either question. If the request is ambiguous, ask which document and which fields are needed before assembling the package.

Reach the service through a route you independently know, rather than treating the incoming message as its own proof. Find the corresponding task or confirm the case through the established support channel. A logo, a familiar display name or a browser’s connection indicator does not establish who will receive the file. If another upload domain is involved, establish its relationship to the service using an independently reached official explanation; providers have different arrangements.

For example, Coinbase’s identity instructions direct users to its authenticated verification flow and say not to email ID photos to support. That is a provider-specific instruction, not a rule that every crypto company accepts the same upload route. Do not transplant one company’s instructions into a different company’s review.

Decide what may change in this particular document

Kraken’s source-of-funds requirements permit redacting some sensitive data, such as account numbers or a US Social Security number, while essential identifying and transaction information must remain visible. Its policy does not establish permission for another provider, another document type or every field on the same statement.

The distinction can matter even within one service. Coinbase’s account-review guidance permits redaction only where its submission flow allows it. Before altering a disputed field, ask what the reviewer accepts and retain the answer with your case notes. Do not change amounts, invent missing entries or remove a required part of the transaction history to obtain a different review outcome.

A PDF needs a content check, not a colour check

Work on a separate disclosure copy and keep the original privately. Label the copy clearly enough that you can distinguish it in a file picker. A name such as ‘review-copy’ is more useful than several nearly identical files called ‘final’. Avoid placing a full passport or account number in the filename merely to identify the attachment.

Use an actual redaction function appropriate to the file. Adobe’s redaction instructions distinguish selecting material, applying the redaction and saving the result. Marking a region for removal is not the same as completing those steps. A drawing tool’s filled box is not a substitute for an operation that removes the content.

Visible text is only part of the check. Adobe’s sanitization guidance identifies hidden information including metadata, comments and layers. Inspect the relevant categories in the tool you use and save the prepared copy. A neat-looking first page does not establish what remains elsewhere in the document or in its attachments.

1. Confirm that the requested edits are permitted and that the unedited original remains separate.
2. Remove the approved fields with a proper redaction operation and apply the changes.
3. Review hidden content using the editor’s relevant inspection or sanitization features.
4. Save the disclosure copy, close it and reopen the file from its actual saved location.
5. Inspect every page; try searching for and copying the removed text, and review document properties and attachments where applicable.
6. Check that required names, dates, amounts and transaction details remain legible, then select that exact copy for submission.

Search and copy tests can reveal an obvious failed redaction; passing them is not a forensic guarantee for every PDF structure. If you cannot establish how your editor handles the document, use a documented workflow or seek competent help with a non-sensitive sample first. Do not upload the real statement to an unfamiliar ‘free redaction’ site simply to test whether it can hide a number.

Photos and screenshots need their own release check

For a support screenshot, inspect the whole frame before sending it: account menus, browser tabs, notifications and neighbouring conversations may be unrelated to the problem. Recreate a narrower view where possible. Keep the error message, relevant reference and context intact; an attractive crop that removes the diagnostic detail can lead to another request for the same evidence.

Photo metadata is a separate issue. Apple’s sharing guide allows location sharing to be turned off in Photos’ sharing options. This does not establish that every other piece of metadata or an earlier shared copy disappears. First check whether an identity capture requires an original image; do not process that file using a generic privacy recipe contrary to the review instructions.

Send a bounded package and keep a small receipt

Before uploading, compare the attachment list with the request and remove unrelated drafts. Recheck the destination and case reference at the moment of submission. Keep a local note of the filenames, the route used and what you intentionally disclosed. There is usually no need to reproduce the full identity document again inside your own support summary.

If an attachment is rejected, ask which requirement failed before resending an expanded archive. A clearer original, a different permitted format or an explanation may be relevant; more personal information is not automatically the answer. Editing a local copy after submission does not retract the earlier disclosure. Questions about retention or deletion should address the recipient’s actual processing and rules.

For KOT.CASH, read the AML policy alongside how an exchange works when assessing a request connected with an order. A simple no-account swap does not eliminate the possibility of a transaction review. These pages do not establish which redactions will be accepted in an individual case; confirm the request instead of assuming the examples above describe KOT.CASH’s upload interface.