QR2Stripe is built to touch as little personal data as possible. Here is exactly what is handled, by whom, and why.
Last updated: 18 November 2026.
Who we are
QR2Stripe (the Android app, the QR2Stripe Pay WordPress plugin, the embed script and the website qr2stripe.com) is operated by RadomÃr Vach, Na Veselà 928/15, 140 00 Czech Republic, company ID 718 00 816. For the website, for support and for our custom integration service we are the controller of the personal data described below.
Privacy questions and requests: [email protected].
The short version
- We never see card numbers. Cards are read and processed by Stripe Terminal. Neither the app, your website nor we receive or store card numbers or CVV codes.
- Your payments stay between you and Stripe. Money goes to your own Stripe account. The app and the WordPress plugin talk to your website and to Stripe, not to a QR2Stripe server of ours.
- No advertising, no selling of data. We do not sell personal data and do not use it for advertising.
- You are in control. The payment list on the phone can be cleared at any time, and you can ask us about any data we hold.
Who is responsible for what
QR2Stripe is a tool that a business (the “merchant”) uses to charge its own customers. That gives three different situations:
| Situation | Who decides how the data is used |
|---|---|
| You visit qr2stripe.com or write to us | We are the controller. This policy applies. |
| A merchant takes a payment from a customer with the app and a website or plugin | The merchant is the controller of its customers’ and orders’ data. Stripe acts as an independent controller or processor for payment data under its own terms. We provide the software and do not receive this data. |
| We build or run a custom integration for a merchant | We act as a processor on the merchant’s instructions, under a separate agreement. |
If you are a customer who paid a merchant and you want to know what the merchant holds about you, please contact the merchant first. We will gladly help you find the right contact.
The QR2Stripe app
The app is used by the merchant’s staff to scan a payment QR code and collect a card or phone payment with Tap to Pay.
| Data | Why | Where it goes |
|---|---|---|
| Camera image | To recognise the payment QR code | Processed on the phone by Google ML Kit. Images are not stored and not sent to us. |
| Payment request: reference or order number, merchant name, description, amount, currency, website address | To show you what is being charged and to start the payment | Fetched from the merchant’s website or backend that created the QR code |
| Operator access token | To let the app prove it may take payments for the merchant | Stored encrypted on the phone (Android Keystore) and sent over HTTPS to the merchant’s website or backend |
| Card and payment details | To take the payment | Handled by Stripe Terminal. Never read or stored by the app or by us. |
| Approximate device location, device integrity and security information | Required by Stripe to provide Tap to Pay and to prevent fraud | Collected by the Stripe Terminal SDK and processed by Stripe under Stripe’s Privacy Policy |
| List of accepted payments: reference, description, merchant, website host, amount, currency, time, Stripe payment ID. At most the newest 100. | So you can see your latest payments and send a confirmation | Stays in the app’s private storage on the phone, excluded from backups, no card data. Not sent anywhere by the app. |
| Webhook settings and queue (only if you switch the webhook on) | To notify your own system after every successful payment | Payment details are sent to the address you entered, which you choose and control. The address, headers and signing secret are stored encrypted on the phone. Undelivered calls wait in a queue of at most 50 and are removed when delivered, after 10 attempts, or when you switch the webhook off. |
The app asks for permission to use the camera and the approximate location. Without the camera it cannot scan codes, and without the location Tap to Pay cannot run. You can withdraw either permission in the Android settings at any time.
The app has no advertising, no analytics and no tracking of its own, and it does not create an account with us. If you share a payment confirmation by e-mail or message, it goes through the app you choose, under that app’s own privacy policy.
The WordPress plugin and the embed script
The QR2Stripe Pay plugin runs inside the merchant’s own WordPress site. It stores payment records (reference, description, amount, currency, status, Stripe payment ID and the related order data the merchant supplies) in the merchant’s own WordPress database, and it keeps Stripe keys and the webhook secret in the merchant’s own settings. This data stays on the merchant’s hosting. We do not receive it. The plugin does not delete payment records automatically; the merchant decides how long to keep them and is responsible for informing its own customers.
The embed script and the open protocol work the same way: they connect the merchant’s own website to the app and to Stripe. A merchant who uses them should mention payment processing by Stripe in its own privacy policy.
This website
- Server logs. Like every website, our web server and hosting provider process technical data about each request (IP address, date and time, page requested, browser and device type) to deliver the site, keep it secure and find errors. Our legal basis is our legitimate interest in running a secure website.
- Cookies. We use only cookies that are strictly necessary for the website to work. We do not use advertising or analytics cookies. If that changes, we will ask for your consent first and update this page.
- Documentation. The guides at /documentation/ are public pages. Reading them does not require any account.
- Links to other sites. Links to Stripe, Google Play and other external sites lead to services with their own privacy policies.
Contacting us and support
When you e-mail [email protected] we process your e-mail address, your name if you give it, and the content of your message, to answer you and to keep a record of the conversation. The legal basis is our legitimate interest in answering enquiries and, if you ask about a service, steps taken before or under a contract. Please do not send card numbers, Stripe secret keys or access tokens by e-mail.
Custom integration service
If we build or operate an integration for you, for example a service on your own server that moves Stripe payments into an accounting system, we process only the fields your system needs, only on your instructions and under a data processing agreement with you. The service runs on your infrastructure unless we agree otherwise in writing.
Why we may process data (legal bases)
- Contract (Art. 6(1)(b) GDPR): to provide a service you asked for, such as a custom integration.
- Legitimate interests (Art. 6(1)(f) GDPR): to run and secure the website, answer enquiries and prevent abuse.
- Legal obligation (Art. 6(1)(c) GDPR): to keep accounting and tax records.
- Consent (Art. 6(1)(a) GDPR): only where we ask for it, for example for optional cookies if we ever add them. You can withdraw consent at any time.
Who else is involved
- Stripe processes card-present payments, device and security information for Tap to Pay, and the merchant’s Stripe account. See stripe.com/privacy.
- Google provides the ML Kit scanner used for on-device QR recognition, Google Play Services and Google Play, which distributes the app.
- Our hosting and e-mail providers store this website and our mailbox on our behalf.
- Google Play sells the app subscription. It handles your payment details and the subscription; we receive only the information needed to confirm that your subscription is active and to meet our accounting duties.
- The merchant whose website, plugin or system the app is connected to.
- Authorities and advisers where the law requires it, and our accountants and lawyers under a duty of confidentiality.
We do not sell personal data.
Transfers outside the EEA
Stripe and Google may process data in countries outside the European Economic Area, including the United States. These providers rely on safeguards such as the EU-US Data Privacy Framework or Standard Contractual Clauses. Details are in their own privacy policies.
How long we keep data
- In the app: the newest 100 payments, until you clear the list or uninstall the app. The webhook queue holds at most 50 calls until delivered or dropped, as described above.
- Support e-mails: as long as needed to handle your request and afterwards for the time we may need them to resolve a dispute.
- Server logs: for a short period set by our hosting provider, then deleted or overwritten.
- Contract, invoice and accounting records: for the period required by tax and accounting law.
- On a merchant’s website or in Stripe: as decided by the merchant and by Stripe, because we do not hold it.
Security
All traffic between the app, the merchant’s website and Stripe uses HTTPS; the app does not allow unencrypted connections. The operator token and the webhook secret are stored encrypted on the phone. Each QR code can be paid only once and expires after a few minutes, and the app accepts QR codes only from websites the merchant has added. No system is perfectly secure, but we design QR2Stripe so that there is little data to protect.
Your rights
For the data we control, you have the right to access it, correct it, have it erased, restrict or object to its processing, and receive it in a portable format. Where processing is based on consent, you can withdraw it at any time. Write to [email protected]; we answer within one month. Some data we must keep by law, such as accounting records, and we will tell you if that applies.
You also have the right to complain to a data protection authority, in particular in the country where you live or work. In the Czech Republic this is the Office for Personal Data Protection (uoou.gov.cz).
Children
QR2Stripe is a business tool and is not directed at children. We do not knowingly collect personal data from children.
Changes to this policy
When the product or the law changes, we update this page and the date at the top. If a change is significant, we will say so on the home page or in the app’s release notes.
Contact
Questions about this policy or about your data: [email protected].