Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does "batch disjointness" offer enough flexibility? #331

Open
palenica opened this issue Feb 16, 2022 · 3 comments
Open

Does "batch disjointness" offer enough flexibility? #331

palenica opened this issue Feb 16, 2022 · 3 comments
Labels
possible-future-enhancement Feature request with no current decision on adoption

Comments

@palenica
Copy link
Collaborator

Is there interest in exploring support for differentially private querying schemes that allow multiple passes over data?

@csharrison csharrison added the possible-future-enhancement Feature request with no current decision on adoption label Jun 26, 2023
@keke123
Copy link

keke123 commented Jul 14, 2023

To ensure our solution is privacy preserving we do not allow reprocessing of reports. This is the current implementation of our privacy budget mechanism. We heard feedback that allowing the same report to be processed multiple times would be useful for certain use-cases (e.g. #732), and exploring options to enable it. If there are additional use cases, we would appreciate learning about them.

Thank you!

@alois-bissuel
Copy link
Contributor

Multiple passes over the data has the interesting property of recovering from failures.
An adtech (or any user of the aggregation service) might make some mistakes when calling the service (eg calling the service with the wrong keys or dataset).
With multiple passes, there is a chance of recovering some of the data which might have otherwise been lost.

@wualbert17
Copy link

FYI, the Aggregation Service team is currently looking into supporting requerying, which could help with this use case. If you're interested, please take a look at privacysandbox/aggregation-service#71.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible-future-enhancement Feature request with no current decision on adoption
Projects
None yet
Development

No branches or pull requests

5 participants