template-resolver-user-data

GDPR (Art. 20 export / Art. 17 erasure) coverage for the template-resolver feature’s user-content-entry entity — the per-user half of the content store (mail signatures, personal reply snippets). Mounts the EXT_USER_DATA export hook so a user’s own entries land in the export bundle; the delete hook is a deliberate no-op because content is annotated userOwned, so erasure runs via crypto-shredding (destroying the owner’s subject key) rather than a physical delete, which would not survive an event replay. Mount this whenever createTemplateResolverFeature declares a collection with ownership: "user" — the boot guard otherwise refuses the entity. Requires user-data-rights, optionalRequires template-resolver.

How it fits

What this feature needs to run (Requires).

flowchart TB
  n_template_resolver_user_data["template-resolver-user-data"]
  subgraph how_reqs["Requires / optional"]
    n_user_data_rights["user-data-rights"]
    n_template_resolver["template-resolver"]
  end
  n_user_data_rights --> n_template_resolver_user_data
  n_template_resolver -.->|optional| n_template_resolver_user_data

Dependencies

• Requires: user-data-rights
• Optional: template-resolver
• Activation: always on (not toggleable)

Extensions & cross-feature APIs

• Registers extension: userData → user-content-entry