Tempo Takes Zones Privacy System Into Production With Deel

Tempo, a blockchain for stablecoin payments, said on Oct. 14 that payroll platform Deel is the first customer using its Zones privacy system in production, keeping contractor balances and payout history out of public view.

According to Tempo’s Deel case study, the payroll company’s treasury deposit into its Zone remains visible on the public network. Which contractors receive payments, how much each receives and what they hold are private. Contractors see their own balances, while Deel retains access for reconciliation and audit.

The rollout adds privacy to an existing wallet that expanded to eligible contractors in more than 80 countries in August. Tempo says the integration leaves Deel’s existing customer wallets and treasury infrastructure unchanged, with embedded-wallet provider Privy supporting Zones through its APIs.

Tempo outlined Zones in April, when it described availability with design partners and phased production deployments ahead. The product remains in limited access.

Private Balances, Public Connections

Each Zone maintains a private ledger connected to Tempo’s public network through a portal that holds its backing assets. The privacy documentation makes the boundary clear: the operator can read the ledger, and deposits and withdrawals leave public records, including token amounts and public-network addresses.

Operators can restrict which participants and assets a Zone supports and apply token-issuer transfer policies, according to Tempo’s technical description. The model keeps records away from public observers without hiding them from the business running the Zone.

Private accounts can also use public financial products. Tempo posted a demo of an account depositing into a Zone, accessing a public Earn product and bringing its position back into the Zone. “Its balance and holdings inside the Zone remain private,” the company wrote.

The current developer preview is narrower than a general-purpose private blockchain: general account-to-account token transfers and user-deployed contracts are disabled. Funding through its deposit and withdrawal infrastructure is supported.

Tempo’s settlement documentation also says execution-proof enforcement depends on the deployed verifier and network configuration. Forced exits are not generally available, leaving withdrawals dependent on the operator continuing to process and submit batches.