This policy describes what data ShortsPipeline receives, why it is needed, how Google/YouTube access is used, and how users can manage their data.
ShortsPipeline may store name, email, Google avatar, account settings, connected YouTube channels, upload history, publishing statuses, support requests, and subscription data.
Video files are used to perform the actions selected by the user: upload, queueing, metadata generation, and publishing.
The user connects a YouTube channel through OAuth. Access is used only for actions the user starts in ShortsPipeline: upload preparation, publishing, scheduling, and status retrieval.
Access can be revoked in Google Account settings or inside ShortsPipeline settings.
Payments and subscriptions are processed by the payment provider. ShortsPipeline stores subscription status, order identifiers, and payment events, but does not store full bank card data.
Account access is protected through Google OAuth and the app cookie session. YouTube access can be revoked in Google Account or ShortsPipeline settings. Payments use the hosted checkout and billing portal from the payment provider.
The user can request account deletion, export of key information, or disconnection of integrations. Use the contact page or in-product account settings for requests.