Back to Studio

StreamPulse Studio

Privacy Policy

Effective October 8, 2026

This policy explains what data StreamPulse Studio accesses when you connect your YouTube, Twitch, TikTok and Instagram accounts, how it is used, stored and processed (including by Google Gemini for the Studio Inspector), and how you can revoke access at any time.

1.Overview & Commitment

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, Twitch, TikTok or Instagram 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.

2.Data We Access (Read-Only)

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 Studio Inspector 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.
  • TikTok Display API (scopes user.info.basic and video.list): your display name and avatar, and your public videos with their titles, descriptions, length, cover images, links and view, like, comment and share counts. This data is used solely for Distribution Attribution: comparing how your clips perform across platforms inside StreamPulse.
  • Meta Graph API v26.0 (Instagram Reels) via Facebook Login (scopes instagram_basic, instagram_manage_insights, pages_show_list, pages_read_engagement and business_management): the list of your Facebook Pages, including Pages held in a Meta Business Portfolio (the portfolio's name and Pages are read only to find the Instagram professional account linked to one; StreamPulse never changes your business settings), that account's username, name and profile picture, and your Reels with their captions, thumbnails, links, likes, comments and insights (views, reach, saves, shares and interactions). This data is used solely for Distribution Attribution inside StreamPulse. StreamPulse does not request, access or store your personal Facebook profile content, friends, posts, private or direct messages, or contacts.

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.

3.Zero-Database Architecture & Token Storage

  • No StreamPulse user database. StreamPulse doesn't run a central database of users, channels or credentials, and never stores an unencrypted token. If you subscribe to a paid plan, your subscription and payment are handled by our payment processor, Stripe, which records which channel the plan belongs to; StreamPulse never sees your card details.
  • 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.
  • Your Discord webhook stays in your browser. If you connect the Discord Briefing Bot, the channel webhook URL is saved in your browser's localStorage. It reaches StreamPulse's server only with a test ping or briefing you send, is used for that one delivery, and is never stored or logged there.
  • Sessions are sealed in encrypted cookies. The access tokens that let StreamPulse read your connected accounts are encrypted on our server with AES-256-GCM (with an authentication tag, so a tampered cookie is rejected) and stored only in HTTP-only, secure, SameSite cookies in your browser that page scripts cannot read. This applies to every connection: YouTube, Twitch, TikTok and Instagram. A token is decrypted in server memory only while it's used for a live request to that platform. Cookies expire after 30 days (an Instagram connection when Meta's roughly 60-day token does), 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.
  • A five-minute cache for TikTok and Instagram posts. So the Studio and the Studio Inspector don't fetch the same posts twice, your TikTok and Instagram post metrics are kept in server memory for up to five minutes, then discarded. They are never written to disk or a database, and disconnecting either account clears them right away.
  • 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.

4.Data Protection Mechanisms & Security Safeguards for Google User Data

StreamPulse treats the data it receives from Google APIs (your YouTube channel profile, videos and analytics, and the OAuth tokens that grant access to them) as sensitive data, and protects it with the following technical and administrative safeguards.

Encryption in transit and at rest

  • Encryption in transit. All communication between your browser, StreamPulse's servers and Google APIs is encrypted with Transport Layer Security (HTTPS, TLS 1.2 or higher, and TLS 1.3 wherever your browser supports it). StreamPulse sends HTTP Strict Transport Security (HSTS) headers so browsers refuse to connect to it over unencrypted HTTP.
  • Encryption at rest. OAuth access and refresh tokens are encrypted with AES-256-GCM, an industry-standard authenticated encryption algorithm, using a server-held key that is never sent to your browser. Each sealed value carries an authentication tag, so any tampering is detected and the value is rejected. The encrypted tokens are stored only in HttpOnly, Secure, SameSite=Lax cookies, which page scripts cannot read and browsers send only over HTTPS.

