Privacy features are planned
Privacy
Confidential payments on an open ledger
A public chain lets anyone verify a payment, and it also lets anyone read a salary. Gleo is designing confidential payments for the cases that need them, such as payroll and treasury, while the proof that every transfer adds up stays public and auditors keep their view.
The idea
Public proof, private details
The usual choice is a public ledger nobody can use for payroll, or a private one nobody can check. Gleo keeps the proof open and the details closed: anyone can confirm that no money was created or lost, while only the parties and their auditors can read the amounts.
Who needs it
Two audiences, two different concerns
Companies and institutions
A treasury does not want competitors reading its positions, and an employer cannot publish payroll. Amounts must be hidden from the public while auditors and regulators can still see them.
Developers
Builders want privacy as a setting per asset or per flow, using standard tools, rather than a separate chain with its own wallets and liquidity.
Design
How privacy will work on Gleo
- 01
Public unless chosen otherwise
Ordinary transfers on Robinhood Chain show sender, recipient and amount. That makes them easy to verify, and it stays the default. - 02
Opt-in, asset by asset
An issuer will be able to mark an asset as confidential, so balances and amounts are encrypted on-chain while each transfer still proves it balances. - 03
Built for audit
Confidential assets carry a viewing key held by the issuer and its auditor, so compliance never depends on the public seeing everything.
Building blocks
The parts the privacy work is built from
None of these are live on Gleo yet. Each one is labelled planned until it ships and has been audited.
- Confidential tokens PlannedEncrypted balances and amounts, with proofs that every transfer balances.
- Private payments PlannedTransfers that hide who paid whom from the public but not from the parties.
- Zero-knowledge verifiers PlannedContracts that check a proof instead of reading the data behind it.
Where it matters
Payments that should stay between the parties
Payroll
Pay staff on-chain without publishing everyone's salary.Treasury management
Move reserves between entities without signalling strategy.Business payments
Keep supplier prices and customer purchases between the two sides.Institutional settlement
Settle large trades without showing positions to the market.
FAQ
Questions about privacy on Gleo
Are my Gleo payments private today?
No. Transfers made with the Send tool are ordinary public transactions on Robinhood Chain; anyone can see the addresses and amounts on the explorer.
Could confidential assets be used to dodge compliance checks?
They are designed not to be. Confidential assets carry issuer and auditor viewing keys, and holder approval still applies to every transfer.
Does this website track me?
The privacy policy has the detail. In short: there are no accounts, and practice receipts stay in your own browser.
Talk to us
Need confidentiality for a real flow?
Tell us what has to stay private and who still needs to see it. That shapes what we build first.