Evidence File

  • Home
  • / Evidence File
image

Usage Evidence File for Suspected Image Misuse

A usage evidence file brings together the essential facts of a suspected unauthorized image use. It records where the image appears, how it is used, what ownership materials are available and whether any license or stock-platform record may explain the use.

  • Capture full URLs and dated screenshots
  • Compare the online use with original source files
  • Review stock-platform and licensing records
  • Prepare a clear chronology of publication and discovery
  • Organize evidence for platform or counsel review
  • Identify gaps before escalation

The goal is not to overstate a claim. The goal is to create a factual file that can be reviewed, explained and used responsibly.

image
  • Category: Copyright Evidence
  • Updated: May 21, 2026
  • Used for: Platform review
  • Website: Atlantic Image Defense
  • Tags: evidence, monitoring, rights
  • Location: New York, USA
image
Evidence-file model

A navigable record that separates documents, assertions, observations and decisions

Atlantic’s evidence-file model is intended to help reviewers and authorized recipients understand the record without searching across unrelated emails, folders and spreadsheets. It is an organizational instrument, not a guarantee of legal admissibility.

  1. 01Cover and authority
  2. 02Chronology
  3. 03Protected image
  4. 04Observed uses
  5. 05Licence review
  6. 06Communications
  7. 07Decision log
  8. 08Manifest
01

Recommended structure

A complete file may include a cover sheet, parties and authority, protected-work record, source-file references, publication timeline, occurrence table, screenshots, URL list, contact sources, licensing analysis, communications, recipient submissions, payment records, decision history and technical manifest.

Sections that contain no information should be marked not available or not applicable rather than silently omitted where the absence matters.

02

Document status and provenance

Each item should identify whether it was supplied by the requester, captured by Atlantic, generated by the system, received from the recipient or obtained from a public registry. Dates should distinguish creation, receipt, capture and later modification.

The file should avoid presenting a requester allegation as an Atlantic finding or a technical observation as a legal conclusion.

03

Manifest and versioning

A manifest can list filenames, identifiers, hashes, sizes, storage locations, generation dates and relationships. It helps detect missing or changed items and supports controlled exports.

When a formal PDF is corrected, the previous version should remain linked and the reason for supersession should be recorded.

04

Recipient and counsel views

A recipient should see only the information required to understand and answer the matter, not unrelated private data. Counsel may receive a broader factual package under documented authorization.

Access links, downloads and submissions should be logged and revocable.

Legal and institutional references

These links point to official or institutional sources. Their inclusion does not mean that every text applies to every matter.

General information only. Atlantic does not issue judicial determinations, guarantee outcomes or replace counsel licensed in the relevant jurisdiction.

Read the evidence principles