Privacy Preference Declaration for Home Networks

Introduction The rapid growth of Internet-connected devices in the home has introduced new and often overwhelming challenges to personal privacy. While many of these devices collect sensitive data by design, the tools offered to users to understand or control that collection are fragmented, confusing, or entirely absent. When privacy settings do exist, they are often buried in obscure menus, expressed in legal or technical jargon, and lack the contextual clarity needed to support meaningful decision-making. The result is a fragmented operational model. Users must manage privacy through device-specific controls that vary widely in quality and semantics, while device vendors and service providers often implement isolated mechanisms with no common way to convey household privacy preferences across devices. This lack of a shared signaling model makes it difficult for households to understand which devices have been presented with which privacy expectations, and it makes interoperable deployment harder for implementers. frames mass data collection as a technical threat, urging protocol designers to limit exposure through encryption and data minimization. While this principle is crucial in adversarial, internet-scale contexts, the model proposed in this document takes a different approach: rather than hiding data flows, it seeks to govern them. Privacy here is not achieved by making devices blind, but by making user-defined preferences visible to devices and associated services. This use of privacy is related to, but distinct from, the privacy guidance in , which emphasizes reduced observability, linkability, and identifiability in protocol design. Those properties remain important, but PPD focuses on a different home-network problem: a user needs a consistent way to express household privacy preferences and to know that those preferences were made available to participating devices or associated services. This document is also aligned with the user-agency goals described in , but it is narrower and more operational. It describes an architecture for privacy-preference signaling and recordkeeping, not a general framework for human-rights analysis or for constraining device behavior. Home networks are a significant and operationally important IoT environment. They commonly place a local administrative boundary around large numbers of devices, many with limited or no end-user interface, making them a concrete target for a privacy-preference signaling architecture. In this architecture, discovery identifies candidate participant-facing service endpoints. Trust in a selected endpoint, and in the policy instances it presents, is established separately through the applicable protocol and security mechanisms rather than by discovery alone. This also addresses an asymmetry common in current deployments: the household user is often required to acknowledge device- or vendor-defined terms, while the household has no comparable way to record that a participating device or associated service was presented with the household's privacy policy. PPD introduces a reciprocal signaling path in which presentation and acknowledgment of a household policy instance can be recorded by the household domain. The objective is to provide a coherent architectural basis for devices and associated services to retrieve, acknowledge, and keep current with household privacy preferences within that administrative domain.

Conventions and Definitions The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. The terms below define both protocol roles and core concepts used by this architecture. The definitions of privacy, transparency, and user control are included here because they describe the conceptual scope of PPD rather than separate protocol mechanisms.

Terminology

Privacy:: In this document, the ability of users to understand and shape how data about them, their household, or their home environment is collected, used, retained, and shared by devices and associated services.
Transparency:: The property that data practices are made visible and understandable to the user, including what data is collected, how it is processed, where it is shared, and what policy preferences apply.
User control:: The ability of a user or household to define privacy preferences and make those preferences visible to devices or associated services in a consistent and actionable way.
Privacy Preference Declaration (PPD):: A structured expression of household privacy preferences that can be discovered, retrieved, and acknowledged by PPD participants.
PPD service endpoint:: A participant-facing service, and the baseline discovery target for participants, through which a PPD participant discovers, retrieves, and acknowledges applicable policy instances.
Policy authority:: The authoritative source of household policy state and of any inputs used to derive an effective policy for a participant. The policy authority may be local or remote. Participants are not required to discover or address the policy authority directly in the baseline architecture.
Household policy:: A policy selected or maintained for a home network that represents the household's privacy preferences.
Effective policy derivation:: The logical function, performed by or on behalf of the policy authority, that determines the effective policy instance for a participant.
Effective policy:: The policy instance that applies to a particular PPD participant at a particular time, after effective policy derivation has resolved household policy state and any applicable participant-specific inputs.
PPD participant:: A device, or a trusted intermediary such as a backend service acting on behalf of a device, that participates in PPD by retrieving and acknowledging an applicable policy instance.
Policy instance:: A specific version or representation of an effective policy that can be identified for acknowledgment and recordkeeping.
Association:: The state established when a PPD participant has retrieved the current applicable effective policy and acknowledged receipt of that specific policy instance.
Current association:: Association state that still corresponds to the latest applicable effective policy for the participant and remains fresh according to the renewal model enforced by the PPD service endpoint.
Association freshness:: The property that an association remains within the bounded interval, or before the renewal deadline, accepted by the PPD service endpoint for treating that association as current.
Stale association:: Association state that still refers to the latest applicable effective policy instance, but whose freshness can no longer be confirmed because renewal did not occur within the bounded interval accepted by the PPD service endpoint.
Needs reassociation:: A state in which current association cannot be confirmed because the applicable effective policy changed, participant state relevant to effective policy derivation changed, or enough state was lost that the existing association no longer applies reliably.
Reassociation:: The process by which a PPD participant recovers from stale association or a needs-reassociation state and re-establishes current association.
Broken association:: A state in which stored or reported information is contradictory or incomplete enough that current association cannot be determined reliably.
Policy acknowledgment:: A signal that a PPD participant has received a specific effective policy instance. A policy acknowledgment is not a statement that the device is compatible with every policy term or that the device will behave in a particular way.
Network-observed device:: A device that is visible to the local network through ordinary network observation but that has not established association through PPD.
Unmanaged device:: A network-observed device that is not known to participate in PPD or is not currently manageable through PPD association.

