> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tachyon.pe/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance and selective disclosure

> Confidential by default, auditable on demand. How integrators layer compliance on top of Tachyon's viewing-key model.

Tachyon is built so that confidentiality and compliance don't compete. Intents are private by default, and your users (or you, on their behalf) can grant **scoped, verifiable visibility** to specific counterparties, auditors, regulators, accountants, without making anything public.

## The model in one paragraph

Every intent is encrypted end-to-end. Only the user's viewing key can decrypt it. The user can then either reveal a single intent, a date range, or a set of intents to a designated counterparty. The counterparty receives a verifiable record. Nothing about this disclosure is published on-chain, and disclosure is **scoped**, granting visibility to one transaction does not grant visibility to others.

<Info>
  Tachyon never holds a user's viewing key. Disclosure is always something the user (or the integrator on their behalf, with their key material) initiates.
</Info>

## What you can disclose

<CardGroup cols={2}>
  <Card title="A single intent" icon="file">
    Show a counterparty the exact contents of one transaction, amount, recipient, settlement hash.
  </Card>

  <Card title="A range of intents" icon="calendar-range">
    Hand an auditor the full set of intents for a quarter, or a specific account.
  </Card>

  <Card title="A summary" icon="chart-pie">
    Provide aggregate totals (e.g., total inflow, total outflow) without exposing individual intents.
  </Card>

  <Card title="Proof of receipt" icon="receipt">
    Give a counterparty a verifiable receipt for a payment they expected to receive.
  </Card>
</CardGroup>

## How it fits with KYC and sanctions screening

Tachyon does not perform KYC at the protocol level. Integrators apply their own compliance layer **before** signing an intent, for example:

* Verify the user's identity at onboarding
* Screen the recipient address against sanctions lists
* Apply per-transaction or daily limits

Once an intent is signed and submitted, the protocol enforces only the cryptographic and accounting rules. Compliance posture is your product's responsibility; Tachyon ensures that confidentiality doesn't prevent you from honoring it.

<Warning>
  Tachyon cannot block or reverse a settled intent. KYC and sanctions checks must happen before submission.
</Warning>

## Configurable disclosure by use case

<AccordionGroup>
  <Accordion title="Payroll disbursements">
    Keep individual contributor amounts confidential from each other and the public. Grant viewing access to HR or external auditors so they can verify the full payroll without amounts becoming public knowledge.
  </Accordion>

  <Accordion title="Cross-chain treasury transfers">
    Move funds across chains without exposing volumes to competitors. Grant a compliance officer scoped viewing access to verify that transfers respect reporting thresholds or sanctions policies.
  </Accordion>

  <Accordion title="TWAP and algorithmic execution">
    Execute schedule-driven orders without leaking strategy. Risk managers retain full visibility into execution details internally while the market sees only fresh stealth-address activity.
  </Accordion>

  <Accordion title="Tax reporting">
    Users can export a verifiable record of all intents in a tax year using their viewing key, without making the data public on-chain.
  </Accordion>
</AccordionGroup>

## What Tachyon does not control

* Tachyon cannot read intent contents and so cannot produce compliance reports on a user's behalf.
* Tachyon cannot add or remove viewers after submission. If a counterparty needs visibility into a future intent, the user must grant access at submission time or share via their viewing key afterwards.
* Tachyon cannot freeze, block, or reverse settled intents.

This is by design: your compliance posture does not depend on Tachyon's availability or cooperation.

<Card title="Set up viewing permissions" icon="eye" href="/guides/viewing-permissions">
  Walk through granting auditor access at intent submission time.
</Card>