Privacy Policy

StreamPulse is built privacy-first. It works as an executive producer for your channel: it reads your analytics, turns them into decisions, and keeps as little of your data as possible, for as short a time as possible.

• We never sell, rent or broker creator data. Your data is not shared with advertisers or data brokers, and it is not used for advertising.
• We only read. StreamPulse cannot upload, edit, delete or publish anything on your YouTube or Twitch accounts.
• We don't keep a database of your channel. Your analytics are fetched when you open the Studio and used to build that view, not stored.

StreamPulse only accesses a platform after you choose to connect it, and only with read-only permissions.

• YouTube Data API and YouTube Analytics API (scopes youtube.readonly and yt-analytics.readonly): your channel profile, your videos and their metadata (titles, descriptions, chapters, publish and scheduled dates), and channel and per-video analytics such as views, watch time, audience retention and traffic sources. This data is used solely to produce your view corridors, retention curves, cadence heatmaps, traffic-source audits, clip suggestions and Copilot answers inside StreamPulse.
• Twitch Helix API (scope user:read:broadcast, plus public channel data): your channel profile, broadcast history and past broadcasts, clips, and viewer pacing for your streams. This data is used solely for broadcast analysis, clip suggestions and release-day planning inside StreamPulse.

StreamPulse's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. StreamPulse uses YouTube API Services; by connecting YouTube you also agree to be bound by the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy.

We do not access your email inbox, contacts, payment details, private messages or any data from accounts you haven't connected.

• No server-side database of your analytics. Channel and video data is requested from YouTube and Twitch when you use the Studio and is not written to any StreamPulse database.
• Your clip decisions stay in your browser. Which clips you queue, dismiss or hide is saved in your browser's localStorage, along with your theme choice. It never leaves your device, and clearing your browser's site data removes it.
• Sessions are sealed in encrypted cookies. The access tokens that let StreamPulse read your connected accounts are encrypted with AES-256-GCM and stored in HTTP-only, secure cookies that page scripts cannot read. They expire after 30 days, and disconnecting an account deletes its cookie immediately.
• Small preference cookies. We also store your time zone (so analytics follow your local calendar) and your Demo Mode choice. Neither contains personal channel data.
• Abuse protection. To prevent spam, the server briefly keeps a network identifier in memory to rate-limit feedback and AI requests. It is not stored or logged long-term.

The StreamPulse Copilot and hook brainstorming use Google Gemini. When you ask the Copilot a question or request packaging ideas, StreamPulse sends Gemini your request together with the relevant context from your connected channels (for example, a video's title and key metrics, or a clip's details) so the answer is specific to you. This happens in real time and only when you use those features.

• StreamPulse does not use your private data to train AI models. AI processing is conducted via Google Gemini APIs in accordance with Google's API Data Governance terms.
• Copilot conversations are not saved by StreamPulse; closing or refreshing the Studio clears them.
• Gemini is called only from our servers. Our API keys are never exposed to your browser.

You are in control of your data and can revoke StreamPulse's access at any time:

• Google / YouTube: remove StreamPulse in your Google Security Settings. This immediately stops StreamPulse from reading your YouTube data.
• Twitch: disconnect StreamPulse under Twitch Settings → Connections.
• In StreamPulse: disconnecting an account from the Studio deletes its session cookie from your browser right away.
• On your device: clearing this site's data in your browser removes your saved clip decisions and preferences.

Because StreamPulse doesn't store your channel analytics on its servers, there is no server-side copy left to delete once access is revoked. If you've sent us a feedback report and want it deleted, contact us as described below.

When you send a report through the in-app Feedback form, we receive your message, the report type and, only if you add it, your email address. If you leave “include diagnostics” on, the report also includes the workspace you were on, your time zone, whether you were in Demo or Live mode, which platforms were connected, and your browser and operating system. Reports are delivered to our team's private Discord workspace and used only to fix issues and improve StreamPulse.

StreamPulse is not directed to children under 13, and we do not knowingly collect personal information from them. Connecting a YouTube or Twitch account requires meeting those platforms' own minimum age requirements.

If we change how StreamPulse handles your data, we will update this page and its effective date. Material changes, such as requesting new permissions, will be made clear in the Studio before they take effect.

Questions, data requests or concerns? Email ayushmanisharma@gmail.com, or use the Feedback button in the Studio header (or the link at the bottom of this page) and leave an email address so we can reply. See also our Terms of Service.