Copyright Evidence

Core evidence categories

A robust file may include the original or source file, embedded metadata, export history, publication records, contributor statements, contracts, licences, screenshots, full URLs, page context, correspondence, recipient responses and payment records.

No single item automatically proves the entire case. Source files can be copied; metadata can be changed; screenshots can omit context; platform records can be incomplete. Reliability comes from corroboration and documented handling.

• Source and derivative files
• Rights and authority records
• Observed-use records
• Licence and distribution records
• Communications and decisions
• Storage and integrity records

Integrity controls

Cryptographic hashes can help identify whether a stored file has changed since hashing. Version identifiers, timestamps, manifests and audit events help explain the storage history.

A hash does not establish who created the work, when it was created or whether the person presenting it owns the relevant rights. Those questions require additional proof.

Authentication and admissibility

In U.S. federal proceedings, authentication generally requires enough evidence to support a finding that an item is what its proponent claims. The court determines admissibility and may consider relevance, hearsay, completeness, best-evidence rules, privilege and other requirements.

Atlantic can organize records and preserve system information, but it cannot guarantee that a court, platform or authority will admit or credit a particular item.

Corrections without erasure

If an incorrect URL, date, classification or identity is discovered, the corrected value should be recorded together with the reason and historical value where appropriate. Silent replacement weakens trust.

Generated PDFs and formal records should be immutable once issued; revisions should create a new version linked to the prior document.