Skip to content

Commit 04cae6d

Browse files
authored
Update explainers for fenced frame privateAggregationConfig restrictions. (#154)
1 parent a53a027 commit 04cae6d

File tree

2 files changed

+5
-7
lines changed

2 files changed

+5
-7
lines changed

flexible_filtering.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -201,7 +201,8 @@ We do not currently plan to allow the filtering ID bit size to be configured for
201201
Protected Audience bidders as these flows require context IDs to make the scale
202202
practical; we do not currently plan to expose context IDs to bidders (see the
203203
[explainer](https://github.com/patcg-individual-drafts/private-aggregation-api/blob/main/report_verification.md#specifying-a-contextual-id-and-each-possible-ig-owner)
204-
for more discussion).
204+
for more discussion). We also do not plan on allowing these fields to be set
205+
from within fenced frames, as they may have access to cross-site information.
205206

206207
#### Backwards compatibility
207208

@@ -301,8 +302,6 @@ to the potential for a large number of null reports, see
301302
[explainer](https://github.com/patcg-individual-drafts/private-aggregation-api/blob/main/report_verification.md#specifying-a-contextual-id-and-each-possible-ig-owner)
302303
for more discussion. Identical considerations would apply to this batching ID in
303304
the `shared_info`; so, we would not allow a batching ID to be set for bidders.
304-
Note that Protected Audience auction winners could still report using Shared
305-
Storage in the rendering (fenced) frame.
306305

307306
#### Backwards compatibility
308307

report_verification.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -525,10 +525,9 @@ significant design and exploration.
525525
## Shared Storage in Fenced Frames
526526

527527
When a shared storage operation is run from a fenced frame instead of a
528-
document, we can’t simply set a contextual ID. Winning ads of FLEDGE auctions
529-
are required to be _k_-anonymous and can’t communicate with their embedder. So,
530-
any high entropy contextual ID could not be joined to information outside the
531-
Fenced Frame.
528+
document, we can no longer set a contextual ID. Any cross-site information the
529+
fenced frame has could be embedded in the context ID, so the ability to set it
530+
is disabled.
532531

533532
Instead, we propose allowing a Private State Token to be bound to the
534533
FencedFrameConfig output of a FLEDGE auction. We would reuse the FLEDGE bidder

0 commit comments

Comments
 (0)