Legal
Privacy Policy
This page explains how UseShorts processes video on your computer and when its features use external services.
UseShorts Cloud Posting
UseShorts and UseShorts Cloud Posting at useshorts.app are operated by GROUPAI APP. Cloud Posting is a service for creators to organize their completed clips and review delivery to social accounts they authorize. It is currently restricted to owner acceptance; ordinary customer access and TikTok public posting are disabled pending provider approval and operational launch checks.
If you choose Cloud Posting, completed exports and generated thumbnails are stored privately with their account and posting-profile associations. Playback and download use time-limited authorization. Local source videos and exports are not deleted by a cloud delivery. Cloud storage and posting availability are separate from the desktop software licence.
Video processing
UseShorts processes your source video on your computer for framing, preview and export. Your selected output files are written locally.
Clip discovery and premium captions use the external services described below.
Cloud AI clip discovery
For clip discovery, transcript text, timestamps and candidate-opening details are sent to the configured cloud AI provider for analysis. This analysis does not require uploading the entire source video to that provider.
YouTube Cloud Posting
UseShorts uses YouTube API Services only after you choose to connect a YouTube account. We request YouTube management permission to identify the channel you select, upload completed clips you expressly choose, read their processing and visibility status, and update publication schedules you request. Google labels this permission as access to see, edit, and permanently delete YouTube videos, ratings, comments and captions. UseShorts uses it for the channel and video delivery features described here; it does not use it to manage comments, ratings or captions, or to delete your YouTube videos. UseShorts does not request or store your Google or YouTube password.
We store the selected channel ID, channel name, channel thumbnail, granted scopes, encrypted OAuth access and refresh credentials, and delivery metadata including the video ID, requested visibility, publication time and time zone, provider processing status, and last status check. We use this data only to show your connected destination, recover the delivery you request, and reconcile its status. We do not sell it, use it for advertising, or use it to train AI models. UseShorts' use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Before a delivery, you choose Private, Unlisted, Public now, or a future public publication time and confirm the displayed channel, completed MP4, title, description, audience choice and synthetic-media disclosure. These confirmed details are sent to YouTube. A confirmed cloud transfer can continue on our server after you close the page. Scheduled videos remain private until YouTube publishes them at the confirmed time. Rescheduling updates that time on YouTube; cancelling an unpublished schedule removes it on YouTube and leaves the video private. We check the provider result before reporting success. You can also change your videos directly in YouTube Studio.
Disconnecting YouTube removes UseShorts' active access for that posting profile and revokes the OAuth grant when it is no longer shared by another profile. It does not delete videos already stored by YouTube. You can also revoke access in Google's security settings. To request deletion of YouTube API data retained by UseShorts, email support@useshorts.app; we will delete applicable stored API data as soon as possible and within seven calendar days. To delete a video held by YouTube, use YouTube or another authorized YouTube client.
Use of YouTube through UseShorts is also subject to the YouTube Terms of Service and the Google Privacy Policy.
Instagram Reels connection and delivery
The restricted Instagram integration connects an Instagram Business or Creator account to a posting profile using Instagram Login. With your permission, we receive its Instagram ID, username, account type and encrypted access credential. We use these only to show your destination, carry out the Reel deliveries you confirm, maintain access and reconcile provider status. We do not request messages, comments, advertising or contacts permissions.
When you confirm a Reel, we send Meta the selected completed MP4 through a short-lived read link limited to that private cloud asset, its caption and your AI-generated-media disclosure. The storage remains private. Instagram publication follows the connected account’s settings and is not a private YouTube upload. A confirmed scheduled job runs on the server with the website and desktop closed; publication can be delayed by provider processing, permissions, limits or outages. You may cancel before publication begins.
Disconnecting removes UseShorts’ active access from the profile and stops pending jobs from using that credential. It does not delete a Reel already published on Instagram. You can revoke the app’s authorisation in Instagram’s Apps and Websites settings. To request deletion of Instagram credentials, account identity and retained delivery data from UseShorts, email support@useshorts.app. We process applicable deletion requests within seven calendar days. Delete published Reels directly in Instagram. Meta’s processing is governed by the Instagram Privacy Policy.
TikTok connection and restricted private posting
The owner-restricted TikTok provider Sandbox supports account connection and private Direct Post tests on useshorts.app. This is not customer availability, public-post approval or a completed Direct Post audit. With your consent, UseShorts receives the authorized TikTok Open ID, display name, available profile image, granted permissions, and access and refresh credentials. Credentials are encrypted on the server; UseShorts does not request your TikTok password. We use this information to show the selected destination and retrieve its current permitted privacy, interaction and duration settings.
Only after your explicit posting confirmation, TikTok receives the selected completed MP4, editable caption, chosen visibility and interaction settings, and applicable AI and commercial disclosures. TikTok downloads the clip through an expiring authorization limited to that delivery and private asset on our verified domain; the underlying storage is not made public. The current Sandbox flow permits Only me (SELF_ONLY) tests. A confirmed job can continue on the server after the website and desktop close.
We retain the posting-profile and destination association, clip reference, chosen settings and consent, requested time and time zone, provider publish/post identifiers when returned, transfer information, processing results, errors and status-check times to operate and reconcile the same delivery. A completed private post may require the connected account to sign in to TikTok Studio; UseShorts does not inspect the TikTok browser session. We do not use TikTok connection or posting data to train AI models or sell it.
Disconnecting clears UseShorts’ stored access and refresh credentials for that posting profile. An active delivery may need resolution before disconnecting is permitted. Connection identity and delivery history are retained separately; disconnecting does not delete a TikTok post or a local export. You can revoke authorization in TikTok’s account settings. Delete a published post in TikTok; Delete from cloud removes the UseShorts cloud asset, not the TikTok copy. To request deletion of retained TikTok identity, connection and delivery data, email support@useshorts.app. TikTok’s handling of transferred content and account data is governed by its Privacy Policy.
Purchases and licensing
GROUPAI APP sells current UseShorts licences and subscriptions directly, with payments processed through Stripe. Historical purchases processed by Lemon Squeezy remain subject to its checkout, billing, and refund processes. UseShorts does not directly store your payment-card details. Purchase and licence information needed to provide access and assist with an order may include order status, purchase timestamp, licence status, activation timestamp, and the number of active computer instances.
Support and refund review
To review a support or refund request, we may use the limited commercial and licensing information above. We may also use your app version if you supply it or it is collected transparently, plus troubleshooting information you voluntarily provide.
Normal refund eligibility review does not require us to collect your source videos, transcripts, captions, exported clips, or prompts. See the refund policy in our Terms for the purchase rules.
Diagnostics and customer content
Customer content is not automatically uploaded as diagnostics. If you contact support, you decide what troubleshooting information to provide. Please avoid sending sensitive content unless it is necessary for your request.
Website analytics and advertising
We use Google Analytics 4 to understand visits, referral sources and actions such as trial starts, plan selections, checkout starts and Windows downloads. Google Analytics may use cookies and process browser and device information. With analytics on, we also send Stripe-confirmed purchase value, tax, currency, product and a hashed transaction ID from our server. We do not send your account email, payment-card details, video content or API keys to Google Analytics.
We also record limited first-party website sessions across public pages and the account entry page using a pseudonymous session cookie. The report includes acquisition source, device category, active time, scroll depth and selected actions, and is retained for 30 days. It does not include your email address, payment details or video content. A new session is created after the session cookie expires.
When analytics is on at Checkout, we retain its Google Analytics client and session identifiers with the Checkout reference for up to 63 days to match a confirmed payment to the original visit. Turning analytics off stops new browser analytics events and prevents those identifiers from being attached to a new Checkout. A payment already linked to an earlier Checkout may still be reported; turning analytics off does not erase events previously sent.
We also use the Reddit Pixel to measure website visits and confirmed purchases related to Reddit ads. Reddit may use cookies and process browser information and a Reddit click ID for attribution. We do not send your account email, video content, API keys or payment-card details to Reddit through this Pixel.
On the public homepage, Microsoft Clarity helps us understand page interactions through masked recordings and heatmaps. We use strict content masking and have disabled Clarity cookies. Clarity is not installed on account, sign-in, or checkout pages. We remove Reddit click IDs and other non-public query parameters before Clarity loads.
External services
YouTube API Services, the caption service, your configured cloud AI provider, Stripe for current purchases, and Lemon Squeezy for historical purchases process the information described above for their respective functions. Their own terms and privacy practices may apply to information sent to them.
Privacy questions
For questions about this policy or a support request, please visit our Questions or support section.