Privacy policy.

1. Scope & contact

This policy describes data handled by the VideoForge team through videoforge.uz, the associated web application and backend, connected VideoForge Workers, and the Chrome extension listed as VideForge. Some web-service features are in development or available only when enabled. The processing described below applies when you use the corresponding feature.

For privacy questions, access or deletion requests, contact sadulagulbekov@gmail.com or @videoforge_admin on Telegram.

2. Data handled by the Chrome extension

The public VideForge extension connects a Chrome profile to your VideoForge workspace. It handles enabled Google Flow image/video tasks and analytics for the YouTube Studio channel you link. A separate operator extension handles Google Vids speech tasks.

• Connection and account details: the pairing code, device identifier and device credential; provider settings, availability and quota/status information. The public extension does not request the Chrome profile email. Provider connection details can include an account identifier hash and account label.
• Task content: prompts, text, reference media, task identifiers and status, and generated images, video or audio needed for your requested tasks. Task inputs reach the selected Google service, and results are returned to VideoForge.
• YouTube Studio data: the selected channel identifier and available video metadata, including video identifiers, titles, visibility, publication dates and available views, likes and comments. Collection focuses on realtime activity over the supported 60-minute and 48-hour windows and available subscriber data. It can include private or unlisted video metadata belonging to that channel. This is not a complete channel history or a guarantee that every metric is available.
• Supported-page activity: URLs of relevant Flow and Studio tabs are read to find the workspace and verify the selected channel. A Flow workspace URL can be stored locally to reopen it. The extension observes relevant page/network responses to detect task results and read selected Studio data. It does not collect general Chrome browsing history, unrelated website activity, keystrokes or personal messages.

The extension sends connection details, task results and selected channel analytics to the VideoForge backend. Google passwords and sign-in cookies are not sent to VideoForge by the extension; the Google pages use the session already present in Chrome. The extension does not provide checkout or collect payment-card details.

All executable extension code is included in its package. Backend messages supply task data, not remotely hosted JavaScript or WebAssembly.

3. Data handled by the website, web application & backend

• Your service account: Telegram user identifier and verified sign-in identity, your chosen display name, account settings, session and connection identifiers, and account/device status. Telegram sign-in does not give VideoForge access to your Telegram chats.
• Your workspace: channels, project settings, ideas, scripts, scenes, prompts, assistant conversations and attachments, uploaded reference media, generated outputs, production task history and publication metadata. Media may be stored by the backend and/or a connected Worker on your computer.
• Connected devices: device labels, software versions, last connection time, provider availability, resource/task status, linked channel/profile identifiers and authentication credentials needed to authorize the device.
• Billing, when enabled: plan and credit balances, orders, amounts, transaction identifiers and payment status. Checkout is handled by Paycard; VideoForge's checkout integration does not receive or store your full card number or card security code. This web-service processing is separate from the Chrome extension.
• Technical data: requests reveal connection metadata, such as IP address, to the servers handling them. Application diagnostics record timestamps, status/error codes and related account, device, project or task identifiers. Hosting infrastructure may also record request URLs, browser information and response status for operation and security.

The landing page uses local storage to remember your language. The web application uses session cookies and related security data for sign-in. The landing page does not include advertising trackers or a third-party analytics SDK.

4. How we use & share data

We use this information to authenticate you and your devices, run the production tasks you request, transfer and display results, synchronize selected channel analytics, maintain billing records when applicable, troubleshoot failures and protect the service.

Data is shared as needed for the feature you use:

• VideoForge infrastructure and your connected devices process and store the account, workspace and task data needed to deliver the service.
• Google services process Flow, Vids and YouTube tasks. When you request publication, your video and chosen publication metadata are sent to YouTube.
• Telegram handles the sign-in you initiate and any message you choose to send to our Telegram support contact.
• OpenRouter and the selected model provider process text, context, media or audio supplied for the AI feature you request. Enabled speech and stock-media features may send their required text or search queries to Microsoft speech services, Pexels or Pixabay.
• Paycard processes enabled checkout and returns order/payment status. Our email or Telegram provider processes support messages you send through that channel.
• A configured channel-promotion provider, if you enable that feature, receives the public YouTube video URL, selected service and requested quantity; VideoForge stores the resulting order identifier and status.

These services handle information under their own policies, including Google, Telegram and OpenRouter. Review the provider you select before submitting confidential material.

We do not sell personal data or transfer it for unrelated purposes, advertising or credit decisions. People may read personal or sensitive extension data only with your explicit consent for the specific data concerned (for example, to resolve a support request), when necessary for security or legal compliance, or as aggregated, anonymized data used for internal operations. Other disclosures are limited to applicable legal requirements, protection against fraud or abuse, or a change of business ownership subject to these privacy commitments.

Chrome Web Store Limited Use: VideForge's use and transfer of information received from Chrome and Google services follow the Chrome Web Store User Data Policy, including its Limited Use requirements. Extension data is used only to provide or improve its stated production and analytics features.

5. Storage & retention

• Extension settings and credentials are kept in Chrome-managed local/session storage, not Chrome Sync, until cleared or the extension is removed. Bounded task receipts may remain locally for recovery.
• Temporary extension media has an expiry of up to 24 hours before backend acknowledgement and up to 10 minutes after acknowledgement. Expired entries are removed during later cache operations; acknowledged entries may be removed earlier to free space. Closing Chrome does not itself immediately erase the cache.
• Channel analytics follows the channel's retention setting: 90 days by default, configurable from 7 to 730 days. Older snapshots are pruned when a new snapshot is accepted; disabling collection does not immediately erase older snapshots.
• Application diagnostics uses a 30-day retention window, with older entries removed by service maintenance.
• Account, workspace, media, task and billing records do not share one automatic expiry. They are retained to provide your workspace and its history, until an applicable deletion request is handled, or for necessary accounting, security and dispute-resolution purposes. Removing a project or conversation from the interface can hide it while retaining its content or task history.

Removing the extension does not erase information already received by the backend, files on your Worker, or data in Google or other provider accounts. Backups and hosting logs have separate lifecycles; contact us for the retention and deletion arrangements applicable to your account. Local files and provider copies may require deletion through their respective device or service.

6. Your choices & deletion requests

You can disable Flow in the public extension popup, change the linked channel's analytics settings, unlink or revoke a device in VideoForge, sign out, or remove the extension. Revocation prevents further authorized requests once enforced by the service; it does not automatically delete existing data.

To request access, correction or erasure of account or backend data, email sadulagulbekov@gmail.com or contact @videoforge_admin. Include enough information to identify your VideoForge account and the data concerned. Do not send passwords, device credentials or sign-in codes. We may ask you to verify account ownership before acting. Account-wide erasure is handled through support rather than an automatic deletion button.

We will explain any information that must be retained for legal, accounting or security reasons. Changes or deletion in VideoForge do not automatically change information held independently by Google, Telegram, AI providers or your local devices.

7. Security

Public backend connections use HTTPS and secure WebSockets. The service authenticates sessions and devices and checks account ownership before granting access to workspace data. Diagnostic summaries are designed to exclude prompts, media and authentication secrets.

Extension credentials and caches rely on Chrome and your device's storage protections. Worker credentials are stored on the connected computer with operating-system access restrictions. This policy does not promise additional application-level encryption of every local file or backup. Protect access to your browser profile and connected devices.

8. Changes to this policy

We publish updates on this page and change the date above. If a feature introduces materially different data handling, we will update the relevant disclosures and obtain consent where required before that processing begins.

Privacy contact: sadulagulbekov@gmail.com · Telegram support