Privacy Policy

Last updated 6 November 2026

Vid0 (“Vid0”, “we”, “us”) is a YouTube creator-intelligence product made up of the website at vid0.in, its API and the Vid0 browser extension. It is owned and operated by Arindam Majumder. This policy explains what we collect, why, who we share it with, how we protect it and the choices you have. By using Vid0 you agree to it.

1. What we collect

  • Account details. When you sign in with Google we receive your name, email address and profile picture. If you sign up with an email address instead, we store that address, the name you give and a one-way hash of your password, and we email you the links that create the account and reset the password. We also store whether you use Vid0 as a creator or a brand, and the workspace you belong to.
  • YouTube data, only if you connect a channel. With your permission we read your channel's data through the YouTube Data API and YouTube Analytics API, using the read-only scopes youtube.readonly and yt-analytics.readonly. That covers your videos, their statistics, and analytics such as views, watch time, impressions, click-through rate and traffic sources. Vid0 never uploads, edits or deletes anything on YouTube.
  • Things you add. Competitors you track, saved ideas, collections of videos you save, titles, descriptions and thumbnails you ask us to score, media-kit details and pricing, and YouTube Studio exports (CSV or zip files) you upload. On a public media kit, uploaded numbers are labelled “self-reported”. A media kit can be published only for a channel you've connected, which shows it's yours; we keep a record of that (which channel and when) while your account exists, even if you later disconnect the channel.
  • Messages. When someone sends a partnership request or inquiry, we keep their name, email, company and message so we can respond.
  • Billing. If you buy a plan, our payment provider handles your card details. We only receive your plan, payment status and the provider's customer and subscription IDs.
  • Technical data. Server logs (IP address, browser, request times and errors), kept briefly to run and secure the service. We use a session cookie to keep you signed in, your browser's local storage for preferences such as layout and filters, and a first-party analytics cookie (below). We don't use advertising or third-party tracking cookies.
  • Product analytics. On vid0.in we use PostHog to learn how Vid0 is used: the pages you visit, where you came from, your browser, device and approximate location (from your IP address), and where you click and scroll. Some visits are recorded as session replays, so we can see where people get stuck. Replays never record what you type. In the signed-in apps, on media kits and on the sign-in pages, replays hide all text, labels, images and charts, and clicks are recorded without the text you clicked, so your YouTube Analytics data and Google account details never reach PostHog. When you're signed in, these events are linked to your Vid0 account ID, account type and plan, not your name or email. Our servers report to PostHog in the same way what happens there: signing up, connecting a channel (how many, and whether analytics access was granted, nothing about the channel), which Vid0 tools you use and the credits they cost, usage limits you reach, and payments and plan changes (amount, currency and plan). For AI features we record which model answered, how many tokens it used and how long it took, never what was asked or answered. When something breaks, the website and our API also send PostHog an error report: the error, where in our code it happened and the page or API route, never the content of your requests, and with database values removed. PostHog keeps a random identifier in a first-party cookie and your browser's local storage. If your browser sends Do Not Track or Global Privacy Control, nothing is collected in your browser and our servers don't report what you do, except that AI usage is still counted without your account ID and payments are still recorded against your workspace.
  • Creator page views. When someone opens a creator's public page on vid0.in, we count the visit so that creator can see how many people viewed their page. We store the day, the referring website's domain (never the full address) or the campaign tag in the link, the country looked up from the IP address by our web host, the type of device, and a visitor code made from that day's random key, the page, and the visitor's IP address and browser. A second code is made the same way from the IP address alone, so one network can't add endless visitors. The IP address itself isn't stored and no cookie is set. Each day's key is deleted when the day ends, so a code can't be traced back to anyone or matched across days. Only the page's own creator sees these numbers, and only as totals. Visits by the creator while signed in aren't counted.

2. The browser extension

