Privacy Policy

• You can watch streams without an account. A cookie with a random ID lets us count viewers and clicks. If you sign in on that browser, we store your account ID with the same ID, so your activity there can be linked to your account.
• If you create an account, we store your name, email address and a one-way hash of your password.
• Creator profiles, live streams and chat messages are public.
• Creators can send their streams to YouTube, Twitch, X and other platforms, and post go-live announcements to Discord. We use those connections only to stream to them, set up the stream there (such as creating the YouTube broadcast and setting the Twitch title) and post go-live announcements, as described below. Access tokens and stream keys are encrypted, and we never sell them or use them for advertising.
• We don't sell personal information, we don't run third-party ad networks, and PeakBot.tv doesn't take payments today.
• You can disconnect a platform in the Creator Studio (if your creator account is suspended, email us to have it removed), revoke access from the platform itself, and contact us at support@peakbot.com to have your data deleted.

Account information

When you create an account, we collect your name, email address and password, and a profile picture if you set one for your account. We store the password only as a one-way hash, never in readable form. We also store whether you have confirmed your email address, your account type (viewer, creator or administrator) and when the account was created and last updated.

Sign-in and session information

When you sign in, we create a session in our database. The session records the IP address and browser user agent of the device you signed in from. Sessions last 30 days and are extended while you keep using the site. They end when you sign out, and all of them end when your password is reset (resetting a password needs email, which isn't switched on yet). To slow down password guessing and spam, we count requests to our account endpoints per IP address; these counters, which include your IP address, are stored in our database. We also count confirmation and password-reset emails per email address, and other requests (such as chat, uploads and clicks) per IP address, briefly and only in memory.

Creator profile

If you become a creator, we collect the details you add to your public profile: your handle (your page address, such as peakbot.tv/yourname), display name, profile picture, banner image, bio, markets and trading styles, links to your social accounts and website, and your streaming schedule.

Content you create

This includes your streams (live video and audio from your screen, camera and microphone, plus titles and descriptions), chat messages, offers and sponsors (names, descriptions, images, banners, links, promo codes and disclosures), go-live announcement templates, studio and layout settings, and guest invite links. It also includes your stream designs from the Stream Designer (borders, sponsor spots, promo codes, text, logos, graphics and layouts), with unsaved drafts and earlier saved versions, and any stream frame you saved before that feature was retired.

Images you upload (profile pictures, banners, offer and sponsor images, logos and graphics for your stream designs, and any stream frame you saved earlier) are stored in our database. Anyone who has an image's link can view it, because these images appear on public pages. We store and serve images exactly as uploaded, including any information embedded in the file, such as camera details or the location where a photo was taken. Remove that information before uploading if you don't want it shared.

Connected platforms

If you connect YouTube, Twitch, X or Discord, or enter a stream key or RTMP server, we store the information described in the sections on Google and YouTube, Twitch, X, Discord and stream keys.

Guests and stream thumbnails

For guests (who don't need an account), we store the display name they enter and when they joined, were admitted, went on or off air and left; see Chat and guests. While a creator is live, we also save still images of the broadcast as the stream's thumbnail; see Live video.

Follows and notification settings

We store which creators you follow, whether you want an email when they go live, and your email notification preferences.

Information collected automatically

• A random viewer ID, stored in a cookie, so we can count each viewer once and tell repeat clicks apart. See Cookies.
• Viewing activity: which stream you watched, when you joined and left, whether you were on a desktop, tablet or mobile device (worked out from your browser's user agent), and your account ID if you were signed in.
• Offer and link activity: when offers are shown to you and when you click an offer, a sponsor banner, or a sponsor or graphic in a creator's stream design. We record the stream (if there is one), where it appeared (for example, which design and which sponsor spot), your random viewer ID and, if you're signed in, your account ID. When you click, we use your IP address and browser details (in memory) to spot repeated or automated clicks, and we keep a keyed hash of your IP address (not the address itself) and, for offer clicks, your browser user agent with the click record so that suspicious activity can be reviewed.
• Technical information: like any website, our servers and hosting provider receive your IP address, browser details and the pages you request in order to deliver the site, and this may appear in server logs. When an error occurs, our error logs may also contain the data the request was handling, such as a chat message or IDs.

We use information to:

• run PeakBot.tv: accounts, sign-in, creator pages, live streams, chat, guests, follows and the Creator Studio;
• send a creator's stream and go-live announcements to the platforms they connect, when they ask us to;
• send email, once it's switched on: PeakBot.tv doesn't send any email today. When email is enabled, we'll use your address to confirm it, to send password-reset links and, if you've confirmed it and kept the setting on, to tell you when a creator you follow goes live;
• show creators statistics about their own streams and sponsors, such as viewer counts, offer impressions, clicks and click-through rates, which they can also download as a spreadsheet (CSV) file;
• keep PeakBot.tv safe: rate limits, detecting fake or automated clicks, automatically masking offensive words and links in chat, reviewing and suspending creator accounts, and investigating abuse;
• comply with the law and respond to lawful requests.

We don't sell personal information, we don't build advertising profiles, and we don't use data from connected platforms for anything other than the features described in this policy.

Some information is public by design. Anyone, including people without an account and search engines, can see:

• creator profiles (handle, display name, pictures, bio, markets, styles, links, schedule) and follower counts;
• live streams, with their titles and viewer counts, and a creator's scheduled and past streams (with each past stream's thumbnail, if one was captured, and its length and peak viewer count);
• the offers, sponsor banners and borders, and graphics creators show, including, while a creator is offline, the sponsors from their default stream design. While a stream is live, viewers' browsers receive the stream's whole saved design, including any sponsors or graphics the creator turned off for that stream;
• chat messages, shown with the sender's name (a creator's display name for creators) and profile picture, if they uploaded one;
• the names guests enter when they join a stream.

Creator pages are listed in our sitemap so that search engines can find them.

Live video and audio are handled by LiveKit, our real-time video provider. When a creator or guest streams, their screens, camera and microphone go to LiveKit, along with the sound of a creator's shared screen or tab if they choose to share it. When you watch, your browser connects to LiveKit to receive the stream, so LiveKit processes your IP address and connection details. LiveKit also tells the player and the broadcast who is speaking, so the layout can feature whoever is talking. Creators can hide their own screens at any time while live. A screen or camera a creator shares still goes through LiveKit to viewers' browsers even when the current layout doesn't show it; use Hide screen, or stop sharing, to stop sending it. A guest's shared screen is sent to viewers only while the creator keeps it in the layout, and the guest can stop sharing at any time.

When a creator sends their stream to other platforms, LiveKit combines the video and pushes it to each platform the creator turned on for that stream, using the server address and stream key for that platform.

Thumbnails: while a creator is live, the Creator Studio saves a small still image (480×270 pixels) of the broadcast picture about one minute after it starts showing the live stream and again about ten minutes after (this restarts if the creator reopens the Studio). It shows whatever is on the stream at that moment, including screens, cameras, guests and graphics. Each new image replaces the last and is kept with the stream. It's shown in the list of past streams on the creator's page, and anyone with the stream's link can view it as soon as it's saved, even while the stream is live. Creators can't remove thumbnails themselves yet; email support@peakbot.com to have one removed.

Recordings: PeakBot.tv does not currently record streams or offer replays. Platforms a creator streams to may keep their own recordings under their own policies. YouTube, for example, normally keeps a live broadcast on the channel after it ends.

Chat

Creators choose whether chat is on for each stream. You need an account to chat. Messages are public (anyone can read them, during and after the stream, while the creator has chat on) and are stored with your account. An automatic filter always masks slurs and, unless the creator turns these settings off, swear words, words the creator blocks and links from viewers. Messages with the worst slurs, a blocked word or (when links are blocked) a link aren't posted. Creators and administrators can remove messages. Removed messages are no longer shown, but we keep them in our records, as we do when a creator turns chat off. You can't currently delete your own messages. The creator can hide one (it stays in our records); to have it erased, contact us.

Guests

Creators can invite guests with a private link. Guests don't need an account. A guest enters a display name; while waiting, their camera preview stays on their own device. Once the creator admits them, they go on air straight away: on a live stream, viewers see and hear them and they're included in the video sent to other platforms. While connected, their camera and microphone go through LiveKit to the creator and the other guests, and a guest can also share their screen (picture only, without sound). The creator can put a guest on air or keep them backstage, hide their camera so only their name shows, or mute them on the broadcast. When a guest is on air, their video, audio and name appear on the stream, including in the video sent to the platforms the creator streams to and in the stream's thumbnail; a shared screen appears only if the creator adds it to the layout. Viewers' browsers and the video sent to other platforms receive a guest's camera, microphone or shared screen only while that guest is on air, and not a camera the creator has hidden, a microphone the creator has muted, or a screen that isn't in the layout. Our servers enforce this through LiveKit, and stop sending a guest's camera, microphone or screen to viewers when the creator takes the guest off air, hides the camera, mutes the microphone or takes the screen out of the layout. If a guest uses modified software to get around these limits, our servers take their media off the stream when they detect it, usually within seconds. We store the guest's name; when they joined, were admitted, went on or off air and left; whether their camera is hidden or they're muted; their place on stage; and a hash of a random key their browser tab holds while they're connected. Invite links stop working after 12 hours, when the stream ends, or when the creator turns them off.

Creators can connect a YouTube channel so that PeakBot.tv can broadcast their stream to it. This is optional, and only creators who choose to connect see Google's consent screen. We don't use Google to sign you in to PeakBot.tv.

Permission we request

We request one permission: https://www.googleapis.com/auth/youtube, which Google describes as letting the app manage your YouTube account. We need it to create live broadcasts on your channel. We ask for offline access so that we can start your YouTube broadcast each time you go live without sending you back to Google.

What we access and do with it

• Your channel: when you connect, we request your channel's basic details from YouTube and keep only its ID and name, which we show in the Creator Studio. The Check button in Destinations uses the same request to confirm that PeakBot.tv can still reach your channel.
• A reusable live stream: we create one live stream on your channel named “PeakBot.tv” and read its ingestion address and stream name (the stream key), so that we can send your video to YouTube. We check that it still exists each time you go live and create a new one only if it's gone. This live stream stays on your channel if you disconnect; you can delete it in YouTube Studio.
• Live broadcasts: each time you go live with YouTube turned on, we create a broadcast on your channel with your stream's title; a description made from your YouTube announcement text (or your default announcement if you haven't written one), always including a link to your PeakBot.tv page, followed by every active sponsor in your stream design (including any you turned off for that stream) with its promo code and tracked peakbot.tv link; and the privacy setting you chose for YouTube (public unless you choose unlisted or private). The broadcast is marked as not made for kids; we also turn on DVR (so viewers can rewind while you're live), set low latency, and set it to start and stop automatically with your video. We then link it to the live stream and check its status. When your PeakBot.tv stream ends, including when it's ended for you (for example, if the Creator Studio stops responding, or an administrator ends it), we try to end the broadcast, or delete it if it never received video. That can't happen if you removed the YouTube destination during the stream or access was revoked, so check YouTube Studio in that case. If sending to YouTube is interrupted during your stream and the earlier broadcast has already ended, we create a new broadcast with the same title and description; earlier broadcasts stay on your channel, and your stream history keeps only the latest one.

Apart from the broadcasts and live stream we create, we don't read or change your videos, playlists, comments, subscribers, YouTube live chat or YouTube analytics, and we don't upload videos.

How OAuth tokens are used and stored

Google gives us an access token and a refresh token. We use them only to make the requests listed above, on your behalf: when you connect or check the connection, when you go live, while you're live (to restart sending to YouTube if it's interrupted), and when your stream ends. We store both encrypted (AES-256-GCM) in our database, with the encryption key kept separately from the database. Tokens are never sent to your browser or shown to anyone. When the access token expires, we use the refresh token to get a new one. If Google rejects the refresh token, we usually mark the YouTube connection as needing attention and ask you to reconnect.