Limitations of Existing Mechanisms Current mechanisms for managing data privacy within the home environment exhibit limitations.

Device-specific Configurations Individual devices often employ unique privacy settings, thereby complicating user management of privacy across the entire network. This complexity can inadvertently lead to unintended data sharing.

Ineffective and Unusable User Interfaces Navigating and configuring privacy settings on individual devices can be a time-consuming and frustrating experience for users. These ineffective interfaces often lead users to habitually agree to relax their privacy preferences without fully understanding the implications of their decisions. This fosters a general resignation towards privacy management, making it difficult for users to exert meaningful control over their personal data and ultimately compromising their privacy expectations.

Relationship to Existing Work

DNT and P3P Protocols like Do Not Track (DNT) and Platform for Privacy Preferences Project (P3P) have not achieved widespread adoption and have proven inadequate for addressing nuanced privacy needs. These protocols do not provide the participant-specific policy signaling, lifecycle handling, or home-network operational posture needed here. They also do not provide a practical basis for recording that a participating device or associated service was presented with a household policy instance.

MUD Manufacturer Usage Description (MUD) is the closest existing precedent for device-to-home-network signaling. MUD is focused on manufacturer-defined network communication intent presented to local network infrastructure. PPD addresses a different problem: household-defined privacy preference signaling, participant-specific effective policy presentation, and recordkeeping about whether a participant was presented with a current household policy instance. The two approaches may complement each other in a deployment, but MUD does not provide the privacy-policy lifecycle or recordkeeping model described here.

Privacy Vocabularies and Policy Models Vocabulary and policy-expression efforts such as the Data Privacy Vocabulary (DPV) and ODRL are closer to the content layer than to the signaling layer. PPD does not attempt to replace such work with a new general-purpose ontology or rights language. Instead, PPD separates concerns: this architecture defines roles and lifecycle, the companion taxonomy work defines the core fields and shared computable floor that can map to richer vocabularies, and the companion protocol work defines the participant-facing signaling path by which an effective household policy is presented and acknowledged.

Operational Scenarios This section describes representative operational cases for the architecture in home-network environments. The scenarios focus on discovery, association, reassociation, and mixed-participant visibility rather than on user-interface details.

Initial Discovery and Association A PPD participant joins the home network and obtains one or more candidate PPD service endpoints through configuration or local network discovery. In a common home deployment model, the PPD service endpoint is hosted by a residential gateway or equivalent home-network service. Discovery identifies reachability, not authority. The participant establishes a secure connection to a selected endpoint, confirms that endpoint through the applicable trust mechanism, retrieves the applicable effective policy instance, and acknowledges receipt of that policy instance. The PPD service endpoint may present policy derived from a local or remote policy authority without exposing that internal topology to the participant. At the end of this process, the participant has established association if the current applicable effective policy has been delivered and acknowledged. The PPD service endpoint also determines the initial freshness state of that association.