The extension shows Vid0 data on youtube.com and studio.youtube.com. It reads only the address of the page you are viewing and the video and channel IDs in it; every title and number it shows comes from the YouTube Data API through our API. To fetch them, the extension sends our API only the video or channel IDs involved, never your browsing history. On Studio's comments pages it reads comment IDs and fetches their text from the YouTube Data API; we don't keep it. The view counts and earlier thumbnails it keeps on your device to show changes over time are deleted after 30 days. When you click a YouTube Studio assistant action, such as “Score title” or “Draft description”, it sends the title, description and tags you are working on, so we can return the result. When you click “Draft reply” on a viewer's comment in Studio, it sends that one comment and the commenter's handle; we read your video's public description to ground the reply and keep nothing. When you ask a question in the “Ask” tab on a video, it sends your question and that video's ID; the conversation is saved to your chat history on vid0.in, where you can delete it. When you save a video to a collection from the thumbnail button, it sends that video's ID and, for a new collection, the name you type. The extension never posts or saves anything in Studio for you: it fills a field, and you click Save or Reply. When you connect the extension to your account, it stores an API token in the browser's extension storage. You can revoke it from the extension's popup or in Settings. When you remove the extension, Chrome opens a page on vid0.in that asks why. Its address carries only the extension's version, whether it was connected to an account, how many days it was installed and on how many days (up to five) it showed data; answering is optional.

3. How we use it

  • To provide the features you use: outlier and keyword research, channel analytics, scores, AI suggestions, media kits and brand matching.
  • To broker brand partnerships you or a brand ask for. Requests go to the Vid0 operator, who contacts the people involved.
  • To secure the service, prevent abuse, fix problems and enforce plan limits.
  • To understand how Vid0 is used and improve it, with the product analytics described in section 1.
  • To contact you about your account, billing or important changes, and to send the weekly digest, which you can unsubscribe from.

We don't sell your personal data, and we don't use it for advertising.

4. YouTube API Services and Google user data

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

Vid0's 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.

How we use it. We use Google user data, meaning your Google account details and your connected channel's YouTube data and analytics, only to provide the Vid0 features you use: your channel dashboard, audits and scores, AI answers about your own channel, the weekly digest and verified stats on your media kit. We don't use it for advertising, we don't sell it, and we don't use it to train AI models. Vid0 doesn't show ads or let third parties serve content or ads. Our product analytics (section 1) never receive Google user data.

When it leaves Vid0. Google user data is transferred only in these cases:

  • When you ask Vid0's AI assistant about your channel, the stats needed for that answer are sent to our AI provider (Anthropic or Nebius) to generate it. Neither uses this data to train its models.
  • The weekly digest email, which includes your channel's recent stats, is delivered through our email provider, Resend.
  • Verified stats from YouTube Analytics appear on your media kit only through a share link you create for a specific brand, limited to the stats you choose. You can revoke a link at any time, and it stops working immediately.
  • To the service providers listed in section 5 that host and run Vid0, to comply with law, or as part of a merger or sale with your data still protected.

Human access. No one reads your Google user data unless you ask us to (for example, for support), it is needed for security (such as investigating abuse), it is needed to comply with law, or it has been aggregated and anonymized for internal operations.

Revoking access. You can revoke Vid0's access to your Google account at any time at Google security settings, or with “Disconnect” on Vid0's channel page. Disconnecting also revokes the grant with Google and deletes that channel's private analytics from Vid0 immediately. Public YouTube data we cache, such as video statistics, is refreshed or deleted within 30 days, as YouTube's policies require.

5. Who we share data with

We share data only with the service providers that run Vid0 for us, and only as needed for the purposes above:

  • Google: sign-in and the YouTube APIs.
  • Cloudflare: domain, network security and content delivery for vid0.in and our API, and routing of email sent to us.
  • Vercel: hosts the website. Railway: hosts the API. Neon: hosts the database.
  • AI providers, Anthropic and Nebius, which generate suggestions such as titles, descriptions, critiques and answers about your channel. We send only the content needed for the feature you requested, and they don't use it to train their models.
  • Resend: sends account emails, such as sign-in links, and the weekly digest.
  • PostHog: product analytics, session replays and error reports for vid0.in and our API, as described in section 1.
  • Polar: processes payments as our merchant of record, including sales tax and receipts.

