VolleyCam Privacy Policy

Google and YouTube User Data

YouTube Live Streaming is optional. VolleyCam passes https://www.googleapis.com/auth/youtube.force-ssl as the only value in Google Sign-In’s additionalScopes argument. Google Sign-In 9.2.0 then adds its standard email and profile basic identity scopes to the authorization request. The YouTube scope is necessary because read-only access cannot create, bind, update, start, or complete the user’s live-broadcast resources. VolleyCam does not request Gmail, Drive, Contacts, Calendar, YouTube Analytics, or YouTube Partner access, and it never asks for or receives a Google password.

1. What Google and YouTube user data VolleyCam accesses

After the user chooses YouTube Live Streaming and authorizes access, VolleyCam processes:

• Google/YouTube authorization credentials managed by the official Google Sign-In SDK, including an access token used for YouTube API requests and authorization state used to restore the connection;
• the selected YouTube channel ID, channel title, and channel-thumbnail URL;
• broadcast title, description, scheduled time, privacy setting, audience setting, thumbnail, lifecycle status, broadcast ID, bound live-stream ID, and viewer/watch URL;
• live-stream ID, status, compatible resolution/frame rate, secure RTMPS ingestion address, and ingestion stream name required for the active session; and
• camera video, microphone audio, and visible scoreboard content only after the user explicitly starts a livestream.

2. Google Sign-In service and SDK processing

VolleyCam uses Google Sign-In for authorization. Although the SDK adds email and profile to the scopes supplied by VolleyCam, VolleyCam does not request extra OpenID claims. During sign-in and restoration, the SDK processes basic profile data from the ID token or, when necessary, Google’s userinfo service and stores the result in its user profile object. VolleyCam’s app-owned code does not read user.profile, the Google profile name or email address, phone number, ID token, or server authorization code. VolleyCam receives the authorization result, verifies the granted YouTube scope, and uses the SDK-provided access token for the YouTube API requests described in this policy.

VolleyCam configures Google Sign-In when the app starts so the optional feature is ready if selected. On supported iOS versions, Google Sign-In 9.2.0’s default App Attest provider may contact Google’s Firebase App Check service to obtain a limited-use App Check token during that preparation, before the user begins Google sign-in. This security-preparation path does not itself sign the user in. Source inspection establishes the enabled code path, not that a request succeeded on every launch or that Google account identity was transferred before sign-in.

Google’s published iOS Sign-In privacy information states that the SDK may collect a user identifier to record OAuth grants and an IP address that may be used to estimate general location for fraud prevention.

The privacy manifest bundled with Google Sign-In 9.2.0 declares the following linked, non-tracking categories: name, email address, phone number, other data types, coarse location, user ID, device ID, and other usage data. It assigns App Functionality to name, email address, phone number, coarse location, user ID, and other data types, and Analytics to user ID, device ID, other usage data, and other data types. These are Google SDK declarations; the SDK-added basic identity scopes do not mean VolleyCam’s app-owned code reads, stores, or receives every declared category. VolleyCam has no code that sends those SDK analytics categories to a PAL Studio server, and PAL Studio does not operate an analytics backend for the app. Google controls its service-side processing under its privacy policy and the user’s Google settings.

3. How VolleyCam uses Google and YouTube user data

VolleyCam uses this data only to provide the user-requested YouTube Live feature: identify the signed-in channel; restore the authorized connection; list, create, select, update, and bind broadcasts and live streams; start, monitor, recover, and complete a broadcast; publish the selected live feed; obtain the viewer link; and let the user open, copy, display as a QR code, or share that link.

PAL Studio does not use Google user data for advertising, user profiling, data brokerage, unrelated analytics, or training generalized artificial-intelligence or machine-learning models. Google’s own processing is governed by the Google policies and SDK declarations linked in this policy.

4. With whom Google and YouTube user data is shared or transferred

VolleyCam does not sell Google user data and does not share it with advertisers or data brokers. Authorization, channel, broadcast, and stream requests travel directly between the user’s device and Google/YouTube as needed to perform the requested action. Live video, audio, and scoreboard content travel directly from the user’s device to YouTube during a livestream.

A public viewer URL and safe broadcast status/title may be sent to the user’s paired VolleyCam Remote device so that the user can use sharing controls there. The viewer URL reaches other people only when the user explicitly invokes iOS sharing, copies or opens it, or presents its QR code. OAuth credentials, authorization headers, RTMPS ingestion addresses, and stream names/keys are not included in Camera/Remote messages, QR codes, or app-generated share and clipboard payloads.

5. How sensitive Google and YouTube user data is protected

VolleyCam uses TLS/HTTPS for Google OAuth and YouTube API requests and requires RTMPS for live media. The official Google Sign-In SDK manages persisted Google authorization and token refresh using Google and iOS platform security. A manually entered RTMPS key is stored separately in the iOS Keychain with device-only protection.

OAuth tokens, authorization headers, RTMPS credentials, and manual stream keys are excluded from match/rally metadata, ordinary logs, Remote messages, QR codes, and app-generated sharing. Error logs use categories and numeric diagnostics rather than response bodies or credentials.

6. How Google and YouTube user data is retained and deleted

The Google Sign-In SDK retains authorization state locally so the user can remain signed in. After successful App Check preparation, the SDK also records a local prepared-status flag; the reviewed source does not establish an App Check token retention period. VolleyCam caches channel ID, title, thumbnail URL, and validation time locally for up to 24 hours. It may retain non-secret broadcast/stream IDs, title, selected quality, and viewer URL while needed to restore or manage a prepared or interrupted session. Reusable-stream configuration metadata may be cached to avoid creating duplicates. Runtime RTMPS ingestion credentials remain only in memory while preparing or running the active session and are then cleared.

Sign Out in Settings → YouTube Live Streaming ends the local Google session and clears VolleyCam’s channel and account-derived session/resource caches, but does not revoke the Google grant. Disconnect YouTube Account asks Google to revoke VolleyCam authorization and clears those local caches. The user may also revoke VolleyCam through Google Account connections. Forget Stream Key separately deletes a manually saved RTMPS key; other Manual RTMPS preferences remain independent of Google account disconnect.

Sign out, disconnect, and app deletion do not delete videos, broadcasts, or reusable stream resources already in the user’s YouTube account. The user controls them in YouTube Studio. Local VolleyCam matches and videos are independent and remain until separately deleted in VolleyCam, Photos, or iOS.

PAL Studio does not retain Google user data on developer-operated servers.