Removals and takedowns
The public removal portal, the deadlines each kind of request carries, and how to respond to one.
Anyone who appears in content covered by Easy2257 can request its removal without an account, at /report/removal.
For someone requesting removal
You do not need an account. You do not need a lawyer. The form asks for six things:
- Your name and your email address.
- How you are connected to the content: it depicts you, you represent the person it depicts, or you are their guardian.
- The basis for the request. If you are not sure which applies, choose Other; the request is still reviewed.
- The web address of each piece of content, one per line.
- What you are asking for, in your own words.
A phone number is optional. When you submit, the confirmation screen shows a reference ID and the date by which the request must be handled. Save the reference ID. It is how you follow up on the request, and it is not emailed to you.
Every request is reviewed by the compliance team. You will not be asked to prove anything before the request is accepted; the review happens on the other side.
The deadlines
Not every request is on the same clock. The deadline is set the moment the request is submitted, and it is shown on the confirmation screen.
| Basis of the request | Deadline | How it counts |
|---|---|---|
| Federal NCII (Take It Down Act) | 48 hours | Calendar hours. Weekends and holidays count. |
| State NCII law | 72 hours | Calendar hours. Weekends and holidays count. |
| DMCA takedown | 7 business days | Weekends excluded. |
| Card network compliance (AN 5196) | 7 business days | Weekends excluded. |
| Other | 7 business days | Weekends excluded. |
The clock starts at submission, not at first review. Nothing pauses it.
As a deadline approaches, the owner of the production named in the request gets warning emails during the final six hours. A request still unhandled when its deadline passes is escalated automatically, and it is recorded as an SLA breach in that month's acquirer report. Handling a request late does not undo the breach; the report counts requests actioned after their deadline the same way.
Responding to a request
Requests naming one of your productions appear under Removal Requests in the compliance section, with the claimant's details masked.
- 1
Find your deadline
The list is sorted by deadline, nearest first, with a countdown on each request. An NCII request gives you 48 or 72 real hours, so treat one as today's work, not this week's.
- 2
Establish what is being asked
Each request shows its basis, the content addresses the requester listed, and their description of the claim. Read the description before acting; the basis chosen on a form is not always the basis that fits.
- 3
Act
Review the request and either action it or deny it. Actioning a removal revokes the production's compliance certificates, so downstream copies of the certificate stop verifying. Denying records your decision without touching the production.
- 4
Record the outcome
The action and its timestamp are recorded against the request. This record is what your acquirer report is built from, and in a dispute it matters as much as the action itself: it is the difference between "handled, on this date, inside the deadline" and an open question.
For requests you believe are wrong: deny them and record why. Denial is a recorded decision, not a dismissal, and it does not stop the clock while you reconsider. If the requester disagrees, the request can be escalated and reviewed again with your notes on it.
Still stuck?
Tell us what you were looking for and we will work it out with you.