Privacy Policy
Who operates this project
OneDayOneEvent is an independent, operator-run educational media project. Questions about this policy or privacy requests can be sent to infopanda04@gmail.com.
YouTube API Services and Google OAuth
OneDayOneEvent uses YouTube API Services and Google OAuth for its own operator-managed YouTube authorization. The client is not a consumer service: external users cannot sign in, connect accounts, or authorize their own channels.
The current integration is limited to authenticated preflight checks. It checks whether the project’s authorization is valid, whether required permissions are available, whether the configured channel binding is correct, whether the channel is linked for upload-capable use, and applicable long-upload eligibility. OneDayOneEvent does not currently use the integration to upload, publish, manage videos, collect analytics, monitor audiences, comments, subscribers, revenue, or other YouTube activity.
Your use of Google and YouTube is also governed by the Google Privacy Policy and the YouTube Terms of Service.
Information accessed and use
Accessed temporarily
For the limited preflight purpose described above, the project may access Google OAuth authorization status, required authorization permissions, and limited YouTube channel-status information needed to verify the configured operator channel and upload-capable readiness. This information is used only to validate the project’s authorization and configuration before any future capability is considered.
OAuth client credentials, access tokens, and refresh tokens are private runtime secrets. They are not public-site data and are not displayed on this site.
Retained in limited form
Limited normalized operational and compliance records may be retained, such as an authorization or preflight outcome, timestamp, retry classification, and internal publication-lifecycle or compliance facts. These records are not used for advertising, profiling, or consumer analytics.
Not intentionally retained
The current preflight contract does not intentionally persist raw YouTube API response bodies, channel identifiers, OAuth permission lists, access tokens, refresh tokens, or raw provider response bodies.
Sharing
OneDayOneEvent sends requests to Google and YouTube only as needed to provide the limited API functionality described in this policy. It does not sell YouTube or Google authorization/API information, use advertising or tracking scripts on this site, or share that information with unrelated third parties.
Authorization, revocation, and deletion requests
The operator can revoke Google authorization through Google Security Settings. OneDayOneEvent also supports an operator-managed revocation process. Revocation prevents future authenticated operations using that authorization.
For a privacy or deletion request, contact infopanda04@gmail.com. Requests are handled manually. There is no public self-service disconnect or deletion interface.
When authorization is revoked or an applicable deletion request is received, authorization-scoped preflight records are handled as soon as possible under the project’s applicable obligations and safe deletion controls. The project does not state a universal fixed retention period or promise automatic deletion in every circumstance.
Operator Terms of Use
This API Client is operated only by the OneDayOneEvent operator and is not offered to external users. By operating or using this API Client, the operator agrees to be bound by the YouTube Terms of Service.
Authorization validity and security
The project periodically checks whether its operator authorization remains valid. If authorization is unavailable or invalid, the matter requires operator review; it does not trigger automatic publication or other consequential action.
The project uses reasonable measures intended to protect its limited authorization information. No method of electronic storage or transmission is completely secure.
Updates to this policy
This policy may be updated if the project’s data practices change. Material changes to YouTube or Google API data handling will be reflected here before the changed functionality is used.