What we store

• your channel ID and channel name, the permission granted, and when the access token expires;
• the encrypted access and refresh tokens;
• the ID of the PeakBot.tv live stream on your channel, its ingestion address and stream key (encrypted), and your YouTube privacy setting;
• for each stream you send to YouTube, the broadcast ID, its YouTube link, the description we sent, and whether it went live or failed.

Who can see it and how it's shared

Your YouTube channel name and broadcast links are shown only to you, in the Creator Studio. Your video and its stream key are sent to YouTube through LiveKit, our video provider, while you're live; LiveKit sends them to YouTube's RTMP ingest, which isn't encrypted. Our hosting provider stores our database. People who operate PeakBot.tv can access the database, including this data, and use that access only to provide support, handle your requests, keep the service secure or comply with the law. We don't share YouTube data with anyone else, we don't sell it, and we don't use it for advertising or for anything other than streaming to your channel.

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

Disconnecting, revoking access and deletion

• Disconnect in PeakBot.tv: in the Creator Studio, open Destinations and remove your YouTube destination. This immediately deletes the stored tokens, channel details and live stream details from our database. Records of streams you already sent to YouTube (the broadcast ID, link, the description we sent and its status) stay in your stream history. If your creator account is suspended, you can't open the Creator Studio; revoke access at Google and email us to have the data deleted.
• Revoke access at Google: visit myaccount.google.com/permissions (also reachable at security.google.com/settings/security/permissions), choose PeakBot.tv and remove its access. Disconnecting in PeakBot.tv doesn't currently revoke access at Google, so do this too if you want to remove PeakBot.tv's access completely. Once you revoke access, our stored tokens stop working, and the next time we try to use them we usually mark your YouTube destination as needing attention. The data listed above stays stored until you remove the destination or ask us to delete it.
• Ask us to delete it: email support@peakbot.com from your account's email address to have all YouTube data we hold about you deleted, including your stream history's YouTube records.

