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.
Technical Capabilities
Overview
The DIU Attribution Engine processes usage events and calculates DIU splits across all contributors. It enforces KYC payout eligibility, blocks attribution for quarantined accounts, and maintains an auditable ledger of all DIU distributions.
Workflow Summary
Usage event ingestion, KYC eligibility check, DIU split calculation, attribution recording, and ledger update.
State Machine
States: receiving → verifying → calculating → attributing → settling. Blocked for non-eligible accounts.
Routing Policy
Operates on governance-tier nodes. All attribution is metadata-only with no PII.
Sandbox Preview
· Test safely, no infrastructure exposedSend a test input to preview how DIU Attribution Engine responds. All execution is isolated — no real routing, storage, or DIU settlement occurs.
Version History
SubZero Governance
View publisher profile →
