YOUR DATA, EXPLAINED

Privacy Policy

Last updated 2 November 2026

1. Scope and service operator

This policy describes data handling by the AutoVideo service available on this website. The service is administered by its deployment operator and is intended for authorized accounts and integrations. The public informational pages can be viewed without signing in.

AutoVideo uses YouTube API Services for connected-channel publishing. Google's handling of information is described in the Google Privacy Policy. Facebook and other configured providers process information under their own policies.

2. Information AutoVideo handles

InformationPurpose
Uploaded videos and images; titles, descriptions, hashtags, and tagsPrepare, preview, store, and publish the content submitted by an authorized operator.
Channel and page identifiers, names, publication times, audience and synthetic-content settingsTarget the authorized destination and apply the selected publishing instructions.
Approval records, upload progress, video/post identifiers, status, timestamps, and error historyOperate schedules, resume uploads, display history, and investigate failures.
Google OAuth client credentials and access/refresh tokensMaintain the connection that an owner authorizes for their YouTube channel.
Facebook Page access tokens, authorized Page names/IDs, granted permissions/tasks, and connection-change historyConnect selected Pages, publish authorized content, validate connections, and identify credential changes. Database Page tokens are encrypted; existing environment tokens may remain in protected server configuration.
Administrator login/session information and API-key identityControl access and attribute authorized actions.
Operational web-server recordsThe hosting server may record IP addresses, request times, browser information, paths, and errors for security and troubleshooting.

AutoVideo does not request or store your Google or Facebook account password. Platform sign-in and consent take place on the provider's services. Admin password confirmation is for the separate AutoVideo administrator account.

Facebook Page authorization

Facebook connection is available only to authorized AutoVideo administrators. After Facebook consent, the server exchanges authorization for a long-lived user token, retrieves the Pages the account is permitted to manage, and lets the administrator select which Pages to connect. Short- and long-lived user tokens are not saved. Pending Page choices are encrypted, expire after ten minutes, and are purged on management access or startup; unselected choices are discarded after import.

Selected Page tokens are encrypted in SQLite using a separately configured Facebook encryption key. Page names, identifiers, connection status, and credential-change history are retained for administration. Page permissions and tasks are used only to establish the requested publishing access. Facebook credentials are not sent to content-generation providers.

Disconnecting a Page removes its database token and disables further local operations. Existing environment tokens remain in server configuration unless the operator removes them. Disconnecting does not revoke Meta authorization, delete Page content, erase publishing history, or undo a publication already accepted by Facebook. Revoke access separately in your Facebook business integration settings and contact the administrator to request local deletion.

3. Google authorization and use of YouTube data

The connection requests the youtube.force-ssl OAuth scope, which supports the video's upload and management operations needed by this service. AutoVideo uses the authorization to identify the connected channel, upload approved content privately, read processing and publication status, and set or remove a publication schedule.

Authorization tokens let the service perform these approved operations while the administrator is offline. AutoVideo stores them encrypted in its SQLite database, with the encryption key configured separately by the deployment operator.

Information received through Google APIs is used to deliver the publishing and status features described here, following the Google API Services User Data Policy and its Limited Use requirements. AutoVideo does not sell this data, use it for targeted advertising, or use it to train generalized artificial-intelligence or machine-learning models.

Authorized administrators can view submitted content and publishing records to operate the service. Access to Google data for other support or troubleshooting work requires the account owner's permission, except where needed for security or compliance with applicable law.

4. Sharing, providers, and security

Publishing sends the selected media, metadata, and publishing settings to YouTube or Facebook. The destination platform determines the eventual audience and processes the content under its own terms. Authorized external tools can submit content to AutoVideo using the permissions assigned to their API keys.

Video or image generation features may send supplied prompts or media requests to the AI, speech, or stock-media providers configured by the service operator. Google OAuth credentials are not included in those requests.

The hosting operator and authorized administrators can access the records and files needed to run, maintain, back up, and troubleshoot this deployment. Data may also be disclosed when required by applicable law or to investigate abuse or security incidents. No data is sold to advertisers.

Access controls, approval requirements, encrypted Google credentials, and HTTPS deployment are used to protect the service. Uploaded image and scheduled-video workflows remove source container metadata as part of preparation; this does not remove information visible or audible in the content itself. No storage or transmission system can guarantee absolute security.

5. Cookies and public pages

AutoVideo uses essential session cookies for administrator sign-in and request protection. The public pages do not add advertising trackers, third-party analytics, or social-media embeds. Following an external link or publishing through a connected provider involves that provider's own services and policies.

6. Retention and deletion

Uploaded assets, schedules, approval history, and publication records are retained on this deployment for publishing operations and the administrator's history needs. The current service does not automatically purge these records on a fixed schedule; removal is handled by the service administrator.

Request removal of your stored uploads, channel information, or publishing history through the contact below. The administrator may need to verify ownership before fulfilling a request. Backups are managed separately and may retain earlier copies until the operator rotates or removes them.

Disconnecting a YouTube channel in AutoVideo removes its stored authorization tokens and disables further local uploads. It does not delete the channel's other local records, delete videos on YouTube, or cancel publication schedules already accepted by YouTube. Those actions must be handled separately.

7. Control and revocation

You can cancel eligible scheduled items through AutoVideo before they publish. For YouTube items, the service confirms remote schedule removal before marking a cancellation complete. Review existing YouTube schedules before disconnecting a channel.

You can revoke AutoVideo's Google access at any time through Google Account third-party connections. Revocation prevents future authorized API access but does not, by itself, delete data already stored in AutoVideo or content already sent to a platform. Contact the administrator for local data deletion, and use YouTube Studio or Facebook to manage remote content.

8. Updates

This policy may be updated when service behavior or data practices change. The date above identifies the current version. Material changes should be reviewed before continuing to use connected-channel features.

9. Privacy questions and requests

For support, privacy questions, or a request to remove stored data, contact the AutoVideo service administrator at support@eztechapp.helphonic.com.

Identify the relevant channel or page and describe the data you want reviewed or removed. Never include passwords or authorization tokens.