Broadcasts on your channel belong to you and stay on YouTube. Manage or delete them in YouTube Studio.

Using a YouTube stream key instead

You can also stream to YouTube by pasting a stream key from YouTube Studio instead of connecting your account. In that case we don't use Google sign-in or YouTube API Services. We store only the key, as described under Stream keys.

Creators can connect Twitch so that PeakBot.tv can stream to their channel. We request two permissions: channel:read:stream_key to read your stream key and channel:manage:broadcast to set your channel's stream title when you go live. When you connect, we read your Twitch user ID, login name and display name. We store these along with the encrypted access and refresh tokens. When you go live with Twitch turned on, we fetch your stream key (we don't store it), set your channel title to your stream's title, and send your video to Twitch through LiveKit. We don't change the title back afterwards. You can also paste a Twitch stream key instead of connecting your account.

Twitch's handling of your information is described in the Twitch Privacy Notice. To revoke PeakBot.tv's access, disconnect Twitch in the Creator Studio and remove PeakBot.tv under Twitch Settings → Connections.

X doesn't offer a public API for live video, so to stream video to X you paste the server address and stream key from X Media Studio. We store them as described under Stream keys.

When you go live with X turned on, the Creator Studio gives you a “Post your go-live to X” button that opens X with your announcement text filled in, and you post it yourself. We store the announcement text with the stream.

