Effective date: November 20, 2026
Privacy Policy
This policy explains how easyvideo handles account information, video projects and connected YouTube data.
Information we process
We process the account information needed to sign you in, your project scripts, messages, media and export records, and the preferences you save. AI and media service providers receive the content required to perform creation requests you make. Do not include information you do not want those services to process.
Google and YouTube API Services
Connecting YouTube is optional. We use Google's OAuth authorization flow and receive authorization tokens, the connected channel's identifier, name and handle, and available channel and video statistics. We read video processing status and actual visibility to report publishing results. We do not receive your Google password.
We use this information to identify your selected channel, carry out publishing requests you explicitly confirm, and show status and statistics to you. When you confirm a post, we send the selected video, title, description, privacy settings and content disclosures to YouTube. Scheduled uploads and statistics synchronization can run when your browser is closed.
Google and YouTube data is not used to train general-purpose AI models, sold, or used for advertising. OneShot, now branded easyvideo, uses YouTube API Services. Our use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Storage and access
We store project and publishing data on servers used to operate easyvideo. OAuth tokens are encrypted at rest, and project and publishing access is restricted to the associated account. Hosting and infrastructure services process data as needed to deliver the service. Session cookies keep you signed in; browser storage retains preferences and local export recovery files. Uploading an MP4 to Publishing Center sends a copy to our server; exporting a video locally alone does not submit it to YouTube.
Retention and deletion
Projects and uploaded media remain available until removed through the applicable product controls. Publishing records and the latest statistics are retained to provide your publishing history. Video statistics snapshots are kept for up to 30 days for YouTube. Unfinished upload sessions expire after 24 hours.
In Publishing Center → Channel accounts, “Delete YouTube data and disconnect” removes your stored YouTube connections, credentials, publishing records, statistics and copies made for queued posts from the live application, and requests Google authorization revocation. This does not delete your creative projects or source MP4s, or videos already uploaded to YouTube. You may remove source media by deleting its project. An upload already submitted to YouTube may still finish.
Ordinary “Disconnect” stops further synchronization, removes local connection credentials and cancels pending tasks; it preserves publishing history. To delete the history as well, use the separate data deletion action. You may also remove access in your Google Account permissions settings. If remote revocation cannot be confirmed, the product tells you to check these settings. Independent backups may retain earlier copies until their backup retention cycle expires; restored data must be checked against subsequent deletion requests before use.
Your choices
You choose whether to connect a channel, which video to publish, its visibility, and whether to publish now or schedule it. You can cancel pending tasks before submission. Use YouTube to manage videos that have already been submitted.
See Google's Privacy Policy for Google's data practices.
Contact and changes
You can manage your YouTube connection and delete its stored publishing data in Publishing Center → Channel accounts. The Google consent screen also identifies the application support contact.
We may update this policy when our features or data handling change. The date below identifies this version.