---
title: "Privacy vs. anonymity and why pseudonymity falls short"
description: "Privacy vs. anonymity in stablecoin payments: how pseudonymity, anonymity and confidentiality differ, why pseudonymity falls short and how to pick a model."
path: "/learn/privacy-vs-anonymity/"
label: "Enterprise"
image: "/cards/learn-privacy-vs-anonymity.webp"
---

_Privacy and anonymity are different goals in stablecoin payments: privacy controls who can see payment details, while anonymity hides who the parties are from everyone. This guide explains pseudonymity, anonymity and confidentiality, why pseudonymity leaves business payments exposed and how to choose a privacy model for each workflow. [See how Tempo Zones keep payment activity private](/zones/)._

On most public blockchains, every stablecoin transfer records the sending address, the receiving address, the token and the amount on a ledger anyone can read. A competitor who receives one payment from a company learns that company's wallet address, and with it the full history of payments that address has made.

Regulated businesses also have the opposite obligation. Auditors, banks and regulators expect payment records on request, and anti-money laundering (AML) rules require firms to know who they pay. A privacy model for business payments has to satisfy both needs at once.

## What is privacy vs. anonymity?

Privacy is control over who can see payment information, while anonymity is the condition in which no one, including counterparties and regulators, can link a payment to the people or businesses behind it.

A private payment can be fully known to the sender, the recipient, the service operator and a regulator, yet hidden from everyone else. An anonymous payment hides identity even from the parties who would normally need it. The difference matters because regulated firms can adopt privacy without giving up the records that compliance depends on.

### Pseudonymity, anonymity, confidentiality and transparency

Four models describe how much a payment reveals and to whom. Public blockchains combine transparency with pseudonymity by default.

| Model           | What the public sees                           | Who can see full details                | Fit for regulated payments |
| --------------- | ---------------------------------------------- | --------------------------------------- | -------------------------- |
| Transparency    | Every payment and balance                      | Everyone                                | Low                        |
| Pseudonymity    | Amounts, timing and addresses, not legal names | Anyone who links an address             | Low                        |
| Anonymity       | Neither identities nor links between payments  | No one                                  | Low, audit trails break    |
| Confidentiality | Little or nothing                              | Parties, operator, authorized reviewers | High                       |

## Why pseudonymity falls short for business payments