Not launched yet: connecting your X account so that PeakBot.tv posts the announcement for you. When it launches, we'll request the tweet.read, tweet.write, users.read and offline.access permissions, store your X user ID, username and encrypted access and refresh tokens, and post your announcement from your account when you go live (unless you turn automatic posting off), keeping a link to the post with the stream. Posts stay on X until you delete them there. We won't read your posts, followers or messages.

X's handling of your information is described in the X Privacy Policy.

Creators can post go-live announcements to a Discord channel by pasting a webhook URL they created in Discord. We check with Discord that the webhook exists before saving it. (Connecting through Discord instead, where you'd pick a server and channel on Discord's own screen and we'd request only the webhook.incoming permission, isn't launched yet.)

We store the webhook URL (encrypted), the webhook's name and the channel and server IDs. We don't read your messages, servers or Discord profile. When you go live with Discord turned on, we post an announcement to that channel with your announcement text, stream title, display name, profile picture and a link to your stream, and keep the announcement text and a link to the posted message with the stream. It mentions @everyone only if you turn that on. The Send test button posts a test message to the same channel.

Removing Discord in the Creator Studio deletes the webhook URL from our database, but the webhook itself stays in your Discord channel until you delete it under Server Settings → Integrations → Webhooks. Discord's practices are described in the Discord Privacy Policy.

For YouTube and Twitch you can paste a stream key instead of connecting your account. For X and any other service that accepts RTMP (such as Kick, Facebook or LinkedIn), you paste a server address and stream key. We store stream keys encrypted (AES-256-GCM). Server addresses are also encrypted, except that some saved before we started encrypting them may still be stored unencrypted until you re-save or remove the destination. We never send a saved key back to your browser, and we use it only to send your stream to that service through LiveKit while you're live. We reject server addresses that point to private or internal networks.

A stream key lets anyone who has it broadcast to your channel, so treat it like a password. To remove a saved key, delete the destination in the Creator Studio. If you think a key was exposed, reset it on the platform that issued it.