No persistent storage and minimal data retention

  • StreamPulse does not store Google account passwords (it never receives them: you sign in on Google's own page), your video files, or your historical analytics in any external database.
  • Analytics data, retention curves and channel metrics are requested from Google when you use the Studio, processed in server memory to build the view you asked for, and discarded once that response is sent. They are not written to disk, logs or a database.
  • Access tokens are kept only for as long as you stay connected, in the encrypted cookie described above, which expires after at most 30 days. You can clear them instantly at any time with the Disconnect button in the Studio.
  • Editor share links that you create carry their clip details sealed and encrypted inside the link itself. StreamPulse keeps no copy on its servers, and each link stops working after 14 days.

Access controls and administrative safeguards

  • Principle of least privilege. StreamPulse requests only read-only Google scopes, and access to its systems, hosting and encryption keys is restricted to authorized personnel.
  • No human reads your analytics. Your private video analytics and channel telemetry are processed automatically and are not viewed by people at StreamPulse.
  • Never sold or brokered. Google user data is never sold, rented or transferred to third parties or data brokers. It is sent outside StreamPulse only to Google Gemini, which processes your Studio Inspector requests on our behalf as described in Third-Party AI Processing, and to destinations you choose yourself, only when you click to send: a Discord channel you dispatch a briefing to (see Discord Briefing Bot) or an editor you share a briefing link with.
  • No advertising. Google user data is never used for advertising, ad targeting, marketing or surveillance.

Google API Services User Data Policy (Limited Use disclosure)

StreamPulse’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Data deletion and revocation

  • You can revoke StreamPulse's access at any time in your Google Account permissions at https://myaccount.google.com/permissions.
  • Clicking Disconnect on your YouTube account in StreamPulse immediately revokes StreamPulse's access tokens with Google and deletes the session cookies holding your tokens and cached channel profile identifiers.

5.Artificial Intelligence & Google Gemini API Processing

The StreamPulse Studio Inspector (opened with ⌘K) and its packaging and hook audits use the Google Gemini API. When you ask the Studio Inspector a question or request packaging ideas, StreamPulse sends Gemini your message together with a summary of the relevant metrics from your connected platforms (for example, recent view totals, where viewers drop off in a video, how your topics are trending, or a clip's details) so the answer is specific to you. This happens in real time and only when you use those features. Your access tokens are never sent to Gemini.

  • Not used to train AI models. StreamPulse uses the paid tier of the Gemini API. Under Google's Gemini API Additional Terms of Service for paid services, Google does not use your prompts, the metrics sent with them, or Gemini's responses to train or improve its models. Google may keep them for a limited time to detect abuse and meet legal requirements. StreamPulse itself never uses your data to train AI models.
  • Conversations aren't archived. Studio Inspector conversations live only in your open Studio session. They aren't saved to any StreamPulse database, and closing or refreshing the Studio clears them.
  • Gemini is called only from our servers. Our API keys are never exposed to your browser.

6.Revocation & Deletion

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.
  • TikTok: in the TikTok app, remove StreamPulse under Settings and privacy → Security → Manage app permissions.
  • Instagram / Facebook: remove StreamPulse under Facebook Settings → Apps and Websites (or Instagram's Settings → Apps and websites). If you granted access to Pages in a Meta Business Portfolio, also remove StreamPulse under Facebook Settings → Business Integrations.
  • In StreamPulse: open the account menu in the Studio header and click Disconnect next to any platform. Disconnecting YouTube from the Studio revokes StreamPulse's access with Google and deletes its session cookie from your browser right away. Disconnecting TikTok revokes StreamPulse's TikTok token, and disconnecting Instagram removes StreamPulse's permissions from your Facebook account; each also deletes its session cookie. Disconnecting Twitch deletes its session cookie.
  • 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.

7.Discord Briefing Bot

If you connect a Discord channel webhook, StreamPulse posts to that channel only when you click Send Test Ping or Dispatch Today's Briefing Now. A test ping contains no channel data. A briefing contains your channel's name, your next publishing window and content target, whether an upload clashes with your streams, your momentum read (including the share of views from YouTube's recommendations), how many clips are awaiting review or queued, and the title and link of your top candidate clip.

Once posted, the message is held by Discord under Discord's Privacy Policy, and anyone in that channel can read it. You can delete it in Discord at any time; deleting the webhook in Discord, or clearing the URL in StreamPulse, stops further briefings.

8.Feedback Reports

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.

9.Children

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

10.Changes to This Policy

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.

11.Contact

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.