> For the complete documentation index, see [llms.txt](https://docs.useprivatus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.useprivatus.com/privacy-and-confidential-transfers/selective-disclosure.md). # Selective Disclosure & Audit Export Confidentiality is not the same as unverifiability. Privatus turns disclosure into a precision instrument: prove specific transactions to specific parties, on your terms, without exposing a single byte of the rest of your financial history. *** ## View keys: read without spend Disclosure in Privatus is built on view keys. Your balance decryption key is separate from your spending key, so you can grant read-only access to encrypted data without ever putting funds at risk. A view key can decrypt; it can never sign. This separation is what makes every disclosure mechanism below possible while custody stays entirely in your hands. *** ## Selective disclosure proofs A selective disclosure proof lets you reveal the amount of a single transaction to a chosen recipient, cryptographically signed so the recipient can trust it wasn't fabricated. You choose what to reveal, to whom, and nothing more. Typical uses: * Sharing a specific payment with a landlord, employer, or counterparty who needs proof of payment * Responding to a request from a tax authority or auditor for a specific transaction * Satisfying a Travel Rule counterparty screening requirement (see [KYC & Travel Rule](/compliance/kyc-and-travel-rule.md)) ### How it works 1. Open the transaction in your feed and select **Generate disclosure**. 2. Choose what to disclose: the amount only, or the amount plus a memo. 3. Privatus generates a proof, signed by your account key, that decrypts and attests to that specific transaction's details. The proof is checkable against the ciphertext recorded on Solana, so the recipient can verify it against the chain, not against Privatus's word. 4. Share the resulting disclosure link or export file with the intended recipient. No other transaction in your history is exposed by this process. The proof is scoped to exactly the transaction you selected, and nothing else. For ongoing oversight, such as an auditor who needs continuous read access to an account, you can instead issue a scoped view key and revoke it when the engagement ends. *** ## Audit export For tax season or bookkeeping, you can export your full decrypted transaction history in one action. * Available from **Settings → Export → Transaction History** * Produces a CSV or JSON file with decrypted amounts, timestamps, counterparties, transaction signatures, and memos * Compatible with major crypto tax tools (Koinly, TokenTax, CoinTracker) This export happens entirely client-side. Your device decrypts your own history using your own view key and writes the file locally. Privatus's servers never see the decrypted export, because they never can. *** ## What Privatus never does * Privatus does not decrypt your transactions on your behalf for a third party. Any disclosure must be initiated and signed by you. * Privatus does not maintain a plaintext copy of your transaction history on its servers. * Privatus cannot generate a valid disclosure proof without your keys. This is a structural impossibility, not a policy: it cannot do this on your behalf even if compelled to try. *** ## Regulatory context This mechanism is what allows Privatus to operate under the "confidentiality, not anonymity" model described in [Regulatory Framework](/compliance/regulatory-framework.md). Your identity is verified at account creation through standard KYC where your tier requires it. Your addresses are public. Your transaction amounts are private until you choose to disclose them, or until compelled by lawful legal process directed at you as the account holder. *** ## Next * [KYC & Travel Rule](/compliance/kyc-and-travel-rule.md) * [Key Management & Custody](/privacy-and-confidential-transfers/key-management.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.useprivatus.com/privacy-and-confidential-transfers/selective-disclosure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.