Privacy by Design in .NET Systems & APIs

Privacy as an engineering discipline is broader than any one regulation. GDPR is the loudest constraint in Europe, but the underlying principles — data minimisation, purpose limitation, storage limitation, integrity, and accountability — show up in HIPAA, ISO/IEC 27701, the AI Act, and every serious internal security standard. The architectural decisions that satisfy one set generally satisfy the rest. The point of this collection is the architecture, not the regulation.

Data minimisation starts in the schema. An Entity Framework User entity that captures birth date, employment status, and marital status “just in case” is a liability the moment somebody requests deletion. Personal data belongs in its own aggregate, attached by reference rather than embedded as columns, with each field tagged for purpose and consent so a query can answer “what may I still process for this person, and why?” The same principle drives EF Core query filters, projected DTOs that strip unrequested fields, and view-model boundaries that refuse to let a database row leak into a response.

Purpose limitation is the API-side counterpart. A password-reset endpoint that returns a full profile, an internal admin tool that exposes every column to every operator, an analytics export that mirrors production schema — each one violates the constraint that data must only be processed for the purpose it was collected for. Resource-based authorisation in ASP.NET Core, field-level access policies, and explicit DTOs per caller intent are the boring mechanics that make purpose limitation enforceable rather than aspirational.

The articles here also cover the operational half: privacy health checks that surface expired consents alongside database connectivity, audit automation that runs at build time so PII added last Tuesday is caught before production, and log scrubbing patterns that keep personal data out of telemetry pipelines that backups and SIEMs would otherwise retain for years.

Cookie Banners Won't Save You From ISO 27701

Cookie Banners Won't Save You From ISO 27701

That boolean column you call “consent”? Regulators will laugh at it.

ISO 27701 demands granular, auditable, expiring consent, not cookie theater. Here’s the complete .NET implementation with Entity Framework Core, middleware validation, and Azure Functions that survives an audit.

Stop Hoarding Personal Data in Entity Framework

Stop Hoarding Personal Data in Entity Framework

The classic monolithic User entity—stuffed with birth dates, phone numbers, employment history, and marital status “just in case”—turns into a compliance nightmare the moment someone requests data deletion. You can’t delete without breaking referential integrity. You can’t keep the data without violating GDPR. You can’t anonymize without retaining fields that should never have existed. The solution isn’t complex: separate operational data from personal data, make consent-based fields nullable and purpose-documented, implement soft deletes with query filters, and validate your API boundaries with integration tests that fail when unnecessary fields leak through. Data minimization isn’t regulatory overhead—it’s architectural hygiene that makes your deletion logic straightforward and your audit responses honest.