Skip to main content
Embedding third-party JavaScript is a trust decision. This page lays out exactly what ChatAds stores and for how long, so you can update your own privacy policy accurately.

​
No Cookies, No Cross-Site Tracking

The widget sets no cookies and does not track visitors across sites. It keeps a small amount of state in the browser’s localStorage, scoped to your widget key:
  • The visitor’s chat session and message history (so a conversation survives a page reload)
  • Daily counters for the per-visitor message limit and your ad frequency cap
  • Whether the visitor opened the widget today (used when your team’s daily limit is reached)
Old entries clean themselves up automatically.

​
What Gets Sent to ChatAds

  • Chat messages the visitor types, plus the AI’s replies.
  • Page context - when page context is enabled (the default), the widget sends a stripped-down copy of the page’s structure and visible text once, the first time a visitor opens the chat, so the AI can answer questions about the article for the rest of the conversation. It is sent compressed, is size-capped, and is held on our servers for at most 24 hours. Scripts, styles, images, media, and anything typed into a form are never included.
  • Usage events - page loads, messages, and link clicks, aggregated per day for your usage charts.
  • Click events - for each inline link click: the page URL, anchor text, destination URL, whether the link was sponsored, country (an ISO code derived from IP; the raw IP is not stored in the click log), browser language, and chat session ID.
Visitor IPs are used server-side for rate limiting (per-visitor daily and per-minute limits) and to derive the country code for Amazon marketplace targeting.

​
Conversation Logs

  • Conversation logging is on by default and can be turned off any time from the Conversations tab; new messages stop being stored immediately.
  • Visitor messages are PII-stripped before storage: emails, phone numbers, and similar identifiers are removed.
  • Transcripts are visible only to your team in the dashboard (and via your own MCP Data Connector key).
If your site covers sensitive topics (health, medical, financial), consider turning conversation logging off from the Conversations tab. PII stripping removes identifiers like emails and phone numbers, but not the free-text content itself, so visitors may type sensitive details into the chat that would otherwise be stored verbatim.

​
Retention

Export CSVs from the dashboard before the 90-day window if you want to keep transcripts or click logs long-term. For your own account data (as a ChatAds user, not a reader), GDPR-style export and deletion controls are on the Account page, with team-level equivalents on the Team page.

​
Visitor Erasure Requests

If a visitor asks you to erase a conversation they had with your widget, forward the request to team@getchatads.com and we will delete the matching transcript and click-log rows within the 90-day retention window. Include any details that help us locate the conversation, such as the approximate date and the page it happened on. Transcripts and click logs are deleted automatically 90 days after they are recorded regardless.

​
What Your Privacy Policy Should Mention

If you embed ChatAds, we recommend your privacy policy discloses that:
  1. An AI chat assistant is provided by a third party (ChatAds), and questions typed into it are processed by ChatAds and its AI provider to generate answers.
  2. Chat transcripts may be retained for up to 90 days.
  3. Chat replies may contain affiliate links (see Affiliate Disclosure).
The widget itself also displays “Links may include affiliate offers” in its footer at all times.
This page describes how the product behaves; it isn’t legal advice. For data processing agreements or region-specific compliance questions, contact us.