VLSTUDIO ← Back to site
// Legal

Social-Platform
Data-Use Disclosures

Last updated: July 1, 2026  ·  Effective: July 1, 2026
// These disclosures exist because YouTube, TikTok, and Meta each require them as a condition of API access. This page states what each platform requires us to say, what we actually collect, and where a required piece of it, most often a disconnect or deletion flow, does not exist yet.

Contents

1. Why This Page Exists

2. YouTube / Google API Services

3. TikTok

4. Meta / Instagram

5. Disconnect Does Not Fully Revoke Tokens Today

6. Domain Consistency and Platform Verification

7. Changes to This Page

8. Contact

1. Why This Page Exists

VLStudio Web's analytics dashboard connects to YouTube, TikTok, and Instagram (Meta) on your behalf, to show channel, video, and audience metrics in one place. Each of these platforms requires an app that accesses its API to publicly disclose, as a condition of continued API access, what data it collects through that API and how it is used. This page is that disclosure for all three platforms, and it supplements our Privacy Policy, Section 6, which summarizes the same facts.

2. YouTube / Google API Services

2.1 Google's Required "Limited Use" Disclosure

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

2.2 What We Collect and Store

If you connect a YouTube channel, VLStudio requests read-only access (the youtube.readonly scope) and stores a long-lived offline refresh token server-side, along with channel and video statistics (subscriber counts, view counts, and comparable metrics). This connection is governed by the YouTube Terms of Service and the Google Privacy Policy, both of which apply to your use of YouTube independently of your relationship with VLStudio.

2.3 The 30-Day Stale-Data Rule

Google's API terms require that cached YouTube data be refreshed or deleted after a limited period, generally within 30 days of collection, rather than retained indefinitely without being kept current or removed. Today, no automatic purge job exists to enforce this on VLStudio's side: cached channel and video statistics are not automatically refreshed or deleted on a 30-day cycle. This is a gap against the platform's own requirement, and we are flagging it rather than describing an automatic purge process that does not yet run.

3. TikTok

3.1 Scopes Used

VLStudio requests basic profile access via TikTok's Login Kit and Display API, specifically the user.info.basic scope, and stores the resulting access tokens server-side to display your TikTok profile and metrics in the dashboard.

3.2 TikTok Developer Terms

Your connection to TikTok through VLStudio is governed by TikTok's Developer Terms, which apply to how TikTok-sourced data is used independently of your relationship with VLStudio.

3.3 No Disconnect Flow Yet

A dedicated disconnect or delete flow for a connected TikTok account does not exist today. Removing TikTok from your VLStudio dashboard view does not currently delete the stored token server-side. This is a gap we are flagging, not a working feature; until it is fixed, you can revoke VLStudio's TikTok access directly from your TikTok account's own connected-apps settings.

4. Meta / Instagram

4.1 Scopes Requested

VLStudio requests the following scopes when you connect an Instagram / Meta account:

These scopes are used to read your profile, recent media, and audience-insight metrics, and to identify the Facebook Page connected to your Instagram business or creator account. The resulting access token is valid for approximately 60 days and is stored server-side; VLStudio requests a fresh token when it expires rather than storing an indefinite credential.

4.2 Meta Platform Terms

Your connection to Instagram / Meta through VLStudio is governed by Meta's Platform Terms, which apply to how Meta-sourced data is used independently of your relationship with VLStudio.

4.3 Data Deletion Request Callback Not Implemented Yet

Meta requires every app using its Platform to implement a Data Deletion Request Callback, an automated endpoint Meta calls when a user requests deletion of their data through Meta's own tools, which the receiving app must act on. This callback is not implemented on VLStudio's side today. This is a gap requiring a fix before this integration is fully compliant with Meta's own Platform Terms, and we are disclosing it rather than asserting compliance we do not yet have. Until it ships, a deletion request routed through Meta's own tools will not automatically reach VLStudio; use the contact details in Section 8 to request deletion of Meta/Instagram-sourced data directly from us in the meantime.

5. Disconnect Does Not Fully Revoke Tokens Today

Across all three platforms, disconnecting a platform from inside VLStudio today does not fully revoke the stored server-side token or reliably call the platform's own revoke endpoint:

We are flagging this clearly across all three platforms rather than describing "disconnect" as a complete server-side revocation today. Until each platform has a working disconnect-and-revoke flow, the most reliable way to fully cut VLStudio's access is to revoke it directly from that platform's own account settings, in addition to disconnecting inside VLStudio.

6. Domain Consistency and Platform Verification

VLStudio's canonical domain is vlstudio.live. Code and configuration in parts of the product have historically also referenced vlstudio.app and vlstudio.io. This inconsistency can cause a platform's own domain-verification check (used by YouTube, TikTok, and Meta to confirm an app's OAuth redirect and app-domain configuration matches what the developer console has on file) to fail or flag a mismatch. We recommend reconciling all OAuth redirect URIs and app-domain configuration across all three platforms' developer consoles to vlstudio.live as the single canonical domain, consistent with the domain decision recorded in our internal shared-facts reference and reflected in our Imprint.

7. Changes to This Page

We will update this page as each flagged gap (the YouTube 30-day purge job, the TikTok and Instagram disconnect flows, the Meta Data Deletion Request Callback, and the domain reconciliation) is fixed, replacing the warning language with a description of the working mechanism. See our Terms Versioning Policy for how material changes to any VLStudio legal document are announced.

8. Contact