Evidence File

  • Home
  • / Evidence File
Hands browsing through a row of archived records

Usage Evidence File for Suspected Image Misuse

A usage evidence file brings together the essential facts surrounding suspected unauthorized image use. It records where the image appears, how it is being used, what ownership material is available and whether a licence or stock-platform record may explain that use.

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

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

image
About this page

This page shows how an Atlantic evidence file is structured. To have a suspected use reviewed, submit a case: the file is built from what you send.

Submit a case
Evidence-file model

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

Atlantic’s evidence-file model consolidates protected-work records, authority, observations, correspondence and integrity controls into a traceable case record that can be reviewed efficiently by authorized recipients, platforms, qualified counsel and competent authorities.

  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 states 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 distinguish creation, receipt, capture and later modification.

The file does not present 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 remains linked and the reason for the replacement is 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.

Atlantic administers rights, evidence and case-resolution workflows under documented authority. Judicial remedies and compulsory measures are pursued through competent authorities and qualified counsel where applicable.

Read the evidence principles