Privacy Policy

Google permissions and channel identity

When a YouTube channel is connected, Ruya requests the following Google OAuth permissions:

• https://www.googleapis.com/auth/youtube.readonly — used to read the names and identifiers of authorized channels so we can verify their identity and identify the intended publishing destination.
• https://www.googleapis.com/auth/youtube.upload — used to upload videos and their metadata to authorized channels, including for scheduled publishing.

Ruya uses this channel information to manage connected channels and direct uploads to the authorized channel selected in the tool.

Video library and publishing

Ruya handles the video files and metadata prepared for publication, such as video titles and descriptions. When a video is published, Ruya sends the video and its metadata to the selected authorized YouTube channel through the YouTube Data API.

Storage and service providers

OAuth tokens are stored on the virtual private server (VPS) and on the PC used to connect Google accounts. Tokens on the VPS allow Ruya to access authorized channels for scheduled publishing without requiring a new interactive sign-in for each upload.

Channel information is stored in a configuration file (channels.json) and a SQLite database. SQLite also stores video metadata, processing and publication statuses, published YouTube video IDs, and publishing schedules.

Source video files are stored in Cloudflare R2. During publication, video files and their metadata are sent to Google/YouTube through the YouTube Data API, using the VPS to run the publishing workflow.

Ruya also supports optional imports from Google Drive. When that feature is used, Google Drive is an additional source of imported files. The YouTube permissions listed above do not describe or authorize Google Drive access; the permissions and data handling specific to that optional integration still need to be confirmed.

The identified data flows involve Google/YouTube, Cloudflare R2 and the VPS, with Google Drive involved when optional imports are used. Ruya is deployed using Dokploy. The VPS hosting provider and the status of any automatic hosting backups remain to be confirmed.

Retention, temporary files, backups and logs

Ruya does not currently implement automatic cleanup based on a retention period. Source videos remain in Cloudflare R2 after publication. No fixed retention period is stated here because the actual retention rules have not yet been confirmed by the operator.

Temporary copies used for uploads are normally deleted at the end of processing. This is not a guarantee that every temporary copy is removed in every case.

A configuration backup exists on the VPS. The existence and handling of other hosting backups remain to be verified. Logs may contain filenames, identifiers and error messages. The retention and manual deletion arrangements for stored data, logs and backups have not yet been fully established.

Use of Google data

The Google data use identified in the inspected publishing workflow supports the channel management and video publishing features described in this policy. No AI-generation calls or mechanism for selling data were found in that workflow.

This finding is limited to the publishing workflow inspected. It does not establish the absence of AI-training uses elsewhere or certify overall compliance.

Ruya’s use and transfer of information received from Google APIs is subject to the Google API Services User Data Policy, including its Limited Use requirements. This policy describes the known implementation and its current limitations; it does not claim Google approval or certification.

Revoke Google access

You can revoke Ruya’s access at any time:

1. Open your Google Account’s third-party connections settings.
2. Select Ruya and review its access to your Google Account.
3. Remove Ruya’s access and confirm the change.

Revoking access prevents Ruya from making further authorized API requests using that permission. Scheduled uploads that depend on that access will no longer work unless the channel is authorized again. Revoking access does not itself delete stored token copies, files, channel information or publishing history held by Ruya.

Deletion capabilities and contact

Deleting a video from Ruya’s library removes its file from Cloudflare R2. It retains the SQLite history and does not delete the video published on YouTube. Published videos can be managed directly through YouTube Studio.

Ruya does not currently have a complete mechanism for deleting a connected account and all associated data. Library deletion and Google access revocation should not be understood as complete erasure of tokens, channel information, publishing records, schedules, logs or backups.

Anes L, the administrator of Ruya, handles requests sent to [email protected]. You may use this address for deletion requests or questions about stored data, identifying the relevant channel and data concerned. Do not send passwords or OAuth tokens.

A method under consideration for checking channel control is to ask the requester to temporarily place a code in the YouTube channel description, then check for its presence. This is a proposed verification method, not an established operational procedure.

A complete manual deletion procedure still needs to be implemented. Contacting the administrator does not mean that complete erasure is already available. No automatic deletion, completion deadline or deletion of backups is promised.

Details still to confirm or implement

• The operational process for verifying a requester’s control of the relevant YouTube channel.
• The VPS hosting provider and the status and handling of its automatic backups, if any.
• Implementation of a complete manual deletion process and confirmation of retention arrangements, including how stored copies, logs and backups can actually be handled.