Direct answer and scope
Static and dynamic labels do not provide enough evidence to rate one architecture above the other. A decision requires records showing the destination encoded in the QR image, any domain or account involved, any redirect between the code and memorial, the authority associated with each layer, and any renewal or subscription dependency. A QR image is only one evidence state and does not establish persistence.
The comparison is limited to documented architecture and continuity questions. It does not establish any vendor feature, service availability, privacy practice, analytics practice, export format, backup process, restoration process, price, account-control arrangement, or succession path. Those values remain unknown until supported by a separate, current primary-evidence record.
How to use the available evidence
Treat each decision point as a request for a dated record, not as a conclusion drawn from the QR type. For destination editability, identify what address is encoded and document whether any destination or redirect can be changed. For control, identify the relevant domain, account, and redirect authority. For continuity, record renewal dependencies, an available fallback record, and the date on which each document was reviewed.
Export evidence belongs in a separate record from live-link evidence. The Library of Congress recommends identifying important web content, exporting selected information, preserving metadata such as the site name or creation date, and organizing the files. An export question should therefore identify what content and metadata are included and whether the result can be read independently. It should not assume that functionality, completeness, restoration, or future readability is preserved.
| Decision point | Record for a static claim | Record for a dynamic claim | Current status |
|---|---|---|---|
| Destination editability | Encoded destination and documentation of whether any layer can change | Encoded destination and documentation of whether any layer can change | Unknown for both labels |
| Domain and redirect control | Domain, account, redirect, and authority records | Domain, account, redirect, and authority records | Unknown for both labels |
| Renewal or subscription dependency | Current terms for every applicable account, domain, host, or redirect | Current terms for every applicable account, domain, host, or redirect | Unknown for both labels |
| Privacy and analytics | Documentation of any scan records, processing, access, and retention | Documentation of any scan records, processing, access, and retention | Unknown for both labels |
| Export and fallback | Export contents, metadata, independent copies, tests, and handoff record | Export contents, metadata, independent copies, tests, and handoff record | Unknown for both labels |
Decision framework
Control and renewal: begin with the exact destination represented by the QR image, then document every separate domain, account, host, and redirect involved. Record which authority applies to each layer and whether that layer depends on a renewal or active subscription. Add a continuity handoff record rather than assuming that possession of the QR image provides access to an account, domain, or redirect.
Privacy questions: request documentation stating whether a scan creates analytics or other records, what information is involved, who can access it, whether a processor is involved, and what retention or deletion terms apply. No current manifest answers those questions for either QR label, so the comparison must preserve each value as unknown rather than assigning a privacy status.
Continuity decision worksheet: keep live memorial availability, exported content, independent copies, readability tests, and continuity handoff as separate entries. For an export, record its contents, included metadata, organization, and the date it was checked. The Library of Congress recommends multiple copies in different locations and periodic checks that saved files remain readable. Those steps do not establish that the live link, domain, redirect, host, or export will continue operating.
Visible fallback and scan review: place a human-readable destination with the physical memorial so a visitor can examine the destination without relying only on the code image. The Federal Trade Commission advises inspecting the address before opening a QR destination and checking recognizable addresses for signs such as misspellings or switched letters. That review does not authenticate the destination or establish that it will remain unchanged.
Evidence limits and unresolved questions
No validated record currently identifies a vendor, platform, QR provider, domain operator, processor, product, feature, account-control arrangement, privacy practice, export, file format, backup, restoration process, succession process, price, availability, review, rating, or turnaround. Static and dynamic values for those fields must remain unknown. A descriptive label, QR image, or redirect claim cannot fill an unanswered field.
The Federal Trade Commission material supports a scan-safety note, while the Library of Congress material supports personal-archiving questions. Neither source establishes vendor-specific architecture or a California-specific requirement for memorial QR codes. Unresolved documents include the encoded-destination record, domain and account authority, redirect authority, renewal or subscription terms, privacy and analytics documentation, export specification, independent-copy record, readability-test record, and continuity handoff.
Questions people ask
The useful questions focus on evidence rather than labels: what destination is encoded, which layers can change, who has authority over accounts and redirects, which renewals or subscriptions apply, what scan information is recorded, what an export contains, where independent copies are kept, when they were last tested, and what continuity handoff exists. Until those records are available, architecture, control, privacy, and continuity remain unresolved.
Evidence behind this page
Each point below is restricted to what the cited primary source supports. Administrative listing status is not a quality endorsement.
| Evidence | Supported point | Scope and limitation |
|---|---|---|
| Evidence 1 | Explain why a physical memorial should show a human-readable destination and why a visitor should inspect a destination before opening it. | Do not claim that a memorial QR code is malicious, safe, secure, permanent, authenticated, monitored, or protected from later destination changes. |
| Evidence 2 | Include a scan-safety note and a checklist question for a visible, verifiable destination outside the code image. | Do not validate a URL, scan a code, open a destination, promise detection of spoofing, or substitute the note for device or security guidance. |
| Evidence 3 | Ask whether a hosted memorial provides an independently readable export, what the export contains, and which metadata accompanies it. | Do not claim that a vendor offers export, that a browser-saved page is complete, that an export preserves functionality, or that a format will remain readable. |
| Evidence 4 | Separate live memorial availability from possession of independent exported copies and from testing those copies. | Do not promise website uptime, domain renewal, redirect continuity, service survival, full export, restore capability, or long-term link operation. |
| Evidence 5 | Publish official method guidance and vendor-question fields only, leaving vendor-specific values unknown until a separate primary-evidence manifest passes review. | Do not name, list, rank, recommend, contact, quote, compare, review, or imply a feature or capability of any vendor or platform. |
| Evidence 6 | Keep every layer visible and unresolved rather than using a QR-present badge as proof of persistence. | Do not guarantee a QR code, link, URL, domain, redirect, account, host, export, backup, restore, or memorial will remain accessible. |
Questions people ask
Are static or dynamic QR codes better?
Neither label can be rated above the other from the current records. The relevant comparison separates the QR image, destination, domain or account authority, redirect control, renewal dependencies, human-readable fallback, export, independent copies, periodic tests, and continuity handoff. The preferred arrangement depends on which of those documented states meets the memorial’s requirements, but vendor-specific values are currently unknown.
What is the difference between static and dynamic QR codes?
The current evidence does not support assigning a universal feature definition to either label. For a particular memorial, document the destination encoded in the image, whether another destination or redirect is involved, what can be changed, and which account or authority controls each layer. A static or dynamic description by itself does not resolve destination editability, control, renewal, privacy, export, or continuity.
Which account and redirect records should be requested?
Request the encoded destination, the relevant domain and account records, any redirect record, the authority associated with each layer, applicable renewal or subscription terms, and a continuity handoff record. Also request a dated fallback record showing the human-readable destination. These records should remain separate because possession of a QR image does not establish control of a destination, account, domain, or redirect.
Does either QR type guarantee a permanent link?
No. Neither a QR label nor the presence of a QR image establishes continued operation of the destination, domain, redirect, account, host, export, backup, or memorial. Independent exports and copies are separate from live availability. The Library of Congress recommends keeping multiple copies in different locations and periodically checking that saved files remain readable, without establishing continued link operation.
Primary sources
- Federal Trade Commission — Scammers Hide Harmful Links in QR Codes Verified 2026-08-26
- Library of Congress — Keeping Personal Websites, Blogs and Social Media Verified 2026-08-26
- Memorial Portrait and Digital Continuity Desk validated source and checklist methodology Verified 2026-08-26