Machine translation without native-speaker review. The English version is binding. · Gaeilge English

Data processing agreement · Gaeilge

Version · Gaeilge 1.4.1, dated · Gaeilge 2026-10-31.

Parties and roles · Gaeilge

Processor · Gaeilge: Tomasz Szuster Contractual commitment · Gaeilge. Controller · Gaeilge: the customer who accepts this agreement. · Gaeilge Governing law: · Gaeilge Polish law; disputes are resolved by the common court competent for the service provider's seat. Contractual commitment · Gaeilge.

For the data a customer stores in its codes, the customer is the controller and DurableQR is the processor. For the customer’s own account (login e-mail address and credentials) DurableQR is the controller; that processing is described in the privacy policy, not in this agreement. The same applies to QR files rendered for visitors of the free generator who have no account. The privacy policy covering accounts and the free generator is available at /privacy/. · Gaeilge

Privacy policy · Gaeilge

This agreement is available on every plan, including the free plan. Contractual commitment · Gaeilge

Subject matter, duration, nature and purpose · Gaeilge

Routing the customer’s QR codes: storing each code’s destination, fallback address and name, redirecting scans, counting them, and rendering QR image files. · Gaeilge

For as long as the customer has an account, and after that until the customer’s data is deleted or returned under point (g). · Gaeilge

Types of personal data and categories of data subjects · Gaeilge

Destination and fallback addresses, code names, the history of destinations with the account identifier of whoever made each change, scan counts, the date of the last scan, one operational log line per scan (code identifier, outcome, time) with a 7-day retention setting, paid analytics daily pseudonyms retained up to 48 hours from the beginning of their UTC day, country and daily aggregates retained 90 days from the beginning of their UTC day, and point-in-time backups of all of these for 35 days. Also the content put into a QR file rendered on render.durableqr.com (for example the contact details of a vCard or a Wi-Fi password), processed to generate the file and possibly served from the CloudFront cache for up to 24 hours (CloudFront does not promise removal at that time). Addresses, names and file content are free text, so they can contain personal data. · Gaeilge

The customer’s users; any person the customer names in a destination address or a code name; people whose details appear in a rendered QR file; and people who scan a code, only as far as the scan count, the date of the last scan, the paid analytics daily pseudonym, country, daily aggregates and the 7-day log line relate to them. DurableQR stores no raw IP address or user-agent value in analytics or operational logs. A daily pseudonym is a privacy control, not anonymity and not an identifier of a person. · Gaeilge

Retention of each type: · Gaeilge Where your data is · Gaeilge.

Processor obligations, Article 28(3) · Gaeilge

(a) Documented instructions · Gaeilge

DurableQR processes the data only to provide the service as the customer configures it through the panel and the API, and on the customer’s other documented instructions, including with regard to transfers outside the EEA, unless Union or Member State law requires otherwise; in that case DurableQR informs the customer of that legal requirement before processing, unless that law prohibits it on important grounds of public interest.

(b) Confidentiality · Gaeilge

Everyone DurableQR authorises to process the data is bound by confidentiality.

(c) Security (Article 32) · Gaeilge

DurableQR maintains appropriate technical and organisational measures, including those listed here.

What the system does today: · Gaeilge TLS 1.2 or later on qr.durableqr.com and render.durableqr.com; no IP address, user agent or referrer is stored for a scan; the scan path has no access to the account table; API calls are not logged; operational logs expire after 7 days (AWS deletes expired events typically within a further 72 hours). Built and running · Gaeilge

(d) Subprocessors · Gaeilge

The customer gives a general written authorisation for the subprocessors listed on the “Where your data is” page. DurableQR announces any new or replaced subprocessor 30 days in advance, the customer may object, and each subprocessor is bound by the same data protection obligations as DurableQR.

(e) Data subject requests · Gaeilge

DurableQR helps the customer, by appropriate technical and organisational measures, to answer requests from data subjects.

What the system does today: · Gaeilge The API lists a customer’s codes and returns each code with its destination history. Built and running · Gaeilge

(f) Security, breaches and impact assessments (Articles 32 to 36) · Gaeilge

DurableQR helps the customer meet its obligations under Articles 32 to 36 and notifies the customer of a personal data breach without undue delay, at the latest 48 hours after becoming aware of it.

(g) Deletion or return at the end · Gaeilge

At the end of the service DurableQR deletes or returns the customer’s data, at the customer’s choice, and deletes existing copies unless the law requires storage.

What the system does today: · Gaeilge The account-deletion panel requires a complete, multi-part export before confirmation. For paid analytics, access to the old generation is invalidated first and a resumable cleanup removes existing pseudonyms and aggregates; a late write remains invisible and keeps its original TTL. After completion, routing records and printed-code redirects remain; only a minimal recovery tombstone remains for up to 36 days. This is not a promise of physical erasure: analytics TTL cleanup is asynchronous, PITR is a rolling 35 days, and copies already delivered to external recipients are outside the panel flow. A deleted code still leaves an irreversible META tombstone in state deleted, keeps its resolver inputs, and its identifier is never reissued. Built and running · Gaeilge

