这是indexloc提供的服务,不要输入任何密码
Skip to content

Addressing use cases with “subsets” #96

@helenyc

Description

@helenyc

[Note: This issue is related to the changes proposed in PR #91 and summarized on issue #92]

The updated First-Party Sets proposal uses “subsets” to correlate different domains added to a set to map to a defined use case.

The previous First-Party Sets proposal required that all domains that were added to a set needed to have a common privacy policy, and common brand, and common ownership. We received feedback from the ecosystem that this joining of all of these different characteristics did not support certain use cases well. For example, a domain may have a more restrictive privacy policy for a domain that is targeted to children, or may have a different policy depending on the regulatory concerns in the country where the company is operating.

The new approach ensures that user privacy is thus met by accommodating the different use cases that a multi-domain entity may have. We have introduced the “subset” approach to design rules for the different use cases in each subset.

Does the “subsets” approach to FPS meet all intended use cases? Where are the limitations?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions