Product
Structured intelligence for affiliate due diligence.
Clawback Registry consolidates documented incidents, business relationships and statements into one structured source for affiliate due diligence and risk assessment.
Relationships
Incidents
Resolved
Incident
EvidenceStatement
Process
Five steps, each one traceable
Operators query and document, reviewers check, and the party concerned can respond. A tutorial in the account guides new users through the first steps.
Exact lookup
Enter a single identifier, such as a domain or channel name, and state the purpose of the check.
Business relationship
For each cooperation you record the start, the end and the contract type. Only an operator with a documented relationship can report an incident or submit a rating about that party.
Incident with evidence
An incident requires at least one piece of evidence and a factual description. A wording check blocks insults, assumptions and judgments.
Review
Evidence and wording are checked before publication. For large amounts and compliance topics, a second review is required.
Statement
The party concerned can respond without an account. The statement appears right next to the incident, and only its wording is checked.
Data model
Four kinds of information
All information is tied to a documented business relationship.
Business relationships
Parties, start, end and contract type. Every incident and every rating belongs to a documented relationship.
Incidents
Documented points of dispute with type, date, supporting evidence and optionally an amount. Several brands of one operator count once.
Statements
The response of the party concerned, optionally with acknowledged and disputed amounts, displayed next to the incident.
Ratings
Operators with a documented relationship rate along a fixed question catalog. The register shows the average across independent operator groups, without operator names.
Incident types
Documentable incidents
Every incident belongs to a documented relationship, carries at least one supporting document and is described factually.
Dispute about a payment: amount, due date or non-payment.
Dispute about the content, term or termination of an agreed cooperation.
Chargeback, or a claim to return amounts that were already paid out.
Dispute about whether delivered traffic meets the agreed requirements.
Dispute about compliance with agreed or legal requirements, for example on advertising or target markets.
Another documented point of dispute that fits none of the other types.
Accepted evidence includes contracts, invoices, platform exports, proof of payment and correspondence. The reporting operator can withdraw an incident and keep its resolution status current.
Custom review logic
Risk status only by your own rules
In your settings you define review logic for your organization. It is off by default and nothing is preset. A risk status results solely from your own rules, is always labeled as the result of your rule and is visible only to your team. As a starting point there is the “Clawback Standard” template, which you adopt with one click and then adjust freely.
If no rule applies, no risk status is shown, and that is not a clearance. Commercial and risk decisions remain with the operator.
Examples of freely chosen rules, not a recommendation
- Risk status yellow if at least one published payment dispute exists
- Risk status red if at least two incidents are open and the latest was less than 90 days ago
- Risk status yellow if at least two operator groups have reported an incident
Lookup
One lookup, one exact identifier
The register is not a list and cannot be browsed. A result appears only on an exact match.
Exact identifier
Domain, email address, company name, payout account, wallet, Telegram name, Twitch or Kick channel name, or a profile on YouTube, Instagram, TikTok, X or Linktree.
Purpose and logging
Each lookup requires a stated purpose: before a cooperation, review of an existing relationship, or compliance review. Every lookup is logged, a daily limit applies per user, and a monitor flags attempts to probe the register.
Result without attribution
The reporting operator is never named. A missing entry does not mean that nothing has happened.
Add documented affiliate intelligence to your due diligence
Access is by invitation. Each operator is verified individually before access is enabled.
Request access