GDPR (Data Controller)

A company that decides why personal data is used holds the heaviest privacy duties in Europe. Lawfulness, transparency and individual rights all trace back to that decision. This starter gives the runtime side of those duties a defined shape, and the documentation stays yours.

Proof is the real burden. A supervisory authority asks for the basis, the purpose and the safeguard, and it expects the same answer from the system and from the notice. Configuration is the part of that answer that cannot drift.

Consent handling is the distinctive part of the request path. Every call must carry a value in the named consent header, or the gateway refuses it. The declared categories of personal, sensitive and biometric data are recorded with that decision rather than used to narrow it. The gateway confirms that the header holds a value and does not judge what that value means.

Redaction masks national identifier numbers and international bank account numbers before the prompt travels further. Named terms end the request when a prompt reaches for genetic data, biometric records or health data. Those categories need a specific lawful basis, and a general assistant is rarely the right place for them.

Output scoring sets every floor at 0.80, for combined quality, relevance and accuracy. A person then reads whatever survives, because the review stage releases nothing directly to the caller. Your rights process and your transfer assessment take over at that handover point. Treat the reviewer as a full time role rather than an exception path.

Records of processing, impact assessments and breach notices to a regulator remain your documents. The processor starter is the better fit when you act only on instructions from another company.