Remote printQR INTELIGENTE

Remote print - QR inteligente · GOIC SRL

Privacy policy

Effective 3 November 2026 · Version 20261103

Contents
  1. Who we are and how to contact us
  2. Data we use and where it comes from
  3. Where documents go
  4. Why we process data
  5. Phone permissions and your choices
  6. Who can receive data
  7. How long data is kept
  8. Access, correction and deletion requests
  9. Automated rules, children and security
  10. Changes

1. Who we are and how to contact us

GOIC SRL, Romanian registration number J2026057734000 and tax identification number 55698505, with its registered office at Str. Industriei nr. 3bis, Camera 2, Câmpina, Prahova, Romania, provides Remote print - QR inteligente and determines the purposes and means of processing the operational data described here.

For questions, access requests or deletion, contact office@goic.ro. You may also contact us at +40 741 212 266 or at the postal address above. The app's website is https://qri.ro/print/.

This policy covers the Android app, Windows companion and QRI service. It does not replace the policies of Google Play, the app from which you choose a file, or the organisation managing your computer and printer.

2. Data we use and where it comes from

First opening. From version 0.6.11, when internet is available, the app sends QRI a random identifier retained privately for this installation, the phone model, app version and observation time. The server stores a hash of the secret proof, a public support ID, the first observation and most recent observation. Reopenings normally produce at most one report per day; pairing may trigger another update. Offline retries reuse the same proof and do not interrupt printing. For an older installation, this is the first observation after the update, not its historical install date.

After connection we link the observation to the existing service identity used for allowance, without resetting pairings or documents. Administration distinguishes the reported opening, PC pairing and first confirmed job handoff. Allowance reservation or uncertain handoff is not confirmed submission, and a handoff does not prove physical paper output. Direct LAN printing may work without PC pairing. This flow does not retain a click log, screen contents, IMEI, Advertising ID or activity in other apps. These observations are not sent to Google Ads or Firebase.

Pairing and operation. QR pairing creates a technical identity for the Android installation. We use identifiers for the installation, computer and printer, their pairings, public keys and protected technical credentials. The installation identifier is not the phone's IMEI or hardware serial. New pairing does not require a QRI email-and-password account. This does not mean that use of the service is anonymous.

Devices. The phone and Windows companion send device/printer labels, app versions, last activity and printer capabilities. A user-chosen label may contain a person's name. Printer information comes from the paired PC.

Printing and allowance. We use job identifiers, destination, status, event times, page/copy counts, print settings, allowance usage and Free/Premium access status. This metadata supports the queue, access control, accounting, diagnostics and operational usage statistics.

Documents. We process the files you choose or send using Share or Android's print service, and their names, through the route described in section 3. We do not search all documents on your phone.

Subscriptions. When Google Play purchasing is available and you use it, we receive the purchase token and verify the product/plan, state, expiry and renewal with Google. We retain the original purchase-to-installation binding separately from the installation where Premium is active, the encrypted token, its hash, acknowledgement/test indicators and verification times. Technical licence identifiers, access versions and links to replaced purchases support one active phone and prevent an old purchase reactivating. We send Google obfuscated identifiers for the original binding, which does not change when restoring access. QRI does not request or receive your card number or Google account password through this flow. Google Play handles payment. Administrator-granted Premium is separate from a purchase.

Restoring a subscription. At your request, we verify the purchase returned by Google Play on the phone and can move Premium access after confirmation. This mechanism requires no additional QRI account, separate Google sign-in or Google email address. We use a temporary validation request and minimal technical records: pseudonymous installation/licence identifiers, hashes of the token/request, a unique operation identifier, the access version, whether a transfer occurred and operation times. These allow safe retries after an interruption and limit abusive transfers. They are not a consent register and do not contain your documents.

Google Play diagnostics. The Google Play Billing component included in the app can send technical events about its operation to Google. These may include result codes and messages, limited exception information, the app version and a session identifier. Google's mechanism for transporting these events adds information about the device model and manufacturer, Android version/build, configured language and region, network type and network/SIM operator. The configured language and region are not GPS coordinates. This diagnostic flow is separate from subscription verification performed by the QRI server and does not require you to have completed a purchase.

