Privacy Policy

Effective date: October 9, 2026

This policy explains how Advendo Media LLC ("we", "us") collects, uses, stores and shares information in Content OS, our internal content production tool. Content OS is used only by members of our team to manage our own YouTube channels.

1. Information we collect

Account information

• Name, email address and profile picture of team members, entered by an administrator or received from Google Sign-In.
• Password hashes for team members who sign in with email and password.
• Optional notification settings, such as a connected Telegram chat.

Information from Google and YouTube

When a team member connects a YouTube channel, we request these Google permissions:

• Basic profile and email (openid, email): to identify which Google account a channel is connected through.
• Upload videos (youtube.upload): to upload videos, thumbnails and their titles, descriptions and schedules that the team prepared in Content OS.
• View the YouTube account (youtube.readonly): to read the channel's name, thumbnail, videos and their processing and publishing status.
• Manage the YouTube account (youtube.force-ssl): to change a video's visibility or delete a video when a team member asks for it in Content OS.
• View YouTube Analytics reports (yt-analytics.readonly): to show views, watch time, click-through rate and similar statistics for our own videos.

We store the OAuth access and refresh tokens, the channel ID, channel name and thumbnail, the email of the connected Google account, the status of uploaded videos and analytics statistics for our videos.

Content you create

• Video projects, scripts, ideas, notes, comments, tasks and files (recordings, voice-overs, thumbnails, final videos) uploaded by the team.
• Public information about other YouTube videos that the team saves for research, such as titles, statistics and transcripts.

Technical information

• Session cookies needed to keep you signed in, and server logs (IP address, browser, time of request) kept by our hosting provider for security and debugging.

We do not use advertising or tracking cookies.

2. How we use information

• To provide the features of Content OS: planning and tracking video production, uploading to and managing our YouTube channels, and showing analytics for our videos.
• To send notifications that team members turned on (in-app, Telegram or Slack).
• To keep Content OS secure, prevent abuse and fix problems.

We do not sell personal information, and we do not use it for advertising.

3. Google API Services: Limited Use

Content OS's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular:

• We use Google user data only to provide and improve the user-facing features described in this policy.
• We do not transfer Google user data to others except as needed to provide those features, to comply with the law, or as part of a merger or acquisition.
• We do not use Google user data for advertising, and we do not sell it.
• Humans do not read Google user data unless the user agreed, it is needed for security or to comply with the law, or the data is aggregated and anonymised.
• We do not use Google user data to train AI or machine-learning models.

Content OS uses YouTube API Services. By connecting a YouTube channel you also agree to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy.

4. Service providers

We share information only with service providers that process it on our behalf to run Content OS:

• Vercel: hosting, file storage and server logs.
• Neon: database hosting.
• Google / YouTube: sign-in, uploads, channel management and analytics.
• Anthropic: AI features (research analysis, script drafts and the research assistant). Text the team sends to these features may include video titles, transcripts and aggregate statistics of our videos. Anthropic does not use this data to train its models.
• youtube-transcript.io: retrieving transcripts of public YouTube videos saved for research.
• Telegram and Slack: only when a team member turns on notifications there.

We may also disclose information when the law requires it.

5. Storage and security

Data is stored with our providers in the United States. Google OAuth tokens are encrypted at rest with AES-256-GCM. Connections use HTTPS. Access to Content OS is limited to signed-in team members, with permissions based on their role.

6. Retention and deletion

• When a YouTube channel is disconnected in Content OS, we revoke the Google grant and delete its OAuth tokens immediately.
• You can also remove Content OS's access at any time in your Google Account permissions. Content OS then can no longer access the channel.
• Other data is kept while it is needed to run our content operation. To have your data deleted, email us at advendomediallc@gmail.com. We delete it within 30 days, except where the law requires us to keep it.

7. Your rights

Depending on where you live, you may have the right to access, correct, delete or export your personal information, or to object to its use. Email advendomediallc@gmail.com and we will respond within 30 days.

8. Children

Content OS is a work tool for adults and is not intended for anyone under 16.

9. Changes

We may update this policy. We will change the effective date above and, for important changes, notify team members in Content OS.

10. Contact

See also our Terms of Service.