PO Box Blocker · Last updated: 2026-11-16
This Data Processing Agreement (“DPA”) forms part of the agreement between the merchant using PO Box Blocker (“Controller”) and Lucas Albornoz, an independent software developer registered in Argentina (sole proprietor, Monotributo regime), trading as “Ecomtuc” (“Processor”). It applies automatically when the merchant installs the app and takes precedence over the Terms of Service for the processing of personal data. It implements Art. 28 GDPR (and, where applicable, the UK GDPR and the Swiss FADP).
Subject matter: providing the app's features to the Controller. PO Box Blocker adds a checkout validation to your Shopify store that blocks PO box, military, parcel locker and custom-rule delivery addresses according to rules you configure. The check runs inside Shopify's checkout; the app only stores your rules and settings. Duration: while the app is installed, plus the deletion periods in section 9. Nature: collection, storage, use, transmission and erasure by automated means.
| Category | Examples | Purpose | Retention |
|---|---|---|---|
| Customer and order IDs in Shopify privacy requests | Numeric Shopify customer ID and order IDs contained in customers/data_request and customers/redact webhooks (names, emails and addresses are dropped before storing) | Record that the request was received and answered | 365 days after completion; these IDs are not used for anything else |
The app does not receive, read or store customers' names, emails or delivery addresses. The checkout validation is a Shopify Function that runs inside Shopify: it reads the address in checkout and returns a pass/block result without sending the address to us. The only other place an address can reach our servers is the in-app “Test an address” simulator, where the merchant types an address; it is evaluated in memory, shown back to the merchant, and not saved. Merchants should type sample addresses, not real customer addresses. Because no customer contact data is stored, a customers/data_request returns no customer data and a customers/redact has nothing to delete beyond the ID record described above, which ages out after 365 days.
Data subjects: the Controller's customers as listed above (and the Controller's staff only to the extent such data is listed). No special categories of data (Art. 9 GDPR) are processed.
The Processor processes personal data only on documented instructions of the Controller; the installation, configuration and use of the app constitute those instructions. The Processor informs the Controller if it believes an instruction infringes data protection law. The Processor does not process the data for its own purposes.
The Processor is a sole developer who personally performs the processing and is bound by confidentiality. Should anyone else ever be authorised to process the data, they will be bound by written confidentiality obligations first.
The Processor does not hold third-party security certifications (such as ISO 27001 or SOC 2); the measures above are the Processor's own. The Processor may update them as long as the overall level of protection is not reduced.
The Controller gives general authorisation to engage the sub-processors listed below. The Processor imposes data protection obligations on them equivalent to this DPA, informs the Controller of intended changes (by updating this page and announcing material changes in the app) at least 30 days in advance, and the Controller may object; if no solution is found, the Controller may uninstall the app, which ends the processing.
| Party | Purpose | Data | Location | Safeguards |
|---|---|---|---|---|
| Fly.io, Inc. | Hosting of the app and its PostgreSQL database; background job processing | All data listed above under merchants and privacy requests | USA (Ashburn, Virginia) | EU-U.S. Data Privacy Framework certification |
| Tigris Data, Inc. | Storage of encrypted daily database backups (30 days) | All data described above, encrypted by us before upload; Tigris holds no key to read it | USA (company seat); data in Tigris' storage regions | Tigris Data Processing Addendum (part of Tigris' service terms); EU Standard Contractual Clauses (Decision (EU) 2021/914) |
The Processor is established in Argentina, which benefits from an adequacy decision of the European Commission (Decision 2003/490/EC). Transfers to sub-processors outside the EEA rely on an adequacy decision (including the EU-U.S. Data Privacy Framework where the recipient is certified) or, otherwise, on the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914, Module 3 processor-to-processor), which are incorporated by reference where required.
The Processor assists the Controller in responding to data subject requests (including through Shopify's customers/data_request and customers/redact webhooks, which the app implements), with security, data protection impact assessments and consultations with supervisory authorities, taking into account the nature of the processing.
On uninstall (app/uninstalled webhook) we immediately delete the shop's Shopify sessions and access tokens and the stored link to the checkout validation, and mark the shop as uninstalled. Rules, settings and the audit log are kept for a short time so that a re-installation within that window restores your setup. 48 hours after uninstall Shopify sends shop/redact; we then delete every remaining row of the shop (rules, validation link, audit log, shop record, sessions). If shop/redact never arrives, a daily job deletes shops that have been uninstalled for more than 60 days. The only record we keep after shop/redact is the privacy-request record (shop domain, request type, IDs, result), for 365 days, as proof of deletion. Backups of the database expire on the hosting provider's schedule.
The Processor notifies the Controller without undue delay, and where feasible within 48 hours, after becoming aware of a personal data breach affecting the Controller's data, by email to the contact address the Controller has given us or, failing that, the store owner's contact email available to us through Shopify. The notification describes the nature of the breach, the categories and approximate number of records concerned, likely consequences and the measures taken. The Processor also notifies Shopify where Shopify's terms require it.
The Processor makes available the information necessary to demonstrate compliance with Art. 28 GDPR — this DPA, the measures above and written answers to reasonable questions — and allows for audits by the Controller or an auditor mandated by it, with reasonable notice, at the Controller's cost, at most once a year unless required by a supervisory authority or after a breach. Requests: support@ecomtuc.com.
If this DPA conflicts with the Terms of Service, this DPA prevails for the processing of personal data. If the Standard Contractual Clauses apply, they prevail over this DPA.