Older accounts and support. If you recover a previous beta account, we may process the name/email already associated with it, authentication data and existing pairings. If you contact us, we receive your contact address, message and information you choose to send. Do not send passwords, keys, tokens or confidential documents for an ordinary support request.

Technical security. Server connections involve an IP address and technical request information. QRI code uses derived identifiers to limit requests. Hosting infrastructure may separately retain access/security logs; these are distinct from the documents you print.

Local printers. Discovery on the current network uses printer advertisements and technical responses: model/name, local addresses, port, protocol, device identifiers and supported formats/capabilities. The local printer inventory stays on the phone and is not uploaded as a list to the QRI server. An address may be updated after a DHCP change using the printer identity. Usage metadata and allowance/Premium authorization still use QRI, including for direct printing.

Optional connection help. Only after your explicit agreement to send it, we may receive a limited technical report: app/Android version, printer vendor and model, stage, IPP/IPPS/Windows protocol, port and address family, HTTP/IPP error codes, advertised formats, job acceptance and attempt duration. A report has an identifier, is technically linked to its sender and helps group the same issue. It excludes documents, filenames, custom printer names, IP addresses, full printer addresses, keys, tokens, arbitrary exception text and logcat. The HTTPS connection still involves an IP at infrastructure level as described separately below. QRI reports are distinct from Google Play Billing diagnostics.

3. Where documents go

Direct local printing. The phone sends the document to a compatible printer on the same network without uploading the document to the QRI buffer or using Windows as an intermediary. For printers without direct PDF support, rendering and conversion to an accepted format happen on the phone. Conversion buffers are processed in memory; the original/queue may remain encrypted locally. Metadata needed for allowance and access is still verified through QRI.

IPPS uses TLS with certificate verification. Some printers offer only local IPP, which sends the document unencrypted on the local network. We do not claim that every route is encrypted in transit. Use IPP only on trusted networks; people controlling the network or printer might see the document. We do not disable certificate verification to automatically accept any certificate or expose the printer to the internet.

Printing through Windows. The following encrypted-envelope and server-buffer rules apply to the computer route.

The phone keeps the queue encrypted in the app's private storage. It may retain an encrypted copy after handoff for reprinting. You can remove the local copy in Activity. Android app-data backup and automatic transfer are disabled in the app configuration. Uninstalling or clearing app data can lose the queue and local keys.

In the private flow, the document and its name are placed in an envelope encrypted for the destination computer. QRI relays and temporarily stores this envelope in private server storage. This protocol does not send the computer's private decryption key to the server. The route is not RAM-only and we do not describe it as having no server storage.

An envelope transfer attempt has a technical validity of no more than five minutes from its creation on the server. The buffer file is removed before the server confirms durable receipt by Windows. Expired envelopes are removed by periodic cleanup. Expiry prevents use of that attempt; it does not guarantee physical erasure in the same second, particularly during a service or cleanup interruption.

Hosting recovery copies may also include the buffer directory containing encrypted envelopes. Removing an envelope from the active buffer does not mean it is simultaneously removed from those copies. Separate retention rules and deletion requests are explained in sections 7 and 8.

Windows decrypts the document and passes it to the printing system. The PC, driver, spooler and printer may keep their own copies. Choosing a computer or printer managed by someone else can give that administrator access to the document. Use destinations you trust. “Predat Windows” means handoff to Windows, not confirmation that a physical sheet has emerged.

The private-envelope rules do not apply retroactively to older beta data. Historical documents, metadata or technical copies may exist separately; deletion requests must also address such identified data.

4. Why we process data

