Esrap POS Connect Privacy Policy

This Privacy Policy describes how Esrap POS Connect, distributed through Google Play, processes personal data. Last updated on 20.10.2026.

1. Application and Scope

Esrap POS Connect displays a business's Odoo point of sale and connects it to supported printers, scanners, customer displays and payment solutions on an Android device. This policy explains the processing of personal data through the application. It covers only the Google Play distribution with package name ee.esrap.android_pos_shell.

The application is intended for business cashiers and administrators. The point of sale may also process the business's customers' data. A device is paired with the business's Odoo using a QR code or a manually entered code. The application does not create a separate Esrap user account. Odoo accounts are created by the business's administrator, and the application does not offer self-registration.

2. Who Processes the Data

The developer is Esrap OÜ, registration number 17482196, address Laanelinnu tee 3-12, Haabneeme alevik, Viimsi vald, Harju maakond 74001, Estonia. Privacy enquiries and requests: support@esrap.ee.

The business using the application is generally the controller of personal data relating to its cashiers, customers and point-of-sale transactions. It determines its Odoo settings, access rights, enabled connections and data retention practices. To exercise rights relating to point-of-sale transactions or Odoo accounts, contact that business.

Where Esrap provides hosting, administration or support and processes personal data on the business's behalf, Esrap acts as a processor within that service, under the business's instructions and the data processing agreement. Esrap may act as a controller when managing its own support communications, protecting its own systems and defending its own legal claims. Sending a diagnostic package to Esrap does not automatically make all its contents data that Esrap may process for its own purposes.

Google's SDK and payment and device service providers process data they receive according to the relevant service terms and their actual role. Not all application data reaches Esrap.

3. Data Used by the Application

Data come from the user, device, paired Odoo, and enabled device and payment connections. The application has no separate feature for reporting device counts or licence usage to an Esrap central server.

4. Camera and Scanning

The camera reads pairing QR codes and QR codes and barcodes at the point of sale. The application's own scanner processes camera images on the device using CameraX and Google ML Kit. This scanner does not send camera frames to Google or upload them to Esrap or Odoo servers. A recognised code is passed to the pairing function or the business's point of sale according to its purpose.

Android requests permission to use the camera. A pairing code can also be entered manually. Camera permission can be revoked in the device settings, after which camera scanning will not work. Some SUNMI devices use a separate SUNMI scanner application, whose processing is also subject to its provider's terms.

5. Google ML Kit Technical Data

ML Kit may send Google technical device and application information, per-installation identifiers, and scanning performance, configuration and error information. Google uses these to analyse SDK operation and use, maintain and improve it, and detect abuse. On-device image recognition does not mean that telemetry is absent.

Google describes transmission of technical data over HTTPS. Its processing is described in the ML Kit terms, data disclosure and Google Privacy Policy. Esrap does not determine Google's telemetry retention period and cannot delete it from Google's systems by revoking Android camera permission.

6. Collecting and Sending Diagnostics

The application maintains size-limited technical logs and removes or masks sensitive fields in diagnostics. Masking does not guarantee full anonymity. A package may contain device and software information, connection and payment status, timestamps, error codes and technical correlation identifiers.

Administrator-initiated remote diagnostics: an authorised administrator can use the paired Odoo to initiate the creation and delivery of a package to the HTTPS receiving address specified in Odoo's configuration. The device does not request separate confirmation for each upload. This capability is explained during device pairing. The recipient depends on the business's configuration. Esrap receives a package only if it is sent to Esrap or Esrap administers the receiving environment.

Local export: a user can create a diagnostic ZIP file. Creating it does not automatically send it to anyone. The user can share it through Android's sharing options or copy it to an authorised computer via USB/ADB. Sharing through an external email or cloud service is also subject to the selected service's terms.

Esrap uses diagnostic packages it receives to resolve support cases and investigate security and reliability issues. For general application improvement, Esrap uses only anonymous findings derived from them. When acting as a processor, Esrap follows the business's instructions and does not use the package's personal data for independent general analytics.

7. Legal Bases for Processing

The business determines the legal basis for processing its point-of-sale, staff and customer data. Depending on the purpose, this may be contract performance, a legal obligation or a documented legitimate interest. The business provides the necessary privacy information to its staff and customers.

For Esrap's own support communications and security activities, the basis is generally its legitimate interest in resolving support enquiries and protecting systems and legal claims under Article 6(1)(f) GDPR. Where the data subject is personally a party to a contract and processing is necessary to perform it, Article 6(1)(b) applies. Legally required records are processed under Article 6(1)(c). Reliance on legitimate interests also requires consideration of individuals' rights and reasonable expectations.

Processing on behalf of a business takes place under its legal basis, instructions and an agreement meeting Article 28 GDPR. Neither this policy nor device pairing constitutes general consent to data processing. Android camera permission does not replace separate consent to other processing where the law requires it.

