The framework explains why compliance can still provoke objection
Aliases: compliance-appropriateness gap · privacy backlash · normative mismatch
What it is
A contextual privacy mismatch explains how a practice can satisfy minimum legal or policy requirements yet provoke objection by disrupting contextual informational norms. Compliance asks whether an applicable rule is met; contextual integrity additionally asks whether this attribute should flow between these roles under these conditions in service of the activity's legitimate end. Objection may target role transgression, disproportionate purpose, or altered transmission rather than absence of notice.
Why it happens
Legal rules cover broad case classes and may permit processing on several bases, while organizational compliance reduces context to notices, boxes, and access controls. Formal requirements can be met even as a flow gives an unexpected recipient new judgment power and changes institutional relations. Because each step “has a basis,” teams may treat backlash as a communication problem and intensify explanation without repairing the conflicting flow.
Studying it
Case studies can independently code a practice's compliance basis and its contextual-integrity parameters, then locate where the analyses separate. Interviews should elicit the concrete source of objection, followed by parameter-substitution vignettes that test recipient, purpose, or condition. Complaint count alone is weak because discovery and reporting cost determine who appears in the record.
Where it stops holding
Objection does not automatically prove illegality or ethical failure; an unfamiliar flow with strong public value may deserve a new norm. Conversely, silence does not establish appropriateness when people cannot observe or contest the flow. Contextual integrity is a complementary normative analysis, not a way to bypass law. Decisions still need rights, interests, power, and technical facts.
Applying it
- Add a flow-parameter review beside compliance review, documenting established norm, proposed change, and effect on the activity's end.
- Code complaints by role, recipient, purpose, and condition rather than reducing them to unclear copy or user error.
- When a lawful practice is highly unexpected, first test removing recipients, coarsening attributes, or constraining onward transfer before adding explanation.
- Elicit reasoned judgments from affected roles before release and reconcile later complaints with actual flows; revise the implicated parameter and repeat the test.
Related
- Same group: O1.08.1 Appropriate information flow depends on its social context · O1.08.2 Cross-context flow may violate expectations even when technically lawful
- Adjacent: O4.01 Trust signals · P4.01 Value-sensitive design
- Search terms:
contextual privacy mismatch·privacy backlash·legal compliance gap