Privacy Policy

This Privacy Policy explains how Renda Video processes information when authorized users access the service, connect third-party accounts and use the creator workflow.

1. Information processed

Renda Video may process account identifiers, usernames, display names, profile images, OAuth authorization metadata, project information, scripts, generated-media references, publication settings, publication status, audit records and technical information needed to operate the service.

2. Connected social accounts

When you connect a supported social platform, authorization occurs through the provider's official OAuth flow. Renda Video does not request or store the password for your social account. Access and refresh tokens returned by supported providers are stored server-side and protected using application-level encryption.

3. YouTube API Services

Renda Video uses YouTube API Services to let an authorized user connect a YouTube channel, identify the authorized channel, upload an approved video at the user's direction, and check the processing and publication status of that upload.

For the current integration, Renda Video may access YouTube channel identifiers and public channel profile information required to identify the connected channel, together with OAuth authorization data and upload/publication status returned by the YouTube Data API. Renda Video does not collect or store the user's Google or YouTube password.

Renda Video uses information received from Google APIs only to provide the features explicitly requested by the authorized user. Renda Video does not sell YouTube API Data or use it for advertising profiles or surveillance.

Use of YouTube API Services is also subject to the YouTube Terms of Service and the Google Privacy Policy.

4. Google Drive and media storage

If Google Drive is connected, Renda Video may create, read or update files needed for the creator workflow according to the permissions you granted. Media files and related references may be stored so that approved content remains available across devices and deployments.

5. Why information is used

Information is used to authenticate users, protect accounts, maintain sessions, organize channels and projects, generate or retrieve media, display review material, connect authorized third-party accounts, submit content at the user's direction, track publication status, diagnose failures and improve service reliability.

6. AI providers

When an authorized user chooses or enables an AI provider, prompts or media necessary for the requested operation may be sent to that provider. Each provider operates under its own privacy and service terms. Renda Video is designed to send only information needed for the selected operation.

7. Data sharing

Renda Video does not sell personal information. Information may be transmitted to connected service providers only when needed to provide requested functionality, such as authentication, cloud storage, content generation or social-media publishing.

8. Security

The service uses measures such as password hashing, time-based two-factor authentication, protected server-side sessions, encrypted OAuth secrets and access controls. No system can guarantee absolute security, so access credentials and recovery codes should be kept private.

9. Retention and deletion

Project, media and publication records may be retained while needed for the creator workflow, security, backup and history. OAuth credentials and provider-authorized YouTube API Data are removed when the corresponding connection is disconnected or when deletion is requested, subject to data that must be retained for legitimate security or legal obligations. Authorized YouTube API Data associated with revoked consent is deleted as soon as practicable and no later than seven calendar days after revocation.

Deleting data stored by Renda Video does not delete content stored by YouTube. Content on YouTube must be managed using YouTube or another authorized client that provides the applicable deletion feature.

10. User choices and revocation

Authorized users can disconnect supported third-party accounts from Renda Video to stop future access. For YouTube, disconnecting the account revokes the OAuth authorization with Google and removes locally stored authorization credentials and YouTube API Data associated with that connection.

Users can also revoke Google access directly from Google Account third-party access settings. If authorization can no longer be refreshed, Renda Video will require the user to reconnect before performing further YouTube API actions.

11. Changes to this Policy

This Privacy Policy may be updated as the service evolves or integration requirements change. The effective date displayed above identifies the current version.