Privacy Policy

Last updated 15 August 2026 · Wedio is operated by Aivigator Inc., a Texas corporation (USA).

The short version

Wedio reads your YouTube channel's data so it can tell you which videos are losing viewers and what to do about it. We use that data for exactly one thing: running the features you see in the app. We do not sell it, we do not share it with advertisers or data brokers, and we do not train AI models on it. Nothing on your channel changes unless you press the button that changes it. You can disconnect at any time, and everything we hold is permanently deleted within three days, or immediately, if you'd rather not wait.

Google user data at a glance

The first three permissions below are requested only when you connect a YouTube channel. Signing in to Wedio asks for none of them.

The wording above is exactly what Google shows you on the permission screen when you connect a channel. In Google's technical terms these are the scopes youtube.readonly, youtube.force-ssl and yt-analytics-monetary.readonly, plus openid, email and profile for signing in.

What we collect

• Raw Google user data. Everything listed in the table above, read through the YouTube API Services with your authorisation.
• Data we derive from it. Diagnoses of why a video underperformed, suggested titles, descriptions and thumbnails, retention analyses that line up your caption text against the moment viewers left, and before-and-after measurements of changes you approved. This is derived from your channel, so we treat it exactly like your channel data.
• Public information about other videos. To show you what is working in your subject area, Wedio starts from your own YouTube report of which videos yours was being suggested alongside, and then looks up public details of those videos and channels: titles, view counts, durations and publish dates. All of it is information any viewer can see on YouTube. We never combine your data with another Wedio customer's.
• Aggregated, anonymised signals. Counters that record how often each type of improvement helped, hurt, or made no measurable difference across all channels. These are numbers only: no channel identifier, no video identifier, no titles, no text, nothing that could be traced back to you or reconstructed into your content.
• Your account and your decisions. The email address and basic profile of the Google account you sign in with, which suggestions you approved, rejected or reverted, and your plan and usage if you're on a paid plan.

What we do with it

We use your Google user data solely to provide and improve the features you use in Wedio: to diagnose where a video is losing viewers, to draft changes for you to approve, to apply the changes you do approve, to publish videos you upload yourself, and to measure honestly whether any of it worked.

The aggregated, anonymised signals described above are used to improve which suggestions Wedio makes across all accounts. Because they carry no identifiers and no content, they cannot be linked back to your channel.

We do not sell your data, rent it, or share it with advertisers or data brokers. We do not use Google user data for advertising of any kind, for building advertising profiles, for credit, lending or insurance decisions, or for any purpose other than providing and improving the user-facing features described in this policy.

Who your data is shared with

Wedio uses a small number of service providers to operate. Each acts as our processor, receives only what its job requires, is bound by contract to use it solely to provide that service to us, and never receives your Google credentials. This list is exhaustive.

Everything else, from the database and the cache to the file storage and the servers themselves, is infrastructure we run and control. Your channel data is not handed to a third-party data platform.

We may also disclose data where we are legally compelled to, or as part of a merger or acquisition, in which case we would notify you first.

How we protect your data

The permissions Wedio asks for are sensitive, so here is specifically how the data behind them is protected. These are the controls that are actually in place, not aspirations.

Encryption in transit

Every connection to Wedio is encrypted with TLS 1.2 or 1.3 and modern cipher suites; older protocols are refused outright. Plain HTTP requests are redirected to HTTPS, and we send an HSTS header with a two-year lifetime covering all subdomains, so browsers refuse to connect insecurely even if asked to. Every call we make out to Google and to the providers listed above is encrypted the same way.

Your Google credentials

The long-lived token that lets Wedio act on your channel is encrypted with AES-256-GCM before it is stored, with a unique initialisation vector for every record and an authentication tag verified on every read, so a tampered value fails rather than decrypts. The encryption key is a deployment secret that appears nowhere in our source code.

The short-lived access tokens are never stored at all. They are requested from Google when needed, held only in memory, and expire within the hour. Neither kind of credential is ever sent to your browser, written to a log, or given to any third party, including the AI models that generate your suggestions. Our logging censors credential-shaped fields automatically, so a token cannot reach a log even by accident.

Where your data lives, and who can reach it

Your data sits on servers we operate. Only the web server is reachable from the internet: the database, the cache and the file storage publish no public port and can only be reached across a private network internal to our infrastructure. The host firewall accepts nothing but secure administration, HTTP and HTTPS. The database, cache and object storage run with all Linux capabilities dropped, and the credentials for them are delivered to the running containers as secrets rather than built into the images or written into configuration files.

To be precise about what that does and does not mean: your Google credentials carry the additional layer of encryption described above. The rest of your channel data is protected by these network, access and account controls rather than by field-level encryption.

Account isolation

Every request that touches channel data resolves that channel through its owner. A channel that isn't yours does not return a permission error; it does not exist as far as your session is concerned. Sessions expire after eight hours. Access to the app is granted from an allow list that is re-checked on every request rather than only at sign-in, so removing an account takes effect immediately instead of whenever the person next logs in. Where a password is used it is stored hashed with bcrypt, and repeated failed attempts lock the account temporarily.

What the AI can and cannot do

