Privacy architecture

See what we see.

This is a plain description of what Vesta collects, stores, does not collect, and what is public on the blockchain. It is generated from how the system is actually built, not from a policy template.

Vesta is in a test phase on Base Sepolia. Test data may be deleted at any time. This page will be updated in the same release as any change to the system.

What Vesta collects

From merchants (the business creating payment links):

From customers (the person paying):

What Vesta stores

RecordContentsWhy
Merchant accountemail, business name, wallet address, hashed API key, created dateTo let you log in and receive payments
Invoiceamount, description, order number, status, expiry, a random payment reference, your wallet address at the timeTo show the payment page and match the payment
Paymenttransaction hash, block number, paying wallet address, amount, fee split, confirmations, statusTo confirm the payment and show it in your dashboard
Event logtechnical events (invoice created, payment detected/confirmed, errors) with invoice ids and transaction hashesTo operate the service and investigate problems

What Vesta does not collect

What happens on-chain (public, permanent)

Blockchains are public. When a customer pays, the following is visible to anyone, forever, on Base Sepolia:

Invoice descriptions and order numbers stay in Vesta's database and are never written to the blockchain.

Who can access your information

Vesta does not sell, rent or share transaction information with advertisers or data brokers.

How long information is retained

How to verify this

The smart contract that moves the funds is public and small enough to read in a few minutes; it has no owner and no function that lets Vesta move anyone's USDC. The database schema described above is part of the Vesta codebase. When Vesta publishes its source, this page will link to both.