Last updated: 2026-06-29

PulseAI is a Chrome extension that turns live-stream chat on Twitch and Kick into real-time analytics for streamers and viewers. This policy explains exactly what data PulseAI touches, what stays on your device, and what (only with your explicit opt-in) leaves it.

Summary

• All real-time analytics (chat velocity, mood, topics, questions, hype) are computed locally in your browser.
• By default, PulseAI operates no server that receives your data.
• Data leaves your device only if you turn on an optional AI feature (a self-hosted backend URL, or your own provider API key).
• Your API key is stored only on your device, is never logged, and is never sent anywhere except directly to your chosen AI provider.

What PulseAI reads

On twitch.tv and kick.com pages you open, PulseAI reads public live-chat messages (username + message text) to compute analytics. It does not read private messages, account details, payment information, or browsing activity on other sites. The content script runs only on Twitch and Kick.

What stays on your device

The following is stored locally via chrome.storage and is never uploaded:

• Settings, including your AI provider API key — chrome.storage.local.
• Recorded stream-session stats (duration, message counts, hype, mood, topics) used for the "Pulse City" visualization — chrome.storage.local.
• Pinned "Saved Moments", which include short chat transcripts (usernames + message text) you choose to save — chrome.storage.local.
• Transient metrics, insights, and UI state — chrome.storage.session (cleared when the browser session ends).

What leaves your device (opt-in only)

Data is transmitted only when you enable an AI feature:

1. Self-hosted backend (optional). If you set a backend URL in Settings, recent chat snippets — message text and usernames, capped to roughly the last 120 lines — are sent to that server, which you operate and control, for LLM summarization.
2. Bring-your-own-key / BYOK (optional). If you add your own OpenAI or Anthropic API key, recent chat snippets — message text and usernames — are sent directly from your browser to OpenAI or Anthropic using your key. This data is handled under those providers' privacy policies:
   • OpenAI: https://openai.com/policies/privacy-policy
   • Anthropic: https://www.anthropic.com/legal/privacy

PulseAI itself runs no intermediary server in the BYOK path; requests go straight to the provider.