From 708fc4ed9644d1665eb138506898bc278cf4a143 Mon Sep 17 00:00:00 2001 From: Robin Berjon Date: Wed, 28 Jun 2023 12:54:29 -0400 Subject: [PATCH] 'registries are bad, actually' (#294) Co-authored-by: Robin Berjon --- index.html | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/index.html b/index.html index 9edaa502..02ae403d 100644 --- a/index.html +++ b/index.html @@ -683,6 +683,17 @@ and only superseded by specific [=consent=] obtained through a deliberate action taken by the user with the intent of overriding their global opt-out. +One implementation strategy for [=opt-outs=] and other data rights is +to assign [=people=] stable [=identifiers=] and to maintain a central registry to map these +[=identifiers=] to [=people=]'s preferences. [=Actors=] that wish to process a given person's +data are then expected to fetch that person's preferences from the central registry and to +configure their processing accordingly. This approach has notably been deployed to capture +[=opt-outs=] of marketing uses of people's phone numbers or residential addresses. This +approach is not recommended, for multiple reasons: it offers no technical protection against +bad actors, it creates one central point of failure, it is hard to meaningfully audit (particularly +for the scale of processing implied by web systems), and experience with existing systems +shows that they make it hard for [=people=] to exercise their rights. + ### Privacy Labour {#privacy-labour} Privacy labour is the practice of having a [=person=] carry out