Security Considerations

We understand that the data used to generate ads — particularly full chat histories — may contain sensitive, private, or proprietary information.

This page outlines how we protect your data and what guarantees we provide.

Our system is designed to process data temporarily, strictly for the purpose of generating contextual ads.

We guarantee:

• ✅ No data is stored — chat histories, page content, user IDs, and conversations are not stored in any database after the ad is generated.
• ✅ No data is shared — we do not and will never share any content you send with third parties.
• ✅ Single-use processing — chat or page data is processed in memory during the API call and discarded immediately after the response is sent.
• ✅ No tracking — we do not fingerprint or track users through the SDK or API.
• ✅ No ad-related user profiling — we do not build user profiles or persistent logs of conversations.

• All API endpoints are served over HTTPS (TLS 1.2+)
• All SDKs use secure HTTP clients and verify SSL by default
• You should always transmit your `apiKey` and `apiId` securely

• `apiKey` is secret — never expose it in public frontend code
• Use environment variables or server-side proxies when possible
• Regenerate your API key immediately if a leak is suspected

• The Go SDK handles secrets safely in backend environments
• The JavaScript SDK requires only non-sensitive user/session info in the browser
• The React SDK supports declarative security — your API keys can be passed from backend

Our infrastructure and API design comply with privacy-first principles:

• 🛡️ GDPR-Friendly
• 🧩 No cookies or persistent identifiers
• 🧼 Stateless API — all context must be passed in each call

Your chat and page content are used only to determine the most relevant ad.

They are:

• Never stored
• Never reused
• Never shared
• Never profiled

• Getting Started
• API Reference
• Use Cases
• SDKs