Policy Update and Reassociation The household policy, or the participant's effective policy, changes. The PPD service endpoint immediately invalidates current association for the participant. The participant enters a needs-reassociation state until it retrieves and acknowledges the updated effective policy instance. This scenario illustrates that association state is tied to a specific policy instance and not to prior acknowledgments alone. Reassociation re-establishes current association by confirming that the participant has seen the latest applicable policy instance.

Association Freshness Expiry and Renewal The applicable effective policy instance is unchanged, but the participant does not renew within the bounded interval accepted by the PPD service endpoint. The association becomes stale even though no policy change occurred. The participant no longer has current association until it completes the required renewal procedure. This scenario distinguishes stale association from a needs-reassociation state caused by a changed policy instance.

Participant State Change A participant changes in a way that can affect the applicable effective policy instance, such as a declaration update, capability change, or other state change relevant to effective policy derivation. The PPD service endpoint determines that current association can no longer be confirmed using existing state alone. The participant then retrieves and acknowledges the newly applicable effective policy instance. This scenario keeps the architecture focused on policy signaling and recordkeeping without assuming that every state change requires the same local handling or transport behavior.

Mixed-Participant Network Visibility A home network contains both PPD participants and devices that do not participate in PPD. The household can still use local management functions to distinguish associated participants, participants whose current association cannot be confirmed, and network-observed or unmanaged devices. This scenario illustrates that non-participating devices are an expected operational reality. Their presence can inform transparency and local management decisions, but it does not create association or change the baseline signaling role of PPD.

Goals

Enhance User Control

Support a household's ability to define privacy preferences that can be made available consistently across participating devices and associated services.
Provide an architectural basis for recording whether the current applicable policy was made available to a participant.
Create a reciprocal acknowledgment model in which the household can retain a record that a participant or associated service was presented with, and acknowledged, a specific household policy instance.

Promote Interoperability

Establish a standardized mechanism for devices from diverse manufacturers to discover PPD service endpoints, retrieve applicable privacy policies, and acknowledge policy instances.
Support consistent association and reassociation behavior across heterogeneous participants.

Enable Flexibility

Allow deployments to place policy storage and effective-policy derivation locally or remotely without changing the baseline participant-facing contract.
Leave room for deployment-specific protocol profiles where constrained environments or different operational models require them, including trusted-intermediary participation for devices that cannot satisfy the minimum authenticated direct-participant bar.

Facilitate Transparency

Provide a basis for local management functions to distinguish currently associated participants, stale or reassociation-needed participants, and non-participating devices.
Improve visibility into which participants have been presented with the current applicable policy instance, without implying enforcement of device behavior.

Scope This document defines a high-level architectural framework for Privacy Preference Declaration (PPD) in home-network environments. It focuses on roles, trust boundaries, lifecycle meaning, and operational assumptions for making household privacy preferences available to devices and associated services. This document does not delve into specific implementation details, such as message formats, data structures, security algorithms, or user interface design. Furthermore, this document does not define mechanisms that modify device behavior, legal and regulatory considerations, or specific security protocols. Where this document discusses recordkeeping, that recordkeeping is limited to signaling and recording that an applicable household policy was made available to and acknowledged by a PPD participant. That recordkeeping can provide a basis for later accountability, audit, or dispute analysis, but this document does not define enforcement behavior or prove subsequent compliance. Specific implementation details and message formats are expected to be addressed in companion specifications. This document aims to be complementary to existing and future standards related to home networking, IoT security, and data privacy. This document provides the foundation for subsequent work, including:

Privacy Preference Declaration Taxonomy: defines the core vocabulary, extension model, and mapping expectations for the privacy-related terms used by PPD statements and rules, including the shared semantic floor that keeps those terms computable across heterogeneous devices and vendors. That core is intentionally small; richer vocabularies can still be used so long as they remain reducible to the shared baseline primitives.
The companion protocol specification document, , defines the message formats, data structures, and communication procedures for PPD, including mechanisms for PPD service endpoint discovery, metadata confirmation, participant registration, optional participant declaration, policy retrieval, policy acknowledgment, renewal, and reassociation.

