Safety

In the recommended setup, wavebird runs as a sidecar and does not need raw prompt text, conversation history, or user identifiers. See the data firewall.

Semantic relevance targeting is opt-in via explicit consent and CS profiles defined by Compute Sponsoring.

Semantic targeting (topic-based relevance) is only allowed with explicit user consent. In Compute Sponsoring terms, that is the boundary between CS-S and CS-N.

Your app owns the consent UX. The API carries your flags; wavebird enforces them. See Compute Sponsoring.

If the sponsoring path cannot validate a request, it stops. The model response still returns; the ad slot becomes a no-fill.

Sponsors do not write into the prompt, context window, tool inputs, or model selection. The model output is produced without sponsor metadata.

If you choose to render a creative inside the model context, that is an explicit product decision; the API integration keeps ads out of model I/O unless you intentionally wire them in.

You control format, industry blocking, and category sharing through your API configuration.

Rules are enforced before any auction request is sent.

Filled slots generate signed proof events that can be reconciled in settlement.

For the proof evidence pack and benchmark results, see Engineering evidence.

wavebird implements Compute Sponsoring v1.0. The current rollout uses the standard's situational, no-persistence path documented there.