VVero

Legal

Privacy Policy

Effective date: July 15, 2026

Overview

This Privacy Policy explains how Vero collects, uses, stores, and protects information when you use the Vero website, desktop app, and related services.

Information We Collect

How We Use Information

We use information to:

Desktop Product Model

Vero is built around a desktop workflow. Drafts, planning data, and media choices may remain on your device, while connected services may be used for secure account connections and the platform actions you request.

Google and YouTube Data

When you choose to connect YouTube, Vero uses Google OAuth to request access to the Google account and YouTube channel you select. Vero may access your basic Google profile and email address; your YouTube channel identity; and the videos, titles, descriptions, visibility settings, thumbnails, captions, playlists, processing status, comments, and replies needed for the features you use.

Vero uses this data only to show the connected channel in your workspace; upload or schedule videos you select; apply the video details, thumbnail, captions, and playlist choices you provide; confirm delivery and processing status; display channel comments in the Vero inbox; and send replies that you approve or that match an automation rule you intentionally enable. Vero does not support or access YouTube direct messages.

Vero stores encrypted Google OAuth credentials while the connection is active, along with the minimum channel, video, upload, comment, reply, and delivery identifiers needed to provide these features and prevent duplicate actions. Media selected for an upload or schedule may be staged temporarily until its configured expiration. Vero does not sell Google or YouTube user data, use it for advertising, determine creditworthiness, or use it to train generalized artificial-intelligence or machine-learning models.

Cloudflare processes encrypted credentials and related Google or YouTube data only as infrastructure needed to operate Vero. If you explicitly request an AI-assisted reply draft, only the content needed for that request may be sent to the configured model provider under the safeguards described below; it is not used for model training. Vero otherwise does not transfer Google or YouTube user data except when you direct Vero to send content to YouTube, when a service provider is necessary to operate a requested feature, when required by law, or as part of a business transfer with prior notice where required.

You can stop future Google access at any time from Google Account connections. You can also use Vero Support to request disconnection, access, correction, or deletion of the Google and YouTube data associated with your Vero workspace. A deletion request removes active OAuth credentials and associated Vero records unless limited records must be retained for security, fraud prevention, legal, or billing obligations.

Vero's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Third-Party Providers

Vero uses service providers to operate its cloud relay, database, media staging, email, optional payments, and optional AI-assisted features. These providers may include Cloudflare, Stripe, OpenRouter, and the model provider selected for an AI request. They process information only for the service being provided under their own terms and privacy commitments.

When you connect platforms such as YouTube, X, TikTok, Instagram, Facebook, or Threads, those platforms also process information under their own privacy policies. Vero does not sell connected-platform data or use it for unrelated advertising.

AI-Assisted Features

If you request an AI-generated strategy or inbox reply draft, Vero sends the business context and content needed for that request to the AI provider you selected or to Vero's managed beta provider. Managed OpenRouter requests require providers that deny data collection and support zero data retention. OpenRouter may retain request metadata such as token counts and latency, but the request content is not intentionally logged by Vero's managed configuration.

AI output is a draft. Vero does not automatically publish an AI-generated post or send an AI-generated customer reply without the approval required by the workspace. If no compatible privacy-preserving model is available, Vero uses a limited local rule-based fallback instead.

Retention and Security

We retain information only as long as reasonably necessary to operate the requested workflows, maintain security and delivery records, comply with obligations, resolve disputes, and enforce agreements. OAuth credentials and sensitive support content are encrypted at rest. No method of storage or transmission is completely secure.

Your Choices

You may disconnect connected accounts, stop using the service, or request deletion through Vero Support. Disconnecting stops future platform access; an account-deletion request removes associated Vero workspace and connected-platform data except records that must be retained for security, fraud prevention, legal, or operational obligations.

Contact

For privacy questions or deletion requests, use the support form and choose "Privacy or deletion request."