For these limited operational observations of first opening and connection milestones, we pursue the legitimate interest of finding usability problems and improving service operation under GDPR Article 6(1)(f). We use a compact record without advertising profiling or combining it with your Google identity. You may object on grounds relating to your situation or request deletion at office@goic.ro. Settings shows a public support ID; do not send secret proofs or tokens. If we cannot safely identify the data, we explain proportionate verification steps.

We use data needed for pairing, delivery, allowances, restoring a subscription at your request and access verification to provide the service you request and perform our contract with you under Article 6(1)(b) GDPR. Without it we cannot provide connected features or validate the subscription.

Protecting infrastructure, preventing abuse and unauthorised reuse of purchases, investigating incidents and limited operational statistics rely on our legitimate interests in keeping the service safe and functional under Article 6(1)(f). The same basis may support communications with a business customer's representatives who are not themselves parties to the contract. We consider individuals' rights and limit the information used to what these purposes require.

Data required by applicable legal obligations, including lawful requests and relevant financial/accounting records, is processed under Article 6(1)(c). Records kept for a dispute are limited to what is needed to establish, exercise or defend legal claims. A purchase does not justify keeping the printed document indefinitely.

We do not use document content for advertising or training AI models and do not sell user data. Sending an optional connection-help report relies on your explicit agreement requested before sending, under GDPR Article 6(1)(a). Refusing does not prevent other features from working. You may withdraw agreement and request report deletion at office@goic.ro without affecting earlier lawful processing. This agreement does not cover Google Play Billing's own diagnostics. Reading this policy is not blanket consent.

5. Phone permissions and your choices

The camera scans QR codes at your request; you can refuse or withdraw its permission in Android. Notifications show the queue and required actions and can be controlled in system settings. Files are accessed through your selection/sharing or the print service you enable. Internet access and deferred execution support transfers and queue resumption within Android's limits. Refusing a permission may prevent the corresponding feature; it does not constitute consent or refusal for all other processing. We do not request contacts, SMS or microphone permissions for the QRI features described here.

Printer discovery uses network/Wi-Fi state and multicast messages on the current network. It does not request GPS location, scan internet printers or change router settings. Discovery and local checks have technical limits; a saved printer may be refreshed on reconnection. The camera scans QR codes locally; camera images are not uploaded for pairing. Selecting a file does not grant broad access to the phone's photos or documents.

6. Who can receive data

Your chosen computer/printer is the document's destination. To operate QRI we use infrastructure providers, including ROMARG for hosting, and authorised administrative access for maintenance and support. Google Play receives and supplies information needed for payments and subscription verification; its services have their own policies. Google also receives the Play Billing diagnostics described in section 2 through its transport components. Google's policy explains its processing of information received through its services. We may disclose necessary data to advisers or authorities where legally required or needed to defend rights.

Google may process information in multiple countries. Its policy explains its processing and transfer mechanisms: https://policies.google.com/privacy. We do not promise that all processing takes place solely in Romania or the EEA. International transfers for which we are responsible must comply with GDPR requirements, including the applicable transfer mechanism and necessary safeguards. Contact office@goic.ro for information about the recipients and safeguards applicable to your data.

7. How long data is kept

First-open observations not linked to a connected service installation are removed from the active database during administration-list cleanup after three calendar months without reporting. An interruption or cleanup not running may delay removal. Linked observations follow the service-metadata retention rules below. Hosting backups follow the separate rules in this policy.

The queue and local copies remain on your device until you delete them or technical cleanup removes them. Capacity and item-count limits apply; older retained reprint copies may be removed to make room. This is not a guaranteed archive and there is no universal day-based phone retention period.

The server envelope follows the receipt/expiry rules in section 3. Installation, device, pairing, job and allowance metadata is kept for the service relationship, support, security and dispute resolution until it is no longer needed and is deleted, including following a verified request. The current version has no general automatic deletion of this metadata. After three calendar months of inactivity, calculated in Europe/Bucharest time, an installation may be hidden from the current administration list; this is archiving, not deletion.

