Privacy
The API docs treat privacy as a runtime boundary, not a footnote. The public surface is designed so browser and server integrations can use minimized delivery signals instead of leaking raw model inputs to the configured ad path.
Recommended
Default privacy posture
Minimal signal egress
The default path sends only a narrowed delivery signal such as topic category and language, not raw prompt text.
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.
API-first reading
What the docs now assume
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 job creation. The advanced SDK does not change those boundaries.
Need rollout review?
Start in the dashboard, choose Script Tag or Server API, and use contact only when you need rollout review, enterprise coordination, or non-standard integration help. Billing beacon rules live in the API concepts guide.