What is public about a personalized page
Unserved arms stay out of the page, but the audience rules themselves ship to the browser whenever the client runtime is switched on.
Three separate things could in principle be public here: the content someone else was served, the fact that this visitor was classified, and the definitions of the segments themselves. They have three different answers, and only the first one is reliably private.
Content a visitor was not served stays out of their page
Stripping the arms a visitor wasn't served happens as the very last step before the page crosses to the browser — after everything else has been assembled, so nothing downstream can put a losing arm back. Structured data is built from that same served document rather than the stored one, so it can't leak another arm's copy either. This is a deliberate fix for a real earlier leak: arm selection was already server-side then, but the losing arms travelled with the page and were readable in view-source anyway.
What the page tags: two ids, and nothing more
Every page carries a visitor id tag, and a page resolved for a non-default audience adds a second tag naming that audience's id. Both sit in <head>, readable by anyone who views source. They are raw ids, not names — you'd need admin access to turn one into the other. Nothing tags the experiment or variant a visitor landed in.
What the client runtime ships: the audiences themselves
If your site has the client runtime switched on — it’s off by default, and on wherever you use the transparency panel, the self-ID widget or in-page re-evaluation, which is what it powers alongside the transparency panel — then the page hands the browser the list of active audiences so the runtime can re-evaluate them there. That list is not a set of ids. It's the audiences as you authored them.
Older pages may still carry every arm
Pruning covers the variant containers you can create today. It does not cover the older variant-container module that shipped before 0.13.0, which works the opposite way by design: it writes every arm's markup into the page and hides the losing ones with CSS, so a client-side script can reveal the right one. Those placements are left rendering on purpose rather than broken, so any page that still holds one is still shipping all its arms in view-source. The CLI's kywi upgrade:variant-containers reports where they are, and converts them with --apply.
The transparency panel is the opt-in, visitor-facing version of the same audience information — this page describes what's in the page whether or not anyone looks; the panel is the surface a visitor can act on.