Removing a destination in the Creator Studio (Destinations) deletes its stored tokens, keys and webhook URL from our live database right away; encrypted copies can remain in our database backups until those backups are replaced. If you remove a destination while you're live, your video keeps going to that platform until the stream ends. If your creator account is suspended, you can't remove destinations yourself; email support@peakbot.com and we'll delete them. Records of past go-lives (the announcement text and links to the YouTube broadcast, Twitch channel or Discord message) stay with your streams after you remove a destination.

Removing a destination from PeakBot.tv doesn't currently revoke the access you granted on the platform, so to remove access completely, use the platform's own settings as well:

YouTube (Google)

myaccount.google.com/permissions, then remove PeakBot.tv.

Twitch

twitch.tv/settings/connections, then disconnect PeakBot.tv.

X

Automatic posting isn't launched yet, so there's nothing to revoke today. Once it is: x.com/settings/connected_apps, then revoke PeakBot.tv.

Discord

Delete the webhook in Server Settings → Integrations → Webhooks.

Stream keys

Reset the key on the platform that issued it.

Revoking access on a platform doesn't delete what we've stored. Remove the destination in PeakBot.tv or email support@peakbot.com as well.

PeakBot.tv uses only its own cookies and browser storage. We don't use third-party analytics, advertising or tracking cookies.

• Session cookie (__Secure-pbtv.session_token): keeps you signed in. It is set only when you sign in and lasts up to 30 days.
• Viewer ID cookie (pbtv_vid): a random ID that lets us count each viewer once and measure offer clicks, whether or not you're signed in. It lasts one year.
• Browser storage: for creators, whether they were sharing their screen (pbtv-screen:<stream ID>, kept only for that browser tab), so the Creator Studio can resume it after a reload. When you sign out, a small entry (better-auth.message: the event and a timestamp) is saved in local storage so your other open tabs sign out too. Both stay on your device.

You can delete cookies and site data in your browser settings. If you block the session cookie, you won't be able to sign in.

Creators can feature offers, such as their own memberships, courses or newsletters, or a sponsor's product. Offers appear as cards beside the player, as banners or sponsor borders around the stream (and, while a creator is offline, above and below their page's player), as clickable graphics in a creator's stream design, as QR codes or short links drawn into the video, and as links in the description of the creator's YouTube broadcasts. Creators choose the offers they show; PeakBot.tv doesn't sell or place offers itself.

Offer and sponsor links go through PeakBot.tv first (for example, peakbot.tv/o/…), including the ones in YouTube descriptions; older stream-frame links (peakbot.tv/f/…) still work and are counted the same way. When you click one or scan its QR code, we record the click as described in Information we collect and then send you to the destination website. That website has its own privacy policy. We don't add anything about you to the link, and we don't send the website your name, email address or account details; at most, your browser tells it that you came from peakbot.tv.

Creators see totals and rates for their own streams and sponsors, such as viewer counts, impressions, clicks, unique clicks (how many different viewer IDs clicked) and click-through rates, broken down by stream, day and where each sponsor appeared. They can download these totals as a spreadsheet (CSV) file, for example to share with a sponsor; the file contains only totals. We don't give creators or sponsors the identity, email address or IP address of viewers who clicked. All analytics are first-party: we don't send them to outside analytics services.

PeakBot.tv doesn't show ads from ad networks, doesn't let third parties place advertising cookies or trackers, and doesn't use your information for targeted advertising. The offers and sponsor banners you see on a stream are chosen by that creator.

PeakBot.tv doesn't currently offer paid subscriptions, tips, donations or any other payments, and we don't collect payment card or bank details. Paid features are not launched. If you buy something after clicking an offer, the purchase happens on the seller's website under its own terms and privacy policy.

We share information only as described here:

• Service providers that run parts of PeakBot.tv for us: Railway (hosting for our app and database), LiveKit (live video), and, once email is switched on, Resend (sending email).
• Platforms a creator connects: when a creator streams, Google and YouTube, Twitch, X and any RTMP server they enter receive the stream, including on-air guests' video, audio and names, and Discord receives their announcements, as described above.
• Everyone, for public content: profiles, streams, chat messages and guest names, as described in Public profiles.
• Legal and safety reasons: when we believe in good faith that the law requires it, or to protect the rights, property or safety of PeakBot.tv, our users or others.
• Business transfers: if PeakBot.tv is involved in a merger, acquisition or sale of assets, information may be transferred as part of that transaction. Information received from Google APIs would be transferred only with your prior consent, as Google's policy requires.

