Privacy
Send only the context needed for a placement. Keep consent controls explicit and raw prompts out of requests to advertising partners.
Send a privacy-bounded placement request
Send a topic object when you need matching context, and keep prompt_shared false when raw prompt text must not enter the targeting path. For wavebird_consent projects, first record the actual session decision through /v1/consent. The example assumes that permission is current; its flags cannot grant it. Preserve observed Sec-GPC across backend hops.
Create a privacy-bounded placement
privacy.sh
bash
Default privacy posture
Minimal signal egress
Standard SSP request builders project permitted signal fields, such as topic category and language. This does not cover separate model requests, custom adapters or application logs.
Consent-bounded relevance
Semantic relevance must remain bounded by the active consent profile and the current jurisdiction mode.
No model influence
The ad path remains separate from model I/O. Sponsored delivery does not rewrite prompts or influence outputs.
Apply the controls in your integration
Browser teams should read privacy in terms of activation, consent storage, and render-time config. Backend teams should read privacy in terms of the request fields they choose to send into placement creation. The advanced SDK does not change those boundaries.
Need help with your integration?
Share the affected endpoint, request ID, and the behavior you expected. Leave out keys and user content.