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

Degradation schedule · bosanski

Version · bosanski 1.4.1, dated · bosanski 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. · bosanski

After payment stops · bosanski

When · bosanskiState · bosanskiWhat a person scanning the code sees · bosanski
paid_until (Day 1 without payment) · bosanskiGrace · bosanski: 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 · bosanskiThe owner’s destination, unchanged, or the owner’s fallback when the destination is marked unhealthy, exactly as for an active code. Built and running · bosanski
paid_until + 89 full UTC days (Day 90 without payment) · bosanskiFrozen · bosanski: 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 · bosanskiThe 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 · bosanski
Year 2 without payment · bosanskiFrozen · bosanski: 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 · bosanskiThe 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 · bosanski

Every state a code can be in · bosanski

State · bosanskiWhen · bosanskiWhat a person scanning sees · bosanskiWhat the owner can do · bosanski
Active · bosanskiThe code is paid for or on the free plan. · bosanskiRedirect (302) to the destination the owner set. Built and running · bosanskiFull control: change the destination, pause, delete. Built and running · bosanski
Grace · bosanskiFrom paid_until through 89 full UTC days without payment. · bosanskiExactly 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 · bosanskiFull control, with a notice in the panel that payment is due and paid features may be unavailable. Built and running · bosanski
Frozen · bosanskiAt paid_until + 89 full UTC days, with no end date. · bosanskiExactly what an active code does: redirect to the last destination the owner set. Built and running · bosanskiThe 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 · bosanski
Paused by the owner · bosanskiOnly when the owner pauses the code. · bosanskiRedirect 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 · bosanskiPause and resume from the panel. Built and running · bosanski
Blocked for abuse · bosanskiOnly when the destination is found to be malicious (the one exception to the rules below). · bosanskiA plain DurableQR warning page instead of the redirect, naming the address for appeals. Built and running · bosanskiAppeal by writing to the abuse address; a person reviews the appeal and restores the previous state when the block was wrong. Not available yet · bosanski
Deleted by the owner · bosanskiOnly when the owner deletes the code. · bosanskiThe same “unknown code” answer (404) as an identifier that never existed. The identifier is never issued again. Built and running · bosanskiDeletion is final. Built and running · bosanski

What never happens · bosanski

Changing the destination · bosanski

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 · bosanski

How the owner is told · bosanski

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 · bosanski

Taking your codes with you · bosanski

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 · bosanski

The account’s routing map can be exported from the panel and through the API. Built and running · bosanski

Map file format version · bosanski 1. The file carries a checksum named · bosanski sha256 · bosanski. Encodings · bosanski: csv · bosanski, jsonl · bosanski. Columns · bosanski: stable_id · bosanski, current_url · bosanski, fallback_url · bosanski, updated_at · bosanski, actor · bosanski, version · bosanski, state · bosanski.

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 · bosanski License: · bosanski Apache-2.0 · bosanski.

The reference resolver is not available yet. · bosanski

Appealing a block · bosanski

Write to · bosanski abuse@durableqr.com Built and running · bosanski, quoting the address you scanned. · bosanski

Mail sent to these addresses is forwarded to DurableQR. · bosanski

Implementation status of each commitment: · bosanski Commitment status · bosanski.

Changes in this version · bosanski

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

1.4.0 — 2026-10-28

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

1.3.0 — 2026-10-27

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

1.2.0 — 2026-10-27

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

1.1.1 — 2026-10-25

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

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

1.0.0 — 2026-09-28

  • First publication of the DurableQR commitments declaration. · bosanski