NYMIS

The Privacy Cheat Sheet

Explore tools for improving your onchain privacy and protecting your digital identity. Compare how different privacy tools work, what they protect, and where their limitations lie.

Last reviewed Nymis is not affiliated with any listed project.

Explore Privacy Tools

  • Privacy Pools

    Privacy tools

    privacypools.com

    Privacy Pools is a non-custodial protocol for private transfers, swaps, and yield. V2 uses zero-knowledge proofs to conceal activity within a shielded pool, while screening deposits for compliance.

    Best for
    Private transfers and DeFi activity with deposit screening.
    Key limitation
    A centralized screening provider can reject or revoke deposits' eligibility for private transactions.
    View details
    What it protects
    The public link between deposits and withdrawals. V2 also hides the sender, recipient, and amount of transfers within the shielded pool.
    Who can observe your activity
    Public observers can see deposits and withdrawals but not the private activity between them. 0xbow operates the screening service, while independent relayers submit private transactions. Users can operate their own relayer and use anon-RPC to reduce network metadata exposure.
    Privacy mechanism
    Zero-knowledge proofs allow users to transact with shielded balances without revealing which deposits fund their transactions. V2 supports private transfers, swaps, and Aave yield. V1 only supports deposits and withdrawals.
    Trust assumptions
    0xbow operates the Association Set Provider (ASP), which approves deposits and can revoke their eligibility for private spending. L2BEAT currently reports that a single administrative key can upgrade V2's core contracts without delay. According to 0xbow, this is a temporary emergency arrangement, with a multisig planned for October 26, 2026, and a two-week upgrade delay planned for approximately one month later. These changes are not yet confirmed as implemented.
    What remains visible
    Deposit and withdrawal addresses, assets, amounts, and timing remain public. This metadata can enable correlation. Users can exit without ASP approval through a public "ragequit", but doing so reveals the originating deposit.
    KYC requirements
    No identity verification is required by default. Deposits undergo screening and may be rejected.
    Supported networks
    Ethereum, Arbitrum, Base, Optimism, BNB Chain, Robinhood Chain, and Citrea. Supported assets, swaps, and yield opportunities vary by network.
    Additional considerations
    Privacy depends partly on the anonymity set and user behavior. V2 launched in October 2026, so its real-world privacy has limited history. Earlier research by Ethereum Privacy Tools found that address reuse and distinctive transaction amounts weakened privacy for some V1 users.

    Sources & further reading

  • RAILGUN

    Privacy tools

    railgun.org

    RAILGUN is non-custodial privacy infrastructure that lets users shield tokens, make private transfers, and interact with DeFi on existing EVM chains using zero-knowledge proofs.

    Best for
    Private token balances, transfers, swaps, and DeFi activity.
    Key limitation
    Deposits, withdrawals, and external DeFi interactions remain publicly visible.
    View details
    What it protects
    Balances and transactions within RAILGUN's shielded system, including the sender, recipient, and amount of private transfers. The link between deposited and withdrawn funds is also concealed.
    Who can observe your activity
    Only users holding the relevant viewing keys can inspect their private balances and transaction history. Broadcasters, wallet providers, and RPC services may observe network metadata, but do not automatically gain access to shielded transaction details.
    Privacy mechanism
    RAILGUN uses zero-knowledge proofs and encrypted notes to maintain private balances. Users can transfer funds privately or interact with public DeFi protocols through transactions that unshield, execute, and reshield funds.
    Trust assumptions
    RAILGUN has no centralized operator with access to everyone's private balances. Its smart contracts are governed by RAIL token stakers through a DAO. L2BEAT describes a seven-day governance exit window, although its permissions data also identifies upgrade paths requiring further verification. Users additionally depend on their selected wallet, broadcasters, and RPC infrastructure.
    What remains visible
    Shielding and unshielding addresses, assets, amounts, and timestamps are public. DeFi interactions expose the tokens and amounts used by the external contracts. Timing and distinctive amounts may allow transactions to be correlated.
    KYC requirements
    No identity verification is required at the protocol level. Private Proofs of Innocence (PPOI) allow users to demonstrate that shielded funds satisfy screening criteria without exposing their transaction history. Broadcasters generally require these proofs, while direct submission can bypass broadcaster screening.
    Supported networks
    Ethereum, Arbitrum, Polygon, and BNB Chain. RAILGUN is accessible through compatible wallets, including Railway.
    Additional considerations
    Privacy depends on the number of users holding the same asset within the shielded system. RAILGUN charges a 0.25% protocol fee for shielding and unshielding, with additional broadcaster and network fees potentially applying.

    Sources & further reading

  • Aztec

    Privacy tools

    aztec.network

    Aztec is a privacy-first Ethereum Layer 2 that enables developers to build applications with both private and public functionality. Unlike privacy pools, it supports programmable privacy across entire applications.

    Best for
    Private applications, payments, and experimentation with programmable privacy.
    Key limitation
    The network remains in Alpha, with significant security risks and ongoing protocol upgrades.
    View details
    What it protects
    Private smart contract state, transaction details, and function execution, depending on how each application is designed. Applications can combine private and public functionality.
    Who can observe your activity
    Private functions execute and generate proofs on the user's device, so sequencers and validators do not normally see their underlying private data. Wallets, node providers, and applications may still observe metadata or information users disclose.
    Privacy mechanism
    Aztec uses client-side zero-knowledge proofs and encrypted private state, allowing smart contracts to execute private logic while proving its correctness to the network. Transactions ultimately settle on Ethereum.
    Trust assumptions
    Aztec relies on its protocol's cryptography, a decentralized validator network, governance, and the security of individual applications and bridges. As Alpha software, its implementation and upgrade process are still evolving.
    What remains visible
    Public contract functions and state, transaction-related metadata, and information explicitly revealed by applications. Ethereum bridging activity can also expose relationships between addresses.
    KYC requirements
    No protocol-level identity verification. Individual applications and bridges may impose additional requirements.
    Supported networks
    Aztec Alpha mainnet, settling to Ethereum, and a public testnet. Aztec is not EVM-compatible, so existing Ethereum applications cannot be deployed unchanged.
    Additional considerations
    Aztec's Alpha network supports real transactions and early applications, but it is not yet mature infrastructure. A critical vulnerability affecting its V5 proving system was disclosed in August 2026. A V6 replacement is scheduled for no earlier than October 26, 2026, subject to governance execution. Users should verify the active network version and security status before depositing funds.

    Sources & further reading

  • Tornado Cash

    Privacy tools

    github.com/tornadocash

    Tornado Cash is a decentralized, non-custodial Ethereum privacy protocol that uses zero-knowledge proofs to break the public link between deposits and withdrawals. Its immutable pools operate without centralized screening or permission.

    Best for
    Private transfers without centralized approval or deposit screening.
    Key limitation
    Privacy depends on the anonymity set and transaction patterns. Tornado-linked funds may face restrictions from centralized services (CEX, offramp...).
    View details
    What it protects
    The public link between a deposit and its subsequent withdrawal. Observers cannot directly determine which deposit corresponds to a withdrawal based on the cryptographic proof alone.
    Who can observe your activity
    No central operator has privileged access to all deposit–withdrawal relationships. Relayers can see the withdrawal details they process, while frontend operators, RPC providers, and network observers may collect metadata that helps correlate transactions.
    Privacy mechanism
    Users deposit fixed amounts into shared smart-contract pools. A zero-knowledge proof allows them to withdraw to another address without revealing which deposit they made. Unlike RAILGUN or Privacy Pools V2, Tornado Cash does not support private transfers within its pools.
    Trust assumptions
    The core pools are immutable and cannot be upgraded or paused by an administrator. Users still depend on the integrity of the original trusted setup, the software interface they use, and any relayer involved. Governance controls certain peripheral contracts, not the core pools.
    What remains visible
    Deposit and withdrawal addresses, pool denominations, and timestamps are public. Small anonymity sets, distinctive timing patterns, or address reuse can undermine privacy despite the cryptographic protection.
    KYC requirements
    No identity verification, centralized deposit screening, or approval process is required by the core protocol.
    Supported networks
    Ethereum mainnet, with fixed-denomination ETH pools and several ERC-20 pools. Other deployments exist, but their current availability and security should be verified independently.
    Additional considerations
    Tornado Cash was removed from US sanctions lists in March 2025. However, developer legal proceedings remain ongoing, and exchanges may still flag or reject Tornado-linked funds. Historical deanonymization research has primarily identified weaknesses in user behavior and transaction metadata rather than the underlying zero-knowledge proofs. Users should also verify the authenticity of the frontend, given past incidents involving compromised interfaces.

    Sources & further reading

  • anon.wei (Tacit)

    Privacy tools

    anon.wei.limo

    anon.wei is a privacy-focused ETH wallet built on Tacit's shielded pool. Users can deposit ETH, send private payments, and withdraw to fresh addresses using zero-knowledge proofs generated in their browser.

    Best for
    Private ETH transfers and funding fresh wallets without directly linking them onchain.
    Key limitation
    Deposits and withdrawals remain public, and transaction timing or distinctive amounts may reveal connections.
    View details
    What it protects
    The public connection between deposited ETH and subsequent private payments or withdrawals. Transfers within the shielded pool conceal the sender, recipient, and amount.
    Who can observe your activity
    Public observers can see funds entering and leaving the pool, but not the private transfers inside it. RPC providers and transaction relayers may observe network metadata, including submission timing.
    Privacy mechanism
    anon.wei uses Tacit's zero-knowledge shielded pool, where funds are represented by private notes. Proofs are generated locally in the user's browser, allowing private transfers and partial withdrawals without publicly revealing which deposit funded them.
    Trust assumptions
    Tacit's core ETH pool contracts are designed to be immutable, without administrator upgrade or pause permissions. Users depend on the underlying cryptography, trusted setup, browser application, and transaction infrastructure. The protocol documentation reports a public trusted-setup ceremony with 176 contributions.
    What remains visible
    Deposits and withdrawals expose addresses, amounts, and timestamps. Timing, unusual amounts, and withdrawal behavior may allow blockchain analysts to correlate activity despite cryptographic shielding.
    KYC requirements
    No identity verification or centralized deposit approval is described for the protocol. This does not rule out restrictions imposed by individual interfaces or service providers.
    Supported networks
    Ethereum, Base, and Robinhood Chain.
    Additional considerations
    anon.wei supports private ETH payments, partial withdrawals, and wallet recovery from the user's key. Privacy depends partly on the anonymity set, user behavior, and transaction metadata. The underlying Tacit ecosystem supports additional assets and DeFi functionality, but those capabilities should not be confused with features available directly through anon.wei.

    Sources & further reading

  • Curvy

    Privacy tools

    curvy.box

    Curvy is a non-custodial privacy payments protocol combining stealth addresses with zero-knowledge proofs. Users can receive payments through a single Curvy ID, shield their funds, and make private transfers without publicly linking their activity.

    Best for
    Compliant private payments, shielded balances, and transfers through a single payment identity.
    Key limitation
    Privacy depends on Curvy's supporting infrastructure, while deposits and withdrawals can still expose transaction metadata.
    View details
    What it protects
    Stealth addresses conceal the connection between incoming payments and the recipient's identity. Within Curvy's Privacy Aggregator, sender, recipient, amount, and token information are hidden, according to Curvy.
    Who can observe your activity
    Public observers can see transactions entering and leaving the shielded system. Anyone can operate supporting services, including relayers, indexers, and name resolution.
    Privacy mechanism
    Each payment can arrive through a Curvy stealth address called a Portal. The difference between a regular stealth address and Curvy's Portal is that funds received by a Portal can only be shielded in Curvy's Privacy Aggregator or returned to the owner if the compliance checks fail (e.g. to the stealth address). Funds then enter Curvy's Privacy Aggregator, which uses encrypted notes and zero-knowledge proofs to support private transfers and shielded balances. Proofs are generated on the user's device.
    Trust assumptions
    Curvy relies on smart contracts and supporting infrastructure, including relayers, indexers, Portal Broadcasters, and name resolution. Its offchain resolver introduces additional metadata trust. Curvy reports that its smart contracts underwent an independent security audit in 2026. All the offchain infrastructure can be permissionlessly and independently operated by anyone, as the reference implementations are open source at github.com/0xCurvy.
    What remains visible
    When first depositing funds (e.g. shielding), the sender and token of incoming payments remain public. When funds are unshielded, the destination address, amount, and token become visible. Transaction timing may allow deposits and withdrawals to be correlated.
    KYC requirements
    No general identity-verification requirements. Portal Broadcasters perform compliance screening before funds enter the shielded system.
    Supported networks
    Ethereum, Arbitrum, Base, Optimism, Polygon, BNB Chain, Linea, Gnosis, Solana, Tempo, and Robinhood Chain. Starknet supports stealth addresses only.
    Additional considerations
    Curvy charges protocol fees of 0.1% for shielding, 0.1% for aggregation, and 0.2% for unshielding.

    Sources & further reading

  • Fluidkey

    Stealth wallets

    fluidkey.com

    Fluidkey is a self-custodial wallet that generates a fresh stealth address for every incoming payment while displaying funds in one unified account. Users can share a single payment identity without exposing their full wallet history.

    Best for
    Receiving salaries, payments, and donations without publicly linking your addresses or balances.
    Key limitation
    Fluidkey can link all your addresses through its viewing key, and spending can reveal connections between them.
    View details
    What it protects
    The public connection between incoming payments to the same recipient. Each payment arrives at a separate address, preventing observers from easily discovering your other payments and combined balance.
    Who can observe your activity
    Fluidkey holds a viewing key that allows it to identify and monitor all addresses associated with your account. Payers and public observers cannot automatically make those connections, although blockchain analysis can reveal them through subsequent activity.
    Privacy mechanism
    Fluidkey generates a fresh Safe smart account for each incoming payment, controlled by keys derived by the user. Funds appear in one interface, and transactions are executed through the user's accounts rather than a shared mixing pool.
    Trust assumptions
    Users retain control of their spending keys, but rely on Fluidkey's closed-source application, viewing-key infrastructure, address resolver, and relayer. Web users signing in with Google or Apple also depend on Privy. An open-source recovery tool provides a way to access funds independently of Fluidkey.
    What remains visible
    Each incoming payment's sender, token, amount, and subsequent transfers remain public. Spending from multiple Safe accounts, shared funding sources, or common withdrawal destinations can reveal that supposedly separate addresses belong together.
    KYC requirements
    No identity verification for standard crypto functionality. Bank transfers and fiat services require verification through third-party providers.
    Supported networks
    Ethereum, Arbitrum, Base, Optimism, Polygon, Gnosis, and BNB Chain. Available through web and mobile applications.
    Additional considerations
    Fluidkey offers optional yield functionality and a Hide Trail feature routed through Houdini, which introduces exchange intermediaries and additional trust assumptions. In a September 2026 analysis, Ethereum Privacy Tools found that approximately 44% of observable Fluidkey Safe accounts could be linked through public transaction patterns. This illustrates how spending behavior can undermine stealth-address privacy without compromising the underlying cryptography.

    Sources & further reading

  • Cloaked

    Stealth wallets

    clkd.xyz

    Cloaked is a self-custodial privacy wallet that generates a fresh address for every payment received through a single name. Its optional Incognito balance integrates Privacy Pools for additional transaction privacy.

    Best for
    Receiving payments through one identity, with optional shielded spending.
    Key limitation
    Cloaked can recognize addresses belonging to your account and observe deposit–withdrawal associations within its managed Incognito service. These associations are not automatically public, and users retain control over which funds they combine.
    View details
    What it protects
    Stealth addresses prevent public observers from automatically linking payments received through the same identity. Incognito additionally conceals the public onchain connection between deposits and withdrawals made through Privacy Pools.
    Who can observe your activity
    Cloaked can recognize addresses associated with your account through its viewing capability. Its managed Incognito service can also observe deposit–withdrawal associations. This does not automatically expose those relationships to public blockchain observers or give Cloaked control over users' funds.
    Privacy mechanism
    Each incoming payment arrives at a fresh stealth address associated with the user's Cloaked name. Users control their spending keys and can choose which addresses to spend from. Incognito integrates Privacy Pools to obscure the public transaction trail.
    Trust assumptions
    Users retain exclusive spending authority. Cloaked's viewing capability supports address generation and balance tracking but cannot authorize spending. The hosted experience depends on Cloaked's software and services; open-source recovery tooling provides independent access to funds.
    What remains visible
    Each payment's sender, token, amount, and subsequent movements remain publicly observable. Users can keep funds from different receiving addresses separate and choose which sources to spend. Combining several addresses in one transaction publicly links them; change outputs can also be followed onchain.
    KYC requirements
    No general identity-verification requirement is documented. Geographic and sanctions screening may apply, and Incognito deposits are subject to Privacy Pools' screening requirements.
    Supported networks
    Ethereum, Base, Arbitrum One, BNB Smart Chain, OP Mainnet, and Robinhood Chain. Privacy Pools availability depends on supported pools, networks, and assets.
    Additional considerations
    Cloaked provides funding-source controls to help users avoid combining unrelated funds. Users can also recover their keys and withdraw through another Privacy Pools relayer, outside Cloaked's managed withdrawal flow. These options reduce dependence on Cloaked's interface, although using a different relayer does not erase information already observed by Cloaked or other infrastructure providers.

    Sources & further reading

  • Jumper Private Swaps

    Private swaps

    jumper.xyz

    Jumper integrates Houdini Swap to offer private cross-chain swaps and transfers. Funds are routed through separate exchange partners, breaking the direct public link between sending and receiving wallets without requiring a privacy pool.

    Best for
    Swapping or bridging assets without publicly linking source and destination wallets.
    Key limitation
    Privacy relies on exchange intermediaries that process transactions and have access to route information.
    View details
    What it protects
    The direct public blockchain connection between the sending and receiving wallets. This helps prevent straightforward wallet linkage through ordinary swaps and bridges.
    Who can observe your activity
    Houdini coordinates the swap, while its exchange partners process individual parts of the route. These parties may retain transaction information and disclose it when legally required. Public observers can still see the incoming and outgoing transfers separately.
    Privacy mechanism
    Houdini routes transactions through two exchange partners and an intermediary blockchain. This separates the source and destination transfers without relying on shielded pools or zero-knowledge proofs.
    Trust assumptions
    Users depend on Houdini's routing infrastructure and the exchange partners executing the transactions. Houdini states that it never takes custody of funds itself, but the custody and data-retention practices of its exchange partners are not independently established.
    What remains visible
    The source transaction, destination transaction, amounts, assets, and timestamps remain public on their respective chains. Timing and amount analysis may still provide correlation clues, even where no direct transaction path exists.
    KYC requirements
    No account or identity verification is required for the standard private-swap flow, according to Houdini. Exchange partners perform AML/KYT screening, and additional checks or transaction restrictions may apply.
    Supported networks
    Jumper's private-swap integration launched in June 2026 with support for more than 15 chains. Available networks, assets, and routes depend on Houdini's exchange partners.
    Additional considerations
    Private routes may take longer and incur different costs than standard swaps. Houdini states that its private transactions are capped at $400,000. The service protects against direct public wallet linkage, but should not be interpreted as complete anonymity from intermediaries or resistance to every form of transaction correlation.

    Sources & further reading

  • Bungee Incognito

    Private swaps

    bungee.exchange

    Bungee Incognito enables private swaps, transfers, and bridging through privacy routing providers, including Houdini. It helps obscure the public onchain connection between sending and receiving wallets without requiring a shielded pool.

    Best for
    One-off private swaps and transfers between wallets.
    Key limitation
    Privacy and custody depend on third-party routing providers, whose full trust assumptions aren't publicly documented.
    View details
    What it protects
    The direct public onchain link between sending and receiving wallets, making it harder to trace funds through ordinary blockchain transaction paths.
    Who can observe your activity
    Bungee and its routing providers may have access to transaction information. Depending on the route, exchange intermediaries may also observe transfers and associated metadata.
    Privacy mechanism
    Bungee Incognito integrates multiple privacy routing providers, including Houdini, to separate incoming and outgoing transactions. Some routes use exchange-based intermediaries rather than zero-knowledge proofs or shielded pools. The exact mechanism depends on the provider.
    Trust assumptions
    Users depend on Bungee/SOCKET and the privacy providers executing each route. Some providers use exchange intermediaries that temporarily hold funds and process transactions. Custody arrangements, operator visibility, and data-retention practices may vary between providers.
    What remains visible
    Transactions entering and leaving a private route remain publicly observable, including their amounts, assets, and timing. These details may still allow correlation even when there is no direct onchain link between wallets.
    KYC requirements
    Bungee advertises Incognito without mandatory upfront identity verification. However, routing providers may conduct compliance screening or request additional information depending on the transaction or jurisdiction.
    Supported networks
    Incognito initially launched on Solana and Polygon in March 2026, with additional networks subsequently introduced. Supported chains, assets, and routes depend on the available providers.
    Additional considerations
    Private routes may take longer or carry different fees than standard swaps. Completion times, transaction limits, and privacy guarantees depend on the selected provider. Bungee has confirmed that Houdini and other providers are now supported, but detailed documentation covering every provider's routing and custody model is not yet available.

    Sources & further reading

  • NEAR Confidential Intents

    Private swaps

    near.com

    NEAR Confidential Intents enables private cross-chain swaps and transfers through a dedicated execution environment. Transactions on near.com are confidential by default, keeping trading activity and counterparty information off the public NEAR blockchain.

    Best for
    Confidential cross-chain trading and transfers.
    Key limitation
    The service operator can access confidential transaction data, while destination-chain settlements remain publicly visible.
    View details
    What it protects
    Swap amounts, trading pairs, counterparties, and transfer details from public observers during confidential execution.
    Who can observe your activity
    Intents Technology, which operates near.com, can access and retain confidential transaction information. Private-shard validators, solvers, and bridge operators may also see details necessary to process transactions. Information may be shared with analytics providers, screening services, and authorities under the circumstances described in the privacy policy.
    Privacy mechanism
    Transactions execute on a dedicated NEAR private shard operated by permissioned validators. Confidential execution is now the default on near.com, without switching between Main and Confidential modes. Unlike mixing protocols, user funds are not pooled to obscure their origins.
    Trust assumptions
    Users depend on the private shard's permissioned validators, its bridge to NEAR mainnet, transaction solvers, and Intents Technology's data-handling practices. The model relies on restricted access to transaction information rather than fully trustless privacy guarantees.
    What remains visible
    Confidential transactions are not publicly inspectable on the private NEAR shard, including their sender details. Deposits and withdrawals on external public blockchains remain observable, including destination-chain settlements.
    KYC requirements
    No standard identity-verification step is described for confidential execution. Deposits undergo compliance screening, and additional checks or disclosures may apply.
    Supported networks
    Available through near.com, with confidential execution on NEAR's private shard and cross-chain transfers supported through compatible NEAR Intents routes.
    Additional considerations
    Confidential execution works without requiring a separate wallet or client-side proof generation. This makes it convenient for cross-chain trading, particularly when users want to avoid publicly revealing trading strategies. However, its confidentiality guarantees differ substantially from permissionless shielded protocols. NEAR's privacy policy explicitly permits the operator to retain and disclose transaction information for operational, security, compliance, and investigative purposes.

    Sources & further reading

  • nadanada

    Everyday privacy

    nadanada.me

    nadanada provides privacy-focused VPN, no-KYC eSIMs, and phone-number services without requiring an account or identity verification. Its offerings include eSIMs with phone numbers, with cryptocurrency payments supported.

    Best for
    Private internet access, no-KYC mobile connectivity, and phone numbers.
    Key limitation
    Its no-logs policy has not been independently audited, and the service operator's identity and jurisdiction are not clearly disclosed.
    View details
    What it protects
    A VPN masks your IP address from websites and RPC providers while shielding your traffic from your local network and ISP. Its eSIM and phone-number services reduce the personal information needed to purchase connectivity.
    Who can observe your activity
    nadanada's VPN infrastructure can see your connection IP while active, but claims not to retain browsing activity or connection logs. Mobile network operators can still observe device and location data. Payment processors may collect additional information depending on how you pay.
    Privacy mechanism
    nadanada combines WireGuard VPN connections with no-KYC eSIMs, including plans offering phone numbers. Its nada-world bundle also offers French phone numbers.
    Trust assumptions
    Users depend on nadanada's operator, VPN infrastructure, mobile carriers, and relevant payment processors. The VPN's no-logs policy is self-reported, and no independent infrastructure or logging audit was identified.
    What remains visible
    The VPN operator may observe connection metadata, while mobile networks can still access device and location information. nadanada states that Lightning payment invoices cannot be linked to individual VPN endpoints.
    KYC requirements
    No identity verification is required by nadanada for its standard services, according to its published policy. External mobile networks and payment providers may have separate requirements.
    Supported platforms
    WireGuard-compatible devices, eSIM-enabled phones, and web ordering. Phone-number availability depends on the selected plan, including French numbers through nada-world.
    Additional considerations
    nadanada states that its Lightning payment architecture prevents associating a payment invoice with a specific VPN endpoint. This is a provider-reported privacy property, not an independently verified guarantee.

    Sources & further reading

  • Fileverse

    Everyday privacy

    fileverse.io

    Fileverse is an open-source, end-to-end encrypted workspace offering private alternatives to Google Docs, Sheets, and other productivity tools. Its apps include dDocs, dSheets, and encrypted file sharing, with post-quantum encryption and independent data recovery.

    Best for
    Private documents, spreadsheets, file management, and collaboration.
    Key limitation
    File contents are encrypted, but collaboration infrastructure can observe connection metadata and potentially delay updates. Browser-based apps also depend on the integrity of the code delivered to users.
    View details
    What it protects
    Document and spreadsheet contents, files, and collaborative edits through end-to-end encryption. Fileverse is designed so that its operators and storage providers cannot read encrypted content. Users also retain control of their files through open-source tools for independent recovery and export.
    Who can observe your activity
    Collaboration relays can observe connection metadata, such as IP addresses, session timing, and anonymous room identifiers, but not document contents. Fileverse may also process file sizes, timestamps, and account-related metadata. Zero-knowledge access proofs help collaborators verify permissions without disclosing their underlying email or wallet identity to the service.
    Privacy mechanism
    Files are encrypted on the user's device using end-to-end encryption, including post-quantum cryptography in dDocs. dDocs and dSheets use local-first storage and support offline editing, with optional encrypted IPFS storage for sharing and synchronization. Zero-knowledge proofs provide additional privacy for collaboration permissions and account recovery.
    Trust assumptions
    Users depend on the integrity of the web application, encryption implementation, and their own devices. Collaboration servers and storage infrastructure are trusted for availability, rather than access to plaintext content. Fileverse is open source and reports independent security audits. Self-hosting and alternative access methods, including IPFS and Tor, can reduce reliance on its hosted services.
    What remains visible
    Depending on the services used, account information, document sizes, connection timing, collaboration metadata, and IP addresses may remain observable. End-to-end encryption does not conceal all metadata.
    KYC requirements
    No identity verification is required. Users can begin without creating an account.
    Supported platforms
    dDocs and dSheets run in desktop and mobile browsers, with offline functionality and optional encrypted IPFS storage. Both applications are available in public beta.
    Additional considerations
    Fileverse's open-source Walkaway tool allows users to recover and decrypt their documents independently of Fileverse's servers using their backup keys. This reduces dependence on a single provider, although users must securely preserve their recovery credentials.

    Sources & further reading

