Effective 18 October 2026
Privacy Policy
1. Controller and language
Vidlize is a trading name used by one individual resident in Italy who operates as a registered sole trader, not as a company. That individual is the data controller for Vidlize.
Contact: privacy@vidlize.com.
The English version is the controlling version to the extent permitted by mandatory law. Translations are provided for convenience.
2. Data we process
When you authorize Google and YouTube, Vidlize accesses, collects and stores only the following Google and YouTube data needed for the features you choose:
- Google identity data: account subject identifier, email address, display name and profile image;
- Google authorization data: granted scopes and a protected OAuth refresh credential; Vidlize never receives your Google password;
- YouTube channel data: channel identifier, title, thumbnail and uploads-playlist identifier;
- YouTube video data: video identifier, title, description, tags, category, thumbnail, publication time, privacy, upload and processing status, scheduled-publication time, duration, content type, live status, source and audio language, dimensions, view count, etag and existing title-and-description localizations;
- YouTube caption data when caption features are enabled: caption-track identifier, language, name, type, status, draft and availability flags, and the timed caption text and source file only for a track you ask Vidlize to process; and
- Vidlize working data linked to YouTube: translation drafts, selected languages and fields, review and publication choices, job status, publication identifiers, errors and quota usage.
Separately, Vidlize processes your language choices, account and product settings; protected AI provider keys; Stripe customer, subscription, invoice and payment identifiers, plan, currency and billing status; support messages, attachments and email-thread information; and limited security information such as IP address, session, browser, time and error events.
Vidlize does not store the complete card number or CVC.
3. Purposes and legal bases
Vidlize uses this data to create and secure your account, connect your YouTube channel, synchronize your video library, prepare and publish requested localizations, provide subscriptions and support, prevent abuse, diagnose failures and comply with legal obligations.
The legal basis for processing is performance of the contract or steps requested before entering into it, compliance with legal obligations, consent where required, and legitimate interests in security, service reliability and fraud prevention where those interests do not override your rights.
4. Google and YouTube
Vidlize uses Google OAuth and YouTube API Services only to provide the user-facing features you request and follows the Google API Services User Data Policy, including Limited Use requirements.
Google identity and YouTube API data is collected directly from Google and YouTube after you approve access, or from text and files you deliberately submit for a requested workflow. It is stored in Vidlize's protected database and private file storage. Vidlize uses it only to authenticate you; show and synchronize your channel library; classify, filter and select videos; prepare, review, publish, verify or delete the title, description, localization and caption changes you request; keep the latest displayed YouTube state; enforce plan and quota limits; recover requested operations; and diagnose errors and abuse.
Vidlize does not sell Google or YouTube data, use it for targeted advertising or use it to train unrelated general AI models.
Inside Vidlize you may remove an inactive channel candidate, replace the active channel subject to the applicable plan rules, or revoke Google access. Revoking Google access removes the authorization credentials and YouTube-derived working data but does not cancel your Vidlize account or Stripe subscription. Changes already published to YouTube are not removed.
You may also revoke Google access directly at:
https://security.google.com/settings/security/permissions
Google Privacy Policy:
https://policies.google.com/privacy
YouTube Terms:
5. Service providers and disclosures
Vidlize shares data only where necessary to provide the service.
This may include Google and YouTube, Stripe, Vidlize hosting and email providers, the AI provider you choose, and professional advisers or public authorities where disclosure is legally required.
Vidlize offers two distinct ways to use an external AI provider. In connected API-provider mode, Vidlize sends the selected title, description, source and target language information, and the translation instructions to the provider you configured.
In the manual "Your AI" mode, Vidlize prepares a prompt for you to copy into an AI service of your choice. Vidlize does not contact that AI service or receive its password or API key. An uploaded `.vidlize` translation file is treated as untrusted plain text, validated and never executed as code. It is processed in memory and not retained as an uploaded file; accepted translations are stored as ordinary Vidlize drafts and operation records under the retention rules in this Policy.
Some providers may process data in other countries under the safeguards required by applicable law.
Vidlize does not sell personal data.
If caption features are enabled for your account, Vidlize also processes selected YouTube caption-track identifiers, language, name, type, timing and text; caption source files and translation drafts; review choices; publication identifiers and operation status.
Only when you request caption translation, the selected caption text, timing, source and target languages, and translation instructions are sent to the AI provider you chose. Caption source files and drafts are kept in Vidlize private storage only as needed to provide, verify and recover the requested workflow.
6. Cookies, analytics and marketing technologies
Vidlize uses necessary cookies and similar technologies for authentication, security, session management and saved consent choices.
Language and display preferences are stored in the browser where required for the selected settings.
Optional analytics and marketing technologies are used only after the consent required by applicable law has been given.
These technologies may be used to understand how the website and service are used, measure performance and marketing effectiveness, and improve Vidlize.
With analytics consent, Vidlize uses Google Analytics 4 delivered through Google Tag Manager on both public pages and the signed-in service. Browser analytics can include a pseudonymous client and session identifier, page and interaction events, device and referral information, and campaign parameters. Vidlize also sends a limited set of confirmed product events from its server through Google Analytics Measurement Protocol: account creation, actual trial activation, first successful YouTube publication, checkout start and confirmed purchase. Those events may include plan, currency, value and non-identifying workflow attributes. Vidlize does not send your email address, name, Google or YouTube identifiers, video titles, descriptions or caption text to Google Analytics.
Analytics events that occur without analytics consent are not sent later. Withdrawing analytics consent stops future collection and suppresses queued server events that have not already been delivered. Marketing storage and Google advertising signals remain disabled unless marketing consent is also given.
Google Analytics event-level data is configured for a 14-month retention period. Vidlize keeps linkable analytics delivery records and daily activity records for no more than 90 days. Daily aggregate product counts may be retained longer without an identifier that links them to an individual account. Account deletion removes the account-linked analytics context and raw records; aggregate counts already detached from the account remain.
You can accept, reject or change optional analytics and marketing choices through the cookie settings.
Necessary cookies required for authentication, security and operation of the service do not depend on optional consent.
7. Retention
Active sessions last no more than 30 days.
Revoked sessions are removed after a short security period of no more than 7 days.
Stored YouTube API data is refreshed or deleted within the applicable 30-day period. Vidlize periodically verifies saved Google authorizations. If you revoke access in Vidlize, remove a channel, delete your account or make a valid deletion request, affected YouTube-derived working data and private files are permanently deleted as soon as possible and no later than 7 calendar days. If you revoke access directly in your Google Account, Vidlize deletes the affected data as soon as it detects that the authorization can no longer be refreshed and no later than 30 calendar days after revocation.
To prevent repeated free-trial abuse and enforce subscription limits, Vidlize may retain a pseudonymous channel-binding identifier and aggregate usage counters while the account or subscription remains active. These records do not contain YouTube titles, descriptions, videos or channel names. A short-lived anti-abuse marker may be retained for up to 30 days after the last verified connection and no more than 7 days after account deletion.
Resolved support correspondence and attachments are normally retained for 48 months. Information may be kept longer where necessary for an active dispute, security investigation, legal obligation or legal claim.
Operational logs use bounded rotation rather than a guaranteed fixed number of days.
Protected backups that may contain account data or YouTube Authorized Data expire after no more than 6 days.
To prevent restored backups from reintroducing data that was already deleted, Vidlize retains a short-lived deletion record outside those backups for no more than 7 days. It contains no Google or YouTube content.
Payment and accounting information may be retained where required by law, Stripe records or an active dispute.
8. Deletion and your rights
Account deletion is available after any active, trialing or past-due subscription has ended.
This self-service limitation does not prevent you from making a separate personal-data erasure request at privacy@vidlize.com. Vidlize handles such requests under applicable law; payment, legal or claims records that must be retained may remain for the periods stated in this Policy.
Deleting the account removes the account, channel connections, authorization credentials, channel-binding marker, drafts and private account files from the working service. Revoking Google access without deleting the account leaves the account, subscription and legally required payment records in place.
Limited support, payment, legal and backup records may remain only for the retention periods described above.
Depending on applicable law, you may request access, correction, deletion, restriction or portability of your personal data, object to processing based on legitimate interests, withdraw consent and lodge a complaint with a supervisory authority.
Contact:
Italian users may also contact:
9. Security, age and changes
Vidlize uses proportionate access controls, protected credentials, private storage, backups and security monitoring to protect account and service data.
No internet service can guarantee absolute security.
Vidlize is intended for users aged 18 or over.
This Privacy Policy may be updated when the service, providers or applicable law changes. Material changes will be communicated where required.
