Tube-In privacy notice
How Tube-In handles data
Last updated August 20, 2026. Legal review is recommended before public launch.
Tube-In accounts
Tube-In stores account, profile, workspace, onboarding, and creator-intent information needed to provide the service. Supabase Auth identifies the Tube-In user.
YouTube authorization
Connecting YouTube is separate from signing into Tube-In. In Phase 2A, Tube-In requests read-only access to view the authorized YouTube account. Google refresh credentials are encrypted with authenticated encryption and stored only on the server. They are not returned to browser JavaScript or sold.
YouTube source data
Tube-In stores channel and uploaded-video metadata, including titles, descriptions, thumbnails, publication and visibility details, durations, and available snapshot counters. Tube-In uses this data to synchronize and display factual channel information. Phase 2A does not ingest YouTube Analytics or modify YouTube content.
Disconnecting
When an owner disconnects YouTube, Tube-In attempts Google token revocation and removes the stored refresh credential. Previously synchronized source facts remain marked as disconnected history. Disconnecting is not the same as deleting all historical Tube-In data; a separate deletion process should be requested.
Security and questions
Tube-In applies workspace access controls and keeps provider secrets at server boundaries. No security or compliance certification is claimed by this notice. Contact the Tube-In operator with privacy or deletion questions.