For sites, hosts & platforms
Safe harbor is a workflow,
not a paragraph in your TOS.
§512 protects providers who process notices properly: intake, validation, takedown, counter-notices, records. We run that machinery under your brand, a /notice/yourname page that only accepts legally complete submissions, with the full workflow behind it.
Unlimited notices on every tier · X-ARF export · API access on Pro.
What the law actually asks
Four duties, one dashboard
1. A designated agent on file
Registered with the Copyright Office and listed in their public directory, the prerequisite everything else depends on. Our guide walks the filing; done once, renewed every three years (or seven under the current rule).
Register your agent →2. A working notice channel
A page and process the public can actually use. Your branded /notice/yourname intake validates §512(c)(3) elements on arrival, incomplete notices get guided to completion instead of dying in a spam folder.
3. Expeditious takedown
Valid notices result in removal or disablement, with the timestamps to prove the speed if safe harbor is ever challenged. Status tracking per notice; nothing lives in one person's inbox.
4. Counter-notice handling
The §512(g) dance is where providers fumble: restore in 10–14 business days if no suit, keep records, don't tip off badly. The workflow is built in, included on every tier, not an upsell.
The counter-notice timeline →Plus the duty nobody reads: a repeat-infringer policy that's actually enforced, the clause that cost Cox Communications its safe harbor in BMG v. Cox.
The machinery
What running notices looks like here
- 1
Your branded intake page goes live
/notice/yourname, public, linked from your footer, styled to your site. Notices arrive structured, not as freeform emails.
- 2
Validation at the door§512(c)(3)
§512(c)(3) elements checked on submission: work identification, location, contact, good-faith statements. Invalid notices get guidance; valid ones proceed.
- 3
Processing and tracking
Forwarding to the right property, takedown actions, per-notice status and timestamps, the expeditious-removal record, generated as you work.
- 4
Counter-notices and exports
The 10–14 day clock tracked automatically; X-ARF machine-readable export and API access feed your abuse tooling on Pro and above.
Pricing
Unlimited notices on every tier
Basic
1 property
- Branded intake page (/notice/you)
- §512(c)(3)-validated submissions
- Notice forwarding + status tracking
- Counter-notice workflow included
Pro
5 properties
- Everything in Basic
- X-ARF machine-readable export
- API access for abuse tooling
ISP
25 properties
- Everything in Pro
- Priority handling
- Built for hosts, ISPs & platforms
Half the typical incumbent program price ($10/$50/$250+), with counter-notices and X-ARF included rather than gated.
Compliance FAQ
What operators ask
The problem, precisely
Drowning in dmca@ is a policy risk, not just a chore
- • Invalid or incomplete notices consume staff time before anyone notices they are junk
- • Response timelines live in email threads, unprovable later
- • Repeat-infringer decisions rest on memory, not records
- • Counter-notices cause panic archaeology through inboxes
- • Validation at intake: incomplete notices get flagged, not filed
- • Every action timestamped on the notice record
- • Repeat-infringer history queryable per sender and per target
- • Counter-notice workflows with the statutory clock visible
What you get
Six things the program changes on day one
Notices arrive through a validated form, the statutory elements checked on arrival, instead of unparseable email threads your team has to hand-triage.
When a counter-notice lands, the original notice, the timeline, and the response window are in one place. No reconstructing history from forwarded emails.
Every notice is tracked from received to actioned with timestamps, the record that demonstrates a working repeat-infringer policy if you ever need to show one.
Notices export in the X-ARF abuse-reporting format, so security and abuse tooling can consume them without human re-entry.
List notices, update statuses, and automate routing through the same REST API your other tooling uses, signed webhooks included.
The intake page carries your branding at your URL, not ours, senders see your process, and your legal posture stays yours.
Who it is for
Built for the receiving end of notices
abuse@ volume is the daily reality; the program turns it into a tracked queue with validation at the door.
UGC platforms get structured notices and a repeat-infringer record without building intake tooling.
Forwarding and tracking obligations, met with a workflow instead of a spreadsheet.
Volunteer moderation teams get the statutory scaffolding handled; moderators decide, the program documents.
Sensitive-content notices need discretion and audit trails; both come standard here.
Each client property tracked separately, one dashboard, per-property quotas.
Safe harbor is earned in the handling, not claimed in the footer.
Branded intake, statutory validation, tracked workflow, from $5/month.