Architecture Overview

Assumptions This document makes the following assumptions:

User Control: It is assumed that users have a reasonable level of control over their home network infrastructure. This includes the ability to configure routers, install software updates, and manage device access to the network. This control is essential for users to effectively manage their privacy preferences and make them available to devices within their home network.
Resource Constraints: It is assumed that the home network environment and devices operating therein have resource limitations, such as limited processing power and bandwidth. We limit this assumption by considering that the PPD protocol and its associated mechanisms should be designed with these constraints in mind, minimizing overhead and ensuring efficient operation even on resource-constrained devices. Where a device cannot satisfy the minimum authenticated direct-participant bar, this architecture expects indirect participation through a trusted intermediary rather than weakening the meaning of direct protocol participation.
Security Considerations: It is assumed that home networks in scope of this document are susceptible to typical security threats, including insider threats (or non-malicious misconfiguration) and vulnerability to local attacks. We limit this assumption by considering specific security threats to protect user privacy and the integrity of the privacy policy. This includes considerations for secure policy dissemination, device authentication, and protection against unauthorized access and modification of privacy preferences.
Single User Policy: This document assumes that each device implementing the protocol is governed by a single, unified privacy policy defined by its primary user. While other individuals within the same physical environment (e.g., household) may have different privacy preferences, the protocol is designed with the expectation that a device or associated service can receive the policy established by its primary user. Future extensions could explore mechanisms for managing and reconciling multiple user-defined policies on a single device, particularly in shared or multi-user environments.
Endpoint Discovery and Trust: It is assumed that configuration or local network mechanisms can identify one or more candidate PPD service endpoints for a participant. Discovery alone does not establish that an endpoint is authoritative for household policy. The applicable protocol profile needs a separate way to authenticate the selected endpoint and confirm that policy presented through that endpoint is authoritative for the participant's household context.
Policy Signaling: It is assumed that PPD participants can retrieve the applicable household privacy policy through a PPD service endpoint and acknowledge receipt of that policy instance. This acknowledgment forms the basis of association. It is a receipt signal only; it does not assert that the participant is compatible with every policy term or that it will behave in a particular way. Current association also depends on association freshness as determined by the PPD service endpoint.
Association Freshness: It is assumed that current association expires unless the participant renews within a bounded interval accepted by the PPD service endpoint. Participant-initiated exchanges provide the renewal or recovery path, but the PPD service endpoint remains the source of truth for whether association is current, stale, or in a needs-reassociation state.
Local Recordkeeping: At a minimum, the architecture enables the household to know which PPD participants have acknowledged the current applicable policy. Deployment-specific responses to participants that do not acknowledge policy, or to devices that do not participate in PPD, are local management decisions and are outside the baseline signaling function defined here.

Association State and Freshness This architecture treats the PPD service endpoint as the source of truth for participant association state. A participant establishes association when it retrieves and acknowledges a specific applicable effective policy instance. Current association exists only when both of the following are true:

the acknowledged policy instance still corresponds to the latest applicable effective policy for that participant; and
the association remains fresh according to the renewal model enforced by the PPD service endpoint.

If the applicable effective policy instance is unchanged but the freshness interval expires before renewal, the participant enters stale association. If the applicable effective policy changes, if participant state relevant to effective policy derivation changes, or if enough state is lost that the prior association can no longer be trusted, the participant enters a needs-reassociation state. In either case, the participant no longer has current association. Participant-initiated exchanges provide the renewal or recovery path, but they are not the source of truth for whether association is current. The PPD service endpoint determines whether a participant is current, stale, or in needs reassociation.

Discovery and Policy-Authority Boundary This architecture separates discovery of a participant-facing service endpoint from trust establishment. A participant may learn one or more candidate PPD service endpoints through configuration or local network mechanisms, but discovery alone does not make any candidate authoritative. Before treating a policy instance as authoritative, the participant needs the applicable protocol profile to authenticate the selected endpoint and confirm that it is authorized to present policy for the household context. The participant-facing contract is the PPD service endpoint, not direct access to the policy authority. A deployment may place storage, policy combination, and effective policy derivation behind that service. When the PPD service endpoint and policy authority are distinct, the deployment needs to preserve at least:

