zrsPOS — Privacy Policy
Version of 11 November 2026 · In force from 11 November 2026 Contact: support@zrspos.com
This policy explains what personal data zrsPOS processes, why, for how long and how. It exists in Portuguese and English; the Portuguese version is the binding one.
It is written for four groups of people:
- merchants who install zrsPOS on their Shopify store, and their staff;
- customers of those merchants, whose data appears on the fiscal documents issued through zrsPOS;
- travellers for whom a merchant prepares a tax-free form;
- visitors to zrspos.com, including people who send us an access request.
1. Who we are
zrsPOS is a service provided by José Maria Pinto Cardoso Saraiva de Reffoios, a sole trader (trabalhador independente), tax number 236212419, with tax address in Lisboa. The provider is a natural person, not a company. In this policy, "zrsPOS" and "we" mean that provider.
- Provider: José Maria Pinto Cardoso Saraiva de Reffoios, a sole trader, trading as zrsPOS
- Tax number (NIF): 236212419
- Tax address: Lisboa
- Contact for personal data: support@zrspos.com
- Data protection officer (DPO): none appointed. The GDPR does not require one for this processing (article 37): zrsPOS does no large-scale systematic monitoring and processes no special categories of data. Questions about personal data go to support@zrspos.com.
The Terms of Service and the Data Processing Agreement complete this policy.
2. What zrsPOS does
zrsPOS connects a merchant's Shopify POS to the merchant's own SAGE 50c invoicing software. Every sale, return or exchange at a store's till produces a Portuguese fiscal document, issued by the merchant's SAGE, and zrsPOS prints it. Where the merchant switches it on, zrsPOS also e-mails the document, closes the till and prepares Global Blue tax-free forms.
3. Who is responsible
For the data of the merchant's customers, travellers and staff, the merchant is the controller. The merchant decides to issue the documents and is legally obliged to keep them. zrsPOS is its processor and processes that data only on the merchant's instructions, under the Data Processing Agreement. If you bought from a shop that uses zrsPOS, contact that shop first; we help it answer.
zrsPOS is the controller for:
- merchants' data as zrsPOS customers (account, subscription, billing, contacts);
- access requests sent through our website;
- support e-mails;
- technical data from our servers (request logs, errors) and the security of the service.
4. Data we process for the merchant
We receive this data from Shopify when a sale, return or refund happens, from the merchant's SAGE, or from the merchant's staff at the till through the zrsPOS extensions.
| Data | What for |
|---|---|
| Customer's name, NIF, billing address | Required content of a Portuguese fiscal document |
| Customer's e-mail and phone | Finding or creating the customer in the merchant's SAGE; e-mailing the document, if the merchant turns that on; finding the document at the till |
| Order lines, amounts, payment method, store, returns, store-credit vouchers | Issuing, correcting, reconciling and reprinting the document; closing the till |
| Online orders, only when returned at a store's till | Finding the original sale for the return |
| Document data returned by SAGE (number, ATCUD, QR, totals) | Printing, reprinting and reconciling |
| Tax Free (optional): traveller's first and last name, country of residence, nationality, passport or other travel document number, type, issuing country and expiry, date of birth, sex, the document's machine-readable zone (MRZ), and optionally e-mail and phone | Preparing the Global Blue tax-free form the traveller asks for |
| Merchant's staff: Shopify staff identifier; staff e-mail when Shopify provides it; salesperson name as the merchant types it | Knowing who closed the till, switched the store live, reviewed a difference or imported a sale; linking the salesperson to the document in SAGE |
| Store devices: serial number, model and versions of PrintBoxes and of Android devices running the zrsPOS Print app; connected printers; tablet and register names | Printing, pairing and support |
| PrintBox diagnosis (only when support asks for it): IP and MAC addresses and names of the devices on the store's local network, and the PrintBox's last log lines | Finding printers and fixing printing problems |
How Tax Free capture works.
- At the till, the Tax Free extension saves the traveller's first and last name, country, and travel-document number and type in the Shopify order's attributes.
- At the counter, the tablet running the zrsTaxFree app photographs the passport's machine-readable zone and sends the image to our server.
- The server reads the image by text recognition on our own server, in memory. The image is neither stored nor sent to anyone else. The text read stays in memory for about two minutes at most, to combine several reads.
- Staff confirm the fields, which are sent to Global Blue to issue the form.
We do not process payment card data or special categories of data.
5. Where this data goes, on the merchant's instruction
- The merchant's own SAGE, which issues the certified document. zrsPOS looks the customer up by NIF or e-mail; if none is found, it creates a customer record there with name, NIF, e-mail, mobile and address. That record lives in the merchant's SAGE, which the merchant manages.
- The merchant's Shopify store. The document's reference is written to the order. A NIF entered at the till is saved on the order and, when a customer is attached, on that customer's profile. Tax Free details stay in the order's attributes.
- The store's printer, which prints the receipt or the tax-free form.
- Global Blue, only for tax-free forms the merchant issues with its own Global Blue account.
- The European Commission's VIES, when a company NIF is given and its name or address is missing: zrsPOS sends the country code and VAT number to validate it and obtain the company's public details (only if the merchant's SAGE does not have them).
- Our e-mail provider (Resend), when the merchant e-mails a document to a customer. The e-mail goes out in the shop's name, from zrsPOS's address or from the shop's own domain once the shop has verified it with us.
6. Data we process as controller, and legal bases
| Data | Purpose | Legal basis (GDPR art. 6(1)) |
|---|---|---|
| The merchant's account: Shopify store domain, the app's access to the store, configuration (SAGE address and key, printers, devices, Global Blue login, templates, the shop's sending address, e-mail addresses chosen for till-close summaries and online-return alerts), the organisation's name, NIF, billing and support e-mails | Providing the service subscribed to | (b) contract |
| Subscription and usage (plan, stores, documents counted, packs), billing and service notices | Billing through Shopify and informing the merchant about its account | (b) contract; (c) legal obligation (accounting records) |
| Website access requests: company, NIF, name, e-mail, phone, Shopify domain, number of stores, SAGE version, plan, message, and the sending IP address | Answering the request and preparing the merchant | (b) pre-contractual steps; (f) legitimate interest in protecting the form from abuse (IP) |
| Support e-mails | Answering | (b) contract or pre-contract; (f) legitimate interest when not a customer |
| Server logs (IP, time, address requested, errors) | Running, securing and fixing the service | (f) legitimate interest in a secure, working service |
| Log of our team's access to a merchant's account | Showing who accessed what and what changed | (f) legitimate interest; (c) accountability (GDPR arts. 5(2) and 32) |
| Log of data and erasure requests received from Shopify | Showing we handled them | (c) legal obligation (accountability, GDPR art. 5(2)) |
We do not use personal data for marketing, profiling or automated decisions, and we never sell it. Payments for zrsPOS are processed by Shopify; we do not see card data.
7. Cookies and browser storage
- zrspos.com (the website, the manual and these pages) sets no cookies and uses no analytics or advertising tools. Its pages load their typeface from Google Fonts, so the browser connects to Google's servers, and Google receives the visitor's IP address.
- The zrsPOS admin runs inside the Shopify admin and loads Shopify's own scripts, whose cookies are governed by Shopify's policies. zrsPOS keeps only the interface language, in the tab's session storage.
- The zrsTaxFree tablet app keeps in the tablet's local storage its pairing code, the shop's address, the language and theme, and in session storage the id of the last Tax Free session. It keeps no traveller data.
All of this is strictly necessary for the service requested, so no consent is needed.
8. Who processes data for us (sub-processors)
The full list, with regions, is at Sub-processors. In short:
| Provider | What for | Where |
|---|---|---|
| Railway Corporation | Application hosting | EU (region europe-west4, Netherlands); US company |
| Supabase, Inc. | Database and backups | EU (region eu-west-1, Ireland); US company |
| Resend (Plus Five Five, Inc.) | Sending e-mail | US; merchants' own sending domains in the EU (region eu-west-1, Ireland) |
| Google Ireland Limited (Google Workspace) | Support mailbox (support@zrspos.com) | EU and US |
Shopify (Shopify International Limited, Ireland), Global Blue, the merchant's SAGE and its SAGE partner are not our providers: they are the merchant's own platform, tax-free provider and invoicing software, and receive data because the merchant uses them. Cloudflare provides only our domain's DNS, does not carry our traffic and receives no personal data.
9. International transfers
Hosting and the database run in the European Union. Some providers are US companies and may process data in, or access it from, the United States. For those transfers we rely on the European Commission's Standard Contractual Clauses (Implementing Decision (EU) 2021/914) in each provider's data processing terms. When the merchant uses Tax Free, the traveller's data goes to Global Blue in Switzerland, which the European Commission recognises as giving adequate protection (adequacy decision). You can ask for a copy of the safeguards at support@zrspos.com.
10. How long we keep data
While the app is installed:
| Data | Kept |
|---|---|
| Raw events received from Shopify (orders, refunds) | 90 days in full, for retries and audit. Then cut down to a non-personal skeleton (order number, totals, lines, store, payment method) |
| Records of each issuing attempt | E-mail, phone and travel-document data removed 90 days after the issuing finished (for a record still unresolved, failed or pending, 90 days after the sale came in). Name, NIF and address stay as part of the fiscal record |
| Our copy of each issued fiscal document (name, NIF, billing address, lines, totals, number) | For the legal retention period for invoicing records (10 years), then deleted. E-mail and phone are removed on request and after the uninstall |
| Content of printed receipts | Deleted after 30 days. For a fiscal document only a record that it was printed stays, so a later print comes out as a copy (2.ª via) |
| Passport data in the Tax Free session | Deleted 7 days after the session ends (1 day after an abandoned session expires) |
| Image of the passport's machine-readable zone | Not stored |
| Traveller's name and travel-document number in the order's attributes | In the merchant's Shopify, which controls them. In our copy of the raw event, 90 days |
| Our copy of the issued tax-free form (for reprints) | Deleted 90 days after the form is final (issued or voided). The form's record (Global Blue reference, amounts, traveller's name and country) stays until an erasure request for that order, or the uninstall |
| Store-credit vouchers | As fiscal records; the customer's e-mail is removed on request and after the uninstall |
| Till closes and reconciliation records (totals, counted cash, identifier of who closed or reviewed) | As business records, like the documents they summarise |
| Salesperson (staff) names | While the app is installed |
| Configuration change log | 400 days |
| Resolved operations incidents | 400 days after resolution |
| Website access requests | Deleted after 24 months |
| The merchant's organisation, subscription and billing records | For as long as our accounting and tax obligations require (up to 10 years) |
| Server logs | Kept by the hosting provider for a limited period |
| Database backups | Deleted data may remain in the database provider's managed backups until they are replaced |
After the merchant uninstalls zrsPOS, Shopify sends us an erasure notice 48 hours later. Before erasing, we check with Shopify that the app really was uninstalled. We then delete:
- the shop's configuration, credentials and encryption key;
- printers, PrintBoxes, tablets and devices;
- document templates, till-close settings and the e-mail addresses in them;
- salespeople and their names;
- the shop's sending domain, which is also removed from our e-mail provider;
- raw Shopify events, receipt content, the change log and incidents;
- all Tax Free sessions and form copies.
The following stay, for the legal period above and without customers' e-mail or phone:
- our copy of the issued fiscal documents and of the records that issued them;
- till closes and reconciliation records;
- the organisation's, subscription and billing records. The organisation's contact e-mails are deleted when its last shop uninstalls.
The certified originals are in the merchant's SAGE, its legal archive. If the merchant reinstalls before the notice, nothing is deleted.
Request records. When Shopify sends us a customer's data or erasure request, we record it. The record holds the customer's Shopify id, the order numbers and a one-way fingerprint of the e-mail, never the e-mail itself.
11. Your rights
You have the right of access, rectification, erasure, restriction, portability and objection to processing based on legitimate interest. Write to support@zrspos.com. We answer within one month (GDPR art. 12(3)).
For data on a shop's fiscal documents the shop is the controller: contact the shop. Shopify passes us the requests the shop receives, through the mandatory compliance webhooks, and we act on them:
Data request (
customers/data_request). We record it, our team is alerted, and within 30 days we give the merchant the data we hold for those orders.Erasure request (
customers/redact). We automatically remove:- the e-mail and phone everywhere we copied them (documents, issuing records, raw events, store-credit vouchers);
- the personal parts of the raw events, cutting them to their non-personal skeleton;
- the passport data of the Tax Free session and our copy of the tax-free form for those orders.
We cannot erase the name, NIF or address on an issued fiscal document, because Portuguese law requires the document to be kept intact. We record why, so the merchant can explain it. The same applies to the copy in the merchant's SAGE, which the merchant manages.
Shop erasure (
shop/redact). See section 10.
Merchants can see and change in the app everything they have configured.
You also have the right to complain to the Portuguese data protection authority, the Comissão Nacional de Proteção de Dados (CNPD), www.cnpd.pt, or to the authority of the Member State where you live or work (GDPR art. 77).
12. Security
- Isolation. Every record is bound to the store it belongs to. An automated test fails the build if any database query could reach another store's data unfiltered.
- Encrypted credentials. The SAGE key, Shopify access and Global Blue login are encrypted in the application (AES-256-GCM) under a key unique to each shop, itself encrypted under a master key held only in the hosting environment. On uninstall the shop's key is deleted.
- Connections. We use TLS on every connection we control, including the database (with certificate verification), Shopify, Global Blue and the e-mail provider. Two exceptions depend on the merchant's choice: the connection to SAGE uses TLS only if the SAGE address is https (zrsPOS warns when it is not), and the "Direct" printer mode, for demos and tests, sends receipts unencrypted to the printer's public address. The recommended modes (Epson Server Direct Print, the zrsPOS Print app and the PrintBox) connect to us over TLS.
- Storage. The database provider encrypts the database and its managed backups at rest.
- Webhooks and sessions. Shopify webhooks are verified by HMAC and admin sessions by signed token. Requests are rate-limited per shop, and pairing is locked after repeated failed attempts.
- Our access. Access to merchants' data is limited to the provider. The operations console requires a password and a second factor (TOTP), its sessions expire, and it keeps an audit log of actions (including viewing documents and assisted setup sessions, which take place only at the merchant's request, are time-limited and appear in the merchant's change log).
- Logs. Credentials and secrets are removed from logs.
Our data-loss prevention plan and incident response policy are available to merchants on request. If a security incident affects a merchant's data, we notify that merchant within 24 hours of confirming it.
13. Changes and contact
We post changes to this policy here and notify merchants of material changes by e-mail or in the app.
If the service passes to a company we control or to a successor of the zrsPOS business (Terms of Service, section 19), that entity becomes the controller for the data in section 3 and takes on the commitments in this policy. We update this policy and notify merchants before the change takes effect.
Questions: support@zrspos.com.