zrsPOS — Data Processing Agreement (DPA)
Version of 11 November 2026 · In force from 11 November 2026
This Data Processing Agreement ("DPA") is entered into, under article 28 of Regulation (EU) 2016/679 ("GDPR") and Portuguese Law 58/2019, between:
- Controller: the merchant that installs zrsPOS on its Shopify store (the "Merchant"); and
- Processor: José Maria Pinto Cardoso Saraiva de Reffoios, a sole trader (trabalhador independente), tax number 236212419, with tax address in Lisboa, providing the service under the trade name zrsPOS, contact support@zrspos.com ("zrsPOS"), or its successor under section 16. Data protection officer: none appointed.
The DPA forms part of the Terms of Service and applies from the installation of zrsPOS. Its commitments stand on their own and do not depend on any other clause of the Terms. On personal-data matters it prevails over the Terms and over any other agreement between the parties about zrsPOS.
The DPA exists in Portuguese and English; the Portuguese version is the binding one.
1. Definitions
"Personal data", "processing", "controller", "processor", "data subject", "personal data breach" and "supervisory authority" have the meaning given in article 4 GDPR. "Sub-processor" means a third party zrsPOS engages to process personal data on the Merchant's behalf.
2. Subject matter
zrsPOS processes personal data on the Merchant's behalf so that the Merchant's own SAGE 50c issues and corrects Portuguese fiscal documents (invoices, simplified invoices, invoice-receipts, credit notes and returns documents) for transactions made at the Shopify POS of the Merchant's stores; to print those documents, keep working copies and reconcile them with Shopify and SAGE; to close the tills; and, where the Merchant switches them on, to e-mail documents, manage store-credit vouchers and prepare Global Blue tax-free forms through the Merchant's own Global Blue account. The article 28(3) summary is in Annex A.
3. Duration
The DPA lasts for as long as zrsPOS is installed on the Merchant's store and, after that, for as long as zrsPOS keeps Merchant data under section 12.
4. Nature and purpose
Automated processing, triggered by the Merchant's Shopify store events (orders, refunds, returns, locations), by the responses of the Merchant's SAGE and by the actions of the Merchant's staff in the zrsPOS admin, the Shopify POS extensions, the zrsPOS Print app and the zrsTaxFree tablet app. Processing is limited to what those purposes require. zrsPOS does not process this data for its own purposes, does not sell it and does not use it for marketing or profiling.
5. Data subjects and categories of data
Data subjects: (a) the Merchant's customers who buy or return at a store; (b) online-order customers, only when the return is made at a store; (c) travellers for whom a tax-free form is prepared; (d) the Merchant's staff whose actions are recorded; (e) owners of devices on the store's local network (PrintBox diagnosis only).
| Category | Fields | Source |
|---|---|---|
| Identity | first and last name; NIF | Shopify order; till |
| Contact | e-mail; phone | Shopify order |
| Address | billing address | Shopify order |
| Transaction | lines, amounts, payment method, store, returns, store-credit vouchers | Shopify order and refund |
| Fiscal | certified document data (number, ATCUD, QR, totals) | the Merchant's SAGE |
| Tax Free (optional) | traveller's first and last name; country of residence; nationality; passport or travel-document number, type, issuing country and expiry; date of birth; sex; machine-readable zone (MRZ); optional e-mail and phone | till; zrsTaxFree app |
| Staff | Shopify staff identifier; staff e-mail when Shopify provides it; salesperson name as the Merchant types it | POS and admin sessions; configuration |
| Devices | serial numbers and models of PrintBoxes and Android devices; on diagnosis, IP and MAC addresses and names of devices on the local network | PrintBox; zrsPOS Print app |
The passport image. The zrsTaxFree tablet sends an image of the machine-readable zone to the zrsPOS server, which reads it by text recognition on the server itself, in memory, and returns the fields for the Merchant's staff to confirm. The image is neither stored nor sent to any third party.
Not processed: payment card data and special categories of data (GDPR art. 9).
6. The Merchant's instructions
6.1. zrsPOS processes personal data only on the Merchant's documented instructions, including with regard to transfers to third countries, unless EU or Portuguese law requires otherwise; in that case it informs the Merchant first, unless the law forbids it.
6.2. The Merchant's instructions are: these Terms and this DPA; the configuration the Merchant sets in the zrsPOS admin; the events the Merchant's Shopify store sends; and the actions of the Merchant's staff in the zrsPOS extensions and apps. On those instructions zrsPOS in particular:
- looks customers up in the Merchant's SAGE by NIF or e-mail and, if none exists, creates the customer record there with name, NIF, e-mail, mobile and address;
- writes the document's reference to the Shopify order, saves a NIF entered at the till on the order and, when a customer is attached, on the Shopify customer's profile;
- validates a business customer's VAT number in the European Commission's VIES when the name or address is missing and SAGE does not have them;
- sends the traveller's data to Global Blue, with the Merchant's Global Blue account, to prepare the tax-free form;
- e-mails documents to customers when the Merchant turns this on, in the Merchant's name, from zrsPOS's address or from the Merchant's verified domain.
6.3. zrsPOS tells the Merchant if, in its opinion, an instruction infringes the GDPR or other data-protection law.
7. Confidentiality
zrsPOS ensures that the persons authorised to process the personal data (its team and those of its sub-processors) have committed to confidentiality or are under a statutory duty of confidentiality, and that they access it only as needed to run the service, give support or fix incidents. Access to the Merchant's data is limited to the provider.
8. Security (article 32)
zrsPOS applies the technical and organisational measures in Annex B, appropriate to the risk. It may update them provided the overall level of protection is not reduced.
9. Sub-processors
9.1. The Merchant gives general authorisation to the sub-processors in Annex C (and on the public Sub-processors page).
9.2. zrsPOS notifies the Merchant, by e-mail to the billing address and on the public page, at least 30 days before adding or replacing a sub-processor. The Merchant may object on reasonable data-protection grounds within that period. If the parties find no solution, either may end the affected service without penalty.
9.3. zrsPOS imposes on each sub-processor, by contract, data-protection obligations equivalent to those in this DPA (GDPR art. 28(4)), and remains liable to the Merchant for their performance.
9.4. Not sub-processors of zrsPOS, because they receive data as a result of the Merchant's own use and relationships:
- Shopify, the store platform and source of the order data;
- Global Blue, the Merchant's tax-free provider, only when the Merchant enables Tax Free (its data goes to Switzerland, covered by an EU adequacy decision);
- the Merchant's SAGE and its SAGE partner (whoever installs, hosts or maintains it);
- VIES, the European Commission's public VAT-number validation service.
10. International transfers
10.1. zrsPOS's hosting and database run in the European Union. Some sub-processors are US companies and may process data in, or access it from, the United States.
10.2. For those transfers zrsPOS relies on the Standard Contractual Clauses approved by Commission Implementing Decision (EU) 2021/914 (Module 3, processor to processor) in each sub-processor's data processing terms, with any supplementary measures needed. If none of these safeguards applies, zrsPOS does not make the transfer.
10.3. The Merchant may ask for a copy of the applicable safeguards.
11. Assistance to the Merchant
11.1. Data-subject rights. zrsPOS helps the Merchant answer data-subject requests. Through Shopify's mandatory compliance webhooks:
- Access (
customers/data_request): zrsPOS records the request, alerts its team and, within 30 days, gives the Merchant the personal data it holds for the orders named. - Erasure (
customers/redact): zrsPOS automatically erases the e-mail and phone everywhere it copied them for those orders (documents, issuing records, raw events, store-credit vouchers), cuts the raw events to their non-personal skeleton, and erases the passport data and its copy of the tax-free form. Name, NIF and address stay on the fiscal document because keeping them is a legal obligation of the Merchant; zrsPOS records this outcome and its basis so the Merchant can answer the data subject. The customer record zrsPOS created in the Merchant's SAGE is managed by the Merchant.
The log of these requests keeps the customer's Shopify id, the order numbers and a one-way fingerprint of the e-mail, never the e-mail itself. Requests zrsPOS receives directly from data subjects are forwarded to the Merchant without undue delay.
11.2. Security, impact assessments and prior consultation. zrsPOS helps the Merchant comply with GDPR articles 32 to 36, taking into account the nature of the processing and the information available to it.
12. Retention, deletion and return
12.1. While zrsPOS is installed, the periods in Annex D apply.
12.2. At the end of the contract. Before uninstalling, the Merchant can export the list of its documents (CSV) and download or reprint each document; the certified originals are in its own SAGE. This is how data is returned.
12.3. After the Merchant uninstalls zrsPOS, Shopify sends the shop/redact notice 48 hours later.
zrsPOS checks with Shopify that the app was uninstalled and then deletes: the shop's configuration,
credentials and encryption key; printers, PrintBoxes and devices; templates, till-close settings and
the e-mails in them; salespeople; the sending domain (also at the e-mail provider); raw events;
receipt content; the change log and incidents; all Tax Free sessions and form copies. It also erases
the contact fields of the fiscal documents and issuing records it keeps.
12.4. Mandatory retention. Only the following remain, without e-mail or phone: the copy of the fiscal documents and issuing records, till closes and reconciliation records. They are kept for the period Portuguese tax law imposes on the Merchant (10 years), on the Merchant's behalf, and deleted at the end of that period. The Merchant authorises this retention.
12.5. Deleted data may remain in the database provider's managed backups until they are replaced. If the Merchant reinstalls before the notice, nothing is deleted.
13. Personal data breach
13.1. zrsPOS notifies the Merchant without undue delay and in any case within 24 hours of confirming that a breach affects the Merchant's data, so that the Merchant can notify the CNPD within 72 hours (GDPR art. 33) and, where required, the data subjects (art. 34).
13.2. The notification includes, as far as known: the nature of the breach, the categories and approximate number of data subjects and records concerned; zrsPOS's contact; the likely consequences; and the measures taken or proposed. Information not yet known is provided later, in phases.
13.3. zrsPOS documents every breach, its circumstances and the measures taken, and cooperates with the Merchant. zrsPOS does not notify the CNPD or data subjects on the Merchant's behalf without the Merchant's instruction, unless it has its own legal duty to.
14. Demonstrating compliance and audits
14.1. zrsPOS makes available to the Merchant the information needed to demonstrate compliance with GDPR article 28 and keeps a record of processing activities as processor (art. 30(2)).
14.2. The Merchant may audit compliance with this DPA once a year on 30 days' notice, or without that limit after a breach affecting it. Audits are first by written questionnaire, and by inspection, by an auditor bound by confidentiality, where the questionnaire is not enough. Each party bears its own costs, unless the audit reveals a material breach by zrsPOS.
15. Liability
Each party is liable for the damage caused by its own breach of this DPA or of the GDPR, under GDPR article 82 and Portuguese law. Nothing in this DPA limits either party's liability towards data subjects.
16. Assignment
16.1. zrsPOS may transfer its position as processor under this DPA, together with the Terms, to a company it controls or to a successor of the zrsPOS business (Terms, section 19). It notifies the Merchant before the transfer takes effect, by e-mail to the billing address and in the app, giving the new processor's identity and contact.
16.2. Whoever takes over the position takes on every obligation in this DPA, without reducing any: the same instructions, security measures (Annex B), sub-processors (Annex C) and retention periods (Annex D). Any later change follows the rules of this DPA, including the 30-day notice in section 9.2.
16.3. The Merchant authorises this transfer in advance. If it disagrees, it may cancel at any time (Terms, section 16.2), and its data follows section 12.
16.4. The Merchant may not transfer its position under this DPA without zrsPOS's written consent (Terms, section 19).
Annex A — Description of the processing (article 28(3))
| Item | Description |
|---|---|
| Subject matter | Issuing and correcting Portuguese fiscal documents in the Merchant's own SAGE for Shopify POS transactions; printing, working copies and reconciliation; till close; document e-mail, store-credit vouchers and Global Blue tax-free forms, where enabled |
| Duration | While zrsPOS is installed, plus the periods in Annex D |
| Nature | Automated, triggered by Shopify events, SAGE responses and the Merchant's staff actions |
| Purpose | Meeting the Merchant's invoicing obligations and the features it enables |
| Types of data | Section 5 |
| Data subjects | Section 5 |
| Special categories | None. No payment card data |
| Instructions | Section 6 |
| Sub-processors | Annex C |
| Deletion and return | Section 12 and Annex D |
Annex B — Technical and organisational measures (article 32)
| Area | Measure |
|---|---|
| Tenant isolation | Every record is bound to the Merchant's store. An automated test fails the build if a query could reach another store's data unfiltered. Printer and device credentials identify the store themselves; no request can name a store other than its own |
| Encryption in transit | TLS on every connection zrsPOS controls, including the database (certificate verified), Shopify, Global Blue and e-mail. The connection to the Merchant's SAGE uses TLS when the SAGE address is https; zrsPOS warns when it is not and recommends https. The "Direct" printer mode (demos and tests) sends receipts unencrypted; Epson Server Direct Print, the zrsPOS Print app and the PrintBox connect to zrsPOS over TLS |
| Encryption at rest | Database and backups encrypted by the provider. The Merchant's credentials (SAGE key, Shopify token, Global Blue login) additionally encrypted in the application with AES-256-GCM, under a key unique to each shop, itself encrypted under a derived (HKDF) master key held only in the hosting environment. The shop's key is deleted on uninstall |
| Authentication | Shopify webhooks verified by HMAC; admin sessions by Shopify signed token plus a time-limited surface credential; lifecycle and compliance events checked to come from the shop's registered app |
| Team access control | Individual accounts, no shared accounts; scrypt password hashing and mandatory TOTP second factor; roles (owner, support, read-only); expiring sessions (12 h idle, 7 days maximum); login rate limiting. Access to merchant data is limited to the provider |
| Audit log | Team actions (including viewing documents and issuing records, retries and assisted setup sessions) go to an audit log. Assisted sessions take place only at the Merchant's request, are time-limited, allow only approved routes (never billing), log every request before running it, and their changes appear in the Merchant's change log |
| Abuse protection | Rate limits per shop and per device; pairing lockout after failed attempts |
| Minimisation | Contact data and raw events cut back on the Annex D schedule; passport image never stored |
| Technical logs | Authenticated, store-tagged request logs; credentials and secrets removed from logs, including those in URLs |
| Availability and integrity | The database provider's managed backups; queue and retries so a failure at SAGE or a printer never loses a document; a check in SAGE before any retry, to avoid duplicates |
| Development and testing | Separate test environments (test store and test SAGE); automated test suite on every change, including the tenant-isolation test |
| Incidents | Section 13 and the incident response policy |
Annex C — Authorised sub-processors
| Sub-processor | Purpose | Data location | Transfer safeguard |
|---|---|---|---|
| Railway Corporation | Application hosting | EU — region europe-west4 (Netherlands); US company | Standard Contractual Clauses |
| Supabase, Inc. | Database and backups | EU — region eu-west-1 (Ireland); US company | Standard Contractual Clauses |
| Resend (Plus Five Five, Inc.) | E-mail: documents to customers in the Merchant's name (when enabled), till-close summaries and alerts the Merchant sets up, notices to the Merchant, alerts to the zrsPOS team | US; merchants' own sending domains in the EU (region eu-west-1, Ireland) | Standard Contractual Clauses |
| Google Ireland Limited (Google Workspace) | Support mailbox (support@zrspos.com), which receives the Merchant's correspondence and operational alerts (for example a data request naming order numbers) | EU and US | Standard Contractual Clauses |
Changes to this Annex follow section 9.
Annex D — Retention periods
| Data | Period |
|---|---|
| Raw Shopify events | 90 days in full; then cut to a non-personal skeleton |
| Issuing records | E-mail, phone and travel-document data removed 90 days after the issuing finished (unresolved records: 90 days after the sale came in) |
| Fiscal documents (zrsPOS's copy) | The Merchant's legal retention period (10 years), then deleted; contacts removed on request and on uninstall |
| Receipt content | 30 days; the record that the document was printed stays |
| Passport data in the Tax Free session | 7 days after the session ends (1 day after an abandoned session expires) |
| Passport image | Not stored |
| Tax-free form copy | 90 days after the form is final (issued or voided); the form's record (Global Blue reference, amounts, traveller's name and country) until an erasure request for the order, or the uninstall |
| Store-credit vouchers | As fiscal records; e-mail removed on request and on uninstall |
| Till closes and reconciliation | As business records, with the documents |
| Salesperson names | While installed |
| Change log | 400 days |
| Resolved incidents | 400 days after resolution |
| Backups | The database provider's managed backups, until replaced |
| Server logs | Kept by the hosting provider for a limited period |