Fraud prevention
Reduce the risk of unauthorized reports.
Identity verification
Some takedown or reporting workflows may require proof that you are the person shown, the rights owner, or an authorized representative.
Baseline service may not require ID verification. This page remains useful for workflows that later require proof of authority.
Why verification matters
Verification can help prevent abuse of the takedown process and support legitimacy where a platform or host requires proof.
Reduce the risk of unauthorized reports.
Show that the customer or representative can request action.
Some platforms may require identity or ownership proof.
Agencies may need documented authority for managed clients.

When required
The baseline service may not need identity verification, especially if payouts and partner KYC are handled elsewhere. Use it only when the workflow requires it.
A host or platform may require proof.
Agencies may need authority documentation.
Escalation may require additional confirmation.
Support may need more context before action.

Provider flow
Do not collect ID documents in ordinary reference uploads.

Tell the customer what requirement triggered verification.
Use a dedicated provider or approved secure process.
Store only the verification status needed for workflow decisions.
Proceed with notice or reporting only where authorized.
Privacy
If verification is ever added, final copy must explain what is needed, who processes it, what is stored, how long it is retained, and how the customer can ask questions.

Contact support before uploading sensitive documents anywhere.