How it works
From catalog upload to filed takedown in 4 steps.
DSP Watch closes the loop between detection and action. You import your catalog once. We scan 6 DSPs on a tier-weighted nightly cadence, surface only the findings worth working on, and ship a §512(c)(3)-verbatim takedown through the adapter that fits the host. The counter-notice clock is tracked end to end.
Step 01
Upload your catalog
Import once, drift never.
- Send a CSV with ISRC, UPC and the ownership proofs DSPs ask for (rights chain, distributor receipts, master licence, signed split sheets).
- DSP Watch normalizes metadata, deduplicates across releases and binds every track to its rightful workspace under Postgres row-level security.
- After import, our reconcile job re-syncs nightly with your distributor's catalog feed so changes (new ISRCs, withdrawn releases, label transfers) never silently drift out of scope.
Step 02
Nightly scans across 6 DSPs
Tier-weighted — high-priority artists scanned daily, cold tier monthly. MusicBrainz + DSP search APIs.
- Spotify, Apple Music, YouTube, Tidal, Deezer and Amazon Music are queried with ISRC, UPC and a fuzzy metadata pass tuned for title/artist/duration drift.
- MusicBrainz cross-reference and DSP search APIs catch the long tail — re-releases under altered artist names, transliterations and karaoke covers that try to evade ISRC matching.
- Tiering routes scan budget: tier-A catalog (your top 5% of streams) gets a 24h cadence, tier-B every 72h, cold tier monthly. You set the tier rules; the scheduler obeys.
Step 03
Findings sorted by actionability
Hard signal gate keeps the noise out. Only ISRC, UPC or fingerprint matches gate actionability above 0. Fuzzy matches sit at 0 until you verify.
- Every finding is scored 0–100 by detection confidence, distributor mismatch, evidence completeness and urgency — so the top 5% of cases bubble to the top of the queue.
- Hard signal gate: a finding only crosses actionability 0 once an ISRC, UPC or audio fingerprint matches. Fuzzy-only matches stay at 0 and sit in the explorer until a human confirms.
- Findings ≥ 80 auto-queue for one-click review, 50–79 flag for analyst attention, sub-50 stay quiet for context. Your inbox shows what's worth working on today, not every noisy near-miss.
Step 04
One-click takedown with court-ready evidence
Pick an adapter, review the §512(c)(3)-verbatim package, hit Submit. The counter-notice clock starts. We warn you at T-3 days.
- Choose from 5 adapters — dmca_generic, spotify_form, apple_form, youtube_cid, distributor_forward — and the evidence bundle attaches itself automatically.
- Review the §512(c)(3)-compliant PDF (all 6 statutory elements, hash-chained audit log, signer attestation under MFA freshness), then submit. The case or claim ID is captured on the response.
- We start the §512(g) counter-notice clock the moment a counter-notice lands and fire action.counter_notice_warning at T-3 business days so legal never misses the reinstatement window.
Behind the scenes
What happens when a finding lands
Every candidate match passes through the same 5-stage pipeline before it ever reaches your inbox. The pipeline is deterministic, replayable and hash-chained, so the path from raw scan to actionable finding is auditable end to end.
-
Stage 1
Detect
The DSP scanner returns a candidate match and tags it with the signal type (ISRC, UPC, fingerprint or fuzzy).
-
Stage 2
Group
Candidates are grouped per offending release so a 12-track unauthorized upload becomes one finding, not 12 duplicates in your inbox.
-
Stage 3
Score
The actionability scorer combines detection confidence (0.35), distributor mismatch (0.25), evidence completeness (0.25) and urgency (0.15) into a 0–100 score.
-
Stage 4
Enqueue
Findings ≥ 80 land in the one-click action queue. 50–79 flag for analyst review. Sub-50 sit in the explorer.
-
Stage 5
Notify
An outbound webhook (finding.created) fires to your ops stack, and queued findings appear in the in-app inbox with a Slack-style unread badge.
Your role
What you do
Three actions, in this order. Most queued findings clear in under 90 seconds of analyst time because evidence completeness is already 100% by the time you arrive.
-
Action 1
Triage in inbox
Open the inbox, sort by actionability, and clear the top of the queue. Confirm or dismiss fuzzy-only candidates that need a human eye.
-
Action 2
Build evidence
Confirm the rights basis, attach any missing proof (only needed when evidence completeness < 100%), and re-authenticate with MFA before signing.
-
Action 3
File action
Pick the adapter that matches the host, review the generated §512(c)(3) PDF, attest and submit. The action timeline tracks every state change to resolution.
Start your trial.
14 days free. Import a catalog, see real findings in the first nightly scan, and ship your first §512(c)(3)-compliant takedown before the trial ends.