Find the Right Privacy Tool

Main use caseToolsHow it works
Receive/send payments
Fluidkey Cloaked Curvy Privacy Pools anon.wei
Stealth addresses make receiving payments harder to link, while shielded pools can also break the public transaction trail. The level of privacy depends on the tool and how it's used.
Fund a fresh address
Privacy Pools RAILGUN Tornado Cash anon.wei Curvy
Depositing into a shielded pool breaks the public link between sending and receiving addresses, but timing, amounts, and transaction patterns can still reveal connections.
Keep DeFi activity private
RAILGUN Privacy Pools V2 Aztec
Private balances or private execution can support transfers, swaps, yield, or app activity, depending on the tool.
Make private swaps
Jumper Bungee Curvy NEAR Confidential Intents
Private swaps can use shielded transactions or intermediary routing, depending on the tool.
Keep trades and counterparties private
NEAR Confidential Intents
Transactions execute confidentially instead of appearing fully on a public chain.
No-KYC eSIM, VPN and more
nadanada
Privacy infrastructure reduces IP exposure to websites and RPC providers.
Keep documents private
Fileverse
Local encryption protects document contents during storage and collaboration.

Tools may support multiple use cases. The examples above highlight common applications, not their full capabilities.

Key Privacy Concepts

Privacy
Control over what specific observers, such as the public, a counterparty or a service operator, can learn about your activity. Privacy is always relative to an observer: a tool can hide you from the public while its operator still sees more.
Anonymity
An action is anonymous when an observer can't single it out or link it to you among a group of plausible candidates. It depends on the size of that group and on what the observer can see and correlate, so it is rarely absolute.
Anonymity set
The group of possible participants an observer can't tell apart, such as all deposits of the same amount in a pool. A larger set usually improves privacy, but distinctive timing, amounts or behavior can shrink it to a few candidates.
Zero-knowledge proof (ZKP)
A cryptographic method for proving a statement is true without revealing the information behind it. Privacy tools use ZKPs to prove, for example, that a withdrawal is backed by a valid deposit without revealing which deposit funded it.
Transaction metadata
Information surrounding a transaction rather than its contents: timing, amounts, addresses, gas payments, IP addresses and network activity. Even when a tool hides the link between transactions, metadata patterns can still reveal connections.
Stealth address
A fresh address generated for each incoming payment, so payers and observers can't easily connect a recipient's payments or see their total balance. Senders and amounts stay public, funds aren't mixed, and spending from several stealth addresses together can link them.
Shielded pool
A smart contract holding many users' funds, where zero-knowledge proofs hide which deposit funds a later withdrawal or private transfer. Deposits and withdrawals remain public, so privacy depends on the anonymity set and on avoiding distinctive timing or amounts.
Private execution
A network where smart-contract logic and state can themselves be private, with proofs generated on the user's device. Unlike a shielded pool, it can make whole applications private, though each app decides what stays public and bridging can expose activity.
Intermediary routing
Funds pass through third parties, such as exchanges, that send a fresh transfer to the destination. The public chain shows no direct link, but the intermediaries see their part of the route, may hold funds in transit and may keep records.
Viewing key
A key that lets its holder see otherwise private wallet activity, such as balances, incoming payments or transaction history, without being able to spend funds. What it reveals varies by protocol, and some wallet providers hold one for every user.
Association Set Provider (ASP)
In Privacy Pools, the party that decides which deposits may be spent privately, by publishing a list of approved deposits. It can delay or revoke approval; users whose deposits aren't approved can still exit publicly, which gives up privacy for those funds.
KYC and KYT
KYC (Know Your Customer) verifies who you are, usually with identity documents. KYT (Know Your Transaction) screens where funds come from and go, often using blockchain analytics. A service can skip KYC and still screen transactions.

Research & Data

This directory is based on official documentation and independent research. We aim to provide accurate, unbiased information, but inclusion does not imply endorsement. Some links are referral links; these arrangements do not influence our evaluations.

Found an error or outdated information? Let us know on X.