Pseudonymity hides names but leaves everything else in public view. Researchers showed more than a decade ago that addresses can be grouped and tied to real services by following how funds move between them ([Meiklejohn et al., 2013](https://cseweb.ucsd.edu/~smeiklejohn/files/imc13.pdf)), and commercial blockchain analytics firms now do this at scale. Once one address is linked to a company, its past and future payments are linked too.

Three common workflows show what leaks:

- **Payroll.** A monthly run from one address to the same set of wallets reveals headcount, pay dates and, for anyone who identifies an employee's wallet, that person's salary. The guide to [salary privacy with stablecoins](/learn/salary-privacy-with-stablecoins/) covers this case in detail.
- **Supplier payments.** Recurring transfers to the same recipients show which vendors a company uses and roughly how much it spends with each, information that weakens its position in price negotiations.
- **Treasury movements.** A large transfer to an exchange or a market maker ahead of a quarter close can signal a cash need or an FX position before the company discloses it.

Generating a fresh address for each payment reduces some links but adds operational cost, and deposits, withdrawals and timing patterns still connect activity back to the business.

## What businesses need instead of anonymity

Full anonymity conflicts with the controls regulated firms already run. KYC ties accounts to verified identities, the Travel Rule requires many providers to share sender and recipient information on transfers, and auditors need to trace each payment to an invoice and an approval. A workable model has three parts:

- **Confidentiality from the public.** Amounts, counterparties and balances stay out of public view, so competitors and outside observers cannot reconstruct payment flows.
- **Role-based access inside the business.** Finance sees payments for [payment reconciliation](/learn/payment-reconciliation/), compliance sees what it needs for screening, and support teams see the transactions tied to customer requests.
- **Selective disclosure.** The business or its operator can hand specific records to an auditor, a bank or a regulator when a review, dispute or investigation calls for them, without making everything public.

## How to choose a privacy model for each payment workflow

The right model depends on what a workflow reveals and who has a legitimate reason to see it. Working through four steps per workflow keeps the decision specific:

1. **List who must see the data.** Start with the sender, the recipient and the internal teams that process the payment, then add parties with occasional access, such as external auditors, banking partners and regulators.
2. **List what a public record would reveal.** For a payroll run, that includes headcount, amounts and pay dates. For a treasury sweep, it includes balances, timing and venues.
3. **Map disclosure triggers.** Write down which events require records, such as a year-end audit, a chargeback or a regulator's information request, and what data each one needs.
4. **Check the boundaries.** Note where funds enter and leave the private environment, because those points often stay public, and confirm how local data protection and AML rules apply in each market.

A supplier run and an internal treasury transfer usually reach different answers. More secrecy is not the aim; the aim is that each party sees what it needs and no more. The guide to [privacy by design](/learn/privacy-by-design/) covers how to build these choices into a payment system from the start.

## Limits of payment privacy

Confidential payments reduce what the public sees, but they do not remove every trace. Funds moving into and out of a private environment usually leave a public record, and moving funds in does not hide their earlier public history. Timing, wallet activity and offchain records such as invoices and bank statements can still be correlated.

Privacy also does not change legal obligations. Firms still screen counterparties, file reports and answer information requests, and the rules on data retention and disclosure vary by jurisdiction. Converting between stablecoins and bank money runs through [on- and off-ramps](/learn/stablecoin-on-off-ramps/) that follow local banking hours and keep their own customer records.

## Where Tempo fits

Tempo is a payments network for stablecoins that offers privacy through Zones, private execution environments connected to Tempo Mainnet.

- **Private balances and transfers.** [Tempo Zones](/zones/) keep balances and transfers inside a Zone hidden from the public, while users see their own transactions and balances.
- **Operator visibility for compliance.** The Zone operator can see all activity in its Zone to support reconciliation and audits, and can share specific records with auditors and regulators.
- **Visible boundaries.** Deposits into a Zone show the sender, token and amount on Tempo Mainnet, and withdrawals show the recipient, token and amount, while the account inside the Zone stays private.
- **Issuer controls.** Token issuers can set allowlist or blocklist rules through the [TIP-403 Policy Registry](https://docs.tempo.xyz/protocol/tip403/spec), and [Deel](/customer-stories/deel/) uses Zones to keep contractor wallets private.

KYC, sanctions screening, record retention and the legal review of disclosure rules remain the customer's responsibility. [Contact the Tempo team](/contact/) to discuss private payment workflows.

## FAQ

### What is the difference between privacy and anonymity?

Privacy controls who can see payment details, while anonymity hides who the parties are from everyone. A private payment can still be fully known to the sender, the recipient, the operator and regulators.

### Is pseudonymity the same as anonymity?

No. A pseudonymous wallet address hides a legal name but leaves amounts, timing and counterparties public, so observers can often link the address to a real business with offchain data.

### How does KYC affect anonymity in stablecoin payments?

KYC links accounts to verified identities, so payments through regulated providers are not anonymous to those providers. Payment details can still be kept private from the public.

### Why are wallet addresses alone poor business records?

An address shows where funds went but not who received them or what the payment was for. Accounting and reconciliation need counterparty names, invoice references and approvals stored alongside the address.

### Why does dispute resolution depend on identifiable parties?

Resolving a duplicate payment, a missed invoice or unauthorized activity requires knowing who sent and received the funds. A fully anonymous payment leaves no counterparty to contact or hold to a contract.

### What level of privacy do most businesses need?

Most regulated businesses need confidentiality: payment details hidden from the public, visible to the parties involved, and disclosable to auditors and regulators on request.