We may also disclose data if the law requires it, or to protect the rights and safety of our users or of Vid0. When you publish a media kit, the details you chose to show are public to anyone with the link.

6. How we protect your data

We treat Google user data, including your YouTube channel data and analytics, and your OAuth tokens, as sensitive data, and protect it with these measures:

  • Encryption in transit. All traffic between your browser, the extension, our website, our API, Google's APIs and our service providers uses HTTPS (TLS), with HTTP Strict Transport Security on vid0.in and our API. We don't accept or send this data over unencrypted connections.
  • Encryption at rest. Google OAuth tokens are encrypted before they are stored. The tokens for your connected YouTube channel use AES-256-GCM, with a key kept separate from the database in our hosting provider's secret store. The short-lived access tokens used to read your YouTube data are kept only in memory. Our database provider also encrypts all stored data, including backups, at rest.
  • Hashed credentials. Passwords are stored only as salted, one-way hashes (scrypt). Extension and API tokens, and sign-in and password links, are stored only as SHA-256 hashes, so a copy of the database can't be used to sign in. Session cookies are signed, HTTP-only and sent over HTTPS only.
  • Least-privilege access. We request only the read-only YouTube scopes Vid0 needs. Every request for channel data is checked against the signed-in user's workspace, so one account can never read another account's private data. Access to production systems and the database is limited to the Vid0 operator, protected by multi-factor authentication, and used only to run, secure and support the service.
  • Minimal sharing. Your private YouTube Analytics data is not sold, not used for advertising, and not shown to other Vid0 users or brands unless you create a share link for them. Our service providers only process data on our behalf, under their own security and confidentiality commitments.
  • Deletion and revocation. When you disconnect a channel, we revoke the Google grant with Google and delete that channel's private data and tokens immediately. If Google access is revoked or expires, the connection is deleted after 7 days.
  • Monitoring and incidents. We log requests and errors to spot abuse and problems, apply security updates to our dependencies, and review security reports promptly. If a breach affects your personal data, we will notify you and the relevant authorities as the law requires.

No system is perfectly secure, but we work to protect your data with these safeguards. To report a security issue, email [email protected].

7. Storage and retention

Data is stored with the providers above, which may process it outside your country, including in the United States.

  • Your account and the things you add: while your account is active.
  • A connected channel's private analytics and tokens: until you disconnect it, or 7 days after Google access is revoked or expires.
  • Public YouTube data we cache, and statistics derived from it: refreshed or deleted within 30 days.
  • Ideas and scripts you save keep each video's ID. Its title, channel name and thumbnail are refreshed from YouTube every 30 days, or removed if we can't refresh them.
  • Ask Vid0 chats: results fetched from YouTube are removed after 30 days, and your channel's analytics are removed from your chats as soon as you disconnect it.
  • Creator page view counts: 13 months. The daily key behind visitor codes: deleted when its day ends.
  • Server logs: kept briefly, only to run and secure the service.

You can delete your account yourself under Settings → Delete account. We revoke your Google grants and delete your personal data, your workspaces and everything in them, and any connected channel's data straight away. If you ask by email instead, it's done within 7 days. The only exception is records the law requires us to keep, such as invoices.

8. Your choices and rights

You can view and edit most of your data in the app, disconnect your channel, revoke API tokens and share links, unsubscribe from the weekly digest and unpublish your media kit. Turning on Do Not Track or Global Privacy Control in your browser turns off product analytics. You can delete your account under Settings → Delete account. To get a copy of your data, correct it or delete your account by email, write to [email protected]; deletion requests are completed within 7 days. Depending on where you live, including under India's Digital Personal Data Protection Act, 2023, you may have further rights, and we will honour them.

9. Children

Vid0 is not meant for children under 13, or under the minimum age to use YouTube in your country. We don't knowingly collect their data.

10. Changes and contact

We may update this policy. If the changes are significant, we will let you know in the app or by email before they take effect. For privacy questions or requests, contact Arindam Majumder at [email protected].

© 2026 Arindam Majumder. All rights reserved. Questions: [email protected]. See also the Privacy Policy and Terms of Service.