Privacy Policy
Effective Date: September 28, 2026 | Last Updated: October 6, 2026
1. Introduction
Welcome to Velocity Studio (operated by kreggscode.com, "we", "our", or "us"). We provide a multi-channel video distribution, localization, and publishing platform that enables content creators, international networks, and organizations to schedule and publish original video content to their authorized YouTube channels.
This Privacy Policy explains how our application accesses, collects, uses, stores, and protects your information when you use Velocity Studio.
2. YouTube API Services Integration
Velocity Studio uses YouTube API Services to allow creators to connect their channels, verify channel metadata, and publish video content directly to YouTube.
• By using Velocity Studio, users are agreeing to be bound by the YouTube Terms of Service .
• Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy , including the Limited Use requirements.
• Please refer to the Google Privacy Policy for complete information on how Google collects and processes personal information.
3. Information We Access and Collect
When you explicitly connect a YouTube channel to Velocity Studio via Google OAuth 2.0, we access the following information strictly to provide video management and publishing functions:
- YouTube Channel Information: Channel ID, channel title, profile avatar URL, and subscriber/video count statistics (used solely to display your channels on your dashboard).
- OAuth Access & Refresh Tokens: Cryptographic access tokens returned by Google's OAuth 2.0 flow to authorize video uploads on your behalf.
- Video Metadata: Titles, descriptions, category IDs, tags, privacy status, and thumbnails that you configure for your uploads.
Important: We never access your Google account password, personal emails, search history, payment credentials, or contacts.
4. Device Information, Cookies, and Local Storage (Policy III.A.2g Disclosure)
In compliance with YouTube API Services Developer Policy III.A.2g, we provide the following explicit disclosure regarding device storage and cookies:
• Direct Device Access & Local Storage: Velocity Studio stores, accesses, and collects information directly and indirectly on and from users' devices. This includes placing, accessing, and recognizing cookies, browser local storage (LocalStorage), and session storage (SessionStorage) on users' devices or browsers.
• Purposes of Storing Information on User Devices: We store information locally on your device solely to:
- Maintain authenticated user sessions and OAuth 2.0 authorization state during video publishing workflows.
- Store user preferences, selected channel references, and user interface configurations locally on your device.
- Track in-progress video upload tasks, chunk progress, and resumable upload session endpoints to prevent upload interruptions.
• Third Parties (Google LLC & YouTube): Third parties, including Google and YouTube (via Google Identity Services and YouTube API endpoints), also store, access, and collect information directly and indirectly on and from users' devices, including by placing, accessing, or recognizing cookies, device identifiers, and similar technologies on users' devices or browsers when you sign in with Google or interact with YouTube API Services. This collection and processing is governed by the Google Privacy Policy.
• User Control Over Cookies and Device Storage: Users have the right and ability to clear, block, or manage cookies and local browser storage at any time through their web browser settings. Please note that clearing local storage will reset your local session preferences and require re-authenticating with Google.
5. How We Store and Protect Your Data
- No Third-Party Sharing or Sale: We do not sell, rent, lease, or trade your YouTube user data, OAuth credentials, or personal information to third parties, advertising networks, or data brokers.
- Encryption: OAuth tokens and user configuration settings are protected using industry-standard TLS 1.3 encryption in transit and AES-256 encryption at rest.
- Strict Access Controls: Access to channel management functions is restricted strictly to authorized channel owners through Google OAuth 2.0.
6. Data Refresh, Update, and Deletion Schedule (Policy III.E.4a-g)
In compliance with YouTube API Services Developer Policies III.E.4a through III.E.4g, Velocity Studio enforces the following data lifecycle schedule:
• Token Lifecycles & Automatic Refresh: OAuth access tokens automatically expire after 3,600 seconds (1 hour). Refresh tokens are only utilized on-demand when actively publishing video content or checking authorization status.
• Channel Metadata Refresh Frequency: Channel statistics and video metadata retrieved via the YouTube Data API are refreshed upon every active user session, and at minimum every 24 to 48 hours to ensure data accuracy and prevent stale metrics.
• 30-Calendar-Day Maximum Retention Limit: In strict compliance with Policy III.E.4a, no YouTube API Data is retained in temporary cache or persistent storage for longer than thirty (30) calendar days without being refreshed from the YouTube API.
• Immediate Deletion Upon Disconnection: When a user disconnects their channel or revokes authorization via the dashboard, all associated channel data, OAuth tokens, and cached metadata are permanently deleted from application storage immediately (within 24 hours).
• User Deletion Requests: Any user data deletion request submitted to support@kreggscode.com is processed and completed within 48 hours.
7. Revoking Access & Data Deletion
You have full control over your YouTube channel permissions and stored data at all times:
support@kreggscode.com and all records will be permanently deleted within 48 hours.
8. Children's Privacy
Velocity Studio is designed for content creators, publishers, and developers aged 18 and older. We do not knowingly collect personal information from individuals under the age of 13.
9. Contact Information
If you have questions, comments, or concerns regarding this Privacy Policy or our compliance with YouTube API Developer Policies, please contact us: