Direct answer and scope
The handoff should be an evidence index, not an access grant. It can identify where records are expected to exist, which documents or exports have been considered, whether an independent copy is separately accounted for, whether a review has occurred, and which questions remain unresolved. It should not contain account credentials, recovery details, personal identifiers, memorial content, or a decision about who has legal authority.
Separate the live destination from the materials that could be used to understand or recreate it. Record the current control status for an account, domain, destination, or redirect as distinct from the status of a human-readable fallback and an independently readable export. Record the vendor or commissioner copy separately from any copy held outside the commissioned service.
A future custodian briefing can describe the evidence categories and the questions to ask a professional or vendor. It should not decide succession, transfer an account, interpret a contract, determine copyright, or treat an unanswered item as established.
How to use the official evidence
For photographs and other digital records, start with a private source-location inventory. Official Library of Congress guidance identifies possible locations such as cameras, computers, removable media, and web locations. The record can show whether each category has been considered without collecting a device name, account, file path, photograph, or file.
Then document the organization of selected material. Questions may cover descriptive file names, tags or other metadata, folder structure, and a brief explanation of how the folders and files are arranged. National Archives guidance describes basic metadata in terms of who, what, where, and when, but decisions about which nonpublic details should accompany a preservation copy should remain private.
For a hosted memorial, ask whether an independently readable export exists, what it contains, and which metadata accompanies it. Do not treat a browser-saved page as a complete export, and do not assume that an export preserves the hosted service’s functionality. Live availability, possession of an export, and testing of that export are separate records.
Preservation guidance also supports recording copy locations and review activity separately. The Library of Congress describes at least two copies in different locations and periodic readability checks; the National Archives describes a 3-2-1 approach involving three copies, two different media, and one off-site copy. These are planning references, not proof that any particular copy can be restored.
Decision framework
Use seven separate evidence questions. First, what is the current control status for the account, destination, domain, or redirect? Second, what document or export status can be shown? Third, where is a private handoff record kept without granting access? Fourth, has a copy or destination been tested for readability or operation? Fifth, which questions must be directed to a professional or vendor? Sixth, which status remains unknown? Seventh, what access has deliberately not been granted?
For contracts and copyright, list the document title or record category privately and identify which rights are claimed. Questions may distinguish delivery from permission to reproduce, prepare a derivative work, distribute, display, publish, edit, archive, or authorize later use. Copyright Office guidance states that a copy embodying a work and copyright ownership are distinct. It also states that copyright ownership transfers generally must be written and signed by the owner or authorized agent, while noting that a nonexclusive transfer does not require a written agreement.
For privacy and data handling, ask the relevant business or professional why each requested data category is needed and what the written retention and disposal term says. The FTC organizes data-security planning around taking stock of personal information, reducing what is kept, protecting retained information, disposing of information no longer needed, and planning for incidents. It also recommends considering where information is stored, how it moves, who receives it, and which outside service providers participate.
For California privacy applicability, keep residency and covered-business status as separate questions. The California Privacy Protection Agency states that CCPA rights belong to California residents and that businesses subject to the law must honor those rights through specified methods. The evidence supplied here does not resolve either applicability question or the outcome of any request.
Limits and what to verify next
No validated platform, artist, host, QR provider, domain operator, processor, product, feature, account-control record, export record, file-format record, backup record, restore record, privacy record, succession path, price, availability, review, or turnaround manifest is attached to this launch pack. Vendor-specific answers therefore remain unknown until separately validated with primary evidence.
Ask the relevant provider or professional what account and destination controls exist, what happens to a hosted memorial if access changes, whether an export can be supplied, what that export includes, how support and incident questions are handled, and what written retention and disposal terms apply. These are questions for verification, not findings about any particular provider.
Preservation review is active rather than a one-time permanence promise. A record may note whether selected files were checked for readability and whether copies were reviewed, while leaving the result and future actions unresolved when evidence is absent. A QR image should likewise be recorded separately from its underlying destination, domain control, redirect control, fallback, export, copies, and tests.
This checklist does not grant account authority, create legal succession, transfer copyright, establish a privacy-law route, or decide whether a person may access or use a memorial. Current contract terms, rights documents, account rules, and applicable official guidance should be verified through the appropriate professional or official route.
Questions people ask
A future custodian briefing should identify the current control record, destination and redirect records, human-readable fallback, contracts and rights documents, export status, copy locations, readability-test status, privacy applicability questions, and unresolved vendor questions. It should not include credentials or decide who has authority.
A private handoff can identify the existence and location of records without transferring access. Account, domain, and destination control should be documented as separate evidence states, and the record should state which access has not been granted. No identity or account information is needed for this checklist.
A backup is a separate preservation copy, not proof of access to a hosted memorial. The live destination, an independently readable export, copies held in different locations, and tests of those copies should each have their own evidence status.
A contract or copyright license should not be treated as automatically transferred. Record which rights are claimed and which written document is relied upon. Ownership of a copy is distinct from copyright ownership, and the supplied guidance does not determine the effect of a particular agreement.
If a platform closes or an account becomes inaccessible, the handoff record can show whether an independent export, fallback, or separately held copy was previously documented and tested. It cannot promise service survival, export completeness, restoration, or continued access. This checklist organizes evidence and unresolved questions. It does not create legal succession, transfer account authority, interpret a contract, determine copyright, or resolve California privacy-law applicability.
Prepare continuity handoff questions without credentials
Keep account control, recovery, renewal, destination and succession evidence separate without entering a password, recovery code, account, URL or successor identity.
Account, recovery, renewal and succession manifest: manifest_not_ready.
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 | Display California residency and covered-business status as separate applicability questions that remain unresolved until verified. | Do not infer residency, covered-business status, an exemption, a request method, a response deadline, or the outcome of a consumer request. |
| Evidence 2 | Turn those headings into vendor questions about data inventory, minimization, safeguards, disposal, and incident response. | Do not certify security, privacy, compliance, breach readiness, encryption, deletion, or the adequacy of any vendor control. |
| Evidence 3 | Ask why each requested data category is needed and what the written retention and disposal term says. | Do not determine what is integral, set a retention period, approve a collection practice, or ask a visitor to provide the information to this site. |
| Evidence 4 | Include questions about processors, hosting, support, export, backup, and disposal without naming or assuming any service provider. | Do not invent a platform architecture, subprocessors, storage location, access control, cross-border transfer, encryption state, or data-flow answer. |
| Evidence 5 | Use separate evidence rows for each responsibility and keep every unsupported response unresolved. | Do not score a vendor, imply that a privacy policy proves practice, provide technical security advice, or guarantee protection of a memorial. |
| Evidence 6 | Publish neutral vendor questions and official routes only, with every vendor-specific answer marked unknown until primary evidence is separately validated. | Do not name a vendor, summarize a vendor policy, claim a privacy feature, infer image analysis, or state that an account or memorial is protected. |
| Evidence 7 | Use a controlled source-location inventory status without asking for a photograph, device, service, account, or file path. | Do not scan devices, discover files, connect to accounts, upload photos, or claim that the inventory is complete. |
| Evidence 8 | Include file-naming, metadata, and folder-manifest questions in the portrait handoff checklist. | Do not collect names, relationships, dates, locations, descriptions, tags, filenames, folders, or other metadata from a visitor. |
| Evidence 9 | Ask whether an independently readable preservation copy exists outside the commissioned service. | Do not claim that two copies prevent loss, approve a medium or location, or treat a vendor-hosted copy as independent without evidence. |
| Evidence 10 | Describe preservation as an active review process rather than a one-time permanence promise. | Do not guarantee readability, prescribe a universal replacement schedule for every medium, automate a reminder, or claim that an online service will remain available. |
| Evidence 11 | 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 12 | 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 13 | Include master, approved, display, export, and documentation version-status questions without inventing a required file set. | Do not prescribe a file format, resolution, color space, layer structure, naming convention, or number of versions for a commission. |
| Evidence 14 | Keep the vendor copy, commissioner copy, and independent backup evidence states separate. | Do not count an unverified copy, guarantee recovery, approve a storage provider, or state that an inaccessible file is preserved. |
| Evidence 15 | Use the hub as the federal preservation-method route and keep vendor features and file decisions separately evidenced. | Do not claim that the Library endorses a vendor, format, platform, QR system, portrait workflow, cloud host, or memorial service. |
| Evidence 16 | Offer this as one official naming approach for a private archive, not as a required artist filename. | Do not rename files, collect filenames, state that another naming scheme is invalid, or claim that naming alone preserves a file. |
| Evidence 17 | Prompt the visitor to decide privately which nonpublic metadata should accompany preservation copies and which should not be displayed. | Do not ask for or publish a person's name, relationship, date, location, event, biography, image description, or other memorial metadata. |
| Evidence 18 | Use the official approach as a planning reference and show each copy and location category as an unresolved evidence state. | Do not guarantee data survival, prescribe a vendor or medium, verify a backup, treat synchronization as backup, or claim that an off-site copy can be restored. |
| Evidence 19 | Distinguish possession of a source photograph, portrait file, print, or exported memorial copy from copyright ownership and permission. | Do not decide who owns a physical or digital copy, who owns copyright, whether a use is licensed, or whether a source photograph may be used. |
| Evidence 20 | Ask which rights are claimed, whether the arrangement is exclusive or nonexclusive, and which signed document is relied upon. | Do not interpret a clause, decide whether a transfer occurred, draft a license, prescribe exclusivity, or state that an unsigned permission is invalid. |
| Evidence 21 | Separate portrait delivery from permissions to reproduce, edit, distribute, display, publish, archive, and authorize later use. | Do not decide whether a planned use implicates a right, whether an exception applies, or whether a person may publish, edit, print, share, or display a work. |
| Evidence 22 | 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 23 | 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. |
| Evidence 24 | Render the compact brief on the homepage and the full checklist on a separate page outside model-written editorial text. | Do not output owned, licensed, permitted, private, secure, backed up, restorable, exportable, permanent, accessible, compliant, recommended, ready, or complete. |
| Evidence 25 | Describe the tools as anonymous in-page organizers whose controlled selections reset locally and are not sent to the publisher. | Do not add image analysis, face recognition, biometric processing, generation, restoration, personalization, cloud export, saved project, account connection, vendor submission, or background request. |
| Evidence 26 | Show selected labels, unresolved questions, scope notes, and internal reading routes with a reset action. | Do not calculate a score, select a vendor, provide a legal result, or recommend proceeding with a commission or hosted memorial. |
Questions people ask
What should a future digital memorial custodian know?
The custodian should know which control, contract, rights, export, copy, location, fallback, and review records exist, along with the questions that remain unresolved. The briefing should not provide credentials or decide legal authority.
How can account and domain information be handed off privately?
Record the existence and status of account, domain, destination, and redirect controls separately from the handoff notes, and identify access that has not been granted. Do not place credentials, account identifiers, or personal information in the checklist.
Does a backup grant access to a hosted memorial?
No conclusion about hosted access follows from the existence of a backup. A live memorial, an independently readable export, separately held copies, and tests of those copies are distinct evidence states.
Can a contract or copyright license transfer automatically?
Do not assume that it does. Record the rights claimed and the document relied upon. Copyright guidance distinguishes possession of a copy from copyright ownership and addresses written, signed transfers while noting a separate rule for nonexclusive transfers; a particular agreement still requires appropriate review.
What if a memorial platform closes or an account becomes inaccessible?
Separate the status of the hosted destination from any independent export, fallback, or copies held elsewhere, and record whether those materials were checked for readability. The checklist does not establish that a service, link, export, or copy will remain available or usable.
Does this checklist create legal succession or account authority?
No. It organizes evidence and unresolved questions without deciding succession, transferring account authority, interpreting a contract, determining copyright, or resolving California privacy-law applicability.
Primary sources
- California Privacy Protection Agency — Frequently Asked Questions Verified 2026-08-26
- Federal Trade Commission — Protecting Personal Information: A Guide for Business Verified 2026-08-26
- Library of Congress — Personal Digital Archiving Verified 2026-08-26
- Library of Congress — Keeping Personal Digital Photographs Verified 2026-08-26
- Library of Congress — Keeping Personal Websites, Blogs and Social Media Verified 2026-08-26
- Library of Congress — Keeping Personal Digital Records Verified 2026-08-26
- National Archives — Digitizing Family Papers and Photographs Verified 2026-08-26
- U.S. Copyright Office — Copyright Basics, Circular 1 Verified 2026-08-26
- Memorial Portrait and Digital Continuity Desk validated source and checklist methodology Verified 2026-08-26