Direct answer and scope
A useful export review begins with a written content list rather than a general promise of portability. Ask whether the export includes the selected memorial text, images, descriptions, dates, and other identified material. Ask which metadata accompanies the files, how the folders are organized, and whether documentation explains the structure. Do not assume that a browser-saved copy captures every selected item or preserves any function associated with the hosted version.
Record the status of each relevant version separately. Questions may cover source material, an approved version, a display version, an exported version, and supporting documentation, but no particular set of versions is required by the supplied guidance. Descriptive file names, organized files, and documentation of folder structure are preservation topics to discuss without prescribing a format, resolution, naming system, or technical specification.
Keep possession and copyright in separate records. Ownership of a copy containing a work does not itself transfer copyright in that work. Delivery of a photograph, portrait file, print, or memorial export therefore should be distinguished from permissions concerning reproduction, editing, distribution, display, publication, archiving, or authorization of later uses. The relevant agreement and other primary records must be examined without assuming who owns a copy, who holds copyright, or what a planned use permits.
Account and continuity questions also require separate answers. Identify who controls the hosting account, domain, destination, redirect, and any human-readable fallback, then document the handoff process for each relevant layer. The presence of a QR image or link does not answer those control questions. No current vendor manifest establishes any export, account-control, hosting, backup, restore, processor, privacy, succession, or continuity value.
How to use the official evidence
Use Library of Congress personal digital archiving guidance as a preservation-method source, not as evidence about a particular memorial service. Its guidance supports identifying important web content, exporting selected information, retaining useful metadata, organizing files, keeping copies in different places, and checking periodically whether saved files remain readable. Those steps do not establish what a vendor supplies, whether an export preserves hosted functions, or whether a given format will remain readable.
Use Copyright Office guidance to frame separate questions about copies and permissions. Ask what files or physical items will be delivered, and ask independently what written permissions address reproduction, editing, distribution, display, publication, archiving, and later use. Official copyright guidance does not resolve the parties’ rights, the effect of an agreement, or whether a specific use is allowed.
Use California privacy sources only after treating California residency and covered-business status as separate applicability questions. For a potentially covered business, locate its current privacy notices and request methods. Ask where account, photograph, memorial, visitor, commission, and support data flow; what purposes are stated for each category; and what written retention, deletion, and correction routes apply. The official regulations hub is the route for current regulatory text when more detail is needed, but it does not establish any vendor’s practices.
Use the Federal Trade Commission business guide to organize questions rather than to evaluate a vendor. Request an inventory of relevant data, the reason each category is requested, where it moves, who receives it, which outside service providers participate, what safeguards are described, how disposal is addressed, and what incident planning is documented. Keep inventory, access, protection, disposal, and incident planning as separate evidence states instead of treating a policy statement as proof of operations.
Decision framework
Start with the control layer. Request primary documentation identifying the party that controls each relevant account, domain, destination, and redirect, along with the documented continuity handoff. Record absent documentation as unresolved. Do not use control of one layer as evidence of control over another, and do not treat a QR image as evidence about the destination or account behind it.
Next, define the export layer. List the selected content and versions, then request an itemized statement of what the export contains, what metadata accompanies it, and how its folder structure is documented. Ask what is required to read the exported material and which elements, if any, still depend on the original service. Test a possessed copy separately from the hosted memorial and record the date and result of each readability check without projecting future performance.
Then separate copies by custodian and location. Record the service-held copy, commissioner-held copy, and any independently held copy as different evidence states. Library of Congress guidance recommends multiple copies in different places and periodic readability checks, but an unverified copy should not be counted. Copy possession also remains distinct from copyright ownership and permissions.
Finally, map data handling. Ask which categories are collected, why they are needed, where they move, who receives them, which processors participate, and what the written retention, disposal, deletion, correction, and incident terms say. For California privacy questions, verify residency and covered-business status before drawing conclusions about applicability. Preserve every unanswered vendor-specific field as unknown.
Limits and what to verify next
No validated vendor or platform documentation is attached for privacy practices, security measures, retention, deletion, processors, incidents, account control, export contents, file formats, backups, restoration, pricing, availability, or succession. Vendor-specific values must therefore remain unknown until current primary evidence is separately validated. Official preservation, copyright, privacy, and business-security materials provide different question sets; they should not be combined into one standard.
Request the current contract, export specification, account-control documentation, privacy notice, request routes, processor information, retention and disposal terms, and continuity handoff that correspond to the contemplated service. Compare each document with the content inventory and version list. Verify current California requirements through the official state sources when applicability matters, and use the Library of Congress material separately for preservation methods.
Check export and account-control evidence separately
Ask whether an independently readable export and current hosting-account control are documented. The page does not enter an account, inspect a platform or declare a memorial portable.
Platform export and account-control 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 | Include a California-scoped question asking a potentially covered vendor where commission, account, photograph, memorial, visitor, and support data flow. | Do not assume that a vendor is subject to the CCPA, that a file or portrait is personal information, or that a particular request must be granted. |
| Evidence 2 | Prompt a California consumer to locate the vendor's current privacy request method and written deletion and retention terms when the law applies. | Do not promise deletion, determine an exception, delete data, submit a request, or state that a vendor or memorial record is covered. |
| Evidence 3 | Include a California-scoped question about the current correction route for account or profile data when applicable. | Do not promise correction, classify portrait likeness or memorial content as inaccurate personal information, or determine that the right applies. |
| Evidence 4 | Ask a potentially covered vendor to identify its current privacy notices and request routes without supplying the site's own interpretation. | Do not state that a vendor sells or shares data, infer cross-context behavioral advertising, submit an opt-out, or decide whether conduct is discriminatory. |
| Evidence 5 | Keep sensitive-information questions tied to the current official California source and a vendor's disclosed practices. | Do not classify a memorial image, story, relationship, account, photograph, or deceased person's data as sensitive personal information or determine that the right applies. |
| Evidence 6 | 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 7 | Ask an applicable business to state the purpose and retention basis for each data category used in a portrait or hosted memorial service. | Do not evaluate necessity or proportionality, certify a privacy practice, or apply the rule to a business whose status has not been verified. |
| Evidence 8 | Link to the current regulations hub when a visitor needs primary California regulatory text beyond the consumer checklist. | Do not summarize a rule not separately verified, choose a regulation for a visitor, interpret legal text, or claim that the hub establishes vendor compliance. |
| Evidence 9 | 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 10 | 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 11 | 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 12 | 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 13 | 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 14 | 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 15 | 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 16 | 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 17 | 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 18 | 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 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 | 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 21 | 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 22 | 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 23 | 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 24 | 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 25 | 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 digital memorial export include?
Ask for an itemized statement covering the selected memorial content, relevant versions, accompanying metadata, file organization, and documentation of the folder structure. Also ask what is needed to read the exported material without the original service. Official guidance supports making an inventory and preserving metadata, but it does not establish a required file set or any vendor’s export contents.
Does having an export mean I own the content?
No ownership conclusion follows from possession alone. Copyright Office guidance distinguishes ownership of a copy from copyright ownership. Record possession of the export separately from written permissions concerning reproduction, editing, distribution, display, publication, archiving, and later use.
Who should control the hosting account or domain?
The evidence does not identify who should control a particular account or domain. Ask current documents to identify control of the hosting account, domain, destination, redirect, and continuity handoff separately. Do not treat control of one layer as proof of control over the others.
Can an exported memorial work without the original platform?
That remains unknown until the exported copy is tested independently. Ask what the export contains, what is required to read it, and which elements still depend on the original service. Keep live availability, possession of a copy, independent readability, and periodic test results as separate records.
Do California privacy rights guarantee a full memorial export?
The supplied California sources describe privacy rights for California residents involving businesses subject to the CCPA, but they do not establish that a memorial vendor is covered or that a full memorial export must be supplied. Verify residency, covered-business status, current notices, and request methods separately.
Does this page compare export features across vendors?
No vendor comparison is supported. No validated vendor manifest supplies export, account-control, hosting, backup, restore, privacy, processor, or continuity values. The available evidence supports neutral questions and preservation methods while leaving vendor-specific answers unknown.
Primary sources
- California Attorney General — California Consumer Privacy Act Verified 2026-08-26
- California Privacy Protection Agency — Frequently Asked Questions Verified 2026-08-26
- California Privacy Protection Agency — CCPA Regulations 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 Websites, Blogs and Social Media Verified 2026-08-26
- Library of Congress — Keeping Personal Digital Records 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