Studio Pilot — Privacy Policy

Last updated: April 21, 2026 · Effective: April 21, 2026 · Operator: Studio Pilot (studiopilot.ca)

Google API Services User Data Policy — Limited Use Disclosure.

Studio Pilot'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.

We only use Google user data to provide or improve user-facing features that are prominent in the Studio Pilot user experience. We do not transfer Google user data to third parties except as necessary to provide or improve these features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to users. We do not use Google user data to serve advertisements. We do not allow humans to read Google user data, except with your explicit consent, when necessary for security purposes, to comply with applicable law, or for operations where the data has been aggregated and anonymized.

We do not use any Google user data to train, fine-tune, or improve generalized or third-party artificial intelligence or machine learning models.

Introduction & Scope
Data Accessed — the specific Google user data we access
Data Usage — how we use Google user data and the purpose
Data Sharing — third parties and the purpose of sharing
Data Storage & Protection — how we secure your data
Data Retention & Deletion — how long we keep it and how to delete it
Your Rights
Children's Privacy
Changes to This Policy
Contact Us

1. Introduction & Scope

Studio Pilot ("we," "us," or "our") is an AI-powered YouTube creator tool operated by an individual developer (Kaiden Whaley) from Canada. Studio Pilot automates YouTube uploads by generating titles, descriptions, tags, thumbnails, and chapters using AI, then publishing videos on the user's behalf via the YouTube Data API.

This Privacy Policy describes, in full, how Studio Pilot accesses, uses, stores, shares, retains, and deletes user information — including data obtained through Google APIs — when you use our service at https://studiopilot.ca. It applies to all users of Studio Pilot worldwide.

This policy specifically addresses the requirements of the Google API Services User Data Policy and complies with the Limited Use requirements for sensitive and restricted OAuth scopes.

2. Data Accessed

When you sign in to Studio Pilot with your Google account and connect your YouTube channel, we request your consent to the following Google OAuth 2.0 scopes. You see each scope on Google's consent screen and may decline any of them.

2.1 OAuth scopes requested

Scope	Sensitivity	What it grants
`https://www.googleapis.com/auth/userinfo.email`	Non-sensitive	Your Google account email — used to create and identify your Studio Pilot account.
`https://www.googleapis.com/auth/userinfo.profile`	Non-sensitive	Your Google profile name and profile picture — displayed in the Studio Pilot header.
`https://www.googleapis.com/auth/youtube.upload`	Restricted	Upload videos to the YouTube channel you connect.
`https://www.googleapis.com/auth/youtube`	Restricted	Set metadata (title, description, tags, category, privacy status, scheduled publish time) on the video you upload, and read your channel's ID and display name to confirm which channel is connected.
`https://www.googleapis.com/auth/youtube.force-ssl`	Restricted	Required by Google to perform YouTube Data API v3 operations over HTTPS (applied to thumbnail uploads and metadata edits).
`https://www.googleapis.com/auth/youtubepartner`	Restricted	Apply a custom thumbnail image to the video you uploaded.
`https://www.googleapis.com/auth/yt-analytics-monetary.readonly`	Restricted	Read-only access to your YouTube Analytics, used to power the Studio Pilot dashboard (video performance metrics: views, watch time, subscriber change). Read-only — we cannot modify analytics data.

2.2 Exact data fields we access, collect, or receive

Google account identity: Email address, display name, profile image URL, Google account ID (sub).
OAuth tokens: Access token and refresh token issued by Google's OAuth 2.0 authorization server.
YouTube channel metadata: Channel ID, channel title (display name), channel thumbnail URL.
Upload confirmation data: The YouTube video ID, video URL, and upload status returned by the YouTube Data API after a successful upload.
YouTube Analytics metrics (read-only, aggregate): Per-video views, watch time minutes, average view duration, subscribers gained/lost, and estimated revenue (only if present on your account). Displayed back to you in your Studio Pilot dashboard.

2.3 What we do NOT access

Studio Pilot does not access, read, collect, or store any of the following:

The contents of your YouTube videos (video files) beyond the file you upload through Studio Pilot in that session — and those files are streamed to YouTube, not stored by us (see §5).
Comments, replies, private messages, or community posts on your channel.
Your subscriber list, subscriber identities, or viewer identities.
Your YouTube watch history, search history, or recommendations.
Your Google Drive files, Gmail messages, Contacts, Calendar, Photos, or any other Google service data.
Any Google user data belonging to any user other than you (the signed-in user).

3. Data Usage

