[proposals] Aggregate measurement with the Private Aggregation API (#13)

alexmturner has just created a new issue for https://github.com/patcg/proposals:

== Aggregate measurement with the Private Aggregation API ==
**Problem**
Browsers are now working to prevent cross-site user tracking, including by partitioning storage and removing third-party cookies. There are a range of API proposals to continue supporting legitimate use cases in a way that respects user privacy. Many of these proposals, including [Shared Storage](https://github.com/pythagoraskitty/shared-storage) and [TURTLEDOVE](https://github.com/WICG/turtledove), plan to isolate potentially identifying cross-site data in special contexts, which ensures that the data cannot escape the user agent.

Relative to cross-site data from each user, aggregate, noisy data can leak less information about individual users, and yet would be sufficient for a wide range of use cases that rely on third-party cookies today (e.g. [reach measurement](https://github.com/patcg/meetings/issues/12)).

**Proposal summary**
This API proposal introduces a generic mechanism for measuring aggregate, cross-site data in a privacy-preserving manner. In particular, this would be available in isolated contexts that have access to cross-site data (such as a Shared Storage worklet).

The potentially identifying cross-site data is encapsulated into ‘aggregatable reports’. To prevent leakage, this data is encrypted, ensuring it can only be processed by an aggregation service (e.g. [this proposal](https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATION_SERVICE_TEE.md)) that will aggregate the reports, add noise and limit how many queries can be performed. This service was originally proposed for use by the [Attribution Reporting API](https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATE.md), but allowing more general aggregation would support additional use cases.

**Explainer**
More detail about the proposal is available in an [explainer](https://github.com/alexmturner/private-aggregation-api). I’d be happy to move this explainer to the PATCG Individual Drafts org (once I have the necessary permissions).

Please view or discuss this issue at https://github.com/patcg/proposals/issues/13 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 4 May 2022 15:23:24 UTC