1. Who operates this service
Clipper Studio is currently an independently operated video-production tool. The operator is the controller of the personal data described here. A working operator contact address will be displayed below before the service is made publicly available.
Contact us at mwrdev.infos@gmail.com.
2. Data we collect and process
Depending on the features you use, Clipper Studio processes:
- Account data: your email address, account identifier, authentication session, and basic Google profile information when you choose Google sign-in.
- Creator content: source videos you upload, extracted audio, transcripts and timestamps, suggested clip ranges, captions, editing choices, rendered clips, titles, descriptions, and scheduling choices.
- YouTube authorization data: OAuth access and refresh tokens, granted scopes, token expiry information, connected channel ID, channel name, and channel avatar.
- YouTube publication data: uploaded video IDs, requested visibility, scheduled publication time, upload state, and API errors.
- YouTube analytics data: authorized video or channel metrics such as views, likes, comments, watch time, average view duration, and subscribers gained, when available.
- Operational data: background-job status, progress, timestamps, and diagnostic error messages needed to run and troubleshoot the service.
- Billing data: subscription plan and status, Stripe customer and subscription identifiers, billing period, and cancellation state. Clipper Studio does not receive full payment-card details.
3. How we use data
We use this data only to authenticate you; store and process the content you provide; transcribe and analyze that content; let you review, render, upload, and schedule clips; display authorized YouTube information and analytics; maintain security; and diagnose failures. Clipper Studio does not sell personal data or YouTube API data and does not use it for advertising.
YouTube API data is not sent to OpenAI and is not used to train an AI model. AI clip scores and suggestions are generated independently from source content uploaded directly by the user.
Clipper Studio's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.
4. Google and YouTube permissions
Connecting YouTube is separate from signing into Clipper Studio. The application requests permissions to upload videos, read authorized channel information, and read authorized YouTube Analytics reports. You choose whether to connect a channel and whether to initiate an upload or schedule a publication.
Your use of YouTube remains governed by the YouTube Terms of Service and Google's handling of data is described in the Google Privacy Policy.
5. Service providers and disclosure
Data is disclosed only as needed to provide the requested features:
- Supabase provides authentication, PostgreSQL database services, and private object storage.
- Stripe provides hosted checkout, payment processing, subscription management, and billing records.
- OpenAI receives extracted speech audio for transcription plus transcript excerpts, sampled video frames, and source-derived activity signals for structured clip analysis.
- Google and YouTube receive OAuth requests, uploads, video metadata, and analytics requests that you authorize.
- The deployment provider processes web requests and application logs when the service is hosted.
These providers process information under their own terms and privacy commitments. We may also disclose information when legally required or necessary to protect the service and its users.
6. Storage and security
Source files and renders are held in private storage. Database rows use per-user access controls. Google OAuth tokens are encrypted by the application before database storage and are used only on the server. Signed, time-limited links are used to access private media. No system can guarantee absolute security, but we use safeguards appropriate to the sensitivity of the data.
7. Retention and deletion
Account records, creator content, and processing records are retained while needed to provide the service or until you delete them or request deletion. YouTube API data is refreshed or deleted within the periods required by YouTube's Developer Policies; raw metric snapshots older than 30 days are removed rather than treated as current data.
Disconnecting YouTube attempts to revoke the active Google credential and removes stored YouTube OAuth credentials, the connected-channel profile, publication API records, and metrics. The separate Delete stored YouTube data action provides the same deletion control even if a channel is already disconnected. A verified deletion request is completed as soon as practical and no later than seven calendar days. You can also revoke access from your Google Account connections. See the Data Deletion page for all available options.
Some limited records may remain temporarily in provider backups or security logs according to provider retention cycles or where required by law, and are not restored to the active service.
Important: deleting data from Clipper Studio does not delete videos already uploaded to YouTube. You must delete those separately in YouTube Studio.
8. Your choices and rights
You can decline to connect YouTube, disconnect it later, delete individual source projects through the product, or request deletion of your Clipper Studio account data. Depending on where you live, you may also have rights to access, correct, export, restrict, object to, or delete personal data, and to complain to your local data-protection authority.
9. Children
Clipper Studio is not directed to children and is not intended for use by anyone under the minimum age required to manage their own Google account in their country. The creator remains responsible for accurately declaring whether uploaded YouTube content is made for children.
10. Changes
We may update this policy as the service or applicable requirements change. The updated date above will identify the current version. Material changes will be communicated through the service or another appropriate channel when required.