> ## Documentation Index
> Fetch the complete documentation index at: https://docs.veromerchants.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Privacy and Data Ownership

> Who can read a digital receipt, and who decides where it goes

Receipts show what someone bought, so it's fair to ask who else can see them. The short answer: only the customer, and anyone they choose to share with.

> [card] Locked before it leaves your checkout
>
> Each receipt is encrypted for one customer before it's sent anywhere. It stays locked the whole way to their banking app.

> [card] Only the customer has the key
>
> The key that opens a receipt is kept on the customer's own device. Merchants, banks and Vero can't read it.

> [card] The customer decides who sees it
>
> Customers can share receipts with a bank, a brokerage, an expense or tax app, or anyone else they choose, one receipt or many at a time.

> [card] Not locked to Vero
>
> Receipts follow an open standard, the Digital Receipt Protocol. Customers can take them with them if they switch banks or apps.

***

## What each party can see

| Who | What they can see |
| - | - |
| **You, the merchant** | Your own sales, as you do today. Once a receipt is sent, you can't read the locked copy. |
| **The customer's bank** | The charge amount and store name, which it already has from the payment. Not the items. |
| **Vero** | Only the locked copy, which it can't read. |
| **The customer** | Everything on the receipt. |
| **Apps the customer chooses** | Only the receipts the customer shares with them. |

***

## Why it's hard to fake

Every receipt carries two digital signatures: one from the merchant and one from the customer's bank. If anyone changes a single item or price, the signatures no longer match and the receipt shows as unverified.

***

## Want the details?

These pages explain the same points for security teams, banks, brokerages and developers.

> [card] [Encryption and key ownership](https://docs.veromerchants.com/digital-receipts/protocol/encryption.md)
>
> The encryption, signatures and key storage behind each card above.

> [card] [Portability and sharing](https://docs.veromerchants.com/digital-receipts/protocol/portability.md)
>
> How banks, brokerages and other apps get access to receipts.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.