Privacy
Peer keeps your transactions private and your personal data off-chain.
How payment verification stays private
When you verify a payment, your client verifies a measured AWS Nitro Enclave, encrypts the payment-platform session material to that enclave, and asks it to read the matching payment over HTTPS. The seller and Peer operators cannot read the encrypted session material. The enclave produces a signed attestation that the payment matched the order: right amount, right currency, right recipient, and right time window.
Only that attestation result touches the chain. Your name, account details, balances, and other transactions do not.
Who sees what
| Data | Who can see it |
|---|---|
| Your payment handle (e.g. Revtag, Venmo name) | Peer services and your direct counterparty; it is not published on-chain |
| Payment metadata shown for selection | The originating page or integrator after you approve extension access |
| The full payment record used for verification | The measured verification enclave |
| Your wallet address and order amounts | Public, like any on-chain transaction |
| Your encrypted payment-platform session material | The measured enclave can decrypt it in memory; sellers and Peer operators cannot |
What this means in practice
- Sellers never see your bank balance or history; buyers only see the payee details a seller chose to publish.
- There is no KYC on the protocol — your identity lives with your payment platform, not on-chain.
- On-chain observers can see amounts, wallet addresses, and the payment-method hash, which maps to a known platform. They cannot identify the off-chain accounts or counterparties from that data alone.
For the technical detail behind this, see Buyer TEE Verification in the protocol docs.