Where your data is

Version 1.4.1, dated 2026-10-31.

Regions

WhereWhat runs there
eu-central-1 (Frankfurt, Germany)Amazon DynamoDB (codes, destinations, scan counters, paid scan analytics pseudonyms, countries and daily aggregates), AWS Lambda (scan path, API, file rendering, sign-up check), Amazon Cognito (accounts), Amazon API Gateway (API), Amazon CloudWatch Logs (operational logs), Amazon S3 Built and running
us-east-1 (N. Virginia, USA)AWS Certificate Manager: the TLS certificate CloudFront requires to be issued there. It holds no customer data. Built and running
CloudFront edge locations worldwideAmazon CloudFront delivers durableqr.com, qr.durableqr.com (scans) and render.durableqr.com (file downloads). Scan responses are never cached. Downloaded files are cached, see below. Built and running

Downloaded QR files and the CloudFront cache

A QR file downloaded from render.durableqr.com is generated from the content in its address (for a Wi-Fi code that includes the password; for a vCard, the contact details). CloudFront may serve that file, keyed by that address, from the cache of any of its edge locations worldwide for up to 24 hours; CloudFront does not promise to remove it from the cache at that time. The content is never written to our logs. The address also stays in the browser history of whoever downloaded it. Built and running

What is kept, and for how long

DataKept, and status
Code record: destination, fallback address, name, owning account identifier, destination history with author and timeFor the life of the code. No expiry. Built and running
Scan counter and date of the last scan (UTC day, no time of day)For the life of the code. Each scan tries to update the counter and the date; the update is best effort, so a scan can go uncounted and the date can lag behind the real last scan. Built and running
Operational log line per scan: code identifier, outcome, HTTP status, time. No IP address, no user agent, no referrer.7 days configured; AWS deletes expired log events asynchronously, typically within a further 72 hours. Built and running
API calls: not logged. Only errors and the Lambda platform’s own start/end lines.7 days configured; AWS deletes expired log events asynchronously, typically within a further 72 hours. Built and running
File downloads: format, size and duration of rendering. Never the encoded content.Log lines: 7 days configured, deleted by AWS typically within a further 72 hours. The file itself: served from the CloudFront cache for up to 24 hours; CloudFront does not promise removal at that time. Built and running
Point-in-time recovery backups of the code table: every code record, counter and destination history as it was at any momentA rolling 35 days, the AWS default (our code enables recovery and does not set the period). A record removed from the table stays recoverable from these backups for that time. Built and running
CloudFront access logs (IP addresses and similar)Not collected: access logging is off on all three distributions. Built and running
Account: e-mail address (the login) and credentials, held by Amazon CognitoThe account-deletion panel requires a complete, multi-part export first; after completion, only a minimal recovery tombstone remains for up to 36 days while routing records and printed-code redirects continue. Built and running
Paid analytics daily pseudonym: derived from IP address, browser information, a day key and code identifier; raw IP and user-agent values are not retainedUp to 48 hours from the beginning of the UTC day. Late writes keep their original expiry; disabling, transfer and deletion invalidate access before resumable cleanup. Approved, not in use yet
Paid analytics country and daily aggregates: approximate unique scans and country distribution for completed UTC days90 days from the beginning of the UTC day. DynamoDB TTL cleanup is asynchronous and usually takes further days; no promise of physical deletion exactly on day 90. Approved, not in use yet

Subprocessors

Who, and statusPurpose and dataLocation
Amazon Web Services In use
Amazon Web Services EMEA SARL
Hosting, storage, delivery, accounts, and the sign-up and verification e-mails sent by Amazon Cognito from its default sender.Everything listed on this page.Luxembourg
Google (Web Risk) In use
Google Cloud Poland Sp. z o.o.
Checking destination and fallback addresses against Google’s list of malicious sites, to block abuse; the addresses are checked when a code is saved and rechecked.The destination and fallback addresses, when a code is saved and when they are checked again.Warsaw, Poland; location not published by Google; Cloud DPA §10.1 allows processing in any country where Google or its subprocessors have facilities

Contact

Privacy and data protection: privacy@durableqr.com Built and running. Abuse: abuse@durableqr.com Built and running.

Help and account recovery (lost authenticator): support@durableqr.com Built and running. Write from your account's email address; we turn two-step verification off after confirming the request by email.

Mail sent to these addresses is forwarded to DurableQR.

Operator: Tomasz Szuster Contractual commitment.

Changes in this version

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.
  • 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.
  • Advanced timeline[0].transition from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc.
  • Advanced timeline[1].transition from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc.
  • Advanced timeline[2].transition from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc.
  • 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.
  • The owner approved the existing DPA text on 2026-10-30 without changes to its provisions.

1.4.0 — 2026-10-28

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

1.3.0 — 2026-10-27

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

1.2.0 — 2026-10-27

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

1.1.1 — 2026-10-25

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

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

1.0.0 — 2026-09-28

  • First publication of the DurableQR commitments declaration.