Preserve NCII Evidence Without Re-Sharing the Material

How to Preserve Digital Evidence Without Re-Sharing Intimate Material

Start with the page location and platform record, not a new copy of the intimate image. When it is safe, preserve the URL, account identifier, visible date and time, surrounding threat or context, report confirmation, platform response, and appeal result.

Do not download, forward, cloud-sync, or ask another person to send intimate material merely to document it. Do not let a general article decide whether to retain or delete the only existing file. The right handling depends on safety, age, location, platform process, and possible legal or investigative needs.

Preserve what locates the post

A platform needs enough information to find the depiction. The most useful record is often the direct page, post, message, profile, or media URL.

Also record the username, account ID when visible, post ID, group or channel name, visible date and time, and the route used to reach the content. If a search result or message led to it, note the search terms or message context without copying the intimate asset.

If the platform uses disappearing content, do not assume this page can tell you how to capture it safely. Record the non-image context you can preserve without creating another copy and seek qualified guidance for the material itself.

Separate direct observation from what someone told you

Write down what you directly saw, when you saw it, and on which service. If another person found the content, distinguish their observation from yours.

Avoid turning a recollection into a technical conclusion. "The page displayed this account name at this time" is more reliable than "this person uploaded it" when the platform has not established who controlled the account.

flowchart TD
    A["Locate the platform page safely"] --> B["Record URL, account, date, and context"]
    B --> C["Submit through the platform's current process"]
    C --> D["Save confirmation number and submission time"]
    D --> E["Save platform response and action time"]
    E --> F["Record unresolved copies or appeal result"]
    A --> G["Do not create or circulate a new intimate copy"]
    G --> H["Seek qualified direction for the file itself"]

Keep the platform's own record

The TAKE IT DOWN Act request needs a signature, information sufficient to locate the depiction, a brief good-faith nonconsent statement with relevant information, and contact information.

After submission, save the confirmation page, confirmation number, delivery record, submitted text, submission time, platform response, removal time, reason for denial, and appeal result where available.

The FTC recommends that platforms provide a tracking number and status. If a platform lacks the required process or fails to act on a valid request, those records can help make a specific complaint through TakeItDown.ftc.gov.

Minimize sensitive information

A documentation file can expose the person's identity, contact details, relationships, location, threats, and reporting history even when it does not contain the image.

Store only what serves a defined purpose. Limit access. Avoid putting the record in a shared folder, group chat, public note, or broadly synchronized workspace by default. Before sending it to another person or service, confirm why they need it and what they will retain.

This general guide cannot select a storage system, retention period, encryption method, evidence format, or recipient for a specific situation.

Treat minor-related material differently

If the depicted person was under 18 when the image or video was taken, use specialized current guidance.

NCMEC says not to download or ask someone to send nude, partially nude, or sexually explicit minor-related material merely to submit it to Take It Down. The service should be used from a device that already has the file.

Do not apply an adult screenshot, hashing, or file-handling suggestion to minor-related material. Age in the image controls the service path, even when the depicted person is now an adult.

A screenshot is not automatically the safest answer

A screenshot can capture a URL bar, username, date, or surrounding threat. It can also create a new intimate copy, trigger cloud synchronization, expose the material in a photo library, or include more personal information than intended.

This page therefore does not tell every reader to take one. Preserve non-image context when possible. Get qualified current direction before handling the intimate asset, especially when a minor, threat, investigation, court process, or immediate safety issue may be involved.

The Department of Justice rights page explains that separate civil rights may exist under federal law. It does not make one evidence practice correct for every claim or jurisdiction.

Removal can change what remains visible

Fast removal and careful documentation can pull in different directions. Waiting to create a perfect record can prolong exposure. Acting without retaining any context can make later follow-up harder.

The practical response is to preserve the safest available location and process information promptly, then use qualified help for decisions about the file and any legal or investigative record.

[[How to Request Removal of Nonconsensual Intimate Imagery]] gives the platform and age-based service path. The guide does not require a person to reproduce the material before asking a covered platform to act.

This page provides general information, not legal advice, emergency guidance, a litigation hold, chain-of-custody protocol, forensic instruction, or evidence opinion. It was reviewed against current FTC, DOJ, and NCMEC sources on July 28, 2026.

This guide was developed with AI assistance and reviewed against the sources linked above. Dalton Anderson is responsible for the final editorial judgment.