Constraint Sensitive Data is what happens when your systems stop treating data as flat. It’s the discipline of embedding rules, relationships, and context into every read and write. Instead of only tagging data as sensitive, you define how, when, and by whom it can be touched—automatically, without relying on someone to remember the policy.
It starts with constraints. Not just foreign keys and null checks, but policy-level constraints. Example: a field that can only be seen if the requesting service passes an authorization check tied to a regulation. Or a record that becomes read-only once it moves into an audited state. These constraints live inside the data model, executed at the lowest possible layer, so there’s no path around them.
This approach changes how sensitive data flows. Instead of building brittle middleware rules and API filters, constraint logic binds itself to the data. Any system that queries it inherits the same protections. It reduces risk from human error, shadow APIs, or rogue processes. The guarantees go with the data wherever it travels.