> For the complete documentation index, see [llms.txt](https://argon-4.gitbook.io/argon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://argon-4.gitbook.io/argon-docs/legal/privacy-policy.md). # Privacy Policy What Enclave keeps on your device, what leaves it and to whom, and what the software never does. **Effective date:** September 6, 2026 **Version:** 1.0 This Privacy Policy describes how the Enclave wallet software, including the SureSign signing kernel (the "**Software**"), handles information, and what the individual developer who publishes it under the name "argonmining" (the "**Developer**," "**we**," "**us**," or "**our**") does and does not do with information. It also covers this documentation site and our support channels. Capitalized terms not defined here have the meanings given in the [Terms of Service](/argon-docs/legal/terms-of-service.md). {% hint style="info" %} **The short version.** Enclave has no servers, no accounts, and no analytics. The Developer does not collect, receive, store, or process any information about you through the Software. Everything the Software stores stays on your device, encrypted where it is sensitive. To function, the Software sends your **public** addresses and the transactions **you** sign to the blockchain networks and public data services you choose, exactly as any wallet or block explorer does. Those services see your public addresses and your IP address. None of them, and not the Developer, ever receives your recovery phrase, private keys, password, or passkey. {% endhint %} ## 1. Scope This Policy applies to: * the Software, in every Official Build; * this documentation site; and * the support channels listed in Section 11. It does not apply to any Network or Third-Party Service the Software can reach. Each of those is operated by someone else under its own privacy practices, which you should review. The [Third-Party Services and Non-Affiliation Notice](/argon-docs/legal/third-party-services.md) identifies them. ## 2. The Developer collects nothing through the Software The Software is a program that runs on your device. The Developer operates no server, database, account system, telemetry endpoint, or backend for it. Accordingly, through the Software the Developer does **not** collect, receive, or have access to: * your recovery phrase, private keys, public addresses, balances, or transaction history; * your password, passkey, or any authentication credential; * your name, email address, phone number, government identifier, or any contact or identity information; * your IP address, device identifiers, location, or browsing history; * the websites you visit or the content of any web page; * usage analytics, telemetry, crash reports, performance metrics, or error logs; or * the content of any message you send. There is no "account" to create and nothing for the Developer to look up about you. If you write to us for support, we receive what you send us (see Section 8). ## 3. What the Software stores on your device The Software stores the following in your browser's extension storage on the device where it is installed. Nothing in this Section is transmitted to the Developer. | Data | Where and how | Notes | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Recovery phrase and private keys** | Encrypted vault in extension local storage. The vault is sealed with XChaCha20-Poly1305 under a key derived from your password with Argon2id, or from a passkey through the WebAuthn PRF extension and HKDF-SHA256. | Generated on your device. Never leaves the encrypted vault except into memory while the wallet is unlocked. Never logged. | | **Session key** | Memory only, while the wallet is unlocked. A single unlocked/locked flag is kept in extension session storage so the interface knows the state. | Discarded on lock, on the auto-lock timer (5 minutes by default; adjustable), or when the browser closes. | | **Public wallet records** | Extension local storage, unencrypted. | Public addresses and derivation indexes, address and Note labels, the local activity journal, vault and escrow records, Deal Desk conversation state, dApp connection permissions, custom node/indexer/Igra endpoints, display and privacy settings, and cached balances, token lists, and images. These contain no secrets. | | **Terms acceptance record** | Extension local storage, unencrypted. | The version of the Terms of Service you accepted, the time, and whether you accepted by creating, restoring, or unlocking a wallet. Nothing else; no identifier. Kept so the Software can tell you which version you accepted and show the notice again only when the Terms change. | | **Passkey** | Held by your authenticator (your device's platform authenticator, a hardware key, or a passkey manager), not by the Software. | If your authenticator syncs passkeys (for example, iCloud Keychain or Google Password Manager), that syncing is governed by the authenticator provider's policy, not by this Policy. The Software receives only the PRF output needed to derive the vault key, and only at unlock. | Uninstalling the Software deletes all of the above from that device. The Developer cannot recover any of it. Your Digital Assets remain on the relevant Network and can be restored in any compatible wallet from your recovery phrase. ## 4. What leaves your device, to whom, and why To read balances, show history, and broadcast the transactions you authorize, the Software communicates over the Internet with public blockchain nodes and public data services. The Developer operates none of them. Each receives, at most, the information in the table below together with your IP address and ordinary connection metadata, exactly as your browser sends when it loads any website. | Recipient (default endpoints) | Operated by | What is sent | Purpose | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Kaspa nodes** — `luna.kaspa.blue`, `muon-10.kaspa.blue` (or your own node) | Public community nodes; not the Developer | Your public addresses (to subscribe to balance changes); transactions you have signed | Reading balances and UTXOs, live updates, broadcasting your transactions | | **Kaspa REST index** — `api.kaspa.org`, `api-tn10.kaspa.org` | Kaspa community | Your public addresses; transaction ids you are tracking | Address history, confirmation tracking, finding your addresses when you restore a wallet | | **Token and name indexers** — `api.kasplex.org`, `tn10api.kasplex.org`, `api.knsdomains.org`, `insdomains.org`, `krc721-api.kat.foundation`, `krc721.kat.foundation`, `krc721-testnet.kat.foundation`, `krc721-tn10api.kat.foundation`, `kascov.io` | Kasplex; KNS Domains; INS Domains; KAT Foundation; kascov | Your public addresses | KRC-20 and KRC-721 balances, names you hold, covenant records | | **Igra EVM Layer** — `rpc.igralabs.com`, `galleon-testnet.igralabs.com`, `igra-node.kat.foundation` (or your own endpoint); `explorer.igralabs.com`, `explorer.galleon-testnet.igralabs.com`; `attester-dashboard.igralabs.com` | Igra Labs; KAT Foundation | Your Igra address; contract reads (`eth_call`) needed to quote an action; transactions you have signed. The attester dashboard receives nothing about you. | EVM Layer balances, token and collectible lists, transaction status, quotes; network statistics | | **Provider configuration and market data** — `api.katbridge.com`; `igra.zealousswap.com`, `cdn-zealous-swap.fra1.cdn.digitaloceanspaces.com`; `kaskad.live`, `testnet.kaskad.live`, `reactor.kaskad.live` | KAT Foundation; Zealous Swap; Kaskad | Nothing about you. These endpoints serve public configuration (bridge vault address, minimums, fees), token lists and logos, and market rates. Your positions and quotes are read from the Igra RPC, not from the provider. | Bridge parameters, token metadata, lending market data and contract addresses | | **KatPool** — `app.katpool.com` | KatPool | The mining address you enter on the Miners page | Pool statistics for that address | | **Markets discovery**: `api-defi.kaspa.com`, `api.kron.technology`, `idx.kron.technology` | KaspaCom; KRON | Public catalog and health requests do not include wallet information. Trade and liquidity quotes request the selected token and, when needed, the chosen trader address to locate token or LP Notes. Launch preparation checks public policy and symbol availability. If you choose to publish a launch, KRON receives the exact reviewed public metadata, creator public key and listing signature. No wallet secrets, cookies or credentials are sent. The services see your IP address and connection metadata. | Public Igra pair and Kaspa covenant token listings while Markets or token details is open. Market-listed logos also load automatically from their published image URLs; those hosts see your IP address and the image requested, but receive no wallet address, cookies or referrer. | | **Consensus names**: `api.dotk.name`, `api-tn10.dotk.name` | dotk | Requested names, receive and Desk owner addresses, and record-deposit lookup keys. No wallet secrets, cookies or credentials are sent. | Locate candidate names and public records. Bundled Rust programs and your Kaspa node verify the resulting ownership before use as a payment address. | | **Image and metadata sources** · `images.kat.foundation` (IPFS gateway), `kaspa-lens.com`, Igra explorer image URLs | KAT Foundation; kaspa-lens; Igra Labs | The content identifier or token of the image being fetched. This reveals to the gateway which collectibles or tokens you are viewing. | Token logos and collectible artwork. Images are fetched by the extension and rendered from a local copy; the extension's pages are prohibited by their content security policy from loading images directly from any remote host. Market-listed logos load automatically from their published URLs without cookies or referrers. The bounded decoder produces a local still image; signed genesis artwork also requires its digest to match. Other artwork whose address points at any host other than these pinned ones · for example a host named by a token's creator or an NFT's minter · is not fetched until you choose to load it for that specific token or collectible; that choice is stored on your device for that asset and host only. | | **CoinGecko** — `api.coingecko.com` | CoinGecko | Nothing about you | Public KAS/USD price for fiat display and for sizing the Developer Fee | | **WalletConnect relay** — `relay.walletconnect.org` and related `*.walletconnect.org` / `*.walletconnect.com` hosts | WalletConnect Foundation / Reown | End-to-end encrypted session messages, only after you pair a dApp; your public Igra address is shared with the dApp you paired | Connecting Igra dApps that use WalletConnect | | **Websites you connect** | The website operator | Your chosen public address, after you approve the connection; signatures, after you approve each request | dApp connections through the KIP-12 Kaspa provider or the Igra EIP-1193 provider | | **The Kaspa network itself (Deal Desk)** | No one; a public ledger | Messages between deal parties, encrypted to the recipient and signed by you; the sender and recipient addresses, timing, and size of each message are public | Coordinating escrow deals | | **Your own endpoints** | You | Whatever you configure | If you enter your own node, indexer, or Igra endpoint in Settings, the Software asks your browser for permission to reach that host and then sends it the data described above instead of the default. | Every recipient above sees your **public** addresses and your IP address. None receives your keys. The Software can only reach the hosts listed in its manifest and any host you explicitly add in Settings; your browser enforces that list. It ships no remote code. ## 5. What the Software never does * **No accounts, sign-ups, profiles, or identity verification.** * **No analytics, telemetry, crash reporting, A/B testing, advertising identifiers, cookies, or tracking pixels** of any kind, from the Developer or from any third party. * **No reading of web pages.** The small script the Software places on pages only lets a site ask to connect to your wallet. It reads no page content, holds no keys, and relays nothing you have not approved inside the Software. * **No selling, renting, sharing, or disclosing of information** — there is none to disclose. * **No use of any information for advertising, credit, lending, insurance, employment, or eligibility decisions.** * **No remote code.** Everything that runs ships inside the extension package. The signing kernel is WebAssembly bundled in the package. * **No communication with the Developer.** The Software has no endpoint belonging to the Developer to talk to. The only thing the Developer ever receives from your use of the Software is the Developer Fee, when you choose to sign a transaction that includes it, on the public Kaspa ledger. ## 6. Public blockchain data Blockchain networks are public ledgers. Any transaction you broadcast, any covenant you create, any name you register, and any Deal Desk message you send is recorded permanently and visible to anyone, together with the addresses involved. The Software cannot delete, hide, or alter anything once it is on a Network, and neither can the Developer. Address labels and Note names you create stay on your device and are not published unless you include them in a transaction payload. KRON curve and pool trades include `kron:r:enclave` in their signed Kaspa payload to attribute originating trading volume to Enclave. This public software tag adds no user or account identifier and does not add a separate wallet charge. Provider settlement is separate from the Enclave fee shown in the transaction review. If you reuse an address, anyone can link the transactions that use it. The Software's privacy defaults (fresh receive addresses, Note Management, and cluster visibility) help you avoid this, but they are tools, not guarantees. ## 7. This documentation site This site is hosted by GitBook, Inc. When you visit it, GitBook processes your IP address and standard web request data, and may set cookies, under its own privacy policy, available at [gitbook.com](https://www.gitbook.com). The Developer does not add any analytics or tracking to this site and does not receive visitor data from GitBook beyond what GitBook shows to every publisher in aggregate. ## 8. Support channels If you contact us, we receive what you send: * **Email** to : your email address, the content of your message, and any attachments. We use it only to respond to you and to fix the issue you report. We keep support correspondence for as long as needed to resolve the matter and for a reasonable period afterward for reference, then delete it. * **Direct messages** to @argonmining on X, Telegram, or Discord: processed by those platforms under their own policies. * **Feedback board** at [enclave.fider.io](https://enclave.fider.io/): posts, votes, and comments are public and are processed by Fider under Fider's privacy policy. Signing in to post uses the identity provider you choose there; we see the display name and email Fider shows us and use them only to follow up on your report. * **Beta group** on Telegram: messages are visible to the group's members and are processed by Telegram under Telegram's privacy policy. The group is for builds and discussion; bug reports belong on the feedback board. Never send your recovery phrase, private key, password, or passkey through any channel. We will never ask for them, and we cannot help you if you disclose them. ## 9. Chrome Web Store If you install the Software from the Chrome Web Store, Google collects information about the installation and use of extensions under Google's privacy policy. The Developer sees only the aggregate statistics Google provides to every publisher (such as install counts and regions), which contain no individual data. The Developer receives no information from Google that identifies you. ## 10. Security The Software is designed so that a compromise of any server would reveal nothing about you, because there is no server. On your device, secrets are protected by the encrypted vault described in Section 3, by a minimal-permission browser extension architecture in which no secret ever enters a content script or web page, and by the SureSign kernel's rule that only the Rust signing core may handle keys or construct transactions. The Software's source code is public so that these properties can be verified. No software can protect a device that is itself compromised. Malware, a malicious browser extension, a shared browser profile, or physical access to an unlocked device can expose anything on it, including your wallet. Keep your recovery phrase offline and your device secure. ## 11. Your rights and choices Because the Developer does not collect personal information through the Software, there is nothing for the Developer to access, correct, delete, port, or stop selling on your behalf, and no profile to opt out of. You control all of your Wallet Data directly: * **Access and portability:** your data is on your device; your recovery phrase restores your wallet in any compatible software. * **Deletion:** uninstall the Software or remove the wallet in Settings to delete all Wallet Data from that device. * **Endpoints:** replace the default node, indexers, and Igra endpoint with your own in Settings, including a node on your own machine. * **Connections:** revoke any website's access in Settings. * **Support correspondence:** you may ask us to delete our copy of any correspondence you sent us by writing to . **United States state privacy laws.** Residents of California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, and other states with comprehensive privacy laws may have rights of access, correction, deletion, portability, and to opt out of the sale or sharing of personal information and of targeted advertising and profiling. The Developer does not sell or share personal information, does not engage in targeted advertising or profiling, and does not process sensitive personal information. Because the Developer does not collect personal information through the Software, the Developer is not, in the Developer's understanding, a "business" or "controller" subject to those laws with respect to the Software; nonetheless, you may exercise any right you believe you have by writing to , and we will respond within the period required by applicable law. We do not discriminate against anyone for exercising privacy rights. We honor Global Privacy Control signals to the extent they are applicable to a site that performs no tracking. **Users outside the United States.** The Developer is a United States person and publishes the Software from the United States. The Software is not directed at any particular country. If you use the Software from outside the United States, the network services you select may be located anywhere, and any information you send to them is governed by their practices. To the extent the laws of your jurisdiction (for example, the EU or UK General Data Protection Regulation) apply to the Developer's handling of support correspondence, the legal basis is the performance of our response to your request and our legitimate interest in maintaining the Software, and you may exercise your rights by writing to the address above. ## 12. Children The Software is not directed at children under 13, and the Terms of Service require every user to be at least 18. The Developer does not knowingly collect information from children. If you believe a child has provided information to us through a support channel, write to and we will delete it. ## 13. Changes to this Policy We will update this page and the effective date and version number when this Policy changes. Material changes will also be noted in the Software's release notes where practicable. Your continued use of the Software after a change takes effect indicates acceptance of the revised Policy. Prior versions are retained in the repository's history. ## 14. Contact * Email: * Feedback board: [enclave.fider.io](https://enclave.fider.io/) * Direct message to **@argonmining** on X, Telegram, or Discord The Developer publishes Enclave as an individual and is the sole party responsible for this Policy. Privacy questions about any Network or Third-Party Service must be directed to its operator.