credit-user-data

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

GDPR (Art. 20 export / Art. 17 erasure) coverage for kumiko-credit’s credit and bauspar entities. Mounts the EXT_USER_DATA export + delete hooks so a user’s own credit lines and Bausparverträge (scoped via ownerUserId) are included in the data export; delete hard-purges the user’s own rows, anonymize severs the owner link but keeps the row for retention. Kept separate from credit so consumers without the user-data-rights pipeline don’t pull a hard dependency — requires credit, 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_credit_user_data["credit-user-data"]
  subgraph how_reqs["Requires"]
    n_credit["credit"]
    n_user_data_rights["user-data-rights"]
  end
  n_credit --> n_credit_user_data
  n_user_data_rights --> n_credit_user_data

Dependencies

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

Extensions & cross-feature APIs

• Registers extension: userData → credit, userData → bauspar