authenticity of the effective policy instance presented to the participant;
integrity of policy-instance identifiers and association-freshness metadata;
an unambiguous binding between the selected PPD service endpoint and the policy authority on whose behalf it presents policy.

These are architectural invariants. The companion protocol specification document, , defines the participant-facing transport, metadata confirmation, and security-profile expectations, while deployment profiles still choose concrete mechanism details.

Key Components User Interface: A user-friendly interface (e.g., mobile app, web portal) for creating and managing privacy preferences. PPD Service Endpoint: A participant-facing service through which PPD participants discover, retrieve, and acknowledge applicable policy instances. In a common home deployment model, this service is hosted by a residential gateway or equivalent home-network service. A participant may learn candidate PPD service endpoints through configuration or local network discovery, but it treats a selected endpoint as authoritative only after the applicable trust mechanism succeeds. Policy Authority: The authoritative source of household policy state and any inputs used for effective policy derivation. The policy authority may be local or remote. A PPD service endpoint can obtain policy from a policy authority without exposing internal storage or computation topology to participants. Participants are not required to discover or communicate with the policy authority directly in the baseline architecture. Effective Policy Derivation: The logical function, performed by or on behalf of the policy authority, that determines the applicable policy instance for a participant. Participant Declarations and Consent Requests: Optional participant inputs that can disclose data-handling declarations or request consent for uses not covered by baseline policy. These inputs are distinct from the minimal path of policy retrieval and policy acknowledgment. Where a deployment exposes a coarse comparison result for participant declarations at the protocol boundary, that result belongs on the declaration path rather than in the effective policy or policy acknowledgment objects. That comparison surface is diagnostic only; it is not a baseline negotiation channel, policy-relaxation mechanism, or homeowner-prompt path. Recordkeeping and Management Mechanisms: Deployment-specific mechanisms for presenting association state, participant status, effective policy views, and network-observed devices to the household. Such mechanisms are not device-behavior requirements in the baseline PPD architecture.

