1. Correction request types (8)
Eight correction_type values from PART 3 §10.3 are operated in v1.
| Type | Meaning | First reviewer | Default priority |
|---|---|---|---|
| factual_error | Factual error (birth date, affiliation, works) | Data Operator | normal |
| photo_replacement | Photo replacement (copyright, inappropriate image) | Data Operator | normal |
| remove_from_cluster | Detach from issue cluster (incorrect grouping) | Trust & Safety | normal |
| score_dispute | Dispute about the score | Algorithm Operator | normal |
| risk_classification_dispute | Dispute about Risk Watch classification | Risk Operator + Senior | high |
| data_takedown | Full data removal / suppression | Senior Admin + legal | urgent |
| duplicate_entity | Consolidate duplicate registrations | Data Operator | normal |
| alias_correction | Alias / romanization correction | Data Operator | low |
2. SLA by priority
The SLA clock starts at submitted_at and runs 24/7.
| priority | First response | First result notice | Completion |
|---|---|---|---|
| urgent | 4 hours | 12 hours | 24 hours |
| high | 8 hours | 24 hours | 48 hours |
| normal | 24 hours | 48 hours | 72 hours |
| low | 48 hours | 72 hours | 7 days |
SLA extensions are allowed only for stated reasons (external legal review, awaiting more info, algorithm recompute). Extensions require advance notice to the requester.
3. Celebrity legal-representative verification
Requests from celebrities or their legal representatives go through a verification process.
- Step 1 (paperwork): notarized seal + power of attorney + business card or business registration
- Step 2 (verification): reply with the case_id from the law office's official email (anti-phishing)
- Step 3 (agency confirmation — optional): cc the celebrity's agency's official email
Celebrity-side requests are automatically assigned priority='urgent' (24-hour SLA). Takedown requests are processed via the staged response procedure.
4. Media-side requests
Verified via the outlet's corporate email (e.g., @hani.co.kr) and a business card.
- Source attribution correction → update media_sources master and recompute scores
- Article data suppression → individual article suppressed=TRUE or outlet-wide credibility 0
- Detach own article from cluster → remove from issue_clusters
- Dispute outlet-credibility evaluation → Algorithm Operator review, master adjustment if warranted
5. Standard rejection codes (8)
| Code | Natural-language reason |
|---|---|
| INSUFFICIENT_EVIDENCE | The submitted evidence is insufficient. Please resubmit with additional materials. |
| FACTUAL_VERIFIED_NO_CHANGE | Your request was reviewed but the current information matches a verified source. |
| OUT_OF_SCOPE | The request is outside the Backers100 correction policy. |
| ALGORITHM_NOT_DISPUTABLE | Algorithm scores are computed outputs and are not subject to corrections. |
| DUPLICATE_REQUEST | A previous request on the same matter has already been processed. |
| THIRD_PARTY_DISPUTE | This is a third-party dispute that Backers100 cannot adjudicate on its own. |
| LEGAL_PROCEEDINGS_PENDING | Relevant legal proceedings are ongoing. |
| IDENTITY_VERIFICATION_FAILED | Legal-representative status could not be verified. Please resubmit with the required documents. |
6. Request form
7. Submission channels
- Correction requestsSupport@backersby.com
- Security incidentsSupport@backersby.com
- General inquiriesContact@backersby.com