A decentralized exchange adds a privacy-preserving transaction layer to attract users in high-surveillance markets. Within six months, a correspondent bank flags the flow as structurally opaque, the payment rail closes, and the regulator opens a formal investigation into whether the platform facilitated sanctions evasion. The technology worked as designed – obfuscating transaction graphs and shielding participant identities – but the legal question the exchange now faces is whether that design itself constitutes a breach of anti-money laundering duties, and whether the firm can demonstrate compliance when the underlying data was never collected.
Privacy technology in digital assets – zero-knowledge proofs, mixers, ring signatures, stealth addresses and shielded-pool architectures – sits at the intersection of cryptographic innovation and regulatory enforcement. For a VASP (virtual asset service provider) operating under FATF Recommendations, the Travel Rule and national AML regimes, the choice to integrate, support or transact with privacy-preserving protocols carries direct compliance exposure. Regulators in the leading hubs – the FCA, MAS, ESMA under MiCA, VARA, and FinCEN – increasingly treat structural opacity as a red flag, and enforcement actions against platforms interacting with sanctioned mixers have established that facilitation liability extends beyond the protocol itself to the businesses that enable access. This analysis examines the compliance obligations that apply when privacy technology enters the transaction chain, the enforcement posture across key jurisdictions, and the operational decisions a VASP must take to manage the exposure without abandoning legitimate privacy use cases. For firms building privacy features into custody, payments or DeFi interfaces, the framework below maps the line between lawful cryptographic design and conduct that regulators treat as deliberate AML evasion.
What regulatory framework governs privacy technology in digital assets?
No jurisdiction has enacted a dedicated "privacy-coin statute." Instead, regulators apply the existing AML and sanctions architecture to privacy-preserving protocols by focusing on the VASP's duties rather than the technology itself. Under FATF Recommendation 15, a VASP must conduct customer due diligence, monitor transactions for suspicious activity, and comply with the Travel Rule – the obligation to pass originator and beneficiary information with each transfer above a jurisdiction-specific threshold. Privacy technology that obfuscates sender, receiver or transaction amount creates a structural conflict with these duties, and the regulatory response has been to hold the intermediary – the exchange, the custodian, the wallet provider – liable for failing to collect or verify data that the protocol deliberately withholds.
The MiCA regime in the European Union establishes this principle explicitly. A crypto-asset service provider authorised under MiCA must implement systems and controls to detect and prevent money laundering and terrorist financing, including real-time transaction monitoring and suspicious-activity reporting. Where a token or protocol employs privacy features that prevent the CASP from obtaining the required originator and beneficiary data, the regulator's position – articulated in ESMA's supervisory guidance – is that the CASP may not support that asset or must apply enhanced due diligence sufficient to satisfy the underlying AML obligation. In practice, this has driven widespread delisting of privacy-focused tokens from EU-licensed platforms.
In the United Kingdom, the FCA's approach under the Money Laundering Regulations is functionally identical. A cryptoasset firm registered under the MLR must screen counterparties, monitor for sanctions exposure, and file suspicious activity reports where required. Privacy technology that prevents the firm from identifying the ultimate beneficial owner of a transaction or tracing funds to a sanctioned address places the firm in breach, regardless of whether the user's intent was lawful. The FCA has stated in supervision correspondence that "structural anonymity" – design choices that make compliance impossible – is not a defense to an AML failure.
FinCEN in the United States treats privacy protocols through the lens of facilitation and money-services-business obligations. A platform that enables users to transfer value using a mixer or a shielded-pool token is a money transmitter and must register, implement a written AML program, and file currency transaction reports and SARs. Where the protocol's design prevents the platform from meeting these obligations, FinCEN's enforcement position is that the platform must either refuse to support the protocol or implement compensating controls – enhanced KYC at on-ramp and off-ramp, transaction limits, or blockchain analytics sufficient to demonstrate that funds entering the privacy layer were clean. The 2022 sanctions designation of Tornado Cash and subsequent enforcement actions against platforms that continued to interact with the protocol signal that facilitation liability is real and that a platform's claim of technical inability to monitor does not excuse the breach.
In Singapore, MAS applies a risk-based framework under the Payment Services Act. A DPT service provider must conduct ongoing due diligence and transaction monitoring, and the regulator expects the provider to assess whether a token's privacy features are consistent with the firm's risk appetite and AML controls. MAS has issued guidance stating that tokens with "enhanced anonymity features" warrant enhanced due diligence or outright exclusion, and that the decision to support such assets must be documented in the firm's risk assessment and approved by senior management. The operational effect is that most Singapore-licensed platforms do not support privacy coins or privacy-layer integrations.
Across these regimes, the common thread is that the VASP bears the AML obligation, not the protocol. A privacy protocol may be legal to develop, legal to use in a peer-to-peer context, and protected as a matter of cryptographic free expression in some jurisdictions – but the moment a licensed intermediary facilitates access, the intermediary must satisfy the KYC and transaction-monitoring duties that apply to any other digital-asset service. If the technology prevents compliance, the regulator's answer is to refuse the service, not to grant an exemption.
How do sanctions apply to mixers and privacy pools?
The designation of Tornado Cash mixer addresses by the US Office of Foreign Assets Control in August 2022 marked a turning point in how regulators treat privacy technology. OFAC added dozens of Ethereum addresses associated with the Tornado Cash smart contracts to the Specially Designated Nationals list on the basis that the protocol had been used to launder proceeds of North Korean state-sponsored hacks, including the Lazarus Group's theft from Ronin Bridge. The designation did not allege that every use of Tornado Cash was illicit – only that the protocol as a whole had facilitated sanctions evasion and money laundering to such a degree that blocking the addresses was warranted under national-security authorities.
For VASPs, the legal consequence is immediate and mechanical: any transaction that touches a sanctioned address is prohibited, and a platform that processes such a transaction – even unknowingly – is in breach of sanctions law. Because Tornado Cash operates as a set of immutable smart contracts on Ethereum, and because users interact with those contracts by sending funds to designated deposit addresses, any VASP that permits a customer withdrawal to a Tornado Cash address, or that accepts a deposit from an address that recently interacted with the mixer, is facilitating a sanctions violation. The fact that the underlying code is decentralized and that no individual controls the protocol does not remove the VASP's obligation to screen and block.
This enforcement posture extends beyond US-based platforms. OFAC sanctions have extraterritorial effect: a non-US VASP that processes a transaction involving a designated address, where that transaction touches the US financial system or involves a US person, is within OFAC's jurisdiction. In practice, this means that any VASP with a correspondent banking relationship in the United States, or any platform that holds US-dollar stablecoin reserves, must implement OFAC screening as part of its transaction-monitoring stack. The major blockchain analytics providers – Chainalysis, Elliptic, TRM Labs – have integrated OFAC sanctions lists into their monitoring tools, and most licensed exchanges now block deposits from addresses flagged as mixer-linked or sanctioned.
The broader principle that emerges is that facilitation liability for sanctions evasion does not require intent. A VASP need not know that a customer is using a privacy protocol to launder funds; the act of processing the transaction is sufficient to trigger liability if the transaction involves a sanctioned address. This is a strict-liability regime, and the compliance standard is zero tolerance. A platform that permits even a single mixer withdrawal, or that accepts a deposit from a recently mixed address without enhanced due diligence, exposes itself to enforcement, frozen banking rails, and potential criminal referral.
Beyond OFAC, the European Union's sanctions framework operates on similar principles. While the EU has not designated a privacy protocol in the same manner as Tornado Cash, the EU sanctions regulations prohibit making funds or economic resources available to designated persons and entities, and member-state competent authorities have the power to freeze assets and investigate sanctions breaches. A CASP operating under MiCA that interacts with privacy technology must screen for EU sanctions exposure, and the inability to identify a counterparty due to protocol design is not a defense. ESMA's position is that if a CASP cannot perform sanctions screening on a particular transaction type, the CASP must refuse to offer that transaction type.
In a recent cross-border enforcement matter, a European exchange that processed withdrawals to a mixer-associated address faced parallel investigations by its national AML authority and the US Department of Justice, even though the exchange had not onboarded any US customers. The exposure arose because the mixer had been used in a ransomware scheme targeting US infrastructure, and the exchange's facilitation of the withdrawal was treated as part of the laundering chain. The exchange ultimately settled with supervisory penalties and a mandatory engagement with a third-party compliance monitor. The lesson for VASPs is that sanctions exposure from privacy technology is not confined to the jurisdiction where the platform is licensed – it extends to every jurisdiction whose sanctions lists intersect with the transaction flow.
Why does the Travel Rule conflict structurally with privacy protocols?
The Travel Rule, articulated in FATF Recommendation 16 and implemented in national AML regimes across the leading digital-asset hubs, requires a VASP to obtain, hold and transmit originator and beneficiary information for virtual-asset transfers above a defined threshold. The rule is modeled on the wire-transfer provisions of the Bank Secrecy Act and is intended to create an audit trail that law enforcement and regulators can follow when investigating money laundering or terrorist financing. For traditional bank-to-bank transfers, compliance is straightforward: the sending bank holds KYC data on the originator, the receiving bank holds KYC on the beneficiary, and the two institutions exchange the required data fields through SWIFT or another messaging layer.
Privacy-preserving protocols break this model at multiple points. A shielded-pool architecture – such as Zcash's sapling protocol or the now-sanctioned Tornado Cash – obfuscates the link between sender and receiver by pooling funds and issuing cryptographic proofs of balance rather than recording discrete transfers on a public ledger. The originator's address, the beneficiary's address, and the transaction amount are not visible on-chain, and in many cases not even the VASP facilitating the transfer can reconstruct the data required for Travel Rule compliance. Where a user withdraws from an exchange to a shielded address, and the receiving party later withdraws from the pool to a separate address, the exchange has no ability to identify the ultimate beneficiary or to transmit the required information.
The regulatory response has been to treat this structural conflict as a compliance failure by the VASP, not as a limitation inherent in the technology. Under MiCA, a CASP must comply with the Travel Rule for all transfers above the threshold, and where a protocol prevents compliance, the CASP is prohibited from supporting that protocol. The threshold under MiCA aligns with the EU's Fourth and Fifth Anti-Money Laundering Directives and is applied on a per-transaction basis. A CASP that permits a customer to withdraw to a privacy protocol without collecting and transmitting beneficiary information is in breach, and the fact that the protocol does not expose that information on-chain is not a mitigating factor.
In Singapore, MAS has taken a similar stance. A DPT service provider must comply with the Travel Rule for transfers exceeding the prescribed threshold, and the regulator has stated that tokens with built-in anonymity features are inconsistent with Travel Rule compliance. MAS does not prohibit privacy technology outright, but the regulator expects the provider to demonstrate that it can meet the information-collection and transmission requirements for every supported asset. Where the provider cannot, the asset must be excluded from the platform. This has led to a de facto ban on privacy coins and mixer integrations among licensed Singapore platforms.
The United States applies the Travel Rule through FinCEN's implementing regulation, which requires a money transmitter to collect and retain originator and beneficiary information for transactions above a threshold and to transmit that information to the receiving institution. FinCEN has clarified that the rule applies to virtual-asset transfers in the same manner as fiat wire transfers, and that a platform facilitating a transfer to a privacy protocol must either collect the beneficiary information before the transfer or refuse the transaction. In practice, US-licensed platforms universally block withdrawals to known mixer addresses and flag deposits from mixer-linked addresses for enhanced review or outright rejection.
A practical complication arises with self-hosted wallets. Under the Travel Rule, a VASP must collect beneficiary information when the receiving party is another VASP, but the obligation is less clear when the beneficiary is an individual using a self-hosted wallet. FinCEN's 2020 proposed rulemaking on "unhosted wallets" would have required the originating VASP to collect and verify beneficiary information for transfers above a lower threshold, but the rule was not finalized and the Biden Administration later withdrew it. However, the regulatory expectation remains that a VASP must conduct enhanced due diligence on withdrawals to self-hosted wallets, particularly where the wallet address is associated with a privacy protocol or a mixer. A withdrawal to a freshly generated address with no transaction history is treated as higher risk than a withdrawal to a wallet address with a documented on-chain history, and most compliance programs now require manual review for large withdrawals to new or privacy-linked addresses.
For a VASP designing its AML controls, the operational takeaway is that privacy technology and Travel Rule compliance are currently incompatible. A platform may support privacy-preserving features at the protocol level – for instance, enabling users to generate shielded addresses within the platform's internal ledger – but the moment a transfer exits to an external privacy protocol, the platform loses the data trail required for regulatory compliance and must either refuse the transfer or implement compensating controls sufficient to demonstrate that the platform conducted due diligence on both the originator and the ultimate recipient.
What enforcement actions have targeted platforms interacting with privacy technology?
Enforcement against platforms that facilitate access to privacy protocols has escalated over the past three years, and the actions demonstrate that regulators treat facilitation as equivalent to direct involvement in money laundering where the platform failed to implement adequate controls. In the United States, FinCEN brought an enforcement action against a now-defunct virtual-currency exchange for operating as an unlicensed money transmitter and for failing to implement an adequate AML program. The platform had permitted users to withdraw to Tornado Cash addresses without collecting beneficiary information, and FinCEN alleged that the platform's failure to block mixer withdrawals constituted willful noncompliance with the Bank Secrecy Act. The settlement included a seven-figure civil penalty and a requirement that the platform engage a third-party monitor for three years.
In a parallel criminal matter, the Department of Justice charged the operators of a mixer service with conspiracy to commit money laundering and operating an unlicensed money-transmitting business. The indictment alleged that the service had processed hundreds of millions of dollars in proceeds from darknet markets, ransomware attacks and fraud schemes, and that the operators had marketed the service explicitly as a tool for evading law enforcement. The case is ongoing, but the prosecution's theory – that operating a mixer with knowledge that it facilitates crime is itself a criminal act – has significant implications for developers and platforms that offer privacy-preserving services. The government's position is that even a decentralized protocol can generate criminal liability for its operators where the service is designed to and does in fact facilitate money laundering.
In Europe, a Dutch platform faced enforcement from its national AML supervisor for accepting deposits from addresses linked to a sanctioned mixer. The supervisor found that the platform's transaction monitoring had flagged the deposits as high risk, but that the platform's compliance team had approved them without conducting enhanced due diligence or filing a suspicious activity report. The regulator imposed a penalty and required the platform to upgrade its blockchain analytics tools and to implement automated blocking of deposits from mixer-associated addresses. The case established that a platform's obligation extends beyond screening at the point of withdrawal – the platform must also screen incoming deposits and must block or investigate any transaction that touches a sanctioned or high-risk address, even if the customer's intent appears legitimate.
In Singapore, MAS issued a public reprimand and a financial penalty to a licensed payment institution for deficiencies in its AML controls, including a failure to monitor for transactions involving privacy-enhanced tokens. The regulator found that the institution had supported a privacy coin without conducting a documented risk assessment, without implementing enhanced due diligence for users transacting in that coin, and without training its compliance staff on the specific risks associated with privacy technology. MAS's decision emphasizes that a platform's duty is not merely to avoid sanctioned protocols but to assess and manage the AML risk of every privacy-preserving feature it supports, and to document that assessment in its enterprise risk framework.
These actions converge on a common enforcement theory: a VASP's facilitation of privacy technology is lawful only where the VASP can demonstrate that it conducted adequate due diligence, that it implemented controls sufficient to detect and prevent misuse, and that it did not turn a blind eye to red flags indicating that the technology was being used for illicit purposes. A platform that supports privacy features without adequate controls, or that continues to support a protocol after it has been designated as high risk or sanctioned, exposes itself to supervisory penalties, loss of banking relationships, and in serious cases, criminal referral for conspiracy or aiding and abetting money laundering.
What compliance posture allows a VASP to support lawful privacy use cases?
The regulatory conflict with privacy technology is not absolute. Lawful privacy use cases exist – individuals in high-surveillance jurisdictions protecting financial privacy from authoritarian regimes, businesses shielding competitive transaction data, users managing personal security in high-crime regions – and some regulators acknowledge that blanket prohibition of all privacy features is neither proportionate nor technically necessary. The question for a VASP is how to design a compliance program that accommodates legitimate privacy without crossing into facilitation of money laundering or sanctions evasion.
The starting point is a documented risk assessment that treats privacy technology as a distinct risk category within the firm's enterprise AML framework. Under MiCA, a CASP must conduct a business-wide risk assessment covering products, services, customers and geographies, and the assessment must evaluate the money-laundering and terrorist-financing risks associated with each. Where the CASP offers or supports privacy-preserving features – whether native protocol features, integrations with external privacy layers, or internal mixing functionality – the risk assessment must identify the specific AML and sanctions risks those features create, the controls the CASP has implemented to mitigate those risks, and the residual risk the firm is prepared to accept. The assessment must be reviewed and approved by senior management, updated at least annually, and made available to the regulator on request.
The second element is enhanced due diligence at the user level. A VASP that permits users to interact with privacy protocols must apply a higher standard of KYC at onboarding and ongoing monitoring. This includes verifying the user's identity through multiple independent sources, obtaining and documenting the source of funds, conducting adverse-media screening for sanctions and criminal exposure, and assessing whether the user's stated purpose for using privacy features is consistent with the user's profile and transaction behavior. In jurisdictions where privacy coins are not outright prohibited, licensed platforms that support them typically limit access to institutional or high-net-worth clients who undergo enhanced KYC, and they impose transaction limits and mandatory holding periods to reduce the risk of rapid in-and-out laundering.
The third element is blockchain analytics and transaction monitoring tailored to privacy protocols. Standard on-chain monitoring tools are ineffective against shielded-pool transactions, but forensic techniques exist to identify high-risk patterns even where individual transaction details are obscured. A VASP can monitor the timing, volume and frequency of deposits to and withdrawals from privacy protocols; can flag users whose transaction behavior is inconsistent with their stated business purpose; and can compare the user's transaction graph to known illicit patterns identified by law enforcement. The major analytics providers now offer privacy-protocol monitoring modules, and regulators expect VASPs that support any privacy features to deploy these tools and to document their effectiveness in the firm's annual AML testing.
A fourth, operationally critical, element is automated blocking of sanctioned addresses and high-risk counterparties. Every VASP must screen outbound transfers in real time against OFAC's SDN list and other applicable sanctions lists, and must block any transfer to a sanctioned address. For privacy protocols, this means integrating the mixer-address feeds from Chainalysis, Elliptic and TRM Labs into the platform's withdrawal workflow, such that a user's attempt to withdraw to a Tornado Cash address or another designated mixer is automatically rejected before the transaction is broadcast on-chain. Screening must occur at the point of transfer initiation, not post-execution, because a sanctions violation is complete the moment the funds leave the platform's control.
Finally, the compliance posture must include suspicious-activity reporting discipline. Where a user's interaction with privacy technology raises red flags – for instance, a customer deposits clean funds, immediately withdraws to a mixer, and then redeposits from a different address – the VASP must file a suspicious activity report with the relevant financial intelligence unit, regardless of whether the activity is ultimately determined to be illicit. Regulators treat the failure to file a timely SAR as a separate compliance breach, distinct from any underlying money-laundering offense, and the failure to file is often easier for the regulator to prove than the underlying conduct. A VASP's compliance program must train staff to recognize the red-flag patterns associated with privacy-protocol misuse, must document the SAR decision-making process, and must file within the statutory deadline.
In our cross-border compliance practice, we see VASPs that have implemented this framework successfully continue to support limited privacy features – for instance, opt-in transaction shielding for institutional clients, or integration with privacy protocols that publish zero-knowledge proofs enabling compliance verification – while avoiding the facilitation risk that comes with unrestricted mixer access. The compliance cost is significant – enhanced KYC and monitoring for privacy users can exceed the revenue those users generate – but for platforms whose user base includes legitimate privacy-conscious clients, the investment is preferable to a blanket prohibition that drives users to unlicensed competitors or peer-to-peer channels.
Do developers of privacy protocols face personal liability?
The arrest and prosecution of individuals involved in developing or promoting privacy protocols has introduced a novel and contested area of enforcement, and the outcome of these cases will shape how the next generation of privacy technology is built and deployed. The core legal question is whether writing code that enables privacy – code that is published open-source, that operates autonomously once deployed, and that can be used for both lawful and illicit purposes – constitutes criminal facilitation of money laundering where the developer knows or should know that the code will be misused.
In the United States, the Department of Justice has taken the position that developers of mixing services can be charged with conspiracy to commit money laundering and operating an unlicensed money-transmitting business where the facts demonstrate that the developers marketed the service to criminals, derived revenue from illicit use, or took affirmative steps to conceal the service's facilitation of crime. The indictment of the developers behind a centralized mixer service alleged that the defendants had advertised the service on darknet forums, had structured the service to avoid KYC and transaction limits, and had laundered proceeds from the service through shell companies and foreign exchanges. The government's theory is that these facts elevate the conduct from publishing code to operating a criminal enterprise.
The more contentious question arises with decentralized protocols where no single party controls the infrastructure, where the code is immutable once deployed, and where the developer receives no ongoing revenue. The arrest of a developer associated with Tornado Cash by Dutch authorities in 2022, and the subsequent US charges against another individual linked to the protocol, raised significant debate in the developer community about whether creating and publishing privacy-preserving code is itself a criminal act. The US government's position, as articulated in the indictment, is that the defendants went beyond writing code: they allegedly promoted Tornado Cash to users they knew were laundering criminal proceeds, failed to implement any controls to prevent misuse, and derived financial benefit from the protocol's use in high-profile hacks. The charges include conspiracy to commit money laundering, conspiracy to operate an unlicensed money-transmitting business, and sanctions violations related to processing funds for a designated entity.
The defense argument – supported by civil-liberties organizations and portions of the cryptography research community – is that code is speech, that publishing open-source privacy software is protected under the First Amendment in the United States and analogous free-expression principles in other jurisdictions, and that criminalizing the publication of dual-use cryptographic tools chills legitimate research and innovation. The legal outcome will turn on whether courts accept the government's theory that active promotion and financial benefit distinguish facilitation from mere publication, or whether they find that prosecuting developers for the misuse of their code by third parties is a bridge too far.
In Europe, developer liability under AML law is less developed, but the principle is emerging that individuals who operate or control a virtual-asset service – including the infrastructure behind a privacy protocol – can be held liable as gatekeepers under national AML regimes. The Dutch prosecution of the Tornado Cash developer proceeded under the country's money-laundering and sanctions statutes, and the case is being closely watched as a bellwether for how European authorities will treat decentralized-protocol developers. Under MiCA, liability attaches to the legal entity providing crypto-asset services, not typically to individual developers, but criminal liability under national law remains a possibility where the individual's conduct crosses from development into operation or promotion of a service used for money laundering.
For developers and for VASPs that work with privacy technology, the operational implication is that the line between lawful privacy innovation and criminal facilitation depends on the surrounding conduct, not merely the functionality of the code. Publishing a privacy protocol as open-source research, with clear disclaimers that the protocol must be used in compliance with applicable law, is likely protected. Operating a business that markets the protocol to criminals, derives revenue from its use, and takes no steps to prevent misuse, is likely criminal. The gray area – deploying a decentralized protocol that includes optional privacy features, where the developer has no ongoing control and no revenue model – is the subject of active litigation, and until that litigation resolves, developers should assume that law enforcement will scrutinize not just the code but the intent and the commercial context in which the code was released.
How do privacy-technology rules diverge across the major hubs?
The enforcement posture on privacy technology is not uniform, and the divergence creates compliance complexity for VASPs operating across multiple jurisdictions. In the European Union, MiCA establishes a harmonized framework for crypto-asset services, but privacy coins and privacy protocols are effectively prohibited in practice because CASPs cannot comply with the Travel Rule and the AML obligations while supporting structural anonymity. The few privacy-focused tokens still traded on European platforms are limited to those that offer optional privacy – where the user can choose to shield a transaction but the default is transparent – and even then, the CASP must apply enhanced due diligence and must demonstrate that the user's stated purpose for using privacy is legitimate and not linked to sanctions evasion or money laundering.
In the United Kingdom, the FCA's position is similarly restrictive. Cryptoasset firms registered under the Money Laundering Regulations must conduct transaction monitoring sufficient to detect suspicious activity, and privacy features that prevent monitoring are treated as inconsistent with registration. The FCA has not issued a formal ban on privacy coins, but in supervisory practice, firms that support such assets face enhanced scrutiny, and most have delisted privacy-focused tokens to avoid regulatory friction. The FCA's 2023 guidance on financial promotions makes clear that any marketing of privacy features must not suggest that the technology can be used to evade law enforcement or tax obligations, and that firms promoting privacy must provide balanced risk warnings.
Switzerland takes a more nuanced approach under FINMA supervision. Swiss law recognizes that privacy is a legitimate user interest, and FINMA has stated that privacy-enhancing technology is not per se prohibited. However, a Swiss financial intermediary subject to AML obligations must still conduct adequate due diligence, and where a privacy feature prevents the intermediary from identifying the customer or the beneficial owner, the intermediary must refuse the transaction. In practice, this means that Swiss-licensed platforms can support privacy protocols in limited contexts – for instance, for internal transaction shielding where the platform retains KYC data on both the originator and the beneficiary – but not for external transfers to decentralized privacy protocols where the counterparty is unknown. FINMA's supervisory expectation is that the intermediary's risk assessment and AML controls are tailored to the specific privacy technology in question, and that the intermediary can demonstrate compliance with both the letter and the spirit of Swiss AML law.
In Singapore, MAS applies a risk-based approach under the Payment Services Act but has signaled through guidance and enforcement that privacy-enhanced tokens are high risk and generally incompatible with a DPT service provider's AML obligations. MAS permits a provider to conduct its own risk assessment and to support privacy features where the provider can demonstrate adequate controls, but in practice, no major Singapore-licensed platform supports privacy coins or external privacy protocols. The regulatory expectation is that the provider will either implement controls sufficient to satisfy the Travel Rule and transaction monitoring requirements – which is technically infeasible for most privacy protocols – or will exclude the asset from its service offerings.
The United States presents a fragmented picture. At the federal level, FinCEN treats privacy protocols as high-risk and expects money transmitters to block or conduct enhanced due diligence on privacy-related transactions. OFAC's designation of Tornado Cash and the Department of Justice's criminal prosecutions establish that facilitation of mixer use is sanctionable and potentially criminal. However, at the state level, attitudes vary: some states with active blockchain-developer communities have considered legislation to protect privacy-technology research and open-source publication, while other states align closely with federal enforcement priorities. A VASP operating under a state money-transmitter license must comply with both the state's AML requirements and federal BSA obligations, and in practice, the federal standard – zero tolerance for sanctioned mixers, enhanced due diligence for privacy features – prevails.
For a VASP structuring its compliance program across these jurisdictions, the operational strategy is to design to the strictest standard. If the platform operates in the EU, the UK, Singapore and the United States, it must assume that privacy protocols are prohibited unless the platform can demonstrate full Travel Rule compliance and sanctions screening, which in turn means that the only viable privacy features are those implemented internally, where the platform retains full KYC and transaction visibility. Cross-border divergence is narrowing toward prohibition, and the platforms that have attempted to maintain privacy-protocol support in permissive jurisdictions while blocking it in restrictive ones have found that banking partners and correspondent institutions apply the restrictive standard globally, rendering the multi-jurisdictional approach unworkable.
Can privacy-by-design be implemented in a compliant architecture?
The regulatory conflict between privacy and AML compliance has driven a research effort – within industry, within the cryptography community, and within some regulatory sandboxes – to develop privacy-by-design architectures that protect user confidentiality while still enabling the VASP to meet its legal obligations. These architectures aim to separate on-chain visibility from institutional visibility: the public blockchain does not reveal transaction details, but the VASP retains the ability to produce originator, beneficiary and transaction data to regulators or law enforcement on request. If such architectures prove viable and gain regulatory acceptance, they would allow VASPs to offer privacy features without the facilitation risk that comes with unrestricted mixer use.
One approach is selective disclosure through zero-knowledge proofs. Under this model, a user's transaction is shielded on-chain – observers cannot see the sender, receiver or amount – but the user or the VASP holds a cryptographic proof that can be presented to a regulator to demonstrate the underlying transaction details. The proof is generated at the time of the transaction and is tied to the user's KYC record within the VASP's systems. If the regulator or a court orders disclosure, the VASP produces the proof, which verifies on-chain that the transaction occurred and reveals the details without breaking the general privacy of the protocol. Zcash's "viewing keys" are an early implementation of this concept, and newer protocols are exploring variations that allow the VASP to satisfy Travel Rule obligations by transmitting encrypted beneficiary data along with the on-chain transaction, where only the sending and receiving VASPs can decrypt the data.
A second approach is tiered privacy within a licensed platform's internal ledger. Rather than integrating with an external privacy protocol, the VASP implements privacy features inside its own infrastructure. Users can shield their balances and transactions from other users, but the VASP's compliance team retains full visibility into every transaction and can apply the standard AML monitoring and Travel Rule obligations. This model is functionally similar to traditional banking privacy, where account balances and transaction details are confidential as to third parties but fully transparent to the bank and its regulators. The limitation is that privacy is confined to the platform's internal ledger; once funds move on-chain, the transaction is transparent, and the privacy protections are lost. For users whose primary concern is confidentiality from other platform users or from public blockchain observers – rather than confidentiality from the VASP itself – this model may be sufficient.
A third, more speculative, approach is privacy pools with compliance gates. Under this model, a privacy protocol is designed to accept deposits only from users who have passed KYC with a participating VASP, and the protocol issues zero-knowledge proofs that funds entering the pool originated from a compliant source without revealing which specific user deposited which funds. When a user withdraws from the pool, the receiving VASP can verify the proof and satisfy itself that the funds are not linked to sanctions or high-risk sources, even though the VASP cannot trace the funds to a specific originator. The Travel Rule is satisfied at an aggregated level: the sending VASP transmitted the required data into the pool, and the receiving VASP verified the attestation on withdrawal. This model is under development in several research projects, and some regulators have indicated openness to evaluating it within a sandbox or pilot program, but it is not yet deployed at production scale and has not received formal regulatory approval in any major jurisdiction.
The common challenge across these architectures is that regulators are skeptical of any design that relies on cryptographic assurances rather than direct institutional visibility. A compliance officer can audit a database of KYC records and transaction logs; auditing a zero-knowledge proof requires specialized cryptographic expertise, and the regulator must trust that the proof system has not been backdoored or that the VASP is not generating false proofs to cover illicit transactions. Until regulators gain comfort with cryptographic compliance – which will require a combination of technical education, third-party audits of proof systems, and successful deployments in controlled environments – the default supervisory posture will remain that privacy features are acceptable only where the VASP retains plaintext records accessible to the regulator on demand.
For VASPs exploring privacy-by-design, the path forward is to engage the regulator early – ideally through a sandbox or innovation-office channel – and to propose a specific architecture with a technical specification, a compliance-workflow diagram, and a demonstration that the design satisfies the AML and Travel Rule obligations in a verifiable manner. A VASP that deploys privacy features without prior regulatory clearance, on the theory that the cryptographic design is compliant, exposes itself to the risk that the regulator will disagree and will treat the deployment as a compliance breach. Early engagement does not guarantee approval, but it reduces the risk that the VASP invests in a privacy architecture that the regulator later requires to be dismantled.
How does privacy-technology exposure affect insurance and banking access?
A VASP's decision to support privacy protocols has implications beyond regulatory compliance – it affects the firm's ability to secure and retain crime insurance, errors-and-omissions coverage, and correspondent banking relationships. Insurers and banks view privacy-technology exposure as a red flag indicating elevated money-laundering and sanctions risk, and both industries have tightened their underwriting and due-diligence standards in response to the enforcement actions and sanctions designations of the past three years.
Crime insurance for digital-asset businesses typically covers losses from theft, hacking and fraud, but policies increasingly include exclusions for losses arising from transactions involving sanctioned addresses or from the platform's facilitation of money laundering. An insurer's underwriting questionnaire now routinely asks whether the platform supports privacy coins or privacy protocols, whether the platform permits withdrawals to mixers, and whether the platform's AML program includes specific controls for privacy-related risks. A platform that answers affirmatively to privacy-protocol support but cannot demonstrate adequate controls will face higher premiums, lower coverage limits, or outright denial of coverage. In one matter handled by allied counsel, a platform that supported a privacy coin saw its crime-insurance premium double at renewal, and the insurer imposed a sublimit on claims arising from AML breaches – effectively shifting a significant portion of the regulatory risk back to the platform.
Banking relationships are even more sensitive. Correspondent banks and payment processors conduct ongoing due diligence on their digital-asset clients, and any indication that the client facilitates access to privacy protocols or sanctioned mixers is treated as grounds for account closure. Banks are themselves subject to AML supervision, and a bank that knowingly processes transactions for a VASP that supports mixer withdrawals exposes the bank to facilitation liability and to regulatory scrutiny from its own supervisor. In practice, this means that a VASP seeking to onboard with a Tier 1 bank must represent in the account-opening documentation that it does not support privacy coins, does not permit withdrawals to known mixers, and implements OFAC screening on all outbound transfers. The representation is backed by periodic compliance certifications and by the bank's right to audit the VASP's transaction data.
The loss of a banking relationship is often a business-ending event for a VASP. Without a fiat on-ramp and off-ramp, the platform cannot serve customers who wish to convert between crypto and traditional currency, and the platform's revenue collapses. In recent enforcement matters, we have seen regulators and prosecutors leverage the threat of banking derisking as a compliance tool: a platform that faces a regulatory investigation for AML deficiencies related to privacy technology will often see its bank accounts closed or frozen during the investigation, which in turn pressures the platform to settle quickly and to agree to enhanced compliance terms. For a VASP operating on thin margins, the combination of lost banking access and a regulatory penalty can be fatal.
The operational takeaway is that privacy-technology exposure is not merely a regulatory-compliance issue – it is a business-continuity risk. A VASP that decides to support privacy features must factor in the cost and availability of insurance, the risk of banking derisking, and the possibility that a single high-profile enforcement action in the sector will trigger a wave of account closures and coverage cancellations even for platforms that have not been charged with wrongdoing. In our cross-border structuring practice, we advise clients that the business case for privacy-protocol support must include a contingency for losing primary banking and for operating on secondary or crypto-native rails, which typically means higher transaction costs, limited fiat liquidity, and a smaller addressable user base.
For a scoped assessment of your AML controls around privacy technology – including Travel Rule compliance, sanctions screening and banking-relationship risk – contact OBOLUS at info@oboluslaw.com.
FAQ
What does this regime require from a VASP?
A VASP operating under FATF-aligned AML regimes must conduct customer due diligence, implement real-time transaction monitoring for suspicious activity, comply with the Travel Rule by collecting and transmitting originator and beneficiary information for transfers above the prescribed threshold, screen every transaction against sanctions lists, and file suspicious activity reports where required. Where privacy technology prevents the VASP from obtaining the necessary data – for instance, because a shielded-pool protocol obfuscates sender and receiver identities – the regulator's position across the EU, UK, Singapore and the United States is that the VASP must refuse to support that technology or must implement compensating enhanced due diligence sufficient to satisfy the underlying AML obligation. In practice, most licensed VASPs in the leading hubs do not support external privacy protocols and block withdrawals to known mixer addresses to avoid facilitation liability.
Who must act as MLRO for a crypto firm?
The Money Laundering Reporting Officer is a senior compliance role required by AML regulation in most jurisdictions; the individual holds personal accountability for the adequacy of the firm's AML program and acts as the primary point of contact with the regulator and the financial intelligence unit. Under MiCA, a CASP must appoint a compliance officer responsible for AML and sanctions compliance, and that individual must have the authority, resources and access to senior management necessary to discharge the role effectively. In the UK under the Money Laundering Regulations, a cryptoasset firm must appoint a nominated officer to receive internal suspicious-activity disclosures and to file SARs with the National Crime Agency. In Singapore, a DPT service provider must appoint a compliance officer under the Payment Services Act. The MLRO or equivalent must be named in the licence application, must be approved by the regulator where the jurisdiction requires fit-and-proper vetting, and is personally liable in some jurisdictions for compliance failures that constitute willful neglect or facilitation.
How do regulators audit crypto AML programs?
AML supervision for digital-asset firms follows the same methodology as for traditional financial institutions, adapted to on-chain transaction flows. A regulator conducting an AML audit will request the firm's enterprise risk assessment, the written AML program and policies, transaction-monitoring rules and alert thresholds, KYC files for a sample of customers, and SAR filing records. The regulator will test whether the firm's transaction monitoring detected known suspicious patterns – for instance, by introducing red-flag scenarios and checking whether the firm's systems flagged them – and will review the firm's Travel Rule compliance, sanctions-screening workflow, and staff training records. For firms that support or have supported privacy protocols, the regulator will scrutinize whether the firm conducted a risk assessment specific to those protocols, whether the firm applied enhanced due diligence, and whether the firm filed SARs on customers whose transaction behavior indicated potential misuse of privacy features. The audit typically concludes with a supervisory letter detailing findings and required remediation, and serious deficiencies can result in enforcement action, financial penalties, or suspension of the firm's licence.
About OBOLUS
OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across 70+ jurisdictions, on disputes and on-chain asset recovery across 25+ forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We map the licence stack across operating, custody and payment layers before you commit, and we structure licensing, banking and tax as one mandate rather than three disconnected workstreams. For firms navigating privacy-technology risk, we pressure-test AML controls, draft enhanced due-diligence frameworks tailored to cryptographic privacy features, and represent clients in regulatory investigations where facilitation allegations arise. To discuss your situation, contact info@oboluslaw.com.
By Victor Olsen, Regulatory & Compliance Analyst – Victor specializes in AML frameworks, Travel Rule implementation and the compliance intersection between privacy-preserving protocols and VASP licensing obligations across MiCA, VARA and MAS-supervised regimes.
Related at OBOLUS
- Compliance, AML & Travel Rule for Digital-Asset Businesses – comprehensive advisory on FATF-aligned AML obligations, VASP licensing and cross-border compliance structuring for exchanges, custodians and token issuers.
- Token Buybacks, Burns and Treasury Management: Legal Limits – regulatory and securities-law analysis of on-chain treasury operations for token issuers managing supply and liquidity.
- Regulator AML Audit Defence: Legal Counsel for Digital-Asset Firms – representation in supervisory audits, SAR-filing disputes and enforcement investigations arising from AML deficiencies or allegations of facilitation.
This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.