The AI components that write your diagnoses and suggestions run with deliberately limited authority. They hold short-lived tokens, valid for thirty minutes, scoped to a single channel, and restricted to an explicit allow list of endpoints: reads, plus the ability to write a draft suggestion inside Wedio. None of those endpoints can reach YouTube, and they are never given your Google credentials. The most an AI component can do is put a draft in front of you; your approval is the only thing that reaches your channel.

Every change is recorded

Each change Wedio makes to your channel is written to an append-only audit log capturing what it was before and what it became, so it can be reviewed and, where YouTube allows it, reversed. You can read that log yourself in the app.

Staff access

Access to production systems is limited to the people who need it to run the service. Our support tooling, which lets a named administrator view an account to help with a problem, is disabled by default behind a deployment-level switch, only ever grants fewer privileges than the administrator already has, and stamps that administrator's identity onto every action recorded while it is in use.

Beyond that, we do not read your channel data except when you ask us to help with a support request, when we need to investigate a security or abuse problem, when we are legally required to, or in the aggregated and anonymised form described earlier.

If something goes wrong

If we discover a breach affecting your personal data we will investigate and contain it immediately, and notify affected users and, where required, the relevant regulators without undue delay and within 72 hours of confirming it.

If you believe you've found a security vulnerability in Wedio, please email wedio@aivigator.com with "Security" in the subject. We will acknowledge your report, and we will not pursue legal action over good-faith security research.

Retention and deletion

• While your channel is connected. Day-by-day analytics are kept for 90 days and then folded into monthly summaries. Caption text, diagnoses, suggestions, measurements and the audit log are kept for as long as the channel is connected, because that history is what lets Wedio compare a change against your own past performance.
• Disconnecting a channel removes it from Wedio immediately. Everything we hold for it is then permanently deleted after a 3-day grace window: analytics, caption text, diagnoses, suggestions, generated images, measurements, the audit log and the archived raw reports. Reconnecting inside that window restores your history; after it, the data is gone.
• Deleting immediately. A disconnected channel can be purged right away from Settings, with no waiting period.
• What survives, and why. Two things. The aggregated, anonymised counters described above, which carry no identifier and no content and so cannot be tied to you. And billing and usage records, which we are required to retain for accounting and tax.
• Revoking access. You can revoke Wedio's access to your Google account at any time from your Google account permissions page, independently of anything you do in Wedio.

Making changes to your channel

Wedio never changes anything on your channel on its own. There are exactly two ways a change can happen, and both begin with you.

• Suggestions you approve. Wedio drafts a change and it waits in your inbox. Nothing touches YouTube until you approve that specific change. This covers titles, descriptions, translated metadata, thumbnails, subtitle tracks and playlists. Approved changes are logged, and most can be reverted from the app, and reverting a subtitle track removes exactly the track Wedio added, and nothing else.
• The Publish workspace. If you choose to publish through Wedio, you select a video file from your own device, review the title, description, thumbnail and subtitles that Wedio proposes, and press publish or schedule. Your video file uploads from your browser straight to YouTube; it does not pass through our servers. If the video already has a subtitle track in the same language, replacing it requires a second, explicit confirmation, and we archive the existing track before it is replaced.

Wedio does not delete your videos. It does not post comments, rate videos, or subscribe to channels on your behalf.

Google API Services and Limited Use

Wedio uses YouTube API Services. By using Wedio you also agree to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy.

Wedio's use of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Concretely, that means all four of the following:

• We use Google user data only to provide and improve the user-facing features described in this policy, never for advertising, never to build advertising profiles, and never for credit or lending decisions.
• We do not transfer Google user data to others except as necessary to provide those features (the processors named above), to comply with applicable law, or as part of a merger or acquisition with notice to you. We never transfer or sell it to data brokers, advertisers, or information resellers.
• We do not allow humans to read your Google user data, except with your consent for a support request you raise, where necessary for security purposes such as investigating abuse, to comply with applicable law, or where the data has been aggregated and anonymised for internal operations.
• We request only the permissions our shipped features actually need. Where YouTube offers a narrower permission that can do the job, we use it.

AI and machine learning

Wedio's suggestions are generated by Google's Gemini models, which receive your channel data as described above and return the diagnosis, wording or image you see in the app.

• We train no models. Wedio does not develop, train, or fine-tune any AI or machine learning model on your data: not on your content, not on your analytics, not on your revenue.
• Nor does anyone else, on our behalf. Your data is sent to those models for the single purpose of producing your own output, and is not used to develop or improve generalised models.
• No cross-customer learning from your content. The only thing Wedio learns across accounts is the aggregated, anonymised counters described earlier, which record only which kinds of suggestion tend to work. They contain no content and no identifiers.

Your rights

You can request a copy of the personal data we hold about you, ask us to correct it, ask us to delete it, or object to how we use it, by emailing wedio@aivigator.com. Disconnecting and deleting your channel from Settings already removes the channel data we hold, without needing to ask.

Children

Wedio is not directed to children under 13, and we do not knowingly collect their data.

Changes to this policy

If we make a material change we will update the date above and, where the change is significant, notify you by email. If a new service provider begins receiving Google user data, it is added to the list above in the same release that introduces it.

Contact

Aivigator Inc., a Texas corporation (USA), wedio@aivigator.com
100 N Central Expressway, Suite 914, Richardson, TX 75080-5326, USA