Machine translation without native-speaker review. The English version is binding. · български English

Where your data is · български

Version · български 1.4.1, dated · български 2026-10-31.

Regions · български

Where · българскиWhat 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 worldwide · българскиAmazon 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 · български

Data · българскиKept, and status · български
Code record: destination, fallback address, name, owning account identifier, destination history with author and time · българскиFor 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 moment · българскиA 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 Cognito · българскиThe 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 retained · българскиUp 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 days · български90 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 status · българскиPurpose and data · българскиLocation · български
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. · български