We use Google user data exclusively to provide the user-facing features described below. Every use is directly initiated by you within the Studio Pilot interface. We do not use Google user data for any purpose other than delivering these features.

3.1 Specific uses and their purposes

Feature	Data used	Purpose
Sign-in & account creation	Email, name, profile picture, Google account ID	Create your Studio Pilot account and recognize you on return visits.
YouTube channel connection	OAuth tokens, channel ID, channel title	Authorize Studio Pilot to act on your behalf for the specific, user-initiated actions in this table.
Video upload	Your video file, OAuth tokens	Stream your video directly to YouTube's servers using the YouTube Data API resumable upload protocol, so it appears on your channel.
Metadata application	Title, description, tags, category, privacy, scheduled publish time, OAuth tokens	Apply the metadata you configure (or that our AI generates at your explicit request and you accept) to the uploaded video.
Thumbnail application	Thumbnail image, OAuth tokens	Set the custom thumbnail you selected or generated as the visible thumbnail on your YouTube video.
Analytics dashboard	Video IDs, view/watch-time/subscriber metrics, OAuth tokens	Display per-video performance in your Studio Pilot dashboard so you can track how your uploads perform.
Account disconnect	OAuth tokens, channel ID	Revoke our access to your Google account and delete our stored tokens when you click "Disconnect."

3.2 Uses we do NOT engage in

We explicitly do not use Google user data for any of the following:

Advertising. We do not serve ads and do not share Google user data with advertising platforms, ad networks, or ad-tech vendors.
Profiling. We do not build advertising or behavioral profiles about you.
AI/ML training. We do not use Google user data — including video content, channel metadata, analytics data, or any OAuth-derived data — to train, fine-tune, or improve generalized or third-party AI/ML models, including our own. Data sent to Google Gemini for per-request inference (see §4) is not retained by Studio Pilot or used to train models; Gemini's handling is governed by the Gemini API Additional Terms of Service.
Selling or renting data. We do not sell, rent, or license Google user data to data brokers or any other third party.
Human review. No Studio Pilot employee or contractor reads, views, or otherwise inspects your Google user data, except (a) with your explicit written consent for support, (b) when strictly necessary to investigate a specific security incident or abuse report, or (c) when required by valid legal process.
Actions you did not initiate. We do not perform any action on your YouTube account beyond what you explicitly click, type, or confirm within the Studio Pilot interface.

We do not sell, rent, or share Google user data with third parties for their own independent purposes. The only third parties that receive data are the sub-processors listed below, and each one processes data solely under contract to operate Studio Pilot on our behalf.

Sub-processor	Role	Data shared	Purpose of sharing
Supabase, Inc. (privacy policy)	Backend / database / authentication host	Encrypted OAuth access & refresh tokens, channel ID, channel title, email, upload history records, subscription status.	To store your account securely and to run our server-side edge functions that perform YouTube API calls.
Google LLC (YouTube Data API v3) (privacy policy)	Video publishing platform	Your video file (streamed, not stored), metadata you configure, thumbnail image, OAuth tokens.	To actually publish your video to YouTube — the core purpose of the app.
Google LLC (Gemini AI API) (terms)	AI inference for title / description / thumbnail generation	A small number of video frame images (JPEG thumbnails you or we extract from your video) and the text prompts you type. No Google account data, OAuth tokens, or YouTube channel data is sent to Gemini.	To generate AI suggestions that you review and optionally accept.
Stripe, Inc. (privacy policy)	Payment processing for the Pro subscription	Your email and billing information entered on Stripe's hosted checkout. No Google user data, OAuth tokens, or YouTube data is shared with Stripe.	To process your subscription payments.

All sub-processors listed above are contractually bound (via their standard data processing agreements) to use data only to provide their services to Studio Pilot, to maintain industry-standard security, and not to repurpose data for their own advertising or data-broker activities.

We will also disclose data if required by valid legal process (subpoena, court order, or applicable law), or in the context of a merger, acquisition, or sale of assets — in which case we will notify affected users in advance where legally permissible.

5. Data Storage & Protection

5.1 Where data is stored

OAuth tokens, account records, upload history: Stored in an encrypted PostgreSQL database hosted on Supabase (AWS infrastructure, primarily US regions). Access is restricted by Supabase Row-Level Security (RLS) policies so that a user can only read their own rows, and OAuth tokens are additionally restricted so that no client-side (browser) code can read them at all — only privileged server-side edge functions may.
Thumbnails: Stored in a private Supabase storage bucket with owner-only access policies. Bucket is not publicly listable.
Video files: Never stored. Your video is streamed from your browser through a short-lived edge function proxy directly to YouTube's resumable upload endpoint and is discarded from memory as soon as the upload completes.

