The operational demands are concrete: a lawful basis for each purpose, records of processing, the ability to export or erase everything about one person, and defensible answers about transfers outside the EU. Architecture determines how expensive each of those is to satisfy.
More in Privacy
- AnonymizationIrreversibly stripping data of anything that could identify a person. Unlike pseudonymization, there is no key that brings the identity back.
- CCPACalifornia privacy law giving residents the right to know what is collected about them, to delete it, and to opt out of its sale.
- Consent managementRecording what each user agreed to and enforcing it at collection, so consent is a property of the pipeline rather than a banner.
- Data minimizationCollecting only what a stated purpose needs. The cheapest way to reduce risk is not to hold the data at all.
- Data residencyThe requirement that data physically stays in a given jurisdiction. On Flex you pick the region; on Enterprise it is wherever you deploy.
- Data sovereigntyThe principle that data is subject to the laws of the country it sits in, and that you, not a vendor, decide which country that is.