Skip to content

CheerCam Privacy Policy

Effective 5 November 2026

CheerCam is operated by Victor Procure, carrying on business as CheerCam, in Alberta, Canada (“CheerCam”, “we”). Questions about this policy go to support [at] getcheercam.com.

This policy says what CheerCam does with information, in plain terms. The short version: what you put into the app stays on your phone, with one exception. If you sign in to YouTube, your teams and rosters are copied to a CheerCam service so that every phone streaming the same channel has them, encrypted with a passphrase you choose if you set one (section 2). While you are on the free trial, the phone also reports how much of it has been used, against an identifier for the phone (section 7). Crash reports are sent to Google’s Firebase Crashlytics unless you turn them off (section 8). When you create a team stinger, the team’s logo is sent to a render service and the finished clip comes back to the phone (section 13). Video leaves the phone only when you stream it, to the place you chose. There are no CheerCam accounts.

Everything you enter or create in CheerCam is stored on the device you use it on:

  • Teams, including names, abbreviations, colours, logos, league and division.
  • Rosters, including player names, jersey numbers and any player photos you add.
  • Games, including the sport, the sides, the score and when they were played.
  • Scheduled broadcasts: which sport and teams each one is for.
  • Recordings and replay clips of your games.
  • Sponsor images and video loops, scoreboard graphics and your settings.

Games, recordings, clips, sponsor material and settings never leave the phone. Teams, rosters and scheduled broadcasts leave it only as section 2 describes, and only while you are signed in to YouTube. A team’s logo also leaves it when you create a stinger, as section 13 describes. CheerCam has no user accounts. If you export your teams and games to a file, that file goes only where you send it. Deleting a team, a game or a recording in the app removes it from the phone. Uninstalling the app removes all of it.

Your own device backup (iCloud or Google) may include this data; apart from the team library in section 2 and the prepared logos in section 13, CheerCam has no copy.

2. The team library shared between your phones

Section titled “2. The team library shared between your phones”

When you are signed in to YouTube, CheerCam keeps one copy of your team library for the channel you signed in with, so that another phone signed in to the same channel shows the same teams, logos, rosters and player photos, and a game scheduled on one phone shows its teams on the other. The library holds the items in section 1 marked teams, rosters and scheduled broadcasts, and nothing else.

Where it is: on CheerCam’s service at auth.getcheercam.com, in storage provided by Cloudflare, Inc. It is identified only by your YouTube channel’s id. The service checks your YouTube sign-in with Google on every request and will only ever hand a library to a sign-in for that same channel. It keeps no account, no password and no record of who used it beyond a short-lived note of which channel a sign-in belongs to.

Encryption: you can set a library passphrase under Settings. With one set, the library is encrypted on your phone before it is uploaded, and only a phone that has the passphrase can read it. CheerCam and Cloudflare cannot. Without a passphrase, the library is stored as it is, which includes player photos, and the app tells you so before you add one. If you lose the passphrase, the copy on the service is unreadable; your phones keep their own copies, and setting a new passphrase uploads the library again.

Your control: signing out of YouTube stops the copying and leaves the phone’s library as it is. “Remove cloud copy” under Settings deletes the library from the service at once. Anyone who can manage your YouTube channel can sign in to CheerCam with it and, given the passphrase if you set one, see the library.

Not signed in to YouTube, nothing in this section applies and your teams stay on the phone.

You decide whom you film and photograph. Player photos and rosters are for your own scoreboard graphics. They stay on the phone unless you sign in to YouTube, in which case they are shared with your other phones as section 2 describes. You are responsible for having whatever permission your league, venue or the people involved require before you film, photograph or broadcast them, and in particular for minors, and for deciding whether to set a passphrase before adding player photos. See the User Agreement.

When you go live, CheerCam sends your camera’s video and audio, with the scoreboard drawn in, directly from the phone to the destination you chose:

  • YouTube, into a broadcast CheerCam creates on the channel you signed in with, or
  • an RTMP server whose address and stream key you entered.

