Lexicon › Data and Vendor Dynamics › Consent Drift

Data and Vendor Dynamics

Consent Drift

Theoretical Origin Nissenbaum, 2004 | Washington Law Review

Consent is not a one-time event. It is an ongoing relationship between an organisation, its clients, and the data those clients have trusted the organisation with. When AI tools expand what is done with that data beyond what was originally agreed, the relationship is violated even if no policy has technically been breached.

Definition


What is Consent Drift AI Governance Risk?

Consent drift occurs when the actual use of data expands incrementally beyond the scope of the consent under which it was collected. Each individual expansion may be minor and may occur through legitimate processes: a vendor updates their terms of service, a new AI feature is enabled by default, an integration with another platform is approved without reviewing data flow implications. Cumulatively, however, these incremental expansions produce a substantial gap between what people consented to and what is actually happening with their data.

The drift is typically invisible to the people whose data is involved. Consent frameworks are documented at the point of collection and rarely revisited. The people who provided consent have no mechanism to track subsequent changes in data practice. Similarly, the staff and leadership of the organisation handling the data frequently lack the technical visibility to monitor how AI vendor data practices evolve over time.

Contextual Integrity and Its Violation

Nissenbaum’s framework of contextual integrity provides the clearest account of why consent drift matters beyond technical compliance. Information flows appropriately, she argued, when they match the norms of the context in which information was originally shared. A community health client who shares sensitive personal information in a therapeutic context has a reasonable expectation that it will remain within that context. When AI tools process, analyse, or transmit that information in ways that violate those contextual norms, the violation occurs regardless of whether a consent form technically permitted it.

Research Origin


Nissenbaum (2004) developed contextual integrity as a framework for understanding privacy not as secrecy but as appropriate information flow. Her central argument was that privacy violations occur when information moves between contexts in ways that violate the norms governing the original context. Applied to AI governance, contextual integrity establishes a standard for consent that goes beyond technical permission: data use is appropriate only when it matches the reasonable expectations of the context in which consent was given, not merely when it falls within the letter of a consent document.

Solove (2013) identified what he called the consent dilemma: privacy law places significant weight on individual consent as the mechanism for legitimating data use, but the complexity and volume of modern data practices make meaningful informed consent practically impossible. People cannot meaningfully consent to data uses they cannot anticipate, understand, or monitor. Solove’s analysis is directly applicable to AI tool adoption: the consent obtained at the point of AI implementation cannot anticipate the full range of subsequent data practices, making drift structurally inevitable under consent-based frameworks alone.

Zuboff (2019) provided a comprehensive account of the economic logic driving consent drift in AI and platform contexts. Her concept of surveillance capitalism describes a business model in which behavioural data is extracted from users as a raw material for predictive products sold to third parties. Within this model, expanding the scope of data collection and use is not an incidental feature but a structural imperative. Community organisations adopting AI tools built on this economic logic are not simply choosing a technology. They are entering a data relationship whose terms are determined by that logic rather than by the organisation’s own values.


In AI Contexts


How Consent Drift Shows Up With AI

AI tools handle data differently from the software tools they replace. Where a word processor stores a document locally, an AI writing tool may transmit that document to vendor servers for processing. Where a spreadsheet contains client data in a closed file, an AI analysis tool may pass that data through external APIs. These differences are frequently not surfaced clearly in procurement or implementation processes, and the consent frameworks in place for predecessor tools do not automatically extend to cover AI data practices.

The Terms Update Problem

Vendor terms of service for AI tools change regularly, often with limited notice and with opt-out mechanisms that are practically inaccessible to resource-constrained organisations. Each terms update is an opportunity for consent drift: practices that were not covered by the original agreement become covered by the updated one, typically without any re-engagement with the clients whose data is affected. Organisations that accepted initial terms in good faith may find that subsequent updates have substantially expanded what they have implicitly agreed to on behalf of their clients.

Additionally, many AI tools are offered on platforms that bundle multiple services, making it difficult to understand which elements of the platform are handling which data, under which terms, for which purposes. The complexity itself produces drift, because no one in the organisation has the capacity to track all the relevant data flows across all the relevant vendor relationships simultaneously.

Why It Matters for Nonprofits


The Specific Risk for Community Organisations

Community organisations handle some of the most sensitive personal data in the service sector: health information, experiences of trauma and abuse, immigration status, mental health history, and details of family vulnerability. The people who share this information do so within a relationship of trust built on the organisation’s demonstrated commitment to confidentiality and their community’s interests. Consent drift that exposes this data to uses beyond the original agreement is not merely a compliance failure. It is a breach of the foundational trust on which the organisation’s relationships with its communities depend.

The Compounding Vulnerability

For many of the communities that community organisations serve, the consequences of data exposure extend beyond the individual. Disclosure of health status, immigration status, or involvement with social services can have consequences for employment, family separation, safety, and community standing. The harm from consent drift in community health and social service contexts is therefore not abstract. It lands on people who are already navigating significant vulnerability, in ways that can be severe and irreversible.

Governance frameworks that require active consent review at the point of each new AI tool adoption, at each significant vendor terms update, and on a regular schedule regardless of changes, directly address the structural invisibility that makes consent drift possible.

Australian regulatory context: The Office of the Australian Information Commissioner provides guidance on consent to the handling of personal information under the Privacy Act 1988, directly relevant to how community organisations manage data consent in AI contexts. OAIC guidance on consent ↗

Observable Signals


What to Watch For

These patterns suggest consent drift may be occurring in your organisation’s AI data practices. They are signals worth naming and discussing, not a definitive checklist.

  • The consent framework used with clients was developed before AI tools were adopted and has not been reviewed since, meaning it does not describe the current data practices of the organisation and cannot provide meaningful consent for AI-specific data flows.
  • Staff are unable to clearly describe what happens to client data when it is processed by AI tools, including where it is transmitted, how long it is retained, whether it is used for model training, and what third parties may have access to it.
  • Vendor terms of service updates for AI tools are accepted without review as a routine administrative task, rather than being assessed for changes to data practices that may require updated consent from clients or notification to the organisation’s leadership.

External References


From theory to practice


Understanding the risk is the first step.

The NFH Toolkit gives your organisation practical tools to audit current consent frameworks against actual AI data practices, establish regular consent review processes, and build the vendor oversight capability that protects your communities from the consequences of drift. The Behaviour Risk Cards name this pattern in language your whole team can use.

Not For Humans: Because AI’s greatest risk isn’t technical, it’s Human.