Privacy Policy
Last updated: November 1, 2026
This policy explains what information Clipper Studio (the "Service") collects, how it is used and shared, how long it is kept, and the choices you have. The Service lets you turn long YouTube videos into short vertical clips and publish them to your own TikTok, YouTube, Facebook, Instagram and Threads accounts.
1. Information we collect
- Account information: your name, email address and password (stored only as a one-way hash). If you create API tokens, only a hash of each token is stored.
- Content you provide: links to videos you want to clip, the source videos the Service downloads from those links, transcripts and subtitles made from them, your clip settings and brand kit (including a logo you upload), music and gameplay footage you upload, the channels or keywords you ask Autopilot to watch, and the clips the Service renders with their captions, hashtags and schedules.
- TikTok account information, if you connect TikTok: your TikTok open ID, display name and avatar, the permissions you granted, and the access and refresh tokens TikTok issues to the Service. We do not receive your TikTok password.
- YouTube channel information, if you connect YouTube: your channel ID, channel name and thumbnail, the permissions you granted, and the access and refresh tokens Google issues to the Service. We do not receive your Google password.
- Facebook and Instagram information, if you connect Facebook: your Facebook user ID and name, the permissions you granted, a long-lived access token, and, for each Page and Instagram professional account you choose to connect, its ID, name, username, profile picture link and (for a Page) its own access token. We do not receive your Facebook or Instagram password.
- Threads information, if you connect Threads: your Threads user ID, username and profile picture link, the permissions you granted, and the access token Threads issues to the Service.
- Publishing records: for each clip you publish, the platform's ID and link for the post, its status or error, and when it was sent. For clips posted to TikTok, the view, like, comment and share counts read back from TikTok (see section 5).
- Usage records: the length and processing cost of each render, counted against your monthly render quota.
- Technical information: a session cookie that keeps you signed in, and server logs (such as IP address and request times) used for security and troubleshooting.
Access tokens and refresh tokens for TikTok, YouTube, Facebook, Instagram and Threads are encrypted in our database.
2. How we use information
- To provide the Service: download and transcribe your videos, suggest clips, render them with subtitles, hooks, music and effects, and generate captions and hashtags.
- To upload a clip to your TikTok inbox as a draft, or post it to your profile with the settings you choose, and to show which TikTok account is connected.
- To upload a clip to your YouTube channel as a Short with the title, description and visibility you set, to show which channel is connected, and to check whether an upload you made has finished processing.
- To publish a clip as a Reel to a Facebook Page or Instagram professional account you connected, or as a video to your Threads profile, and to check that the post went through.
- To send a clip only when you ask for it: when you start the upload, when you schedule it in the calendar, when you approve it in the Autopilot review queue for a platform where you switched Autopilot on, or when an API token you created with the publish ability calls the Service.
- To compare hook versions in an A/B test and to learn which kinds of clips do well for you, using the performance numbers of your own clips.
- To keep the Service secure, prevent abuse and fix problems.
We do not sell your information and do not use it for advertising.
3. Sharing with service providers
We share information only as needed to run the Service:
- Google (Gemini API): transcripts and clip details are sent to suggest clips and write hooks, captions and hashtags. Totals of how your own earlier clips performed (views and similar counts, with the hook styles used) may be included to improve those suggestions. When an AI gateway is configured, the same requests go to that gateway first.
- Groq: audio from a video may be sent to create a transcript when the video has no usable subtitles.
- Pexels and Pixabay: short search keywords taken from a clip's topic, to find stock B-roll. Your videos are not sent to them.
- YouTube: the Service downloads the videos you link to.
- TikTok: clips you choose to upload, the requests needed to identify your connected account, and the requests that read the counts of clips you posted.
- YouTube (Google): clips you choose to upload with their title and description, and the requests needed to identify your connected channel and check the status of your uploads.
- Meta (Facebook, Instagram, Threads): clips you choose to publish, and the requests needed to list your Pages, identify the accounts you connect and check the status of your posts. Instagram and Threads download the video from our server: we give them a signed link to that one clip, which stops working after about 120 minutes, and Meta fetches the file through it. Facebook receives the file as an upload from us.
We may also disclose information if required by law.
4. TikTok, YouTube and Meta data
Data received from TikTok, YouTube and Meta is used only to identify the connected account in the Service, to publish the clips you choose, to follow the status of those posts, and, for TikTok, to read the counts described in section 5. It is not sold, not used for advertising and not shared with other parties except the service providers in section 3.
TikTok
The Service asks for the Login Kit and Content Posting API permissions (user.info.basic, video.upload, video.publish) and, to read statistics, video.list. Disconnecting your TikTok account in the Service deletes its stored tokens and profile details from our database. You can also remove the Service in the TikTok app, under your account settings for connected apps and services.
YouTube and Google user data
The Service uses YouTube API Services, with the scopes youtube.upload (to upload your clips) and youtube.readonly (to read your channel name and picture, and the processing status of videos the Service uploaded). Clipper Studio'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. That means we use data from Google APIs only to provide and improve the user-facing features described here, we do not transfer it to others except as needed to provide those features, to comply with law, or as part of a merger or sale with your notice, we do not use it for advertising, and no person reads it except with your consent, for security or abuse investigations, or to comply with law.
Disconnecting the channel in the Service deletes its stored tokens and channel details from our database. You can revoke the Service's access at any time on the Google security settings page. See also the YouTube Terms of Service and the Google Privacy Policy.
Facebook, Instagram and Threads
Facebook Login for Business gives the Service these permissions: pages_show_list and pages_read_engagement (list the Pages you manage and read the basic details of the Page you pick), pages_manage_posts (publish a Reel to a Page you chose), and instagram_basic and instagram_content_publish (read the basic details of, and publish a Reel to, the Instagram professional account linked to a Page you chose). Threads login gives threads_basic (your username and profile picture) and threads_content_publish (publish a video to your profile). The Service reads the list of Pages you can manage only so you can choose; it keeps the Pages and Instagram accounts you chose and nothing about the others. Disconnecting a Page, an Instagram account or a Threads profile in the Service deletes its stored tokens and details from our database, and removing a Facebook login deletes the login with every Page and Instagram account under it.
The same happens without signing in to the Service. When you remove Clipper Studio from your Facebook or Threads settings, or send a data deletion request for it from Facebook or Threads, Meta notifies the Service and it deletes that login right away, with its token, your user ID and name, every Page, Instagram account or Threads profile connected through it, and the publishing records of posts the Service made to them (their post IDs and links). A deletion request answers with a confirmation code and a link to a page showing the status of that request. Your Clipper Studio account itself, which signs in with email and password, is not deleted by these requests; see section 7 to delete it.
Disconnecting in the Service does not remove the Service from the list of apps on the other platform. To do that, remove Clipper Studio from your Facebook Business Integrations, from the Instagram Apps and Websites settings, and, for Threads, from the connected apps in your Threads or Instagram account settings.
5. Statistics we read from TikTok
With the TikTok video.list permission, the Service looks up the view, like, comment and share counts of clips that were posted through the Service, and only those. It stores a snapshot of those counts with the clip. They are used to pick the winner of a hook A/B test, to show how your clips perform and to guide the clip and hook suggestions for your account. The Service does not read your other TikTok videos or your followers.
6. Retention and deletion
- Downloaded source videos are temporary and deleted automatically after about 72 hours without use.
- Projects, transcripts, rendered clips, publishing records and statistics are kept until you delete them from your history, or until your account is deleted. Publishing records for a Facebook Page, Instagram account or Threads profile are also deleted when you remove Clipper Studio from Facebook or Threads, or send a data deletion request from there (see section 4). Rejected Autopilot clips are deleted right away.
- Platform tokens are kept until you disconnect the account, until the platform stops accepting them, or until your account is deleted.
- Account information is kept while your account exists.
- When an account is deleted, its database records are removed at once, including connected-account details and tokens, projects, transcripts, schedules, statistics, API tokens and usage records, and its rendered clips, brand logo and uploaded gameplay footage are deleted from storage. Scheduled posts and Autopilot stop before anything else, so nothing is published after the request. Database backups are rotated, so a deleted account disappears from them as older backups are replaced.
7. Your choices and how to delete your data
- Delete projects and clips from your history at any time.
- Disconnect any TikTok account, YouTube channel, Facebook Page, Instagram account or Threads profile on the Connected accounts page. This stops all publishing to it and deletes the stored tokens.
- Revoke the Service's access on the platform itself: the Google security settings page, the TikTok app's connected apps settings, Facebook Business Integrations, and the Instagram Apps and Websites page.
- Delete your account yourself: open the account menu, choose Akun saya, enter your password and type the confirmation word. The account and all data linked to it are deleted immediately, without a waiting period, and you are signed out. This cannot be undone. Before deleting, the Service asks Google, TikTok and Facebook to revoke its access to your connected accounts; if a platform does not answer, the account is still deleted and you can remove the Service from that platform's settings yourself. Threads offers no way for an app to revoke itself, so remove Clipper Studio from the connected apps in your Threads settings. Posts already published to other platforms stay there.
- Ask us to access or correct your data, or to delete an account you can no longer sign in to, by contacting us below.
8. Security
The Service is served over HTTPS, passwords are hashed, platform tokens are encrypted in our database, and access to each account's projects is restricted to that account. No method of storage or transmission is completely secure, but we work to protect your information.
9. Children
The Service is not intended for children under 13 (or the minimum age required in your country) and we do not knowingly collect their information.
10. Changes
We may update this policy. The date at the top shows the latest version.
11. Contact
Privacy questions and requests: asfahmi5@gmail.com.