ClipJit legal
ClipJit Privacy Policy
How ClipJit collects, uses, protects, and deletes your information — including Facebook Pages and Instagram professional accounts you connect.
The short version
- ClipJit never sells your personal information or your content.
- ClipJit publishes to Facebook or Instagram only when you connect an account and authorize the post.
- ClipJit's YouTube features use YouTube API Services, upload only videos you approve, and always upload them as Private — see the YouTube Terms of Service and the Google Privacy Policy.
- Access tokens are encrypted with AES-256-GCM and deleted as soon as you disconnect.
- You can delete your data at any time — see the Data Deletion Instructions.
01How ClipJit uses the X API
ClipJit uses the X API to connect your X account and publish posts you approve. Connecting is optional and happens only when you choose Connect X Account in ClipJit and authorize ClipJit on X's authorization screen.
Your use of X is governed by the X Terms of Service. X's handling of your information is described in the X Privacy Policy.
ClipJit requests only these X permissions:
tweet.read- Required by X together with posting; used to read back posts ClipJit publishes for you.
tweet.write- Publish a post you approve to your X account.
users.read- Read which X account you connected (its user ID and username) and confirm it is the account you chose.
media.write- Upload the video or image attached to a post you approve.
offline.access- Keep the connection working without signing in again every two hours.
Information ClipJit accesses, stores, and uses through the X API:
- Account details
- Your X user ID, username, display name, and profile image link — used to confirm ClipJit is connected to the account you chose and to show that connection in ClipJit.
- Posts ClipJit publishes for you
- The post text, attached media reference, post ID, link, time, and delivery status, so you can find the post and see what happened.
- Access tokens
- X's OAuth 2.0 access and refresh tokens, encrypted with AES-256-GCM and deleted when you disconnect X in ClipJit.
- ClipJit publishes a post to X only after you approve that exact post in ClipJit. It does not send direct messages, follow or unfollow accounts, like or repost, delete posts, or read your timeline, followers, or messages.
- Before every post, ClipJit confirms with X that the connection still belongs to the account you chose. If it doesn't, nothing is posted.
- Information from the X API is used only to provide these features. It is never sold, never used for advertising, and never shared with third parties other than the service providers that host ClipJit.
02What ClipJit is
ClipJit is an AI-powered video creation and editing platform for creators. ClipJit is operated by Alante Sturgues, doing business as ClipJit (“ClipJit,” “we,” “us,” or “our”).
With ClipJit you can upload or record videos, have them transcribed, find your strongest moments, add captions, effects, and edits, plan your content, and — only when you choose — publish to social accounts you connect.
This Privacy Policy explains what information ClipJit collects when you use the ClipJit website and app at clipjit.com, how we use and protect it, and the choices you have. It applies to everyone who uses ClipJit, including when you connect Facebook Pages and Instagram professional accounts.
03Information we collect
We collect only what we need to run ClipJit:
- Account and profile
- Your email address, your workspace name, sign-in and session records, and preferences such as your theme and default settings.
- Workspace and brand settings
- Team membership, brand kit items (colors, fonts, and logos you upload), style packs, and content plans you create.
- Content you upload or create
- Videos and audio you upload or record, transcripts and captions generated from them, edits, effects, renders and exported files, thumbnails, hooks, titles, and descriptions.
- Publishing information
- Captions, hashtags, schedules, the accounts you choose, approval decisions, and the post IDs and links a platform returns after something is published.
- Performance and analytics
- Performance metrics you enter, and metrics a connected platform returns where that platform provides them.
- Connected-account metadata
- For Facebook and Instagram: your Facebook Page ID and name, your Instagram professional account ID and username, the permissions you granted, and when the access token expires. We store similar identifiers for other platforms you connect.
- Device and log data
- IP address, browser and device type, pages visited, request times, and error logs, used to operate and secure ClipJit.
- Cookies
- An essential session cookie that keeps you signed in, and your theme preference stored in your browser. ClipJit does not use advertising cookies, third-party analytics trackers, or tracking pixels.
ClipJit does not ask for or store payment card numbers. If paid plans are offered, payments are handled by a payment processor.
04How we use information
- Provide ClipJit's features: transcription, finding moments, captions, edits, effects, renders, and exports.
- Connect the social accounts you authorize and publish the content you approve.
- Show your content calendar, publishing history, and performance insights.
- Learn your editing preferences inside your own workspace — for example, which styles and effects you keep or remove — to improve the suggestions ClipJit makes for you.
- Keep ClipJit secure, prevent abuse, fix problems, and enforce our Terms of Service.
- Contact you about your account, security, and important changes.
- Comply with legal obligations.
We do not sell your personal information, and we do not use your content or data from connected platforms for advertising or to build profiles about you.
05How ClipJit uses Meta, Facebook, and Instagram APIs
ClipJit uses Meta's official Facebook Graph API and Instagram Graph API through Facebook Login. Connecting is optional and happens only when you choose Connect with Facebook in ClipJit and approve access on Meta's authorization screen.
When you connect, you may authorize ClipJit to access Facebook Pages you manage and the Instagram professional accounts (Business or Creator accounts) linked to those Pages. You choose which Pages and accounts to share on Meta's authorization screen, and you can change or remove that access later.
ClipJit may request the following permissions:
instagram_basic· Instagram- Read your Instagram professional account's basic profile (account ID and username) so ClipJit can show and verify which account you connected.
instagram_content_publish· Instagram- Publish Reels and posts you approve to your Instagram professional account, and check whether each post finished publishing.
pages_show_list· Instagram & Facebook Page- List the Facebook Pages you manage so you can choose which Page to connect (Instagram professional accounts are linked to a Page).
pages_read_engagement· Instagram & Facebook Page- Read basic information about the Page you choose, including its linked Instagram professional account, to set up and verify the connection.
pages_manage_posts· Facebook Page- Publish Reels and posts you approve to your Facebook Page.
business_management· Instagram & Facebook Page- Access the Pages and Instagram professional accounts you manage through a Meta business portfolio, so they appear when you connect.
ClipJit uses this access only to:
- Identify the Facebook Page and Instagram professional account you connected, and confirm the connection works.
- Publish Reels and posts to that Page or Instagram account — only content you authorize.
- Check whether a post ClipJit published for you succeeded, so ClipJit can show its status.
ClipJit does not read your personal Facebook profile, friends list, or messages; it does not post anything you haven't authorized; and it does not currently request Meta insights permissions. If that changes, we will update this policy and ask for your authorization first.
Data ClipJit receives from Meta is used only to provide the features you use. It is never sold, never used for advertising or profiling, never shared with data brokers, and is handled in accordance with Meta's Platform Terms and Developer Policies.
06How ClipJit uses YouTube API Services
ClipJit uses YouTube API Services (the YouTube Data API) to connect your YouTube channel and upload videos you approve. Connecting is optional and happens only when you choose Connect YouTube in ClipJit and allow access on Google's authorization screen.
By using ClipJit's YouTube features, you agree to be bound by the YouTube Terms of Service. Google's handling of your information is described in the Google Privacy Policy.
ClipJit requests only these Google permissions:
https://www.googleapis.com/auth/youtube.upload- Upload videos you approve to your channel.
https://www.googleapis.com/auth/youtube.readonly- Read which channel you connected, confirm it is the channel you chose, check that it can accept uploads, and show the status of your recent uploads during a connection check.
Information ClipJit accesses, stores, and uses through YouTube API Services:
- Channel details
- Your channel ID, channel name, and handle — used to confirm ClipJit is connected to the channel you chose and to show that connection in ClipJit.
- Channel status and connection checks
- Whether the channel can accept uploads, and the result of your latest connection check, so ClipJit can show connection health.
- Your recent uploads
- The titles, privacy status, and dates of your most recent uploads, read only to display them during a connection check and not stored. For videos ClipJit uploads for you, ClipJit keeps the video ID and link so you can find them.
- Access tokens
- Google's OAuth tokens, encrypted with AES-256-GCM and deleted when you disconnect YouTube in ClipJit.
- ClipJit uploads a video only after you approve it, and every upload is set to Private. ClipJit does not make videos public or unlisted, schedule public releases, notify subscribers, edit or delete your existing videos, or post comments.
- Before every upload, ClipJit confirms with Google that the connection still belongs to the channel you chose. If it doesn't, nothing is uploaded.
- Information from YouTube API Services is used only to provide these features. It is never sold, never used for advertising, and never shared with third parties other than the service providers that host ClipJit.
- ClipJit does not show third-party advertising.
07ClipJit only publishes when you authorize it
Connecting an account does not publish anything. ClipJit publishes content only when you authorize it.
- By default, every post requires your approval before it can be published.
- If you turn on scheduling or automation rules, ClipJit publishes only within the accounts, content types, and schedules you set. You can pause or turn them off at any time.
- ClipJit never publishes to an account you haven't connected, and never uses a connection for anything other than the posts you create in ClipJit.
- Connection checks in ClipJit, such as Test Connection and Run Real Validation, verify access without publishing.
08How OAuth access tokens are stored and protected
When you connect Facebook, Instagram, or another platform, that platform gives ClipJit an OAuth access token. ClipJit protects it as follows:
- Tokens are encrypted at rest with AES-256-GCM using a dedicated encryption key kept as a server secret, separate from the database.
- Tokens are decrypted only in server memory when ClipJit calls the platform for you. They are never sent to your browser, shown in the ClipJit interface, or written to logs.
- The platform app credentials ClipJit uses to talk to Meta are also encrypted with AES-256-GCM.
- ClipJit records when each token expires and asks you to reconnect when it does.
- When you disconnect an account in ClipJit, the stored tokens for that account are deleted immediately.
- Access to production systems is limited to authorized personnel.
09How we process videos, captions, publishing information, analytics, and account metadata
- Uploaded videos and audio
- Stored in private cloud storage and accessed through short-lived signed links. ClipJit processes them to create transcripts, find moments, render edits, and detect where faces appear in the frame so captions and graphics don't cover them. Face detection only locates faces; ClipJit does not identify people or create face recognition templates.
- Transcripts and captions
- Created with a speech-to-text provider and used to build captions, hooks, titles, and edits. You can review and edit them before anything is published.
- AI analysis
- Transcripts and content details may be sent to an AI model provider to suggest hooks, moments, captions, and effects. ClipJit does not sell your content and does not use it to train AI models.
- Publishing information
- Captions, hashtags, schedules, approvals, and the post IDs platforms return are stored so you can see what was published, when, and where.
- Analytics
- Metrics you enter, or that connected platforms return, are stored in your workspace to show performance and improve future suggestions for you. We don't combine them with data from other sources to profile you.
- Account metadata
- Page IDs and names, Instagram account IDs and usernames, granted permissions, and token expiry are stored to show which accounts are connected and to publish to the right place.
10How we share information
We share information only as needed to run ClipJit:
- Service providers that process data on our behalf under agreements that limit how they can use it (listed below).
- Platforms you connect, when you ask ClipJit to publish or to verify a connection.
- Legal and safety reasons, when required by law or to protect the rights, safety, and security of our users, ClipJit, or others.
- Business transfers, if ClipJit is involved in a merger, acquisition, or sale of assets — subject to this policy.
We never sell or rent personal information, and we don't share data received from Meta with data brokers or advertising networks.
11Third-party services and processors
ClipJit relies on the following third-party services. Each receives only the data it needs for its job:
- Cloud hosting and infrastructure
- Application servers, a PostgreSQL database, a Redis job queue, and S3-compatible private object storage for your files.
- Speech-to-text
- Deepgram, to transcribe the audio in videos you upload.
- AI models
- Anthropic, to analyze transcripts and suggest hooks, moments, captions, and edits.
- Social platforms you connect
- Meta (Facebook and Instagram), Google (YouTube), TikTok, and LinkedIn — only when you connect them, and only to connect and publish as you direct.
- Optional features you turn on
- A payment processor (Stripe) if paid plans are enabled; avatar and voice providers (such as HeyGen, Tavus, or Synthesia) only if you enable Creator Twin features and give recorded consent; and licensed stock or media generation providers only if you enable them.
12Security practices
- Encryption in transit with HTTPS (TLS).
- AES-256-GCM encryption at rest for access tokens and platform app credentials.
- Private storage for media files, accessed through short-lived signed links.
- Workspace isolation: your data is scoped to your workspace, and every request is checked for authorization.
- Protection against cross-site request forgery and abuse, including same-origin checks and rate limiting.
- Tokens and secrets are redacted from logs and error messages.
- Least-privilege access to production systems.
No system is perfectly secure. If a security incident affects your personal information, we will notify you and the appropriate authorities as required by law.
13Data retention
- Access tokens
- Deleted immediately when you disconnect an account, or when your account is deleted.
- Your content
- Videos, transcripts, captions, edits, and renders are kept until you delete them or your account is deleted.
- Connected-account metadata and publishing history
- Kept while your account is active and deleted when you delete your account or ask us to delete it.
- Deletion requests
- Completed within 30 days of verifying your request.
- Backups
- Deleted data ages out of backups within 30 days.
- Logs
- Kept for up to 90 days for security and troubleshooting.
- Legal records
- Kept longer only where the law requires it — for example, billing records if you use a paid plan.
14How to disconnect Facebook and Instagram
- In ClipJit
- Go to Integrations (or Provider Activation), find Instagram or Facebook, and choose Disconnect. ClipJit deletes the stored access tokens immediately and stops publishing to that account.
- On Facebook
- Open Facebook and go to Settings & privacy → Settings → Business integrations (on some accounts this is Apps and websites). Select ClipJit and choose Remove.
- On Instagram
- Open Instagram and go to Settings → Website permissions → Apps and websites. Under Active, select ClipJit and choose Remove.
Removing ClipJit in Facebook or Instagram revokes its access at Meta. Meta may rename these menus over time. To also delete the data ClipJit already stores, follow the Data Deletion Instructions.
15How to disconnect YouTube and revoke Google access
- In ClipJit
- Go to Integrations → YouTube and choose Disconnect YouTube. ClipJit revokes its access at Google, deletes the stored Google access tokens immediately, and stops uploading to that channel.
- On Google
- Open your Google Account's third-party access page, select ClipJit, and remove its access.
Removing ClipJit at Google revokes its access to your YouTube channel. To also delete the data ClipJit already stores, follow the Data Deletion Instructions.
16How to disconnect X and revoke access
- In ClipJit
- Go to Integrations → X and choose Disconnect. ClipJit revokes its access at X, deletes the stored X access tokens immediately, and stops posting to that account.
- On X
- Open X's connected apps settings, select ClipJit, and revoke its access.
Revoking ClipJit on X removes its access to your X account. To also delete the data ClipJit already stores, follow the Data Deletion Instructions.
17How to request deletion of your data
You can ask us to delete your ClipJit account and data at any time. Email alante@xtramilecoverage.com from the email address on your ClipJit account with the subject ClipJit data deletion request.
The full process — what to include, how we verify requests, what we delete, and how long it takes — is on our Data Deletion Instructions page.
18Your rights
Depending on where you live — for example, the European Economic Area, the United Kingdom, or U.S. states such as California — you may have the right to:
- Access the personal information we hold about you and receive a copy.
- Correct inaccurate information.
- Delete your personal information.
- Receive your data in a portable format.
- Object to or restrict certain processing.
- Withdraw consent at any time, including by disconnecting an account. This doesn't affect processing that already happened.
- Not be discriminated against for exercising these rights.
To exercise a right, email alante@xtramilecoverage.com. We'll verify your request and respond within the time required by applicable law, usually within 30 days. You may also have the right to complain to your local data protection authority.
19Children
ClipJit is not directed to children under 13, and you must be at least 18 to use ClipJit under our Terms of Service. We don't knowingly collect personal information from children. If you believe a child has given us personal information, contact us and we will delete it.
20International data transfers
Your information may be processed in the United States and in other countries where ClipJit or its service providers operate. Where the law requires it, we use appropriate safeguards for these transfers.
21Updates to this Privacy Policy
We may update this Privacy Policy from time to time. When we do, we'll post the new version on this page and update the effective date. If a change is material, we'll notify you by email or in the app before it takes effect.
22Contact us
Questions or requests about this Privacy Policy or your data:
- Operator
- Alante Sturgues, doing business as ClipJit
- Website
- clipjit.com