dbt integration

Carry PII metadata through dbt models.

Chameleon uses dbt context to help privacy and data teams understand how customer-data policy follows warehouse transformations and derived models.


Why it matters

Model context

Connect model metadata with resources in the PII registry so policy does not stop at raw tables.

Derived identifiers

Track surrogate identifiers and aggregate-only handling where customer data changes shape through transformations.

Owner clarity

Make model ownership and policy status visible when a privacy review needs a data-team answer.


Chameleon workflow
01 / Declare

Use dbt metadata as policy context for warehouse resources and transformations.

02 / Trace

Keep customer-data context attached as raw records become staging, intermediate, and mart models.

03 / Review

Flag policy warnings where derived identifiers or manual-review strategies need attention.

04 / Prove

Include model context in deletion proof workflows when a request touches transformed data.


Proof surface
source: dbt manifest metadata
model: mart_customer_metrics
pii_context: user_surrogate_id
strategy: manual_review