Privacy Policy

Effective Date: September 15, 2026

Privacy Policy For Live - Ryva Live Broadcast Scheduler Effective date: September 15, 2026 Application name shown by Google: Live Application developer and data controller: Ryva Tech Contact: rhean@ryva.ca This policy applies specifically to Live, also called the Ryva Live Broadcast Scheduler (the "Scheduler"). The Scheduler is a locally installed application developed by Ryva Tech that connects OBS Studio to an authorized YouTube channel so the channel owner can schedule and automate live broadcasts. This policy describes how the Scheduler accesses, uses, stores, shares, retains, and deletes Google and YouTube user data. 1. Google Services And Authorization The Scheduler uses Google OAuth 2.0 and YouTube API Services, specifically the YouTube Data API v3. Connecting a YouTube channel is optional. Google displays the requested permission before the user grants access. The Scheduler requests the https://www.googleapis.com/auth/youtube.force-ssl authorization scope because creating, updating, and binding live broadcasts requires permission to view and manage the user's YouTube account. The Scheduler uses this permission only for the broadcast scheduling functions described in this policy. The Scheduler does not request, collect, or store the user's Google or YouTube password. By using the YouTube-connected features, users also agree to the YouTube Terms of Service: https://www.youtube.com/t/terms Google's handling of information is described in the Google Privacy Policy: https://policies.google.com/privacy 2. Google And Youtube User Data The Scheduler Accesses After the user authorizes a YouTube channel, the Scheduler accesses these specific categories of Google user data: YouTube channel identity: the authorized channel's YouTube channel ID and channel display name. These are used to confirm and display which channel is connected. YouTube live-stream information: live-stream IDs and the ingestion details returned for the authorized channel, including the ingestion stream name. These are used only to locate and match the reusable YouTube stream configured in OBS Studio. YouTube live-broadcast information: broadcast IDs, titles, descriptions, scheduled start and end times, privacy status, lifecycle status, and broadcast content settings for upcoming broadcasts. These are used to determine whether a scheduled broadcast already exists and whether its authorized settings need to be updated. Google OAuth credentials: OAuth access and refresh tokens issued after the user grants permission. These tokens authenticate authorized API requests and keep the schedule operating without asking the user to sign in before every broadcast. Google and YouTube API responses: limited technical response and error data needed to complete, confirm, or troubleshoot authorized scheduling operations. 3. How The Scheduler Uses Google User Data The Scheduler uses the Google and YouTube user data listed above only to provide these user-facing functions: Confirm and display the YouTube channel selected by the user. Find and match the authorized channel's reusable live stream to the stream configured in OBS Studio. Create scheduled YouTube live broadcasts on the authorized channel. Generate date-specific broadcast titles and descriptions from templates entered and saved by the user. Set or update the scheduled start time and end time selected by the user. Set the visibility selected by the user: public, unlisted, or private. Bind each scheduled broadcast to the reusable YouTube live stream. Enable automatic start, automatic stop, DVR, and recording from the beginning. Apply the Scheduler's disclosed "not made for kids" broadcast setting. Display connection, scheduling, and automation status to the authorized user. The Scheduler performs these actions only for the YouTube channel the user authorizes and only according to the schedule, title template, description template, timing, and visibility settings saved by the user. It does not publish to a different channel or use Google user data for an unrelated purpose. 4. Google Data The Scheduler Does Not Access Or Use The Scheduler is not designed to access or use YouTube viewing history, YouTube search history, subscriptions, comments, private messages, contacts, Gmail, Google Drive files, Google Photos, payment information, or the user's Google Account password. It does not download or store copies of YouTube videos or other audiovisual content. Google user data is not used for advertising, personalized advertising, retargeting, marketing, credit decisions, lending, surveillance, data brokerage, user profiling, or the development, improvement, or training of generalized artificial-intelligence or machine-learning models. 5. Storage And Security Of Google User Data The Scheduler runs on the computer or server on which it is installed. Google user data used by the Scheduler is not stored in a public Ryva website database or a centralized Ryva cloud account. OAuth access tokens, refresh tokens, and the OAuth client secret are encrypted at rest using AES-256-GCM before they are written to local storage. API communications with Google and YouTube use HTTPS/TLS certificate verification. The Scheduler stores only limited local operational records: the authorized channel ID and name, and the broadcast ID, scheduled date, title, and last-update time for broadcasts managed by the Scheduler. Files containing Scheduler credentials and data are restricted from public web access. API response data that is not required for those operational records is processed temporarily and is not retained as a separate data set. Ryva applies reasonable administrative and technical measures to protect Google user data against unauthorized access, use, alteration, loss, or disclosure. Users are also responsible for securing the computer or server on which the Scheduler is installed, including its user accounts, files, encryption keys, and network access. 6. Sharing, Transfer, And Disclosure Of Google User Data Ryva Tech does not sell Google user data. The Scheduler sends data to Google and YouTube only as necessary to make the API requests authorized by the user. Google user data is not shared, transferred, or disclosed to advertising platforms, data brokers, information resellers, or other unrelated third parties. Google user data may be disclosed only in these limited circumstances: To Google and YouTube to provide the requested scheduling and broadcast-management functions. To a Ryva technician or service provider acting on the user's behalf, only when the user expressly requests support and authorizes that access, and only for the requested support purpose. When disclosure is required by applicable law or valid legal process, or is reasonably necessary to investigate fraud, abuse, or a security incident. No person other than the authorizing user, or an agent expressly approved by that user, is permitted to view the user's authorized YouTube API data. 7. Data Retention, Refresh, And Deletion OAuth access and refresh tokens are retained only while the user's YouTube authorization remains active and only for the scheduling purpose described in this policy. Other stored YouTube API data is retained only while needed to operate the Scheduler and is refreshed or deleted within 30 calendar days. Data that is no longer required is securely deleted from the Scheduler's local storage. A user may request deletion of the Google and YouTube data stored by the Scheduler by emailing rhean@ryva.ca. Ryva may verify that the request comes from the authorizing user. Following a verified deletion request, the associated OAuth tokens and stored authorized YouTube data will be deleted as soon as possible and no later than seven calendar days. Users may also revoke the Scheduler's Google authorization at any time through Google's security settings: https://security.google.com/settings/security/permissions Revocation prevents further authorized API access. When Ryva or the Scheduler becomes aware of that revocation, the associated locally stored Google and YouTube API data will be deleted as soon as possible and no later than seven calendar days. Deleting data stored by the Scheduler does not delete broadcasts, videos, or other content already stored by YouTube. Users can review or delete content stored by YouTube through YouTube Studio. 8. User Control And Changes To This Policy Users retain control over the connected channel and the YouTube actions performed by the Scheduler. If Ryva materially changes the types of Google user data accessed or the purposes for which that data is used, this policy will be updated and users will be asked to provide any additional consent required before the new access or use begins. 9. Google Api Services User Data Policy And Limited Use Ryva Tech'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: https://developers.google.com/terms/api-services-user-data-policy 10. Contact Questions, complaints, access requests, revocation requests, and deletion requests concerning the Scheduler or Google user data may be directed to: Ryva Tech Website: https://ryva.ca/ Email: rhean@ryva.ca