Pillar
Privacy controls for sponsored GenAI
This pillar consolidates privacy-prompts and the underlying data-rule story into one canonical page. The main question is simple: what stays local, what goes to model providers, and what never becomes ad-market data.
The control model
Wavebird treats privacy as an operating boundary, not just a policy footer. Users and developers need to understand provider sharing, consent-gated measurement, local state, and the limits of the sponsorship layer.
That means privacy controls belong in product settings, disclosure copy, and architecture documentation at the same time.
What must stay explicit
A responsible sponsored GenAI product makes prompt handling, provider sharing, and optional telemetry easy to inspect. The product should not ask users to infer these rules from vague UI text.
- • What the model provider receives
- • What remains local to the app or browser
- • Which optional categories require consent
- • What the ad market never receives
Why this is a canonical pillar
The older privacy-prompts route described one slice of the same intent. This page is the broader canonical reference for privacy controls, data rules, and disclosure logic across the product.
It gives search systems and LLMs one clear destination for the privacy side of wavebird-web instead of splitting the meaning across multiple narrow terms.
How it connects back to wavebird.ai
The canonical definitions for wavebird, Compute Sponsoring, and the SDK remain on wavebird.ai. This page explains how those rules surface in the live product and user-facing app.
FAQ
Does the ad market receive prompt text?
No. Prompt handling and provider sharing are separate from the ad-market boundary. The product should make that distinction visible and enforce it technically.
Are privacy controls only a legal page topic?
No. They belong in settings, in-product disclosure, and architecture design, not only in the privacy policy.
What is the relationship to consent?
Consent governs optional categories such as non-essential measurement or stronger personalization. Necessary provider processing for answering the request is a separate product boundary.
Where are the deeper product definitions?
Use wavebird.ai for the canonical glossary and product definitions, and this domain for the live product interpretation of those rules.