TrezorPay is built to need as little data as possible. There is no account, no sign-up and no API key, so TrezorPay never asks for your name, email address, phone number or identity documents. This policy explains what the API and the website do process.
1. Data the API processes
When you create a payment address: the coin and network, the callback URL (including any query parameters you put in it), the destination wallet addresses and their split, the options you set, and the payment address generated for you.
When a payment arrives: its transaction id, the sender address, the amount, the block it was included in and its confirmations, then the forwarding transaction, the fee and the network cost. All of this is already public on the blockchain.
When a callback is sent: the payload sent to your callback URL and the status and time of each delivery attempt.
Server logs: like any web server, the API and the website may log the IP address, the request path and the user agent of each request, to keep the service secure and to investigate errors.
Do not put personal data, such as a customer’s email address or name, in a callback URL. Use an order id and keep the rest on your own server.
2. Why it is processed
To run the service you asked for: generate addresses, detect and confirm payments, forward them to your wallet, compute fees and send callbacks. Also to protect the service against abuse and attacks, and to meet legal obligations. The data is never sold and never used for advertising.
3. The website
The trezorpay.com website and documentation use no cookies, no analytics and no advertising trackers. The documentation remembers your light or dark theme choice in your own browser’s storage; it is never sent to TrezorPay.
4. Who else sees data
Blockchain networks: payments and forwards are public on-chain, as on any blockchain. Blockchain node providers: TrezorPay queries them for blocks, balances and transactions, which means they see the addresses and transactions it asks about. Price providers: asked only for exchange rates, with no data about you. Hosting: the servers that run TrezorPay. Your callback URL: receives the payment details you asked for. Data may also be disclosed when the law requires it.
5. How long it is kept
A payment address and its settings are kept for as long as the address can receive payments, since a later payment must still reach the right wallet. Payment, forwarding and callback records are kept as long as needed to run the service, settle fees and meet legal obligations. Server logs are kept for a short period and then deleted. Data written to a blockchain is permanent and cannot be deleted by anyone.
6. Security
Every request uses HTTPS. The keys that control payment addresses are derived in memory from an encrypted seed and are never stored, logged or returned. Every callback is signed so you can check it really comes from TrezorPay.
7. Your rights
Depending on where you live, you may have the right to access, correct or delete data about you, or to object to or restrict its processing. Because there is no account, a request must show that you control the callback URL or wallet concerned. Deleting a payment address’s settings stops it from forwarding new payments, and on-chain data cannot be deleted. You may also complain to your data protection authority.
8. Children
The service is meant for businesses and is not directed at children.
9. Changes and contact
This policy may be updated; the date at the top shows the latest version. Requests and questions about privacy go through the support channel listed on this website. See also the terms of service.