ai-conversation-user-data

Enterprise Part of the commercial Kumiko Enterprise offering — not in the open framework.

GDPR (Art. 20 export / Art. 17 erasure) coverage for ai-conversation’s designer-conversation-turn entity. Mounts the EXT_USER_DATA export + delete hooks so a user’s Designer-chat prompts and patches are included in the data export; delete hard-purges the user’s own turns, anonymize severs the author link but keeps the row (a blockDelete retention hold requires the data to physically survive). Kept separate from ai-conversation so consumers without the user-data-rights pipeline don’t pull a hard dependency — requires ai-conversation, user-data-rights.

Build it yourself

This Enterprise implementation is optional. If you need a narrower or domain-specific version, you can build an app-owned feature, handler, or job with Kumiko’s public extension points.

Use this package when you want the maintained implementation, its existing contracts, and the surrounding operational behavior. A custom implementation is not drop-in compatible automatically: your app owns its authorization, validation, integrations, tests, security review, and production operations.

Start with Features and composition and Custom write handlers.

How it fits

What this feature needs to run (Requires).

flowchart TB
  n_ai_conversation_user_data["ai-conversation-user-data"]
  subgraph how_reqs["Requires"]
    n_ai_conversation["ai-conversation"]
    n_user_data_rights["user-data-rights"]
  end
  n_ai_conversation --> n_ai_conversation_user_data
  n_user_data_rights --> n_ai_conversation_user_data

Dependencies

• Requires: ai-conversation, user-data-rights
• Activation: always on (not toggleable)

Extensions & cross-feature APIs

• Registers extension: userData → designer-conversation-turn