Contributor KYC Verification
Identity verification is required before any DIU earnings become eligible for settlement to USD. It protects contributors from fraud, keeps one verified human per account, and is designed to support the platform's regulatory obligations.
Why KYC is required
Only verified contributors can earn and settle DIU to USD — unverified accounts are blocked from payouts.
One verified human per contributor account prevents Sybil attacks, wash earning, and identity gaming.
Fraud, sanctions, and risk screening protect the integrity of the settlement layer.
The verification workflow is designed to support GDPR data handling requirements. The SOC 2 Type II audit is a planned independent audit milestone and has not yet been completed. HIPAA-related controls apply when supporting regulated healthcare workloads.
Required for verification
Government-issued ID
A valid passport, driver's license, national ID card, or residence permit. The document must be unexpired and clearly legible.
Biometric face match
A live selfie capture is compared against the photo on your ID document to confirm you are the document holder.
Liveness confirmation
A real-time liveness check confirms the face capture is a live human, not a photo, video, or digital replica.
Privacy guarantees
Encrypted at rest and in transit
All identity data is encrypted end-to-end throughout the verification flow.
No raw PII in audit logs
Audit logs store only verification outcomes and timestamps — never raw identity documents or biometric data.
Used only for verification
Identity data is used solely for contributor verification, fraud prevention, and payout eligibility — never sold or shared.
Minimum retention
DOSFI retains only the minimum verification metadata required for compliance and payout eligibility. Original identity documents are retained only as required by the verification provider and applicable law.
No IP or device tracking
IP addresses, device identifiers, and routing metadata are never collected, stored, or transmitted.
Session-isolated
All interactions are isolated to the current session and governed by controls designed to support SOC 2, HIPAA, and GDPR.
No IP Leakage · No Sensitive Information Exposure
MeshNativeExchange operates under strict no-IP-leakage and no sensitive information exposure rules. All contributor data is treated as confidential and ephemeral.
Contributor IP addresses are never collected, stored, displayed, or transmitted.
Device fingerprints, hardware IDs, and device metadata are never collected or stored.
Node metadata and routing information are never embedded in payout, verification, or dashboard output.
Contributor interactions are isolated to the current session. Data is discarded after verification unless legal retention is required.
Identity details beyond what the contributor explicitly provides during KYC are never inferred or revealed.
The verification workflow is designed to support GDPR data handling requirements. The SOC 2 Type II audit is a planned independent audit milestone and has not yet been completed. HIPAA-related controls apply when supporting regulated healthcare workloads.
Compliance standards
Controls are designed to support these frameworks; certification is not claimed.
Log in to start verification
You need an account to submit KYC verification and become eligible for payouts.
Log in