Machine translation without native-speaker review. The English version is binding. · español English
Degradation schedule · español
Version · español 1.4.1, dated · español 2026-10-31.
Billing-based degradation applies only to codes beyond the three oldest unremoved codes: those three keep their current state and free rights. For the remaining codes, grace applies while paid_until <= now < paid_until + 89 full UTC days; frozen starts at that boundary with no end date. materialization is asynchronous and may lag the boundary. Year 2 means no automatic end caused by non-payment; it does not prevent later payment, pause, abuse action or deletion. · español
After payment stops · español
When · español
State · español
What a person scanning the code sees · español
paid_until (Day 1 without payment) · español
Grace · español: For codes beyond the three oldest unremoved codes, the code enters Grace after payment is due while paid_until <= now < paid_until + 89 full UTC days; the projection is asynchronous. The three oldest codes keep their current state and free rights. Built and running · español
The owner’s destination, unchanged, or the owner’s fallback when the destination is marked unhealthy, exactly as for an active code. Built and running · español
paid_until + 89 full UTC days (Day 90 without payment) · español
Frozen · español: For codes beyond the three oldest unremoved codes, the code enters Frozen at paid_until + 89 full UTC days; it stays there with no end date. The projection is asynchronous, and the three oldest codes keep their current state and free rights. Built and running · español
The owner’s last destination, unchanged, or the owner’s fallback when that destination is marked unhealthy, exactly as for an active code. Built and running · español
Year 2 without payment · español
Frozen · español: For codes beyond the three oldest unremoved codes, the code stays Frozen with no end date. Year 2 means no automatic end caused by non-payment; it does not prevent later payment, pause, abuse action or deletion, and the projection remains asynchronous. The three oldest codes keep their current state and free rights. Built and running · español
The owner’s last destination, unchanged, or the owner’s fallback when that destination is marked unhealthy, exactly as for an active code. Built and running · español
Every state a code can be in · español
State · español
When · español
What a person scanning sees · español
What the owner can do · español
Active · español
The code is paid for or on the free plan. · español
Redirect (302) to the destination the owner set. Built and running · español
Full control: change the destination, pause, delete. Built and running · español
Grace · español
From paid_until through 89 full UTC days without payment. · español
Exactly what an active code does: redirect to the owner’s destination. Billing state does not change the answer, and the scan path has no access to account or billing records. Built and running · español
Full control, with a notice in the panel that payment is due and paid features may be unavailable. Built and running · español
Frozen · español
At paid_until + 89 full UTC days, with no end date. · español
Exactly what an active code does: redirect to the last destination the owner set. Built and running · español
The destination can no longer be changed after the grace schedule reaches day 90, while the code keeps redirecting with no end date. Built and running · español
Paused by the owner · español
Only when the owner pauses the code. · español
Redirect to the owner’s fallback address if they set one; otherwise a plain DurableQR page saying the code is paused by its owner, has not expired and will never be reassigned. No advertising. Built and running · español
Pause and resume from the panel. Built and running · español
Blocked for abuse · español
Only when the destination is found to be malicious (the one exception to the rules below). · español
A plain DurableQR warning page instead of the redirect, naming the address for appeals. Built and running · español
Appeal by writing to the abuse address; a person reviews the appeal and restores the previous state when the block was wrong. Not available yet · español
Deleted by the owner · español
Only when the owner deletes the code. · español
The same “unknown code” answer (404) as an identifier that never existed. The identifier is never issued again. Built and running · español
Deletion is final. Built and running · español
What never happens · español
A code never shows advertising and never redirects to a DurableQR page, a vendor page or anything other than the owner’s destination, the owner’s fallback or the plain notes above. Built and running · español
If the owner set a fallback address and the destination is marked unhealthy, a scan of an active, grace or frozen code goes to the fallback instead. Built and running · español
Destinations are checked automatically and marked unhealthy when they fail; until then every destination counts as healthy. Built and running · español
Routing records carry no expiry, so no code disappears because time passed or nobody logged in. Built and running · español
A code is never deleted for inactivity or for non-payment. Only its owner deletes it. Contractual commitment · español
An identifier is never issued a second time: a new code cannot take an identifier that already has a record. Built and running · español
An identifier is never sold, and never moved to another customer without its owner’s consent. Contractual commitment · español
Every answer the scan service itself gives carries Cache-Control: no-store and Referrer-Policy: no-referrer, so no browser or shared cache may keep a scan answer and the destination site does not learn the code identifier from the Referer header. Two answers come from the underlying infrastructure instead and may lack these headers: an error (5xx) when the code record cannot be read, and the refusal of any request other than GET or HEAD. Neither is a redirect. Built and running · español
Changing the destination · español
A change of destination usually reaches scans within seconds. DurableQR does not promise that the very next scan after a change already sees it. Not available yet · español
How the owner is told · español
State changes (grace, frozen, blocked) are shown to the owner in the DurableQR panel. DurableQR does not promise any other notification of a state change. Not available yet · español
Taking your codes with you · español
The routing map file format is fully specified and published; the specification defines version 1 with CSV and JSONL encodings, SHA-256 checksums and the current record of every code, without destination history. Built and running · español
The account’s routing map can be exported from the panel and through the API. Built and running · español
Map file format version · español 1. The file carries a checksum named · español sha256 · español. Encodings · español: csv · español, jsonl · español. Columns · español: stable_id · español, current_url · español, fallback_url · español, updated_at · español, actor · español, version · español, state · español.
Public release of the open-source (Apache-2.0) reference resolver for the map file format, as a separate repository, is pending. Not available yet · español License: · español Apache-2.0 · español.
The reference resolver is not available yet. · español
Appealing a block · español
Write to · español abuse@durableqr.com Built and running · español, quoting the address you scanned. · español
Mail sent to these addresses is forwarded to DurableQR. · español
Advanced states[1].owner from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc. · español
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. · español
Advanced timeline[0].transition from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc. · español
Advanced timeline[1].transition from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc. · español
Advanced timeline[2].transition from committed to enforced with ADR-0102, lifecycle, worker, cron and transition-test evidence on durableqr-backend@6e8eefc. · español
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. · español
The owner approved the existing DPA text on 2026-10-30 without changes to its provisions. · español
1.4.0 — 2026-10-28
Added the gross public pricing catalog and the account plan and payments screen with a hosted Przelewy24 checkout. · español
Published the payment-stop schedule: grace through paid_until plus 89 full UTC days, then frozen without an end date. · español
1.3.0 — 2026-10-27
Added public PDF pages and paid hosted PDF commitments with explicit file retention and revocation boundaries. · español
Documented public PDF and cover delivery through files.durableqr.com with no malware-scanning promise. · español
1.2.0 — 2026-10-27
Added contract-backed paid scan analytics commitments for daily pseudonyms, country aggregates, generation isolation and asynchronous cleanup. · español
Documented the 48-hour pseudonym and 90-day aggregate retention windows without promising physical deletion at the TTL boundary. · español
1.1.1 — 2026-10-25
Removed the internal ImprovMX transfer note; the administrator's recipient facts remain published. · español
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. · español
states.3.owner advanced from committed to enforced after auditing pause and resume state writes from the panel. · español
states.4.scanner advanced from committed to enforced after auditing abuse blocking, resolver decisions and the appeal warning. · español
states.5.scanner advanced from committed to enforced after auditing the deleted 404 response, tombstone and identifier allocation guard. · español
states.5.owner advanced from committed to enforced after auditing the account deletion service and the absence of a deleted resume path. · español
never.2 advanced from committed to enforced after auditing the monitor schedule, health decision and persisted result. · español
portability.export.description advanced from committed to enforced because the version 1 map format is published and checked. · español
portability.export.availability advanced from committed to enforced because the routing map is exported from the panel and API. · español
subprocessors.1 advanced from approved to enforced after auditing destination and fallback checks in create, update and monitor rechecks. · español
retention.7 advanced from approved to enforced after auditing the complete export, deletion confirmation, routing retention and recovery tombstone. · español
dpa.points.6.technical advanced from approved to enforced after auditing the same deletion flow, PITR boundary and external copies. · español
The routing map export description now states its available panel and API path. · español
The reference resolver description now states that its public Apache-2.0 release is pending in a separate repository. · español
The DPA transfer text now names both destination and fallback addresses for Google Web Risk abuse checks. · español
The committed status label now means Not available yet because it describes customer availability, not build state. · español
Evidence references were refreshed against the pinned source commits and audited line ranges. · español
1.0.0 — 2026-09-28
First publication of the DurableQR commitments declaration. · español