Wrapper privacy-policy template
Use these clauses as a starting point in your own privacy policy. Replace the settings reference and adapt the text if your integration shares more than the standard Wavebird signal set.
Suggested privacy policy addition
privacy-template.txt
text
"Advertising and Monetization
We use wavebird (wavebird.ai) to display sponsored content within our application. When you interact with our app, the following information may be shared with wavebird for ad matching:
- Content topic category (e.g., \"technology\", \"travel\")
- Language preference
- Device type (desktop/mobile)
- Country (derived from IP address)
The following information is NOT shared:
- Your prompts or conversation text (unless you enable enhanced matching in our settings)
- Your name, email, or other personal identifiers
- Your conversation history
wavebird processes this information in accordance with their privacy policy at wavebird.ai/privacy. Ad matching occurs in real-time and no personal data is stored by the ad system.
You can control ad personalization through [your app's settings]."HTML version
privacy-template.html
html
<section aria-label="Advertising and monetization notice">
<h2>Advertising and Monetization</h2>
<p>We use wavebird (wavebird.ai) to display sponsored content within our application.</p>
<p>When you interact with our app, the following information may be shared with wavebird for ad matching:</p>
<ul>
<li>Content topic category (for example, "technology" or "travel")</li>
<li>Language preference</li>
<li>Device type (desktop or mobile)</li>
<li>Country (derived from IP address)</li>
</ul>
<p>The following information is not shared by default:</p>
<ul>
<li>Your prompts or conversation text, unless enhanced matching is enabled</li>
<li>Your name, email address, or other direct identifiers</li>
<li>Your conversation history</li>
</ul>
<p>wavebird processes this information in accordance with their privacy policy at wavebird.ai/privacy.</p>
<p>You can control ad personalization through your app settings.</p>
</section>Suggested text only. Wrappers remain responsible for the final wording of their own privacy notice and for reflecting any optional prompt-sharing or personalization settings they enable.
API first, Script Tag second, SDK third
These pages are the advanced package layer for teams that intentionally choose @csl/wrapper-sdk. Primary onboarding still lives in the API docs, and browser-first installs should start with the Script Tag. Use contact only when you want rollout review, enterprise coordination, or help with non-standard integration constraints. Beacon billing rules live in SDK Concepts.