bricksgdpr¶
A dbt-first Databricks demonstration of GDPR Personal Data controls. Synthetic source extracts flow through typed staging, a separately governed raw-to-pseudonymous map, protected analytical layers, and narrow case views that can resolve selected readable fields.
The Layer1 → Layer2 → Layer3 organization expresses portable data-platform concepts. This executable implementation is Databricks-specific: it depends on Unity Catalog grants, tags and column masks, Databricks SQL functions and secrets, and a Databricks Asset Bundle.
Demonstration, not compliance certification
This repository demonstrates selected engineering controls. It is not legal advice, a complete GDPR control framework, or proof that a deployment is compliant. Production governance must also cover lawful basis, retention, operational approvals, source systems, storage history, caches, exports, backups, and incident response.
New here? Start with the tutorial.
Build and explore the demo uses deterministic synthetic fixtures to take you through a working build and its first observable checks.
The governed path¶
flowchart LR
source["Synthetic source seeds"] --> layer1["Layer1<br/>typed staging"]
layer1 --> map["priva_map<br/>readable values and keys"]
layer1 --> layer2["Layer2<br/>protected tables"]
map --> layer2
layer1 --> quarantine["Quarantine<br/>observable rejects"]
layer2 --> layer3["Layer3<br/>dimensions and facts"]
layer3 --> cases["Case views<br/>selected readable fields"]
map --> cases
Pseudonymized values remain Personal Data. The project never describes them as anonymous, and no real Personal Data belongs in its synthetic fixtures.
Find your way around¶
This documentation follows the Diátaxis framework. Choose the section that matches what you need right now.
-
Tutorial
Learning-oriented. Guided lessons that let you build the demo, trace records, and prove its key invariants one observable step at a time.
-
How-to guides
Task-oriented. Focused recipes for environment setup, deployment, scoped builds, identity provisioning, access validation, and deletion checks.
-
Reference
Information-oriented. Exact resource names, grains, settings, commands, security contracts, selectors, and project paths.
-
Explanation
Understanding-oriented. The reasons behind the trust boundaries, key design, stored masks, quarantine, least privilege, and deletion semantics.