The stream does not pass through CheerCam. Once it reaches YouTube or your server, that service’s terms and privacy policy apply to it. The RTMP address and stream key you enter are stored in the phone’s secure keychain or keystore so you do not have to type them again.

Recording to the phone sends nothing anywhere.

To create broadcasts on your channel, CheerCam asks you to sign in with Google and grant access to YouTube. CheerCam uses the YouTube API Services. By signing in you also agree to the YouTube Terms of Service (https://www.youtube.com/t/terms), and Google’s Privacy Policy (https://policies.google.com/privacy) applies to Google’s handling of your account.

What CheerCam asks for: the YouTube scopes that let it create and manage live broadcasts and read your channel’s name.

What it does with the access: it creates a live stream and broadcast, binds them, starts and ends the broadcast, checks that video is arriving, reads the channel name to show you which channel you are about to stream to, and uses the channel’s id to keep the team library in section 2 with that channel. Nothing else. CheerCam does not read your videos, comments, subscribers or watch history, and does not use YouTube data for advertising or share it with anyone.

Where the sign-in goes: Google requires the code exchange for this kind of sign-in to happen on a web server, so CheerCam runs one small service at auth.getcheercam.com for that step and for the team library in section 2. It holds a sign-in in progress for at most five minutes and then forgets it. It has no accounts and no record of who signed in. The refresh token that keeps you signed in is stored only on your phone, in its keychain or keystore.

Signing out in CheerCam removes the token from the phone and asks Google to revoke it. You can also remove CheerCam’s access at any time from your Google account’s security settings at https://security.google.com/settings/security/permissions.

CheerCam’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

You can run the scoreboard from a second device on the same local network. The two phones talk to each other directly over that network. Nothing goes over the internet and nothing goes to CheerCam.

You can also add other cameras as sources: a GoPro or other RTMP camera, an NDI source, or a phone running VDO.Ninja. GoPro, RTMP and NDI video comes to the phone over the local network and goes nowhere else. A VDO.Ninja camera’s video also travels over the local network, but the two devices first find each other through VDO.Ninja’s public connection service at vdo.ninja, which sees a random stream name CheerCam makes up and both devices’ network addresses. To find a direct route, the phone also asks public address-lookup servers run by Google and Cloudflare for its own network address. None of this goes to CheerCam, and video does not pass through any of these services. VDO.Ninja’s privacy policy is at https://docs.vdo.ninja/help/privacy-and-security-details/vdo.ninja-privacy-policy.

When subscriptions are offered, they are bought through the Apple App Store or Google Play, under those stores’ terms, and the store is what identifies you. CheerCam uses RevenueCat to check whether a subscription is active. RevenueCat receives an anonymous identifier generated for your installation and the purchase records the store provides. It does not receive your name, email address or any of the data in sections 1 and 2. RevenueCat’s privacy policy is at https://www.revenuecat.com/privacy.

The free trial is an hour of streaming or recording per phone. So that reinstalling the app does not start it again, the phone sends CheerCam’s service at auth.getcheercam.com the number of seconds it has used, with an identifier for the phone: on Android, the identifier Android gives CheerCam on that phone, and on an iPhone, a random identifier CheerCam creates and keeps in the phone’s keychain. The service stores the seconds used, when they last changed and, on an iPhone, whether Apple has marked it (below), against a one-way hash of that identifier, and nothing else about you or the phone. On an iPhone, the app also sends a token from Apple’s DeviceCheck service, which CheerCam uses only to ask Apple to remember, against that iPhone, whether its trial has been used. Apple keeps that mark; CheerCam cannot use it to identify you. Once you subscribe, nothing more is sent. The record holds no name, email address or account, so CheerCam cannot tell whose phone it belongs to.

CheerCam sends crash reports so that faults can be fixed, using Firebase Crashlytics, a Google service. A report is sent when the app crashes, or when a stream or recording fails. It contains what the app was doing at the time, its settings (such as resolution and bitrate), the app version, the phone’s model and operating system version, and an identifier Firebase creates for this installation. It does not contain your teams, rosters, footage, titles, channel or stream keys, and it is not linked to you. You can turn crash reports off in Settings > About. Google’s privacy policy is at https://policies.google.com/privacy and Firebase’s privacy information is at https://firebase.google.com/support/privacy. CheerCam does not use analytics or advertising trackers.

  • Camera and microphone: to film and to hear the game. Required for the app to work. The camera is also used when you photograph a roster, which is read on the phone, and to scan the code that pairs a second phone. On Android, reading a roster photo and scanning that code use Google’s ML Kit, which works on the phone: the picture and the text in it are not sent anywhere. ML Kit does send Google basic information about its own use so that Google can maintain it: the phone’s model and operating system version, CheerCam’s name and version, how long a read took, and any error codes. Google describes this at https://developers.google.com/ml-kit/android-data-disclosure. On an iPhone both are done by Apple’s Vision on the phone and send nothing.
  • Photos or files: only when you pick a logo, a player photo, a sponsor image or video, a roster picture or a file to import, and only for what you pick. On an iPhone, saving a recording or clip to your photo library asks for permission to add to it.
  • Local network: to find and talk to a second phone running the scoreboard, and to receive video from the cameras in section 6.

A game controller is paired in your phone’s Bluetooth settings. CheerCam does not ask for Bluetooth permission.

Each permission is used only for the purpose given and can be withdrawn in your phone’s settings.

CheerCam is a tool for the person operating the camera, not for children. It does not knowingly collect information from children. Footage and rosters may include minors; that information is the operator’s responsibility, as section 3 says, and rosters and player photos are shared between the operator’s phones only as section 2 describes and can be encrypted so that CheerCam cannot read them.

Your data is on your phone, where you can see it, change it, export it and delete it yourself in the app at any time. The one copy CheerCam holds, the team library in section 2, is deleted by “Remove cloud copy” under Settings, and CheerCam cannot read it when you have set a passphrase. Beyond that library, the trial record in section 7, which says how much of a phone’s trial is used and nothing about who uses it, and the prepared logos and daily stinger count in section 13, CheerCam holds nothing about you to disclose or correct. To have a prepared logo deleted, send the logo to support [at] getcheercam.com. If you believe otherwise, or have any question about this policy, write to support [at] getcheercam.com. CheerCam is subject to the Personal Information Protection Act (Alberta) and the Personal Information Protection and Electronic Documents Act (Canada); you may also contact the Office of the Information and Privacy Commissioner of Alberta.

getcheercam.com uses Cloudflare Web Analytics to count visits. It sets no cookies and does not identify you or follow you to other sites. For each visit it records the page, the page you came from, and the browser, operating system and country that Cloudflare reads from the request. Cloudflare’s privacy policy is at https://www.cloudflare.com/privacypolicy/. The app itself uses no analytics, as section 8 says.

A stinger is a short animated clip with a team’s logo that plays on air. Stingers are made only when you press Create stinger or Create matchup stinger in the team or game editor. The phone then sends CheerCam’s service at auth.getcheercam.com the team’s logo, or both teams’ logos for a matchup, the sport, whether the phone is Android or an iPhone, and the same phone identifier as the trial in section 7. Team names, rosters and player photos are not sent.

The service passes the logos and the sport, and nothing else, to Modal Labs, Inc., which renders the clips on CheerCam’s behalf and sends them back to the phone. The finished clips are kept only on the phone. Modal keeps a prepared copy of each logo, filed under a one-way hash of the image, so that the next stinger with that logo is made faster. It is kept with no expiry date and is not linked to you, your phone or your team’s name. Modal’s privacy policy is at https://modal.com/legal/privacy-policy.

To limit how many stingers one phone can create in a day, the service counts them against a one-way hash of the phone identifier. The count is deleted after two days.

If you never create a stinger, nothing in this section applies.

If this policy changes, the new version ships with the app and the effective date at the top changes. A change that affects what leaves your phone will be pointed out in the app before it applies.

Contact: support [at] getcheercam.com