We don't sell personal information, and we don't share it for cross-context behavioral advertising.

We don't yet apply fixed retention periods to most information. Today:

• account, profile, follow and settings information is kept while your account exists; if you follow a creator while they're live, a record that your account followed during that stream is kept with the stream even after you unfollow;
• streams and their thumbnails, chat messages (including removed ones), guest names, offers, uploaded images (including replaced ones) and analytics records are kept while the creator's account exists;
• stream designs are kept while the creator's account exists, including designs you delete, their unsaved drafts and up to 50 earlier saved versions of each, so that past streams and sponsor statistics can still show which design was used; a stream frame saved before that feature was retired stays stored, unused, until you ask us to delete it;
• tokens, stream keys and webhook URLs for a connected platform are kept until you remove that destination;
• short-lived items expire automatically: connection requests to a platform after 10 minutes, password reset links after 1 hour, email confirmation links after 24 hours, guest invite links after 12 hours, and sessions stop working 30 days after you last use them (the session record, including the IP address and browser user agent it recorded, stays in our database until you sign out, your password is reset or your account is deleted).

PeakBot.tv doesn't yet have a self-service way to delete your account. To delete your account and the information linked to it, email support@peakbot.com from the email address on the account. When we delete an account, we delete its profile, sessions, follows, settings, chat messages and uploaded images, and for creators also their streams and thumbnails, offers, stream designs and any saved stream frame, studio settings, connected platforms and the analytics for their streams. Records of your viewing, clicks and follows on other creators' streams aren't deleted with your account: they keep the random viewer ID, hashed IP address and browser details recorded with them, and your former account ID, which no longer links to any account. Copies of deleted information can remain in our database backups until those backups are replaced, and in server and error logs kept by our hosting provider until they expire. We may keep information when the law requires us to.

We use measures designed to protect your information, including:

• HTTPS for all connections to peakbot.tv;
• one-way hashing for passwords;
• AES-256-GCM encryption for access tokens, refresh tokens, stream keys, webhook URLs and RTMP server addresses (except some addresses saved before we began encrypting them; each destination's server hostname is also kept unencrypted in your stream history), with the key stored separately from the database; these secrets are never sent to your browser;
• single-use, 10-minute connection requests tied to your account when you connect a platform, so nobody else can attach their account to yours;
• rate limits on sign-in, sign-up, email and other requests;
• a content security policy that limits which scripts can run on our pages.

Your video and stream key are sent from LiveKit to YouTube and Twitch over RTMP, which isn't encrypted in transit.

No method of transmission or storage is completely secure, so we can't guarantee absolute security. If you think your account has been compromised, contact us at support@peakbot.com. Password reset by email isn't available until email is switched on; when it is, resetting your password also signs out all your sessions.

Our service providers may process information in the United States and other countries, which may have data protection laws different from those where you live. By using PeakBot.tv, your information may be transferred to and processed in those countries.

You can:

• see your account details and change your email notification preferences in Settings (changing or resetting your password needs email, which isn't switched on yet; until then, email support@peakbot.com from your account's address for help);
• edit your public creator profile details, offers, sponsors and stream designs in the Creator Studio (deleting an offer or a design hides it but keeps it for your statistics, as described in Data retention; stream frames are no longer offered, so to delete one you saved earlier, email support@peakbot.com). If your creator account is suspended, you can't use the Creator Studio; email us to have this information changed or deleted;
• unfollow creators at any time;
• disconnect platforms and remove stream keys, as described in Disconnecting;
• clear cookies and site data in your browser.

Depending on where you live, including in the European Economic Area, the United Kingdom and some US states such as California, you may have the right to request access to, correction of, deletion of, or a copy of your personal information, and to object to or restrict certain uses of it. To make a request, email support@peakbot.com from the email address on your account. We may need to verify your identity before acting on a request. We won't discriminate against you for exercising your privacy rights. You may also have the right to complain to your local data protection authority.

PeakBot.tv is a trading-focused service and is not directed to children. We don't knowingly collect personal information from children under 13. If you believe a child under 13 has created an account or given us personal information, contact us at support@peakbot.com so we can delete it.

We'll update this policy when our practices change, and the date at the top shows the latest version. If we change how we use information received from Google APIs or another connected platform, we'll update this policy and ask for your consent before using that information in a new way.

For questions or complaints about this policy or our privacy practices, or to make a privacy request, email support@peakbot.com.