5.2 How data is protected

Transport security. All data in transit is encrypted with TLS 1.2+ (HTTPS). HSTS is enabled on studiopilot.ca.
At-rest encryption. Supabase encrypts database contents at rest using AES-256.
Token isolation. Your Google OAuth access and refresh tokens are never transmitted to, stored in, or readable from your browser. They are only accessible to server-side Supabase Edge Functions running under a privileged service role.
Row-Level Security. Every database table containing user data has RLS policies enforcing that auth.uid() = row.user_id, preventing cross-user data leakage.
Least-privilege OAuth. We request only the scopes listed in §2.1 that are necessary for the user-initiated features in §3.1. We do not request broader scopes "just in case."
Short-lived access tokens. Google access tokens expire after 1 hour; we refresh them using the refresh token only at the moment an action is performed.
Infrastructure provider compliance. Supabase is SOC 2 Type II certified.
Incident response. In the unlikely event of a data breach affecting Google user data, we will notify Google and affected users within 72 hours of discovery, as required by the Google API Services User Data Policy.

6. Data Retention & Deletion

6.1 Retention periods

Data	Retained for
Google OAuth access & refresh tokens	Until you disconnect YouTube, revoke at myaccount.google.com, or delete your account. Deleted within 24 hours of any of these events.
Channel ID & channel title	Until you disconnect YouTube or delete your account.
Email, profile name, profile picture	Until you delete your account.
Upload history records (YouTube video ID, date, title you set)	Until you delete your account. You can also delete individual records from the Dashboard.
Thumbnail images in our storage bucket	Up to 90 days after upload, or sooner on account deletion.
Video files	Not retained — streamed directly to YouTube and never stored.
Server logs (non-identifying, for debugging)	30 days maximum, then automatically purged.

6.2 How to delete your data

You can delete your data and revoke our access at any time, through any of the following methods. All methods are free and accessible from within the app or via a publicly available Google settings page.

Disconnect YouTube from within Studio Pilot. Sign in → Dashboard → YouTube Connect card → Disconnect. This immediately deletes your OAuth access and refresh tokens from our database and ends our ability to call YouTube on your behalf.
Revoke access via Google. Visit https://myaccount.google.com/permissions, find "Studio Pilot," and click Remove access. Google will immediately invalidate our tokens; our server detects the invalidation and purges the tokens on our side within 24 hours.
Delete your entire Studio Pilot account and all associated data. Email kwhaley022@gmail.com with the subject "Delete My Account" from the address on the account. We will delete all data associated with your account — OAuth tokens, email, upload history, thumbnails, and subscription records — within 30 days and send a confirmation email when complete. This is a permanent, irreversible deletion.

We also automatically delete OAuth tokens when we detect that Google has invalidated them (for example, after the user revokes access), and we automatically delete orphaned thumbnail files after 90 days.

7. Your Rights

Depending on your jurisdiction (including GDPR in the EU/UK, CCPA/CPRA in California, and PIPEDA in Canada), you may have the right to:

Access a copy of the personal data we hold about you.
Request correction of inaccurate data.
Request deletion of your data (as described in §6.2).
Withdraw consent for us to access your Google account at any time.
Request portability of your data in a machine-readable format.
Lodge a complaint with your local data protection authority.

To exercise any of these rights, email kwhaley022@gmail.com. We respond within 30 days and do not charge any fee for reasonable requests.

8. Children's Privacy

Studio Pilot is not directed to children under the age of 13 (or under 16 in the EU, where a higher age of digital consent applies). We do not knowingly collect personal information from children in those age ranges. If you believe a child has provided us with personal information, please contact us at kwhaley022@gmail.com and we will delete it promptly.

9. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes — in particular, any change in how we collect, use, share, store, retain, or delete Google user data — we will update the "Last updated" date at the top of this page and, for material changes, notify registered users by email at least 14 days before the change takes effect. Continued use of Studio Pilot after the effective date constitutes acceptance of the revised policy.

10. Contact Us

Studio Pilot — Data Privacy Contact

Operator: Kaiden Whaley (sole operator / data controller)
Jurisdiction: Canada
Email: kwhaley022@gmail.com
Website: https://studiopilot.ca

For privacy inquiries, data deletion requests, or questions about this policy, please email the address above with a clear subject line (e.g. "Privacy Inquiry" or "Delete My Account"). We respond to all privacy requests within 30 days.