(h) Information and audits · Gaeilge

DurableQR makes available the information needed to demonstrate compliance with Article 28 and allows audits by the customer or an auditor it mandates, by providing a security description, answers to a security questionnaire and reports of subprocessor audits (including SOC/ISO reports available through AWS Artifact). On-site audits are not available because processing is in the cloud and DurableQR has no data centre of its own. DurableQR immediately informs the customer if, in its opinion, an instruction infringes data protection law.

Transfers outside the EEA · Gaeilge

The data is stored in eu-central-1 (Frankfurt). Every request to durableqr.com, qr.durableqr.com and render.durableqr.com passes through the CloudFront edge location nearest to the person making it, which may be outside the EEA; scan answers are not stored there. QR files rendered on render.durableqr.com may be served from CloudFront edge locations worldwide, including outside the EEA, for up to 24 hours; CloudFront does not promise removal at that time. Destination and fallback addresses are sent to Google Web Risk for abuse checks. CloudFront uses SCCs in the AWS Service Terms/AWS DPA and the EU-US Data Privacy Framework. Google uses the EU-US Data Privacy Framework, with SCCs in its Cloud DPA as a fallback. · Gaeilge

Before launch · Gaeilge

Changes in this version · Gaeilge

1.4.1 — 2026-10-31

  • Advanced states[1].owner from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc. · Gaeilge
  • Advanced states[2].owner from committed to enforced with ADR-0102, lifecycle, worker, cron, transition-test and frozen-edit-guard evidence on durableqr-backend@6e8eefc. · Gaeilge
  • Advanced timeline[0].transition from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc. · Gaeilge
  • Advanced timeline[1].transition from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc. · Gaeilge
  • Advanced timeline[2].transition from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc. · Gaeilge
  • Clarified that billing transitions cover codes beyond the three oldest unremoved codes, grace runs for paid_until <= now < paid_until + 89 full UTC days, frozen starts at that boundary, and materialization is asynchronous. · Gaeilge
  • The owner approved the existing DPA text on 2026-10-30 without changes to its provisions. · Gaeilge

1.4.0 — 2026-10-28

  • Added the gross public pricing catalog and the account plan and payments screen with a hosted Przelewy24 checkout. · Gaeilge
  • Published the payment-stop schedule: grace through paid_until plus 89 full UTC days, then frozen without an end date. · Gaeilge

1.3.0 — 2026-10-27

  • Added public PDF pages and paid hosted PDF commitments with explicit file retention and revocation boundaries. · Gaeilge
  • Documented public PDF and cover delivery through files.durableqr.com with no malware-scanning promise. · Gaeilge

1.2.0 — 2026-10-27

  • Added contract-backed paid scan analytics commitments for daily pseudonyms, country aggregates, generation isolation and asynchronous cleanup. · Gaeilge
  • Documented the 48-hour pseudonym and 90-day aggregate retention windows without promising physical deletion at the TTL boundary. · Gaeilge

1.1.1 — 2026-10-25

  • Removed the internal ImprovMX transfer note; the administrator's recipient facts remain published. · Gaeilge

1.1.0 — 2026-10-20

  • states.0.owner advanced from committed to enforced after auditing destination changes, pause and deletion across the backend and panel. · Gaeilge
  • states.3.owner advanced from committed to enforced after auditing pause and resume state writes from the panel. · Gaeilge
  • states.4.scanner advanced from committed to enforced after auditing abuse blocking, resolver decisions and the appeal warning. · Gaeilge
  • states.5.scanner advanced from committed to enforced after auditing the deleted 404 response, tombstone and identifier allocation guard. · Gaeilge
  • states.5.owner advanced from committed to enforced after auditing the account deletion service and the absence of a deleted resume path. · Gaeilge
  • never.2 advanced from committed to enforced after auditing the monitor schedule, health decision and persisted result. · Gaeilge
  • portability.export.description advanced from committed to enforced because the version 1 map format is published and checked. · Gaeilge
  • portability.export.availability advanced from committed to enforced because the routing map is exported from the panel and API. · Gaeilge
  • subprocessors.1 advanced from approved to enforced after auditing destination and fallback checks in create, update and monitor rechecks. · Gaeilge
  • retention.7 advanced from approved to enforced after auditing the complete export, deletion confirmation, routing retention and recovery tombstone. · Gaeilge
  • dpa.points.6.technical advanced from approved to enforced after auditing the same deletion flow, PITR boundary and external copies. · Gaeilge
  • The routing map export description now states its available panel and API path. · Gaeilge
  • The reference resolver description now states that its public Apache-2.0 release is pending in a separate repository. · Gaeilge
  • The DPA transfer text now names both destination and fallback addresses for Google Web Risk abuse checks. · Gaeilge
  • The committed status label now means Not available yet because it describes customer availability, not build state. · Gaeilge
  • Evidence references were refreshed against the pinned source commits and audited line ranges. · Gaeilge

1.0.0 — 2026-09-28

  • First publication of the DurableQR commitments declaration. · Gaeilge