--- path: /learn/salary-privacy-with-stablecoins/ title: "Salary privacy with stablecoins: what is public" description: See who can view stablecoin salary payments, balances, and withdrawals, and how Tempo Zones protect account activity while preserving authorized access. image: /og/2026-q4/og_2026-q4_learn_salary-privacy-with-stablecoins_title-f5_v01.png publishDate: 2026-10-26 keywords: salary privacy with stablecoins, stablecoin payroll privacy, private stablecoin payments, stablecoin balance privacy label: Payments timeToRead: 5 seoTitle: "Salary privacy with stablecoins: what is public" faq: - question: Are stablecoin salary payments private by default? answer: No. Visibility depends on the network and payment architecture. A transfer to a public address can expose payment and account activity even if the address does not include a person's name. - question: Can a Zone operator see private balances? answer: Yes. The operator can inspect its ledger. Customers' access is scoped to their own accounts. In a Tempo-hosted Zone, both the business and Tempo have visibility. - question: Are deposits and withdrawals hidden? answer: No. Their public records include amounts and timing. Deposits conceal the recipient account inside the Zone, and withdrawals conceal the sending Zone account. - question: Does moving funds into a Zone hide earlier payments? answer: No. Existing public transaction history remains public. The privacy boundary applies to the account information held inside the Zone. locale: en canonical: https://tempo.xyz/learn/salary-privacy-with-stablecoins/ --- # Salary privacy with stablecoins: what is public _Stablecoin salary payments are not private by default. Payroll teams need to separate the information visible on a public blockchain from records available only to workers, operators, and authorized services. [Explore Tempo Zones](https://tempo.xyz/zones/) to see how private balances can fit into a payroll product._ A worker expects to see their pay and account balance without making either available to strangers. The payroll provider needs enough information to deliver the payment, answer support questions, and reconcile its records. Paying into a public blockchain address can expose more than the current payment. An observer may be able to inspect the address's balances, earlier transfers, and subsequent activity. ## What a public payroll payment can reveal On a transparent blockchain, an explorer can show sender and recipient addresses, transferred tokens, transaction timing, and other activity associated with an account. Ethereum's [block explorer documentation](https://ethereum.org/developers/docs/data-and-analytics/block-explorers/) describes these publicly accessible records. Repeated payments to the same address may suggest a payment schedule. If the address is associated with a worker, the public record can become more informative. This is an inference from the available data: a transfer amount alone does not establish a person's salary, employment status, or total income. For a payroll team, the decision is therefore broader than whether a payment displays a name. It includes what a recipient exposes by receiving, holding, using, and withdrawing the funds. For the broader operating model, see the guide to [stablecoin payroll for global teams](/learn/stablecoin-payroll-for-global-teams/). For how privacy methods work on blockchains more generally, see [blockchain data privacy](/learn/blockchain-data-privacy/). ## Who sees what with Tempo Zones Tempo Zones provide a private ledger connected to Tempo Mainnet. Customers access their own account information, and the operator retains access to the underlying ledger. The public network still records activity where funds enter or leave the Zone. The distinction is visible in the [current privacy model](https://tempo.xyz/developers/docs/zones/privacy): |Part of the flow|Visible to the public|Access inside the private environment| |-|-|-| |A deposit into a Zone|Mainnet depositor, token, amount, refund recipient, and timing|The deposit recipient inside the Zone and its memo are encrypted to the operator.| |A worker's balance and account activity inside the Zone|The private account ledger is not shown by a public Tempo explorer.|The worker accesses their own account. The operator can inspect the ledger.| |Another customer's account|No public view of that private account|Account access controls prevent customers from reading one another's balances.| |A withdrawal to Tempo Mainnet|Destination, token, amount, timing, and settlement commitments|The withdrawing account inside the Zone is hidden from public view.| |An interaction with a public application|The application's onchain actions and amounts remain visible.|The Zone account behind the interaction remains private from public observers.| Read access and permission to spend are separate. An account's visibility settings do not decide which services can sign payments. [Account access documentation](https://tempo.xyz/developers/docs/protocol/zones/accounts) describes how authenticated requests restrict balance and activity reads. ## Privacy changes at the boundary A private balance does not make the whole payment journey invisible. An employer's deposit can be public even when the recipient account inside a Zone is concealed. After a worker withdraws to a public address, later activity at that address follows the public network's visibility rules. Using a public exchange, vault, or bridge can also produce public records. Visible amounts and timing can create opportunities to correlate activity. Keeping an internal account private does not erase its earlier public history or guarantee that observers cannot draw inferences. Bank withdrawals introduce another set of records. The payout provider and receiving bank handle information for their part of the payment. Privacy inside a Zone does not hide information that a worker provides to those services. ## Keep the payroll application private too A private ledger is one part of the product. The application still decides which people and services can retrieve records, export them, or display them. For a Tempo-hosted Zone, both the business and Tempo can see balances and activity. Finance, support, and other services need access appropriate to their role. Their access depends on the implementation, including the accounts their credentials can read. The same boundary should extend to support tools, reports, logs, and cached data. A worker should not lose privacy because an application exposes another customer's records. Tempo's privacy documentation explicitly calls out these application controls, and the [privacy by design guide](/learn/privacy-by-design/) covers the same principles across payment workflows. ## What Deel shows in production [Deel uses Tempo Zones in production](https://tempo.xyz/customer-stories/deel/) to keep contractor balances and payout history private. Contractors see their own balances, while Deel retains records for reconciliation and audit. Deel's treasury deposit into the Zone remains visible on Tempo. This means workers use a familiar product while their balances and payout history stay out of public view. Funding, earning, and withdrawing still have different visibility boundaries. ## Build around the supported workflow Tempo Zones are available for enterprises through early access. The [current integration guide](https://tempo.xyz/developers/docs/zones) covers deposits, private balance and activity reads, and withdrawals. It also states that general TIP-20 transfers and user contract deployment are disabled in the current permissioned runtime. Teams should evaluate the deployment's supported assets, funding rules, access controls, and withdrawal process against their actual payroll flow. [Talk with Tempo](/contact/?source_article=/learn/salary-privacy-with-stablecoins/&cta_location=article_footer) about the setup your product needs. ## FAQ **Are stablecoin salary payments private by default?** No. Visibility depends on the network and payment architecture. A transfer to a public address can expose payment and account activity even if the address does not include a person's name. **Can a Zone operator see private balances?** Yes. The operator can inspect its ledger. Customers' access is scoped to their own accounts. In a Tempo-hosted Zone, both the business and Tempo have visibility. **Are deposits and withdrawals hidden?** No. Their public records include amounts and timing. Deposits conceal the recipient account inside the Zone, and withdrawals conceal the sending Zone account. **Does moving funds into a Zone hide earlier payments?** No. Existing public transaction history remains public. The privacy boundary applies to the account information held inside the Zone. --- ## Site links - [Tempo home](/) - [Privacy policy](/privacy-policy/) - [LinkedIn](https://www.linkedin.com/company/tempo) - [X](https://x.com/tempo) - [YouTube](https://www.youtube.com/@tempo) ### Products - [Earn](/earn/) - [Routes](/routes/) - [Zones](/zones/) ### Solutions - [Agentic payments](/solutions/agentic-payments/) - [Credit](/solutions/credit/) - [Cross-border payments](/solutions/cross-border-payments/) - [Institutional settlement](/solutions/institutional-settlement/) - [Stablecoin accounts](/solutions/stablecoin-accounts/) - [Tokenized deposits](/solutions/tokenized-deposits/) ### Developers - [Documentation](/developers) - [Tempo Explorer](https://explore.tempo.xyz/) - [Tempo API](/developers/docs/api) - [Performance](/developers/performance) - [Status](https://status.tempo.xyz/) - [GitHub](https://github.com/tempoxyz) ### Resources - [Blog](/blog/) - [Customers](/customer-stories/) - [Learn](/learn/) - [OUSD](/ousd/) - [Partners](/partners/) - [Reports](/reports/) - [Stablecoin Advisory](/stablecoin-advisory/) ### Company - [About](/about/) - [Careers](/careers/) - [Brand kit](/brand/) - [FAQ](/faq/)