Data Flows This section outlines the high-level data interactions between users, PPD participants, the PPD service endpoint, and the policy authority in the Privacy Preference Declaration (PPD) framework. It describes how privacy preferences are defined by users, made available to participants, and used as the basis for signaling and recordkeeping in a home network environment. The process begins when a user defines a set of privacy preferences that apply to their household. These preferences may express rules such as which types of data may be collected, under what conditions data may be processed or shared, or which retention practices are acceptable. The design of the user interface used to author these preferences, including its presentation, usability, or input modalities, is out of scope for this document, and will be addressed separately. Likewise, the underlying vocabulary and structure of the privacy preferences, including the core fields used in atomic privacy-relevant dataflows and the associated qualifier families, are specified in . Once created, the user's preferences are maintained by a policy authority, which may reside locally on a networked controller or be accessible through other trusted infrastructure. The policy authority may include storage, effective policy derivation, or both. When a new device joins the home network, it initiates an onboarding process during which it obtains one or more candidate PPD service endpoints through configuration or local network mechanisms. Discovery identifies reachable candidates, but does not by itself establish that any candidate is authoritative for household policy. The participant then establishes a secure channel to a selected endpoint and authenticates that endpoint according to the applicable protocol profile before retrieving policy. Following onboarding, the PPD participant performs association, which involves retrieving the household privacy policy and acknowledging receipt of the applicable policy instance. In some deployments, the participant is a backend service associated with the device rather than the local device itself. The PPD service endpoint may present policy derived from a local or remote policy authority without exposing that internal topology to the participant. The participant-facing contract ends at the PPD service endpoint; any split between that service and the policy authority is internal to the deployment. Where those components are distinct, the deployment preserves the authenticity and integrity of the effective policy instance, policy-instance identifier, and freshness metadata presented through the service endpoint. Devices may optionally report their data handling declarations to the PPD service endpoint at this stage. The PPD service endpoint also determines a freshness interval or renewal deadline for the resulting association state. If a device seeks to perform actions not permitted under the baseline policy, for example, collecting or sharing data beyond what the user has authorized, it may initiate a consent request workflow. However, the design and behavior of this consent mechanism is explicitly out of scope for this document. Inappropriate or poorly designed consent flows, such as those that involve excessive prompting, ambiguous language, or misleading options, can inadvertently pressure users into accepting data practices that conflict with their preferences. Even without malicious intent, these experiences may degrade trust and lead to outcomes inconsistent with user expectations. Future specifications should describe consent interactions that are clear, proportionate, and respectful, helping users make informed decisions without friction or fatigue. Current association is not indefinite. If the participant does not renew before the freshness interval expires, the PPD service endpoint treats the association as stale even if the applicable effective policy instance is unchanged. Reassociation is required when current association can no longer be confirmed for a participant. This can occur because the applicable effective policy changed, because participant state relevant to effective policy derivation changed, because the association became stale, or because enough state was lost that the prior association can no longer be trusted. Reassociation re-establishes current association by retrieving and acknowledging the latest applicable effective policy instance, or by completing a renewal procedure defined by the applicable protocol profile when the policy instance is unchanged. Devices are not expected to re-collect consent for data uses already covered by existing, valid consent. To support straightforward implementation and debugging, the companion protocol specification document, , defines a simple machine-readable representation for privacy policies, declarations, and acknowledgment state. JSON is a practical baseline encoding for the architecture and for many constrained home-network deployments. More compact encodings can be considered later if a specific deployment profile demonstrates a need for them. The companion protocol specification document, , defines how association freshness is conveyed, including whether the protocol uses bounded renewal intervals, explicit renewal deadlines, or equivalent lease-style semantics. It also distinguishes stale association from needs-reassociation states caused by policy or participant-state changes. It is important to note that the baseline requirement under this architecture is limited to discovery, retrieval, acknowledgment, and any renewal needed to maintain current association for the user's privacy policy. These actions provide a signaling and recordkeeping mechanism for establishing that the current applicable policy was made available to the participant. However, this document does not define how device behavior is changed by the policy, nor does it specify how to handle cases where a device cannot fully satisfy a given policy. These aspects, including optional status reporting, detailed conflict-resolution procedures, or auditing, may be addressed in future work. Finally, while this document defines the overall data flow and interaction sequence, it does not define message formats, communication protocol details, or consent interface specifications. The companion protocol specification document, , specifies the participant-facing message formats and protocol details. Consent interface specifications, if any, remain future work.

Non-PPD and Network-Observed Devices Home networks commonly include devices that do not implement PPD, cannot be updated to implement PPD, or are visible only through local network observation. The architecture treats these devices as expected operational cases rather than exceptional failures. A local management function can classify such devices as network-observed or unmanaged based on information available within the home network. That classification can improve household transparency by showing that a device is present even though it has not established association through PPD. Network observation does not create association, does not imply that the device has received a household policy, and does not imply anything about the device's behavior. Any local response to unmanaged devices, such as notification, inventory display, or other network management action, is a deployment decision outside the baseline PPD signaling architecture.

Policy Language The specific details of the privacy policy language, including its syntax, structure, and extensibility mechanisms, are out of scope for this document. The policy vocabulary and taxonomy of privacy concepts and attributes are defined in , including the compact identifier model, the shared computable semantic floor, extension namespaces, and the mapping expectations used by the companion protocol specification.

Language Requirements

Human-readable: Policies should be easily understandable by users.
Machine-readable: Policies should be machine-processable for automated interpretation and signaling.
Extensible: The language should be flexible enough to accommodate evolving privacy needs and technologies.
Internationalization-compatible: Policies and identifiers used within them may need to support multilingual environments and non-ASCII characters.

To ensure consistent interpretation and comparison of string-based policy elements, such as device names, labels, or category identifier string handling practices should align with the guidelines defined in . This is particularly important when identifiers or user-facing labels are created, stored, or matched across vendors or systems that operate in different locales or character encodings.

