<article class="google-policy" aria-labelledby="live-google-policy-title">
  <h2 id="live-google-policy-title">Privacy Policy for Live - Ryva Live Broadcast Scheduler</h2>

  <p><strong>Effective date:</strong> September 15, 2026</p>
  <p><strong>Application name shown by Google:</strong> Live</p>
  <p><strong>Application developer and data controller:</strong> Ryva Tech</p>

  <p>
    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 is the complete description of how the Scheduler accesses,
    uses, stores, shares, retains, and deletes Google and YouTube user data.
  </p>

  <h3>1. Google services and authorization</h3>

  <p>
    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
    <strong>https://www.googleapis.com/auth/youtube.force-ssl</strong> authorization scope because
    creating, updating, and binding live broadcasts requires permission to view and manage the
    user's YouTube account.
  </p>

  <p>
    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
    <a href="https://www.youtube.com/t/terms">YouTube Terms of Service</a>. Google's own handling
    of information is described in the
    <a href="https://policies.google.com/privacy">Google Privacy Policy</a>.
  </p>

  <h3>2. Google and YouTube user data the Scheduler accesses</h3>

  <p>After the user authorizes a YouTube channel, the Scheduler accesses these specific categories of Google user data:</p>

  <ul>
    <li>
      <strong>YouTube channel identity:</strong> the authorized channel's YouTube channel ID and
      channel display name. These are used to confirm and display which channel is connected.
    </li>
    <li>
      <strong>YouTube live-stream information:</strong> 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.
    </li>
    <li>
      <strong>YouTube live-broadcast information:</strong> 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.
    </li>
    <li>
      <strong>Google OAuth credentials:</strong> OAuth access and refresh tokens issued after the
      user grants permission. These tokens are used to authenticate authorized API requests and keep
      the schedule operating without asking the user to sign in before every broadcast.
    </li>
    <li>
      <strong>Google and YouTube API responses:</strong> limited technical response and error data
      needed to complete, confirm, or troubleshoot the authorized scheduling operations.
    </li>
  </ul>

  <h3>3. How the Scheduler uses Google user data</h3>

  <p>The Scheduler uses the Google and YouTube user data listed above only to provide these user-facing functions:</p>

  <ul>
    <li>Confirm and display the YouTube channel selected by the user;</li>
    <li>Find and match the authorized channel's reusable live stream to the stream configured in OBS Studio;</li>
    <li>Create scheduled YouTube live broadcasts on the authorized channel;</li>
    <li>Generate date-specific broadcast titles and descriptions from templates entered and saved by the user;</li>
    <li>Set or update the scheduled start time and end time selected by the user;</li>
    <li>Set the visibility selected by the user: public, unlisted, or private;</li>
    <li>Bind each scheduled broadcast to the reusable YouTube live stream;</li>
    <li>Enable automatic start, automatic stop, DVR, and recording from the beginning;</li>
    <li>Apply the Scheduler's disclosed "not made for kids" broadcast setting; and</li>
    <li>Display connection, scheduling, and automation status to the authorized user.</li>
  </ul>

  <p>
    The Scheduler performs these actions only for the YouTube channel the user authorizes and only
    in accordance with 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.
  </p>

  <h3>4. Google data the Scheduler does not access or use</h3>

  <p>
    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.
  </p>

  <p>
    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.
  </p>

  <h3>5. Storage and security of Google user data</h3>

  <p>
    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.
  </p>

  <p>
    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.
  </p>

  <p>
    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.
  </p>

  <h3>6. Sharing, transfer, and disclosure of Google user data</h3>

  <p>
    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.
  </p>

  <p>Google user data may be disclosed only in these limited circumstances:</p>

  <ul>
    <li>To Google and YouTube to provide the requested scheduling and broadcast-management functions;</li>
    <li>
      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 support purpose requested; or
    </li>
    <li>
      When disclosure is required by applicable law or valid legal process, or is reasonably necessary
      to investigate fraud, abuse, or a security incident.
    </li>
  </ul>

  <p>
    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.
  </p>

  <h3>7. Data retention, refresh, and deletion</h3>

  <p>
    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.
  </p>

  <p>
    A user may request deletion of the Google and YouTube data stored by the Scheduler by emailing
    <a href="mailto:rhean@ryva.ca">rhean@ryva.ca</a>. 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.
  </p>

  <p>
    Users may also revoke the Scheduler's Google authorization at any time through
    <a href="https://security.google.com/settings/security/permissions">Google's security settings</a>.
    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.
  </p>

  <p>
    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.
  </p>

  <h3>8. User control and changes to this policy</h3>

  <p>
    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.
  </p>

  <h3>9. Google API Services User Data Policy and Limited Use</h3>

  <p>
    Ryva Tech's use and transfer to any other app of information received from Google APIs will adhere
    to the
    <a href="https://developers.google.com/terms/api-services-user-data-policy">Google API Services User Data Policy</a>,
    including the Limited Use requirements.
  </p>

  <h3>10. Contact</h3>

  <p>
    Questions, complaints, access requests, revocation requests, and deletion requests concerning the
    Scheduler or Google user data may be directed to:
  </p>

  <p>
    <strong>Ryva Tech</strong><br>
    Website: <a href="https://ryva.ca/">https://ryva.ca/</a><br>
    Email: <a href="mailto:rhean@ryva.ca">rhean@ryva.ca</a>
  </p>
</article>