For Google Play integration, periodic server maintenance removes the encrypted token after 60 days and the subscription record after 90 days from the last known expiry. These rules apply to the active database when maintenance runs; an interruption can delay cleanup. They do not mean that Google's records or every technical copy are deleted at the same time. A verified renewal updates the expiry date.

The temporary restore request is valid for five minutes and becomes eligible for removal after expiry. Technical records of completed restore operations are retained for 30 days in the active database. Cleanup runs when preparing a restore or during periodic maintenance; deletion is not guaranteed at the exact second of expiry. The original obfuscated binding follows the retention and deletion procedure for the installation identity, not the operation's 30-day period. These rules do not set the retention of backups or Google's own records.

Logs and recovery copies are separate from the buffer. Database migration snapshots currently have no automatic expiry. Those copies, historical beta data and infrastructure backups require separate handling when deleting data; the five-minute rule does not cover them. Keeping a recovery copy does not authorise its use for other purposes. Where particular data must be kept for a legal obligation or a specific dispute, retention is limited to the necessary data and duration, and we explain the reason on request.

A single expiry period covering all QRI data in infrastructure logs and recovery copies has not currently been confirmed. We do not promise deletion of every copy within a fixed number of days. When handling a request, we explain which data has been removed, which copies require separate handling and any legal reason for retaining particular data. This notice does not authorise retention without a justified need.

Optional help reports are kept in a separate SQL reports database with limited administrative access. They are deleted from the active database when the issue is marked resolved; unresolved reports expire after 30 days and are removed by service cleanup. We do not retain an archive of resolved reports. Active-database cleanup is not a promise of simultaneous deletion from hosting backups; the separate rules below also apply to them. You may request report deletion, quoting its identifier if known.

Saved local printers stay on the phone until removed or merged/refreshed. Removing a printer does not recall documents already accepted by a destination or cancel a subscription.

8. Access, correction and deletion requests

Email office@goic.ro with the subject “Remote print personal data” and describe your request. If known, identify the installation or older beta account concerned, without passwords, tokens or document content. Where we have reasonable doubts, we may request proportionate additional information to verify your link to the data; we do not automatically require a copy of an identity document.

Instructions and a direct way to request deletion: https://qri.ro/print/legal/deletion-20261103-en.html.

Subject to applicable law, you can request access, correction, deletion, restriction and portability. You may object to legitimate-interest processing on grounds relating to your situation. Where processing relies on consent, you may withdraw it without affecting the lawfulness of earlier processing.

We respond without undue delay and normally within one month. Where a lawful extension is necessary because of complexity or the number of requests, we explain the reasons within the first month; the extension may be up to two further months. Requests are normally free of charge. If we refuse all or part of a request, we explain why and how to challenge it.

You may complain to ANSPDCP, Romania's supervisory authority: https://www.dataprotection.ro/?page=Plangeri_pagina_principala, or to the competent authority in your country where applicable. Judicial remedies remain available.

Deletion can remove pairings and information needed to use the service. Deleting the app or QRI data does not automatically cancel a Google Play subscription: cancel renewal separately in Google Play if you no longer want the service. Data on a computer/printer or independently managed by Google may require a request to the respective administrator.

9. Automated rules, children and security

The system automatically applies allowances and verified subscription status to permit or defer print jobs. It does not use documents for credit scoring or advertising profiles. Contact support for human review if an outcome seems incorrect.

The service is intended for people aged 13 and over and is not designed or promoted for children under 13. Minors must meet applicable legal requirements, including parental or representative authorisation where required. A parent or representative who believes a minor's data is being handled improperly can contact us for investigation and appropriate action.

We use HTTPS for QRI services, encrypted queues/private envelopes and access controls. The local IPP route may be unencrypted as explained in section 3; IPPS verifies certificates. Technical completion signals do not certify physical paper output. No transmission or storage is entirely risk-free. Protect access to your phone and PC, keep applications updated and do not share pairing QR codes with unauthorised people.

10. Changes

The applicable version is published at https://qri.ro/print/legal/. For significant changes, we will provide appropriate information before new processing starts and request separate consent where the law requires it.