Your game.
Your information.

What stays on your device

Recordings, game photos, athlete profiles and pictures, team and roster details, scores, saved moments, practice notes and reel projects are stored locally. VBCam uses this information to record, organize, edit and export your games and practices. Its play detection and athlete-following tools process media on the device. There is no separate VBCam account or VBCam-hosted footage library.

Information can leave the device through the connected features described below. Device backups, Photos syncing and copies you place in Files are also subject to your Apple and storage-provider settings.

Photos, files and sharing

VBCam requests permission to add recordings, photos and exported clips or reels to Photos when you choose to save them. Media you select with a system photo or file picker is used in the project you are creating. When you share or export, the app or destination you choose receives that copy and handles it under its own practices. An exported video can contain athlete names, pictures, scores, venue information and other details you include in its graphics.

Deleting a VBCam original does not delete exported copies, device backups or files other people have received.

Google sign-in and YouTube

VBCam uses YouTube API Services for optional Team broadcasts and replay uploads. Google sign-in authorizes access to your selected YouTube channel. The Google sign-in library handles account information and authorization tokens; its saved sign-in credentials are stored in the device’s Keychain. VBCam uses tokens to communicate directly with Google and YouTube, rather than sending them to a VBCam account server. Never send us your password, token or stream key.

VBCam accesses channel identity, broadcast and video identifiers, titles, descriptions, visibility and audience settings, stream configuration, live status and available viewer counts. It uses these to prepare and manage your broadcasts, show their status and viewing links, upload replay videos, and carry out the YouTube actions you choose. Channel identifiers, game-to-broadcast links, stream configuration and replay-upload job information can be retained locally with your games and settings. YouTube receives the video, audio, thumbnails and publishing details sent through these features. Graphics in the stream may include the team, athlete, score or venue information you chose.

Full replay upload is off by default. If you enable it, after a Team game that you streamed and recorded, VBCam can queue the full local recording for upload to your connected channel over Wi-Fi. It creates a separate YouTube video and adds its link to the live video’s description. This is separate from the live archive. To enable it before filming, turn on Full replays in YouTube channel settings or Post the full recording after the game in Recording settings. Your saved choice applies to future games until you change it. Uploads may continue in the background. The replay uses the game or broadcast visibility setting; the fallback is unlisted. Anyone with an unlisted link can generally watch and forward it.

Disconnecting YouTube signs out the local Google session and removes that session’s saved credentials. It does not delete published YouTube videos or every historical channel/video reference in saved games and upload records, and it does not itself revoke Google’s permission grant. You can revoke VBCam’s access in Google Account connections. Manage or delete published videos in YouTube Studio; remove local games and media separately. Contact support for help locating or removing retained local information.

Google and YouTube retain information under their own policies and your account controls. VBCam uses information received from Google APIs to provide these visible features, not for advertising or sale. VBCam’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements where applicable.

By using VBCam’s YouTube features, you also agree to be bound by YouTube’s Terms of Service.

Nearby helpers and Apple Watch

Paired phones and iPads exchange game or athlete context, scores, labels, tagging commands, connection status and, in supported Team workflows, a camera preview over nearby connections. The Apple Watch companion exchanges session information and commands with its paired iPhone. These features do not upload your library to a VBCam server. Pair only with people you trust, leave the session when finished and manage local-network access in device Settings.

Venue search, maps and connection checks

Team venue search uses Apple’s map search services, which receive your search terms and search-region information. Downloading a venue map sends requests identifying the area around the venue to OpenFreeMap. If that service is unavailable, VBCam can request OpenStreetMap data from Overpass servers operated at overpass-api.de, overpass.private.coffee or maps.mail.ru. Those providers receive the requested venue area and normal connection information, such as your IP address. Map data and venue coordinates can be saved with the game and displayed in broadcast graphics. This uses the venue you select; VBCam does not request your device’s GPS location permission.

The optional pregame upload check sends generated test bytes and timing requests to Cloudflare’s speed-test service. It does not send game video or audio. Cloudflare receives normal network information such as the source IP address. VBCam saves the resulting connection measurement locally to help select streaming settings.

Subscriptions

Apple processes subscription payments. VBCam uses Apple-provided transaction and subscription information, including acquisition dates, product identifiers, purchase status and Family Sharing entitlement, to determine evaluation and paid access. VBCam does not receive your payment-card details. Subscription Family Sharing does not share or synchronize your footage. Manage or cancel subscriptions through your Apple Account.

Support, diagnostics and this website

When you email support, Greg Smith and Google Workspace, the email provider, process your email address, message and any attachments you send to respond and troubleshoot. Include only what is needed; avoid private footage, athlete information and account secrets. Support correspondence is retained for resolving requests and necessary business or legal records. You may ask us to delete it, subject to records we need to retain by law.

The current app does not include a VBCam-operated analytics service, advertising tracker, session-replay service or Sentry crash-reporting SDK. If you choose to share diagnostics with Apple, Apple may provide crash reports to the developer under your device settings and Apple’s policies. This policy will be updated before adding a service that changes these practices.

This website is hosted on Vercel. Vercel processes technical request information, including IP address, requested URL, browser information and timestamps, to deliver and secure it, under its Privacy Notice and applicable retention practices. The website includes no added analytics scripts, advertising cookies, signup forms or third-party font requests. Fonts and images are served with the site. Following an external link or emailing support takes you to a service with its own privacy practices.

Your controls, retention and deletion

You can review camera, microphone, Photos and local-network permissions in device Settings. Denying a permission can prevent the related feature from working. Local media and project information remain until you remove them using the app’s storage and deletion tools or remove the app’s data. Temporary processing files and caches may be removed sooner. Historical broadcast links and upload records can remain in local app data after disconnecting YouTube. Removing the app does not necessarily remove device backups, exported media or credentials retained by the operating system; use Apple’s storage and backup controls and Google’s revocation controls as needed.

Recipients control copies you have shared with them. Apple, Google/YouTube, map and network providers and Vercel apply their own retention and deletion practices to information processed by their services. We do not hold a server copy of your local footage or Google authorization tokens, so we cannot remotely recover or delete your device’s original files. For developer-held support information, or help exercising access, correction or deletion rights available under applicable law, email support@vbcamapp.com.

VBCam does not sell personal information, use it for targeted advertising or use your footage to train a developer-operated AI model. Service providers may process information outside your state or country. We use platform protections and encrypted connections where supported, but no storage or transmission method guarantees absolute security.

Children and permission to film

VBCam is a general-audience tool for filming volleyball, including youth sports; it is not directed to children under 13. Parents, guardians and other responsible adults should manage filming and publishing involving children. Follow venue and team rules and obtain appropriate permission before recording or sharing people’s images and information. If you believe a child under 13 has provided personal information directly to the developer, contact support so we can review and address it.

Changes and contact

We will post policy changes here with an updated effective date and provide additional notice or consent where required. For questions, complaints or privacy requests, contact Greg Smith at support@vbcamapp.com.