The rules of the road for contributors, buyers, and stakers on VEIL.
Plain-language terms. Anything technical is enforced on-chain by the programs listed in /docs — this page describes the human side.
By installing VEIL Connect, calling VEIL Query, staking VEIL, or otherwise interacting with the network, you agree to these terms. If you do not agree, do not use the network. This page is maintained by the VEIL project and may be updated; material changes are announced through governance.
The network recognizes six roles: data contributors, quality validators, cohort curators, VEIL stakers, privacy auditors, and referrers. Buyers of aggregate insight are a separate class governed by section 5. Each role's rewards and duties are defined by the on-chain programs (ConsentRegistry, ContributorRegistry, QueryRouter, PaymentSplitter, VEILStaking, Governance).
You represent that data you contribute is generated by devices you own or are authorized to bind, and that you have the right to grant the consent scopes you activate. You may revoke consent at any time; revocation removes you from in-flight and future queries. Raw data never leaves your device readable — VEIL cannot recover data you have not sealed and sent.
Data is encrypted on-device to rotating enclave public keys. Computation runs only inside attested TEEs (NVIDIA CC / AMD SEV) and, for sensitive queries, is trust-split across Arcium-style MPC nodes. Individual records are never persisted after aggregation. Differential-privacy noise is applied inside the enclave before any output leaves.
Buyers receive aggregate, differentially-private results, contributor counts, an attestation hash, a DP proof, and a consent proof. Buyers may not attempt to re-identify contributors, correlate results across queries beyond the disclosed composition budget, or resell raw outputs without written permission. Queries below the k-anonymity floor (default 25) are rejected outright.
Query revenue splits automatically: 60% contributors (pro-rata), 20% compute nodes, 10% stakers, 10% treasury with a burn slice. Contributor payouts may settle via Confidential Balances (Token-2022) at the contributor's option. Nothing on this page is investment advice or a promise of yield.
You may not: (a) attempt to bypass consent enforcement or the k-anon / epsilon floors; (b) submit spoofed or synthetic data as human contribution; (c) use the network to build individual profiles; (d) violate applicable law in the buyer's or contributor's jurisdiction; (e) impersonate an auditor or use auditor keys without authorization.
Parameters that affect contributor safety — allowed categories, approved buyers, epsilon floors, treasury allocation — pass through staker governance with 7 to 21-day timelocks. These terms may be amended by governance proposal; the amended version supersedes prior versions from the block it executes.
The network is provided on an as-is, as-available basis. To the maximum extent permitted by law, the VEIL project disclaims all implied warranties. Nothing here waives rights that cannot be waived under mandatory local law.
For legal notices, use the disclosure address listed in /docs. For security reports, follow the vulnerability disclosure process at /compliance. For consent questions, see /consent-framework.
