Trust Center
Scoped verification design
Verification API designed to return credential trust metadata — not raw offense labels, full criminal histories, or unnecessary provider webhook payloads.
Who this is for: Platform engineers, privacy officers, and compliance teams designing least-privilege verification flows.
Before · over-exposure
Raw payloads spread across email, spreadsheets, and vendor exports.
After · scoped trust state
Credential status, consent, and audit events — only what the decision needs.
Why verification APIs over-collect data
Many screening integrations return full report payloads to platforms that only need a trust decision — creating storage, breach, and compliance risk.
Workers lose control when offense text propagates to every platform that runs a check, even when a simple active/expired status would suffice.
MyFairCheck minimization workflow
Worker report-first review
Workers see full report context in their portal — not via platform API.
Credential issuance
Worker chooses when to share MyFairPass trust state.
Scoped verification
API returns status, check age, IDV, consent, and review-support summary only.
Audit without payload
Verification events logged without storing offense text on platform side.
Benefits
What you gain in a controlled pilot
- Reduced raw record exposure in platform systems
- Worker-controlled credential sharing
- Structured verification response schema
- Audit events without offense payloads
- QR and API paths return the same scoped fields
API schema documentation
See Resources → API & Verification Overview for scoped field definitions.
Not zero risk
Data minimization reduces exposure — it does not eliminate all compliance obligations.
Example
Fictional platform verification scenario
A gig platform calls the verification API for MFP-SAMPLE-00001. The JSON response includes credential_status: active, check_age_days: 45, idv_status: verified, consent_version: 2026.1 — and explicitly excludes offense_text and provider_payload fields.
What we do not claim
MyFairCheck does not claim SOC 2 Type II certification, Clean Slate certification, FCRA legal compliance, or final legal certification. Production use requires counsel and security review.
MyFairCheck supports FCRA-aware workflows, but it does not provide legal advice or certify compliance. Production use requires counsel and security review.
Request pilot access
Join the controlled 2026 pilot with workflow support — not legal certification.