The administrator is Tomasz Szuster Contractual commitment, a sole trader. There is no postal address. Privacy contact: privacy@durableqr.comBuilt and running.
ImprovMX Incorporated, United States, relays messages sent to support@durableqr.com, abuse@durableqr.com and privacy@durableqr.com. Built and running
Landing and free generator
The landing has no contact or pilot-sign-up channel and no marketing tracking. The free generator creates a QR preview locally; downloading a file uses render.durableqr.com. The selected download format is remembered in localStorage. The generator’s forms, local storage and rendering request are not described as absence of processing or as a guarantee that content never leaves the device.
Hosted PDF documents
Public PDF documents and cover images are served from files.durableqr.com through AWS S3 and CloudFront in eu-central-1. A one-time reservation binds the file kind, size, MIME type, request identifier and a SHA-256 checksum before upload; the browser sends the original bytes over HTTPS. The public key is an address, not access control. A request still processes an IP address in transit; the application does not retain that IP as PDF content. No malware scanning is provided. The PDF URL, file history, downloaded copies and any copies saved by a visitor are not recalled by this policy. Binary PDF files are not included in the routing-map export and no backup or restore of their contents is promised. If the account loses the hosting entitlement, the service starts revocation without a grace period; with the required dependencies working, the origin is removed and the ordinary cache window is up to 300 seconds, while an AWS or scheduler outage can delay that work. Pending uploads and cleanup intents remain bounded technical records until they are reconciled; they are not a promise that a document was published.
Hosted gallery and audio files
Gallery photos and audio files are uploaded from the panel to files.durableqr.com, stored on a file server operated by the administrator and served through Amazon CloudFront. A request still processes an IP address in transit. Before publication the service saves photos again without EXIF, GPS and other embedded metadata, and removes tags and cover images from audio files. Published files and the media page are public to anyone who has the address; the address is not access control. Removing or replacing a file, moving the code’s destination away from its media page, deleting or transferring the code, deleting the account and losing the hosting entitlement revoke the files. Cached copies can remain reachable for up to 24 hours, and longer while the file server cannot reach the service. Copies already downloaded or saved by visitors are not recalled. Media files are not included in the routing-map export, and no backup or restore of their contents is promised.
Account
An account uses Amazon Cognito for an e-mail address, password and optionally TOTP. The primary AWS region is eu-central-1; that does not promise that every network transit is within the EEA. Primary service region: eu-central-1 (Frankfurt, Germany) Built and running.
Scans
A scan may update an aggregate counter and the last scan day in UTC, not an exact time. This is best effort: a scan can go uncounted and the day can lag. Separately, the service writes one operational log line per scan with the code identifier, outcome, HTTP status and time, without storing an IP address, user agent or referrer. An HTTP request still technically processes an IP address in transit; “no IP” describes saved scan data, not network transport. When paid scan analytics is explicitly enabled, the service also derives a daily pseudonym from the IP address, browser information, a day key and the code identifier, and stores the country and daily aggregates. Raw IP and user-agent values are not retained in analytics or operational logs. A pseudonym is a privacy control, not anonymity and not an identifier of a person. These analytics commitments are approved against the backend contract; they are not a claim that the feature is currently enabled for every code.
Retention
Code records and counters remain for the life of the code and have no TTL. Operational logs are configured for 7 days and are usually deleted asynchronously within a further 72 hours. Paid analytics daily pseudonyms expire up to 48 hours from the beginning of their UTC day; daily country aggregates expire 90 days from the beginning of their UTC day. When analytics is disabled, a code or account is transferred or deleted, access to the old generation is invalidated first and a resumable cleanup removes existing elements. A late write remains invisible to a new owner or activation and keeps its original expiry. DynamoDB TTL deletion is asynchronous and usually takes further days; this is not a promise of physical zero or deletion exactly on day 90. Point-in-time recovery is retained for 35 days. After account deletion completes, only the minimal recovery tombstone remains for up to 36 days; routing records, printed-code redirects and any copies already delivered to external recipients are not erased by this panel flow. Tombstones and backups do not carry a promise of physical deletion after 35 days.
Data
Retention in the source
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
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
Recipients and transfers
Recipient
Purpose and data
Location
Amazon Web Services EMEA SARL In use
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 Cloud Poland Sp. z o.o. In use
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
Relaying messages sent to the administrator’s support, abuse and privacy mailboxes.
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.
Purposes and legal bases
We use Article 6(1)(b) GDPR for an account and the service or file generation requested by a visitor; Article 6(1)(f) for named legitimate interests in security, abuse prevention and correspondence; and Article 6(1)(c) for legal obligations concerning data protection and GDPR requests. We do not use personal data for marketing or billing purposes in the pilot.
Your rights and complaints
You may request access, rectification, erasure, restriction, portability and objection, subject to the conditions in the GDPR. You may object to processing based on Article 6(1)(f). Write to privacy@durableqr.com. You may also complain to the President of the Personal Data Protection Office (UODO), the Polish supervisory authority. The panel account-deletion flow requires a complete, multi-part export before confirmation; printed codes keep redirecting after the account is deleted, and the routing records remain. Requests about personal data embedded in a public URL are separate and should be sent to privacy@durableqr.com. Built and running
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.