How does wavebird protect your app?
Your product. Your boundaries. Understand who supplies the ads, what data is used and how you stay in control.
Where does my app fit in the advertising market?
Your app is the publisher: you provide the experience and choose where advertising belongs. wavebird connects those placements to established advertising networks and global advertiser demand, so you do not need your own advertiser sales operation.
As the intermediary, wavebird serves both sides: your product rules protect the user experience; advertiser requirements govern where campaigns can run. An ad needs to meet both.
The experience, placements and product rules.
Checks, matching and delivery between both sides.
Campaigns, budgets and advertiser requirements.
How do suitable advertisers reach my app?
Matching combines permitted context, language and placement information with your restrictions and available demand. Safety checks restrict unsuitable contexts; category and domain rules narrow which ads can be considered.
Exclude whole industries.
Block categories that do not belong in your product, such as gambling or adult content.
Block specific domains.
Exclude an advertiser by its landing domain without blocking the entire category.
Choose the placement and format.
Set where ads appear and which formats are allowed. Keep particular plans or surfaces ad-free.
For example, a travel app can permit travel-related advertising while excluding gambling and a competing booking domain. These are selection rules, not a reservation for a particular brand. Available campaigns still determine which eligible ad is returned.
What does the data firewall let through?
The firewall separates the context used inside wavebird from the request sent to an advertising partner. Your app can supply a broad topic directly. If you explicitly enable permitted prompt classification, wavebird reduces that input to abstract matching signals before partner delivery.
Separate ad request
A topic, or optional prompt classification with permission.
- Consent & project rules
- Safety & permitted fields
- No raw prompt forwarded
Topic and language, plus allowed placement, technical and privacy fields.
Raw prompts, conversation history, account records and model output are excluded from the partner ad-matching request. Permitted technical, placement and privacy fields are checked separately; they are not automatically anonymous.
Who asks the user for consent?
Your app presents the required choices and passes them to wavebird. You can connect your consent manager or use the supported consent widget. Prompt-derived ad relevance requires an explicit user choice; without it, that context is not used.
Explain the choices, collect them and communicate changes, including withdrawal.
Validate the supplied signals against project and delivery rules before using them.
See a clear ad label and retain access to the privacy and consent controls you provide.
A consent flag carries a decision; it does not replace your privacy notice or the consent requirements for your integration. If another permitted ad path is available it can be used; otherwise the placement remains empty.
Can advertising change or interrupt the AI result?
The model call and ad request run on separate paths. Advertiser information stays out of prompts, model context, tool inputs and model selection. Render the ad in its own labeled slot, not inside the answer or generated asset.
If required consent is absent, a safety check fails or the ad request times out, no ad is shown for that opportunity. Your integration keeps the AI task running and handles an empty placement without blocking the result.
What does a European base mean for my app?
wavebird is built in Europe, with its infrastructure hosted in Nuremberg, Germany. You get a European infrastructure provider and access to global advertising demand. Your advertising reach is not limited to Europe.
Hosting and advertising delivery are different boundaries: permitted ad-request fields may reach international advertising partners. The privacy notice, processing agreement and subprocessor list describe the applicable data handling.
How can I check what was delivered?
A returned ad is a delivery decision. Render and interaction events are checked separately before they support measurement and billing. Signed evidence connects the recorded delivery to its events, making that chain reviewable.
Use the decision state and validation results to distinguish an available ad, an empty placement and a measured event. This protects publishers and advertisers from treating every ad request as a billable view.
Why is wavebird working on Compute Sponsoring?
Compute Sponsoring addresses trust on both sides: users and advertisers should be able to understand how advertising is separated from generation. The September 2026 paper links an ad exposure to an identifiable compute unit so that this relationship can be examined at the process level. It proposes separation, data-sovereignty and consent principles.
No semantic relevance targeting.
Relevance within the current task or session.
Semantic history carried across sessions.
These categories describe the proposal, not a menu of enabled wavebird features. The current paper is by Christian Leinberger, September 2026. Mario von Bassen co-authored the earlier February 2026 version. This is a category proposal, not a technical specification or certification.
How do I start and add more control through the API?
Begin with one placement and your project rules. Your developer requests an ad, renders the returned placement and handles an empty result. The same approach can support chat, image, video, 3D and music experiences.
Set the boundaries.
Agree on formats, category and advertiser blocks, consent and ad-free areas before wiring the placement.
Connect the first surface.
Use the API and hosted renderer. Verify consent changes, delivery events and the no-ad outcome.
Extend the integration.
Add more surfaces and documented per-request controls as your product needs them. Keep project and platform restrictions in force.
Product and growth teams decide the experience. Developers implement those decisions through project configuration and the API; finance can review measured delivery and revenue.