YouTube data use
Last updated: 29 April 2026
This page describes exactly how MetaSnap interacts with YouTube and the underlying Google APIs when you connect your YouTube channel. It is provided in addition to (and consistent with) the Google-specific section of our Privacy Policy and is intended to make the scope-by-scope behaviour clear to creators, reviewers and auditors.
An Italian version is available at /youtube-data-use-it.html.
1. Why MetaSnap requests access to YouTube
MetaSnap is a content-preparation and publishing tool for creators. When you connect a YouTube channel, MetaSnap can:
- upload short videos you have generated or refined inside MetaSnap to your own YouTube channel, after you explicitly press Publish;
- read your channel's basic metadata (channel name, channel ID, the list of videos you have published) so the publish screen can show the correct destination and the post-publish screen can link to the uploaded video;
- display performance data (views, watch time, subscribers gained) for videos you have published with MetaSnap, so you can review how content is performing without leaving the product. Available on the Pro plan only.
MetaSnap never publishes a video automatically without your explicit confirmation. The only path that uploads to YouTube is the user pressing the Publish button after reviewing the video, title, description, tags, visibility setting and thumbnail.
2. Scopes MetaSnap requests
The following are the only OAuth scopes MetaSnap requests from Google. They are the same scopes declared in our Google Cloud Console OAuth consent screen.
| Scope | Why MetaSnap requests it | Sensitive / Restricted? |
|---|---|---|
openid |
Establish that you signed in with the same Google account whose channel you are connecting. | No |
https://www.googleapis.com/auth/userinfo.email( email) |
Display the connected Google account's email address on the Connections screen so you can confirm which account is linked. | No |
https://www.googleapis.com/auth/userinfo.profile( profile) |
Display your Google profile name on the Connections screen. | No |
https://www.googleapis.com/auth/youtube.upload |
Upload videos you generate inside MetaSnap to your own YouTube channel after you press Publish. This is the core publishing capability. | Restricted |
https://www.googleapis.com/auth/youtube.readonly |
Read your channel's metadata and the list of videos you have published, so MetaSnap can show the correct destination on the publish screen and link to videos after upload. | Sensitive |
https://www.googleapis.com/auth/yt-analytics.readonly |
Read aggregate analytics (views, watch time, subscribers gained) for videos you have published via MetaSnap, on the Pro plan only. | Sensitive |
MetaSnap does not request scopes for: Gmail, Drive, Calendar, Contacts, your friends or subscribers' private data, comments management, livestream control, content-ID management, or any data unrelated to publishing on your own channel.
3. How MetaSnap uses YouTube data — Limited Use
MetaSnap's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:
- User-facing features only. Google user data is used only to deliver the features you enable — connecting your channel, publishing on your behalf, and showing your own performance data.
- No advertising. Google user data is never used for advertising, retargeting, ad personalisation, or for building advertising profiles.
- No model training. Google user data (including video content, metadata and analytics) is never used to train, fine-tune or improve generalised AI / ML models, whether ours or third-parties'.
- No selling data. Google user data is never sold, rented or licensed to third parties.
- No human reads your YouTube content or analytics except (a) with your explicit consent, (b) to investigate a specific abuse or security incident, (c) to comply with applicable law, or (d) where the data has been aggregated and anonymised so it can no longer identify you.
- Minimum data, minimum retention. MetaSnap stores only the OAuth tokens (encrypted at rest with AES-256-GCM), the channel/account identifiers needed to publish, and a record of the videos you uploaded through MetaSnap. Tokens are deleted as soon as you disconnect the channel.
4. How to connect your YouTube channel
- Sign in to MetaSnap.
- Open Distribute → Social Connections.
- Click Connect next to YouTube.
- You will be redirected to Google's consent screen, where Google lists every scope MetaSnap is requesting (the same scopes as the table in section 2).
- Confirm the Google account whose channel you want to connect, review the scopes, and grant access.
- Google redirects you back to MetaSnap. The Connections screen now shows your channel's email and a green Connected badge.
5. How to disconnect your YouTube channel
You can revoke MetaSnap's access to your YouTube data at any time, from two places:
- From inside MetaSnap. Open Distribute → Social Connections → YouTube → Disconnect. MetaSnap deletes the encrypted tokens and the channel metadata associated with your account.
- From your Google account. Visit https://myaccount.google.com/permissions, locate MetaSnap, and click Remove Access. Google revokes the access and refresh tokens immediately; MetaSnap will mark the connection as expired the next time it tries to use them.
Disconnecting does not delete videos you have already published to YouTube — those remain on YouTube and are managed from YouTube Studio. It only severs MetaSnap's ability to act on your behalf going forward.
6. Explicit confirmation before publishing
MetaSnap publishes to YouTube only when you explicitly press Publish on a post. There is no background or scheduled job that uploads to YouTube without a recent, deliberate user action.
The optional Batch automation feature can generate drafts on a schedule from RSS feeds, but auto-publish is opt-in per platform and per source, and is currently disabled by default for YouTube. When enabled, every batch run is logged on the Distribute → Publish History page so you can audit it.
7. Data deletion request
To delete the OAuth tokens and channel metadata MetaSnap holds about your YouTube connection, the easiest path is to use the Disconnect button inside the product (see section 5). If you also want MetaSnap to delete every record related to your account — generated posts, audit logs, support requests — submit a request through the support form or email info@tyaplyap.com. We respond within 30 days as described in our Privacy Policy.
8. Compliance with YouTube's policies
By using MetaSnap to publish to YouTube, you agree to comply with:
- YouTube Terms of Service;
- YouTube Community Guidelines;
- Google Privacy Policy;
- YouTube API Services Terms of Service.
MetaSnap, on its side, complies with the Google API Services User Data Policy, including the Limited Use requirements.
9. Contact
For questions about how MetaSnap uses YouTube data, or to report a data-handling concern, contact us through our support form or at info@tyaplyap.com.