Architectural Direction The architecture assumes a policy representation that is both machine-readable and suitable for user-facing explanation. The taxonomy document is expected to define the semantic vocabulary, while a companion protocol document is expected to define any wire-format or serialization profile needed for exchange. Future specifications should also define how string identifiers--such as device roles, policy tags, or consent status labels--are formatted, compared, and stored, so implementations avoid ambiguous matching behavior. In contexts where internationalized strings are involved, alignment with should be considered to ensure interoperability and consistency.

Future Work This document defines an architectural framework for enabling users to express privacy preferences and signal those preferences within home network environments. Several aspects critical to a fully operational implementation are intentionally left out of scope here and are expected to be addressed in future specifications or companion documents.

Policy Taxonomy and Semantics defines:

A common vocabulary and set of core fields for expressing atomic privacy-relevant dataflows.
Attributes and semantics for data types, purposes, actions, sources, destinations, and qualifier families used in those dataflows.
An extensibility model that allows richer vocabularies while preserving a shared computable semantic floor.

This taxonomy is foundational for consistent policy interpretation across heterogeneous devices and vendors.

Protocol Specification and Message Formats The companion protocol specification document, , defines:

Message formats for participant registration, optional participant declaration, policy retrieval, policy acknowledgment, renewal, and reassociation.
Discovery profiles, lightweight metadata confirmation, and trust-establishment bindings for PPD service endpoints.
Transport-layer considerations, service authentication, and policy-authority trust expectations.
Association freshness semantics, including how renewal intervals or deadlines are conveyed and how stale association is distinguished from needs-reassociation states.
Baseline encoding expectations for structured data, with JSON as a practical starting point and more compact encodings reserved for deployment profiles that need them.

Consent Request Workflow Design Specifications The mechanism by which devices request additional user consent for data uses not covered by the baseline policy is out of scope. However, future specifications should:

Define clear constraints to prevent manipulative or fatiguing consent flows (e.g., dark patterns).
Describe consent interactions that are transparent, infrequent, proportionate, and user-respecting.
Explore user interface standards or API affordances to preserve meaningful choice.

This is a particularly sensitive area and must balance user experience, privacy expectations, and implementation feasibility.

Recordkeeping and Local Management This architecture does not define how devices act on privacy policies or how departures from policy are detected or remediated. The baseline function is signaling: a participant can receive an applicable household policy and acknowledge that policy instance. Future work may include:

Optional participant status reporting models and device-side implementation expectations.
Recordkeeping mechanisms for correlating policy delivery and acknowledgment records.
State models that distinguish current, stale, and needs-reassociation participant status.
Deconfliction strategies for devices unable to meet all user-defined constraints.
Deployment-local management options, such as notifications or inventory display.

User Interface Design Specifications The user-facing interface used to author, modify, and review privacy preferences is out of scope. Future design guidance may address:

User experience design principles for presenting privacy concepts clearly and accessibly.
Models for progressive disclosure of policy impact.
Multi-user and household-role-specific control models (e.g., parental vs. administrative roles).

Interoperability Testing and Reference Implementations Future work may also include:

Development of reference implementations of the PPD protocol, PPD service endpoint, and policy-authority components.
Interoperability testing across devices and vendors.
Conformance guidelines and self-certification procedures.

IANA Considerations This document has no IANA actions.

Internationalization Considerations In contexts where privacy preferences or taxonomy elements involve user-facing or vendor-defined string identifiers, additional work may be required to:

Define string normalization and comparison rules, particularly for internationalized text.
Support identifier consistency across diverse vendors and locales.
Consider alignment with for handling Unicode-aware identifiers in a secure and interoperable way.

Security Considerations For a privacy framework to be effective, it needs to support the expression of user preferences and protect those preferences during transmission, retrieval, and acknowledgment. This section outlines safeguards for confidentiality, authenticity, integrity, and metadata minimization during PPD operations.

