This policy covers the PeakSense desktop app for Windows ("PeakSense", "the app") and the website peaksense.net. PeakSense is made by an independent developer ("we", "us"). Contact: support@peaksense.net.
Depending on the features you use, PeakSense handles the following. All of it is stored and processed on your computer.
PeakSense does not collect advertising identifiers or read the cookies or data of your web browsers. It sends no crash reports or usage counts unless you turn them on (both are off until you do; see section 4).
Only to provide PeakSense's features to you:
We don't use your data for advertising, profiling or training AI models, and we never see it: it stays on your PC.
Everything is stored on your computer, not by us:
%LOCALAPPDATA%\PeakSense for the installed app, and %APPDATA%\PeakSense for YouTube sign-in files), including the app's database, settings, tokens, logs and its sign-in window's profile;Retention:
Security: the data is protected by your Windows account, the same as your other files. Sign-in tokens, the YouTube sign-in session and your OBS password are stored in PeakSense's data folder without additional encryption, so anyone who can use your Windows account could read them. Keep your PC and Windows account secure, and disconnect platforms you no longer use.
We don't sell, rent or share your data. PeakSense sends data from your PC to these services only when you use the related feature. Everything goes directly to the service, except TikTok, Twitch, Instagram and Facebook sign-in requests and the PeakSense relay items below (new-video notifications, and crash reports and usage counts if you turn them on). Each service handles what it receives under its own privacy policy.
| Service | When | What is sent |
|---|---|---|
| PeakSense sign-in relay (auth.peaksense.net, hosted on Cloudflare) | You connect TikTok, Twitch, Instagram or Facebook, PeakSense renews that sign-in, or you disconnect | The sign-in code, PKCE verifier, refresh token or the token being exchanged or revoked. Instagram and Facebook send you back to the relay after you sign in, and it forwards the sign-in code straight to PeakSense on your PC. The relay adds PeakSense's app secret, which can't be kept safely inside a desktop app, and passes the request straight to the platform. Their answer goes back to your PC unchanged. The relay stores and logs none of it. Cloudflare, which hosts it, sees your IP address. |
| PeakSense relay: new-video notifications | YouTube is connected | Your channel ID, so the relay can subscribe to YouTube's public notifications of new videos on your channel (through Google's PubSubHubbub hub). The relay keeps the IDs of your channel's newest public videos for up to 30 days so PeakSense can pick up new streams without asking YouTube repeatedly. Nothing else about your channel is stored. |
| PeakSense relay: crash reports (opt-in) | You turn on "Send crash reports automatically", or send one yourself | The error, a short stack trace, the app and Windows versions. Secrets, your user name, file paths, email addresses and media file names are removed first, and you can see the latest report in Help & About before sending. Kept 90 days. |
| PeakSense relay: anonymous YouTube usage counts (opt-in) | You turn on "Share anonymous YouTube usage counts" | Once a day: how many of each kind of YouTube request PeakSense made the day before, how many uploads, and whether it's Pro. No install, channel, video or account IDs. Kept 180 days and used only to size PeakSense's YouTube API quota requests to Google. |
| Lemon Squeezy (payments) and the PeakSense relay | You buy Pro from the app | Checkout happens on Lemon Squeezy's site, which handles payment details under its own policy; PeakSense never sees them. The app passes a random install ID with the checkout, and the relay keeps your Pro key under that ID for 30 days so the app can activate it. |
| GitHub or Cloudflare R2 (updates) | The installed app checks for updates | A request for the list of releases and, when you update, the download. No personal data. |
| YouTube / Google (YouTube API Services, Google sign-in) | You connect YouTube, browse your streams or playlists, post a clip, or turn on channel watching | Your sign-in, requests for your channel's videos and statistics, the clips you post with their title, description, tags, thumbnail, privacy and schedule. When you download one of your own VODs, the request to YouTube for that video. |
| Twitch | You connect Twitch | Your sign-in, live-status and event subscriptions (raids, subs, bits, channel points, chat), requests for your VOD list, clip creation, and downloads of your own VODs. |
| IGDB (a Twitch/Amazon game database) | Your clip library sorts clips by game | The stream title, tags or description of those clips, used to look up the game's name. No account information is sent. |
| TikTok | You connect TikTok and post | Your sign-in, a request for your posting options, the clip, and the caption and settings you chose. Also a post-status check. |
| Instagram (Meta) | You connect Instagram and post | Your sign-in, a request for your username and account type, the clip and its caption. Also a processing-status check, a check of your daily posting limit, and a request for the post's link. |
| Facebook (Meta) | You connect Facebook and post to a Page | Your sign-in, a request for your name and the Pages you manage, the clip and its description. Also a processing-status check. Disconnecting sends a request that removes PeakSense's access. |
| Kick | You paste a Kick VOD link | A download request for that video. |
| OBS Studio | You connect OBS | Commands to your own OBS (start or stop recording, add chapter markers, save the Replay Buffer, and settings changes you click "Fix" or "Turn on" for). This stays on your PC or home network. |
| Discord or Slack | You add a webhook address | Notification text: stream and clip titles, status and error messages. |
| The PeakSense Discord bot (runs on PeakSense's server) | You add the PeakSense bot to your Discord server | Your server's id and name, the channels, roles and message text you pick, your Twitch channel (so it can announce when you go live while your PC is off), when you're live and the stream's title and game, the titles and links of clips you post publicly, and alert text for your private channel. PeakSense's server keeps the settings, the go-live message it's updating and your last 10 announced posts; removing the bot in the app deletes them. Discord members' presses of its buttons and commands (their user id, roles and the command) are handled and not stored, apart from a short queue of Approve presses and moment marks for your app. |
| Hugging Face | You download a speech model, or add a token for speaker labels | Model downloads and a check that your token is valid. No video or audio is sent. |
| GitHub | First use of face detection or of downloading from your channel | Downloads of the face-detection model and of helper components for the downloader. No personal data. |
| Ollama (optional local AI) | AI scoring is on | Transcript excerpts, sent to Ollama running on your own PC (by default localhost). |
If you connect OBS, PeakSense watches your stream while you're live. It reads the recording OBS is writing on your PC, finds moments, and saves the recording to its local library when you stop.
With Twitch connected, it also records the time of chat messages and events. This lets it find chat spikes and lets you mark moments with a chat command. That log, including viewers' usernames and message text, is stored only on your PC next to the recording. You can delete it with the recording.
Nothing from a live session is sent to us.
PeakSense downloads videos only from your own connected channel. It confirms through the YouTube or Twitch API that the video belongs to the account you connected before downloading. The exception is Kick VOD links you paste, which Kick provides no way to verify. You can turn platform downloads off in Settings → Storage and use OBS recordings or imported files only.
Downloads are saved on your PC and follow the storage rules in section 3.
PeakSense uses YouTube API Services to show your channel's streams and playlists, check a video's owner, upload and schedule your clips, and read statistics of clips you posted. By using PeakSense's YouTube features you agree to the YouTube Terms of Service. Google's handling of your data is described in the Google Privacy Policy.
PeakSense's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
PeakSense uses TikTok's Login Kit and Content Posting API to post your clips to the TikTok account you connect. It reads your creator nickname, avatar and posting options so you can choose privacy and interaction settings for each post. It sends only the clips and captions you choose.
PeakSense can post your clips as Reels to Instagram and, if you choose, to a Facebook Page you manage. They are connected separately, and you don't need Facebook to use Instagram.
instagram_business_basic and instagram_business_content_publish permissions. PeakSense reads your username and account type (Instagram only allows posting to Creator or Business accounts) and publishes the Reels you choose, with your caption.pages_show_list, pages_read_engagement and pages_manage_posts permissions. PeakSense reads your name and the list of Pages you manage so you can pick one, and publishes the Reels you choose to that Page.See the Instagram Privacy Policy and Meta Privacy Policy.
peaksense.net is a static site. If you join the launch list, your email address is collected by our list provider, LaunchList, which also loads a small script on the page. We use the address only to email you once when PeakSense launches.
If you email us, we use your message only to reply. Our web host receives standard request information, such as your IP address and browser type, to serve the pages. We don't use analytics or advertising cookies.
To be removed from the list or have your emails deleted, write to support@peaksense.net. We act within 30 days.
PeakSense is not directed at children. You must be at least 13 years old, and old enough to use each platform you connect under its own rules, to use PeakSense. We don't knowingly collect data from children. If you believe a child sent us their email, contact us and we'll delete it.
We'll post changes here with a new "Last updated" date. If a change affects how the app handles your data, the app's release notes will say so.