Last updated: 2026-10-18
This policy covers the Charles St Bus Layover Monitor project ("this project"), a personal, non-commercial project operated by its developer. It explains how this project accesses, uses, stores, and shares data obtained through Google's APIs, specifically the YouTube Data API v3.
This project livestreams a fixed camera view of a public bus layover bay, with a live overlay showing bus-traffic and noise statistics, to a single YouTube channel owned and operated by the developer. A set of automation scripts, running on the developer's own server, manage that one channel.
This project accesses the YouTube account of its own developer only,
via that developer's own explicit one-time OAuth authorization. It
does not access, request, or process YouTube account data belonging
to any other person. Specifically, using the
youtube.force-ssl scope, this project:
Exclusively to operate this one YouTube channel's live-streaming automation as described above: rotating daily broadcasts, keeping video titles/descriptions/thumbnails current with live statistics, posting status updates to live chat, and recovering the stream automatically if it disconnects. This data is never used for advertising, profiling, analytics about viewers, or any purpose unrelated to operating this channel.
The OAuth credentials (a client ID/secret and a refresh token) that allow this automation to act on the developer's own channel are stored only in a configuration file on the developer's own self-hosted server. They are never transmitted anywhere other than to Google's own OAuth and YouTube API endpoints, and are not accessible to any third party.
This project does not share, sell, rent, or otherwise disclose any Google user data to any third party, for any purpose. There are no advertisers, analytics providers, or other integrations with access to this data.
Credentials are retained only for as long as this project continues operating the channel's automation. The developer can revoke this project's access at any time from their own Google Account permissions page, which immediately and permanently invalidates the stored credentials. To request deletion of any data related to this project, contact the address below.
This project's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
If how this project accesses or uses Google user data changes, this page will be updated accordingly.