> ## 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.

# Security FAQ

> Common questions about how Tachyon protects user data and funds.

<AccordionGroup>
  <Accordion title="Can Tachyon (the organization) see my users' transaction details?">
    No. Intent contents are end-to-end encrypted. Only the user (via their viewing key) and the specific solver assigned the intent can read it. The organization holds no plaintext access.
  </Accordion>

  <Accordion title="Is this like a mixer or tumbler?">
    No. Mixers obfuscate by pooling funds, which can complicate compliance. Tachyon uses confidential intents with [selective disclosure](/concepts/compliance), each transaction is private from the public but verifiable to designated counterparties.
  </Accordion>

  <Accordion title="Who can see a given intent?">
    Only the user (via viewing key), the assigned solver (only the contents needed to fulfill that intent), and any addresses the user designated as viewers at submission time.
  </Accordion>

  <Accordion title="What if I forget to add an auditor as a viewer at submission time?">
    Use post-hoc records. The user can call `tachyon.user.exportRecord` (or `exportRecords`) to produce a verifiable disclosure for any past intent and share it with a counterparty out of band. See [viewing permissions](/guides/viewing-permissions).
  </Accordion>

  <Accordion title="What chains are supported?">
    See the up-to-date list at [supported chains](/concepts/supported-chains). Direct support is expanding; chains not directly supported can be reached via Near Intents and Relay before the confidential leg.
  </Accordion>

  <Accordion title="Are large transfers safe?">
    The protocol is built for production use. While on testnet, do not move real value. Once mainnet launches, transfer-size limits and recommended practices will be documented per [rate limits](/reference/rate-limits).
  </Accordion>

  <Accordion title="Can a viewer drain a user's wallet?">
    No. Viewing access is strictly read-only. Viewers cannot initiate transfers, modify transactions, or move funds in any way.
  </Accordion>

  <Accordion title="How does Tachyon prevent front-running on TWAP?">
    Per-tranche amounts, schedule, and total order size are confidential. The market never sees the parent order or upcoming tranches, only stealth-address fills on the destination chain, with no link between them.
  </Accordion>

  <Accordion title="What happens to user funds if Tachyon goes offline?">
    An on-chain escape mechanism lets users withdraw funds without any Tachyon-operated infrastructure. There is no scenario where outage causes funds to be locked indefinitely.
  </Accordion>

  <Accordion title="Is the privacy quantum-safe?">
    The protocol uses hybrid cryptography designed to resist both current and future (including quantum) attacks.
  </Accordion>

  <Accordion title="How do I report a security vulnerability?">
    Email [sudeep@tachyon.pe](mailto:sudeep@tachyon.pe). Please do not open public GitHub issues for security bugs. See [security overview](/security/overview).
  </Accordion>
</AccordionGroup>

<Card title="Security overview" icon="shield" href="/security/overview">
  Properties Tachyon stands behind, in plain language.
</Card>