8. Recipients and Data Location

Data may reach the paired Odoo environment and its hosting or administration provider, enabled printing or payment services, Google through ML Kit, and a sharing service selected by the user. When Esrap provides a service, authorised personnel, infrastructure providers and, where necessary, legal advisers or competent authorities may access relevant information.

Diagnostic packages sent to Esrap are held in Esrap-managed systems in the European Economic Area (EEA), including support attachments and backups. This does not determine the location of data in the business's own Odoo, Google's SDK, or sharing or payment services selected by the user.

Google services may involve processing outside the EEA. Google describes its safeguards for international transfers in its transfer framework information. The applicable mechanism depends on the service and recipient. The business explains transfers involving its own services. Information about safeguards for Esrap's processing is available at support@esrap.ee.

9. Payments and Printing

Enabled payment connections use external payment applications or terminals, such as SoftPOS or Worldline connections configured by the business. The application processes amounts, identifiers, status and, where relevant, receipts needed to start payments and forward results to Odoo.

The PIN is entered in the external payment solution's interface. Application diagnostics are not designed to retain PINs, full card numbers or raw sensitive payment data. The payment provider describes its processing in its own terms.

Receipt content or images may reach the device's printing service, a network printer or a customer display. The business manages paper copies and the hardware it uses.

10. Retention

• The application's and WebView's diagnostic log buffers each have an approximate 512 KiB size limit. Older entries are overwritten when the limit is reached. There is no fixed time-based deletion period.
• A local diagnostic ZIP uses available log entries from the preceding hour. This does not limit the log buffer's own retention to one hour.
• Up to three recent local exports are retained. Files older than seven days are cleaned up on application launch and after a successful new export, not necessarily as soon as the seventh day is reached.
• A pending diagnostic upload file is removed following successful receipt or final termination of delivery. Temporary failures may cause retries.
• The payment result queue is retained until Odoo acknowledges receipt or the relevant recovery process ends. Some recovery history is limited by the number of entries. There is no universal expiry period in days.
• Diagnostic packages sent to Esrap are deleted from active systems no later than 90 days after the support case is closed. When processing on a business's behalf, its instructions and any agreed shorter period also apply. Only the parts needed for a specific security incident, legal obligation or legal claim are retained longer, until that need ends.
• Backup copies of diagnostic packages expire through the relevant backup cycle. They are not used in ordinary operations. Expired data are deleted again following a restoration. Details of the applicable cycle can be requested at support@esrap.ee.
• Esrap's ordinary support correspondence is generally retained for up to 36 months after active communication ends, unless a contract, law or legal claim requires longer retention. A longer correspondence period does not automatically extend retention of diagnostic packages.

The business determines retention of its Odoo data and packages delivered there. The relevant service provider determines retention of Google's telemetry and copies shared by the user.

11. Unpairing and Data Deletion

Unpairing removes pairing data and WebView's local web session data. It does not delete all local application data or Odoo server data. The per-installation device identifier remains.

Uninstalling the application normally removes its application-specific local data. It does not remove files already shared or uploaded, an Odoo user account, or data held on a server. Unpairing is not account deletion.

To request deletion of personal data sent to Esrap, contact support@esrap.ee. Describe your connection to the application, business and, if possible, support case. Do not send authentication tokens, passwords or payment card data. The right to deletion is not absolute, for example where information must be kept for a legal obligation or claim.

12. Security

The application protects the device authentication token using Android Keystore, and Android application backup is disabled. Odoo connections in normal use employ HTTPS. Diagnostic file sharing uses temporary read permissions, and the application does not request broad file storage access. The Play distribution does not request advertising ID, location or microphone permissions.

The security of network printer and local terminal connections depends on the protocol and the business's network configuration. Not all local data are separately encrypted, and end-to-end encryption is not guaranteed for every connection. The business must restrict device and Odoo access and protect its workplace network.

13. Your Rights and Requests

Subject to the conditions set out in law, you may access your personal data, request rectification, deletion or restriction, receive data in a portable format and object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.

For the business's point-of-sale transactions and accounts, contact that business. For Esrap's processing, write to support@esrap.ee. Where Esrap acts as a processor, it helps direct the request to the controller. We may request proportionate additional information to verify identity.

Esrap generally responds within one month to requests within its responsibility as a controller. For complex or numerous requests, the period may be extended by up to two months, with reasons provided within the first month. You may complain to the Estonian Data Protection Inspectorate or seek a judicial remedy.

14. Policy Changes and Related Information

We update this policy when application features, data flows or legal requirements change. We communicate material changes in an appropriate way, for example within the application or through the business's administrator. Where new processing requires consent, it will be requested before that processing begins.

For Esrap's other website and customer communications processing, see Esrap's general Privacy Policy. The relevant business's notice explains its own Odoo processing. The contact for application-related enquiries is support@esrap.ee.