OPAGO POS – privacy notice
1. Who is responsible
The controller under the General Data Protection Regulation (GDPR) is:
opago GmbH, Moosstraße 4, 83404 Ainring, Germany
Commercial register: HRB 31810. VAT ID: DE359918534.
Privacy questions and general contact: info@opago.com, +49 89 411897390.
Legal notice: www.opago.com/imprint.
The app is a point-of-sale (POS) tool for merchants. Merchants and their staff use it. Customers do not install it.
Notice version: 12 October 2026. At first start, the app shows a privacy step. The user must read and accept this notice before using the app. When this notice changes, the app asks the user to read and accept it again.
No data protection officer is appointed. Send privacy questions to info@opago.com.
2. What the app processes
| Data | Why |
|---|---|
| POS configuration: POS ID, API key, device secret, currency settings, receipt settings, language | To connect the terminal to the merchant's opago account. The data comes from a configuration QR code from the OPAGO Dashboard or from manual entry. |
| Payment data: amount, currency, optional payment note, offline PIN, local payment ID, time, payment status | To create and register a payment and to show its status. |
| LNURL payment data | The app shows each payment as an LNURL (QR code or NFC phone tap). The app never shows a Lightning (BOLT11) invoice on the display and never sends one via NFC. |
| Payment and receipt history on the device | So that the merchant can see past payments. |
Card payments with Bolt Card are switched off in this app version.
3. Camera and NFC
- Camera: only to scan the configuration QR code. The image is processed on the device. The app stores and sends no image.
- NFC: the terminal acts as an NFC tag that gives the payment LNURL to the customer's phone. An NFC tag near the device can open the app; the app reads such a tag only on the device and does not store or send it.
4. What goes to opago servers
The app sends data over HTTPS to api.opago.com:
- payment registration: POS ID, API key (for authentication) and the payment data from section 2; the payment content is also encrypted with the API key;
- payment status queries, the list of supported currencies and the wallet connection of the POS.
When a customer's wallet scans the LNURL, it contacts the opago server directly. During payment registration and the payment callback, the server processes payment data and payer data supplied by the wallet: the UMA identifier, name, address and country. The server uses these data to identify the payer wallet and perform anti-money-laundering and Travel Rule checks.
Before execution, transactions of a paying customer are screened automatically against sanctions lists and risk indicators. The system compares payer and recipient data and the transaction against sanctions lists and risk rules, without a person deciding each case. A transaction can be refused as a result; the payment is then not executed. A paying customer who has a problem with a refused payment can write to complaints@opago.com.
Recipients receive data only as far as needed for the purposes in this notice:
- server hosting providers in the European Union that operate the opago servers on our behalf;
- Microsoft Azure for backups and logs in the region Germany West Central;
- Cloudflare for traffic to the public opago addresses and the related connection data;
- the wallet providers of the merchant and the paying customer, only as far as needed to carry out and check the payment;
- authorities where the law requires disclosure, for example anti-money-laundering supervisors and the financial intelligence unit;
- Google LLC for Google ML Kit diagnostic and usage data (section 5a).
opago servers and backups are located in the European Union. Traffic to the public opago addresses runs through Cloudflare as a processor. Cloudflare can process connection data, including IP addresses and request metadata, and data transmitted through Cloudflare by the opago addresses, at locations worldwide. The transfer safeguards are the EU standard contractual clauses in the data processing addendum with Cloudflare, Inc., and the EU-U.S. Data Privacy Framework certification of Cloudflare, Inc. A copy of the standard contractual clauses is available from the privacy contact at info@opago.com. The data processing addendum is public on Cloudflare's website. Google ML Kit processing and this website are described separately in sections 5a and 9a.
5. Legal basis
We process the merchant and POS data that this app handles (sections 2 to 4) to perform the contract with the merchant (GDPR Art. 6(1)(b)). The POS ID, API key and device secret, and the amount and currency of a payment, are necessary: without them the app cannot connect to opago or register a payment. The payment note is optional. We process technical data for the security and stability of the service on the basis of our legitimate interest (GDPR Art. 6(1)(f)).
Payer-side anti-money-laundering and Travel Rule checks use Art. 6(1)(c) GDPR: legal obligations under anti-money-laundering law and EU rules on transfers of funds. The payer data and check records described in section 4 are kept for five years. Section 5a describes the separate legal bases for Google ML Kit data.
5a. Google ML Kit
The configuration QR scanner uses Google ML Kit by Google LLC. Images are processed on the device and are not sent to Google. When the scanner runs, ML Kit sends diagnostic and usage data from the device to Google:
- device information: manufacturer, model, operating system version and build, and available ML hardware accelerators;
- app information: package name and version;
- an installation identifier;
- performance data, API configuration, input and output sizes, feature version, event types and error codes.
According to Google, ML Kit sends these data over HTTPS and does not pass them to third parties. Google uses the data to measure performance, diagnose errors, maintain and improve the APIs, and detect misuse. Google states no retention period. Sources: ML Kit data disclosure and ML Kit privacy terms.
You can enter the configuration manually instead of using the scanner. Google's Privacy Policy describes its processing of information.
Google may process ML Kit data on servers worldwide. For transfers to the USA, Google LLC is certified under the EU–US Data Privacy Framework. These transfers rely on the European Commission's adequacy decision of 10 July 2023. For transfers to other countries without an adequacy decision, Google relies on standard contractual clauses, as described in its data transfer rules. A copy of the safeguards is available on request by e-mail to info@opago.com.
The scanner is part of the function requested by the merchant: setting up the POS with the configuration QR code. The merchant accepts the terms for this function at onboarding. The legal basis for the scanner function is Art. 6(1)(b) GDPR.
The legal basis for diagnostic data that ML Kit sends to Google is Art. 6(1)(f) GDPR. The legitimate interest is stable and secure operation of the scanner function. The app has no separate consent request.
6. No ads, no analytics SDK
The app contains no advertising, tracking, attribution, crash reporting or analytics SDK of its own. The app's own code sends network requests only to opago servers (section 4); ML Kit is described in section 5a.
6a. Receipt printing
On supported terminals with a built-in receipt printer, the app gives receipt content to the terminal manufacturer's printer software bundled in the app. The EMV library is bundled, but the app does not start an EMV card payment. Bolt Card payments are off. Static inspection of the bundled Java classes and native library dependencies found no direct IP network API and established no additional remote recipient. This inspection does not verify communications by the external device firmware.
7. Storage on the device and retention
- Configuration, settings and payment history are stored encrypted (AES-GCM) with a key in the Android Keystore.
- The LNURL for the current NFC phone tap is stored in app-private storage until the next payment replaces or clears it.
- Payment history stays on the device until the app is uninstalled or its data is cleared.
- Android cloud backup is off for the app. On some devices a device-to-device transfer can copy app data; encrypted values cannot be decrypted on the new device because the Keystore key does not move.
On opago servers, we store data for contract performance until the contract is fully processed. Payer-side anti-money-laundering and Travel Rule records are kept for five years under Art. 6(1)(c) GDPR. Payment or receipt data that serve as accounting records or business correspondence are kept for the longer applicable periods of commercial and tax law. These periods can be up to ten years under section 257 HGB and the Tax Code. After the applicable period ends, the data are deleted.
Technical server log data are deleted after 7 days. Data in the database archive are kept for 5 years where the law requires it.
To request deletion of server data, send an e-mail to info@opago.com. The response is sent within one month. A longer statutory retention period takes precedence over deletion within that month. During that period, use of the retained data is restricted to the legal purpose. The data are deleted when the applicable period ends.
8. Your rights
Under the GDPR you have the right of access, correction, deletion, restriction, data portability and objection, and the right to complain to a supervisory authority. To use your rights, contact info@opago.com. If we process data on the basis of our legitimate interest, you can object at any time (GDPR Art. 21).
The supervisory authority is Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Ansbach. Postal address: Postfach 1349, 91504 Ansbach, Germany. Website: www.lda.bayern.de. Address source: BayLDA contact page.
9. Children
The app is a business tool for merchants and is not for children.
9a. This website
This page is hosted on GitHub Pages (GitHub, Inc.). When you open it, GitHub logs your IP address for security reasons, as described in the GitHub Pages documentation. This page uses no cookies, scripts or trackers.
GitHub, Inc. may process visitor IP addresses outside the European Union under its own privacy statement.
10. Changes
We update this notice when the app or the processing changes. The date at the top shows the last update.