YouTube API Provider Setup #21

Description

Configure Google/Supabase OAuth so Livelatch can request YouTube read-only API access from the LatchID account page.

Implementation Checklist

• In Google Cloud Console, enable YouTube Data API v3 for the Livelatch OAuth project
• Confirm OAuth consent screen allows this scope: https://www.googleapis.com/auth/youtube.readonly
• Confirm Google OAuth authorized redirect URIs include: https://<project-ref>.supabase.co/auth/v1/callback
• In Supabase Auth redirect allow list, add: https://dev.livelatch.com/callback/youtube
• In Laravel env, configure Google OAuth client credentials for backend token refresh:

  GOOGLE_CLIENT_ID=
  GOOGLE_CLIENT_SECRET=

• After deployment and migration, test "Connect YouTube" from /studio/latchid
• Verify a social_accounts row exists with provider_name = youtube

Blocking Issues

Currently blocked on Google OAuth verification.

youtube.readonly is a Google "sensitive" scope, so the OAuth app must pass Google review before non-test users can grant it. Google requires:

• A demonstration video showing the OAuth consent flow and how the scope is used
• A published, publicly reachable privacy policy URL
• A verified app homepage / domain

This depends on the privacy policy being live (see "Data Collection Logic & Compliance Confirmation" issue).

Status (2026-06-17)

Blocked waiting for:

1. Privacy policy publication (blocks Google verification)
2. Google review cycle (typically 2+ weeks)