Compliance
Private settlement that still respects your compliance programme.
Your institution runs KYC, screening, and a compliance policy. Tenebrae Protocol checks that policy is satisfied in every settlement proof at submit.
Two layers. Your institution decides who may operate. Tenebrae Protocol verifies policy at submit.
Architecture for diligence — not a market-licence claim. Ceiling: Stack · FAQ. Job-level boundaries: Use cases.
Two layers
KYC · screening under your compliance policy — before submit.
Compliance policy verified on-chain in every settlement proof.
What you own · what Protocol verifies
| Surface | Owner | At submit |
|---|---|---|
| KYC | Institution / partner | Remains with institution |
| Screening | Institution today | Vendor KYT — roadmap |
| Compliance policy | Institution | Verified in every operation |
| Settlement privacy | Tenebrae Protocol | Client-side zero-knowledge proofs |
| Deposit / withdraw | Public by design | Amounts remain visible on-chain at the public boundary |
Responsibilities stay with the integrating product
Tenebrae supplies the private settlement layer. It does not replace the integrating product’s licence, wallet or custody model, employment or payroll obligations, customer records, or regulatory programme.
| Context | Institution / partner keeps | Tenebrae provides |
|---|---|---|
| Treasury / B2B | Approvals, accounting, upstream screening | Private bilateral settlement after public funding |
| Fintech and vault products | Brand, KYC, card/on-ramp rails, customer ledger | Confidential settlement between public entry and exit |
| Post-payroll privacy | Employment, payroll KYC, public payout | Optional worker-initiated private settlement after payout |
| Batch private disbursement | Recipient policy, screening, programme records | Roadmap multi-recipient orchestration — not shipped |
Tenebrae does not silently capture payroll or other funding rails. Workers and institutions retain control of signing wallets. Detail: Post-payroll privacy · Vaults.