Evidence for AI Copyright Infringement Philippines: Checklist

Last materially reviewed: September 6, 2026

Intellectual Property → AI-Generated Works → AI Training & Enforcement

Direct Answer

Preserve the evidence before sending a complaint. For suspected AI copyright infringement, a rights holder should keep proof of ownership, the original work, publication history, the exact AI prompt and output, model name and version, dates, screenshots, URLs, account details where relevant, repeated tests, and any correspondence with the platform or developer.

Why Evidence Comes First

Online content and AI outputs can change quickly. A model may be updated, a link may disappear, a platform may remove a result, or a developer may alter its safeguards after receiving notice. Capturing the current state creates a reliable record.

Ownership Evidence

Original source files and drafts.
Creation timestamps and project files.
Publication records and URLs.
Employment, commission or assignment agreements.
License agreements.
Copyright registration or deposit records if available.
Evidence showing who controlled publication and exploitation of the work.

AI Output Evidence

Exact prompt text.
Complete output rather than a cropped excerpt.
Model name, product, plan and version if shown.
Date and local time of the test.
Settings or system mode used.
Screen recording where useful.
Exported conversation or output file if the platform permits.

Comparison Evidence

Prepare a side-by-side comparison that highlights the protected material you believe was reproduced. Avoid claiming ownership over facts, ideas, common phrases or unprotectable elements. Focus on identifiable original expression.

Repeatability

If the same or similar output can be generated repeatedly, record multiple tests. This can help distinguish systematic reproduction from a one-off similarity. Do not manipulate prompts simply to manufacture a stronger-looking claim; preserve the full test history.

Evidence of Scraping or Dataset Use

If the issue involves training rather than output, preserve crawler logs, dataset documentation, public statements by the developer, licensing communications, robots or access restrictions, and any dataset search results linking the model to your work.

Before Sending a Notice

Create a dated evidence folder.
Save originals in unchanged form.
Export screenshots and screen recordings.
Record all URLs and identifiers.
Write a factual chronology.
Identify the exact right allegedly infringed.
Choose the correct platform, developer or IPOPHL route.

Related Guides

Build a Package Another Person Can Verify

The goal is a traceable account of what happened. Separate original files, captured service records and your own analysis. Keep a read-only master copy where practicable and work from duplicates. Label any crop, annotation or conversion so it cannot be mistaken for the unaltered capture. These are practical preservation steps, not a guarantee that a court or agency will admit every item.

A practical evidence folder
Folder	Contents	Why it matters
Original work and rights	Source files, dated drafts, publication records and relevant agreements	Identifies the work and the claimant’s rights.
AI session	Full prompt history, outputs, exports, settings and displayed model information	Shows the conditions in which the result appeared.
Comparison	Side-by-side extracts with page, paragraph or timestamp references	Explains the specific alleged copying.
Access and distribution	Relevant logs, dataset references, public URLs and publication dates	Supports particular acts without conflating them.
Chronology and correspondence	Dated events, collection notes, notices and responses	Lets a reviewer reconstruct the sequence.

Record the Capture Conditions

For each session, note who captured it, when, in which time zone, and how the file was obtained. Include the displayed service and model information; if the version is unavailable, say so. Record whether the service had browsing, retrieval, uploaded files or earlier conversation context. Preserve relevant prompts even when they weaken the preferred explanation.

A screenshot can show what was visible, but it may omit the preceding prompt or surrounding interface. Pair it with an available export and a short collection note. A file hash can help compare whether a file has changed after preservation; it does not independently prove authorship, the original creation date or that the displayed event was genuine. Keep the person’s account of collection alongside the files.

Connect Each Item to a Legal Issue

The Intellectual Property Code, Sections 172, 175, 177 and 185 makes the identity of protected expression, the relevant rights, permission and exceptions central to the assessment. Organize the package around those questions. Evidence that a work existed is different from evidence that the claimant owns the right at issue. Include employment, commission, assignment or licensing documents where they affect the claim.

For alleged output copying, mark the expression said to have been reproduced and distinguish facts, ideas or commonplace material. For alleged training use, identify the evidence linking a work to a dataset and the dataset to the relevant system. Do not present a crawler visit as if it were a complete training record. Counsel can then assess the appropriate proceeding and its authentication and filing requirements.

Three Common Evidence Problems

Only a cropped viral screenshot remains

Save the screenshot and its source, identify its limitations, and ask the original tester for the complete session if possible. A later recreation is a separate test with its own date and conditions. Never label it as the original event.

A test produces a close match only after many attempts

Keep the unsuccessful attempts and explain the sequence. Record any excerpt introduced into a prompt. Selectively showing the closest answer can conceal facts needed to evaluate whether the result came from supplied text, retrieval or another mechanism.

A business discovers a questionable output already in use

Preserve the published version, underlying session and distribution information before replacing it. Restrict access to confidential records and share only the material necessary for the recipient’s review. Preserve relevant records when a dispute is anticipated; do not delete the history to make the incident appear smaller.

Prepare a One-Page Handoff

Summarize the work, rights claimed, observed conduct, dates, affected URLs, strongest supporting files, known gaps and requested action. Keep accusations no broader than the evidence. Attach a numbered index instead of an unexplained collection of images. Use the notice guide for a focused request, and the memorization guide when the proposed technical explanation needs testing.

Frequently Asked Questions

Do I need a copyright registration certificate?

Copyright protection generally arises automatically for qualifying works. Registration can still be useful evidence and documentation.

Are screenshots enough?

They can be important, but stronger evidence usually includes complete context, timestamps, URLs, account information and original files.

Should I contact the AI company immediately?

First preserve the evidence. Then send a focused notice through the most appropriate channel.

Official Sources

Important: This article provides general educational information about Philippine law and technology. It is not legal advice and does not create an attorney-client relationship. Laws, agency procedures, platform terms and the facts of each situation may change the result. Verify current requirements through the cited official sources and seek qualified professional advice when your rights, deadlines, money or legal exposure may be affected.

Featured image: Photo by Melinda Gimpel via Unsplash.

What Evidence Should Copyright Owners Preserve for AI Infringement?