Martin Pál

Hi Erik, Thank you for the detailed post. We are working on providing more information. For now, I'll just say that per our recent [update](https://developer.chrome.com/docs/privacy-sandbox/attribution-reporting/summary-reports/#aggregation-service), our initial implementation will support...

Yes, this is AWS Nitro. FYI, we have just published instructions, scripts and binaries needed for running the aggregation service (both locally in untrusted mode and in the cloud in...

Thank you Charlie for responding, and thank you Alois for the question. Agree that a feature like this seems like a win in usability and utility, with no apparent downside...

Just to be clear: the reason we're porposing to round the timestamp to a day boundary is to limit the amount of entropy revealed. If you accept the premise that...

Hi Erik, thank you for your thoughtful comments. On your Option 1, I see a benefit to keeping a separation between the party that holds the key and the party...

Agreed. As you describe, a configuration with two or more Coordinators each holding a part of the key would be resilient to a single Coordinator attack.

FWIW, to me, (3) also seems the easiest choice from the API designer's perspective. It would be up to the adtech to encode the domain/URL/whatever they need using one or...