---
title: "Compliance is an architecture problem"
url: "https://velacria.com/notes/compliance-is-architecture/"
canonical: "https://velacria.com/notes/compliance-is-architecture/"
author: "Julien Le Nestour"
description: "The useful privacy work is not saying no to tracking. It is designing the version legal can approve and platforms can still learn from."
pubDate: "2026-04-15T00:00:00.000Z"
tags:
  - "privacy"
  - "tracking"
  - "measurement"
taxonomies:
  pillar: "privacy"
  format: "short-note"
  tags:
    - "privacy"
    - "tracking"
    - "measurement"
---

The weak version of privacy work is treating compliance as a brake.

The useful version is treating it as an architecture constraint.

What data should be collected? Which platform should receive it? Under what consent state? At what granularity? From browser, server, CRM, or warehouse? With which matching fields? For which business objective?

Those questions are technical, legal, and commercial at the same time. If they are answered separately, the result is either risky tracking or compliant underperformance.

Good tracking architecture has to make those tradeoffs explicit.