Secure Policy Dissemination Communication between PPD participants and the PPD service endpoint needs protection against unauthorized access and tampering. When the PPD service endpoint and policy authority are distinct, deployments also need to preserve policy authenticity and integrity across that boundary. Discovery mechanisms can identify candidate PPD service endpoints, but discovery alone is not sufficient to establish that an endpoint is authorized to present household policy. The companion protocol specification document, , defines explicit participant-facing security profiles and the accountability properties they need to provide. Future deployment profiles still need to identify concrete cryptographic mechanisms, such as encryption and mutual authentication, so that legitimate participants can retrieve privacy policies and detect modification. Those deployment profiles also need to protect the binding between the authenticated participant-facing service endpoint and the policy state it presents.

Anonymity and Metadata Protection Even when privacy policies themselves do not contain sensitive personal information, the act of retrieving or acknowledging a policy can reveal characteristics about the household, such as the types of devices in use, specific user preferences, or behavioral patterns over time. cautions against protocol designs that expose unnecessary metadata, treating the accumulation of such information as a legitimate technical threat. This framework takes that warning seriously: metadata exposure during policy retrieval and device onboarding needs to be minimized to avoid turning privacy infrastructure into a new source of privacy leakage. Concepts from may help inform this effort. introduces techniques for authorization without identification, enabling a client to prove it is authorized without revealing who it is. While is optimized for pseudonymous web authentication over the public internet and assumes a centralized token issuer model, its core ideas, particularly around unlinkable token presentation, could be adapted to the PPD protocol to reduce metadata correlation and minimize household identifiability during policy exchanges. However, this needs careful analysis, as the assumptions of do not fully align with the goals or context of a local, user-governed home network.

Policy Integrity Devices need assurance that the policy retrieved is authentic and unaltered. Integrity protections, such as digital signatures, are necessary to ensure that users' preferences cannot be tampered with in transit or at rest by other devices, malicious actors, or misconfigurations. If policy is obtained through a participant-facing service from a distinct policy authority, integrity protections also need to cover the policy-instance identifier and any freshness metadata presented through that service.

Device Authentication Devices participating in the privacy framework need an authentication model before accessing the PPD service endpoint. This limits policy dissemination to known, authorized participants and helps users maintain trust in the integrity of their home network's privacy relationships. If the PPD service endpoint and policy authority are distinct, the deployment also needs a way to preserve the authenticity of policy state presented through the participant-facing service. By aligning with the concerns raised in and incorporating ideas from where appropriate, this framework seeks to protect users not only from overt data collection, but also from silent inference and passive metadata surveillance. At the same time, it avoids treating anonymity as an end in itself. The goal is to support privacy with recordkeeping, where user-defined preferences are signaled consistently, devices are identifiable only as much as necessary for the exchange, and the user retains visibility into what occurs within their domain.

Policy Acknowledgment and Recordkeeping PPD participants need a way to acknowledge receipt of the applicable privacy policy instance. This acknowledgment should be recorded and verifiable so that the household can determine which participants have seen the current policy. The record needs to bind the participant identity, the acknowledged policy instance, and the time or sequence context in which the acknowledgment was made. For devices that rely on a backend service, the record also needs to distinguish between acknowledgment by the local device and acknowledgment by the backend service acting on behalf of that device. This record is important because it creates a reciprocal acknowledgment path. In many current deployments, the household user is asked to acknowledge device or vendor policy terms, but there is no comparably strong household-controlled record that the participant was presented with the household's own privacy policy. An authenticated and integrity-protected acknowledgment record allows the household to show that presentation and acknowledgment occurred, which can support later accountability or review even when the architecture does not define automated enforcement. The companion protocol specification document, , defines baseline acknowledgment semantics and the protection properties acknowledgment mechanisms need to provide. Future deployment profiles still need concrete mechanisms that remain practical for constrained home-network devices. At minimum, the selected mechanism needs to provide:

participant authentication sufficient to bind the acknowledgment to the device or backend service that made it;
policy-instance integrity so that the acknowledged policy can be identified unambiguously;
freshness or sequencing so that an old acknowledgment cannot be replayed as evidence of current association;
verifiability sufficient for the acknowledgment record to function as a protected receipt of policy presentation and acknowledgment; and
a way to retain or export the acknowledgment record without exposing more household metadata than necessary.

A policy acknowledgment is not, by itself, an assertion about subsequent device behavior. Any local response to non-participation or other local observations is outside the baseline signaling mechanism defined by this architecture.