OpenShorts.io
  • Free AI clipping toolLong video in, captioned Shorts out
  • Video aspect ratio converter16:9 to 9:16 in your browser
  • YouTube to ShortsPaste a link, get vertical clips
  • Opus Clip alternativePrice per minute, features, self-hosting
  • Snazo alternativeFree tier, refunds, clipping for pay
  • Self-host OpenShortsMIT, Docker, no watermark
  • API and MCP serverClip from Claude, Codex, Cursor…
Pricing
  • English
  • Français · accueil
  • Português (Brasil) · início
  • Deutsch · Startseite
  • 日本語 · ホーム
  • Español · inicio
  • العربية · الرئيسية
Log inStart clipping
OpenShorts.io

OpenShorts is an MIT-licensed open-source AI video clipper. OpenShorts.io is an independent deployment of that code.

Product

  • Free AI clipping tool
  • YouTube to Shorts
  • Video aspect ratio converter
  • Open source AI clipper
  • OpenShorts pricing
  • About OpenShorts.io

Resources

  • Source on GitHub
  • Self-host guide
  • API and MCP server
  • Opus Clip alternative
  • Snazo alternative
  • Clipping campaigns

Legal

  • Privacy
  • Terms
  • Refunds
  • Cookie preferences
  • Contact support

© 2026 OpenShorts.io · Code under the MIT licence

Legal

Privacy Policy

How Wang Xiaochun handles your account, the videos you submit and payment details when you use the online clipper at openshorts.io. It does not cover copies of the open-source code that other people run themselves.

Updated 2026-11-18 · OpenShorts.io

01

Who is responsible

openshorts.io is operated by Wang Xiaochun, an individual based in Germany (contact: w.xchun1982@gmail.com). Wang Xiaochun is the controller of your personal data (“we”). For any privacy question or request, write to support@openshorts.io or to w.xchun1982@gmail.com.

02

What we collect

  • Account: your email address and display name, sign-in sessions and the IP address and browser they came from. There are no passwords: you sign in with a one-time code we email you (stored only as a hash, valid for 10 minutes) or with Google, in which case we receive your name, email address and profile picture from Google.
  • Videos: the links you paste, files you upload, the transcript we generate, and the clips, titles and captions produced from them.
  • Usage: the minutes each job used, job status and error codes, so we can enforce plan limits and fix failures.
  • Payments: plan, amount, dates and the reference numbers from Stripe or PayPal. Card and PayPal account details are entered with those providers and never reach our servers.
  • Analytics, only if you agree: pages viewed, referrer, device and browser type, and a coarse location, collected by pvuv.ai after you accept analytics in Privacy preferences.
  • Support: anything you send us by email, the contact form or the chat on the site, with the email address you leave for our reply and the page you wrote from.

03

Why we use it

  • To run the service you asked for: download or receive the video, transcribe it, choose and cut clips, and deliver them to you.
  • To keep accounts secure and stop automated abuse.
  • To bill paid plans and keep the records tax law requires.
  • To send account emails such as sign-in codes and receipts. We do not send marketing email.

04

Who processes data for us

We use these providers only to run the service. Each one receives just what its task needs:

  • Cloudflare (United States, global network): hosting, bot checks with Turnstile, and storage of uploads and clips.
  • Neon (database hosted on AWS in the United States): account, job and billing records.
  • Hetzner (Germany): the servers that download and process videos.
  • Groq (United States): speech-to-text for the audio track.
  • Google Gemini API (United States): reads the transcript to pick clip moments and write titles. While we use Google’s free API tier, Google may use the transcripts it receives to improve its products.
  • Google Sign-In: only if you choose it, to confirm who you are. Signing in gives us no access to your Google Drive, YouTube channel or other Google data.
  • YouTube API Services (Google): only if you connect a YouTube channel, to upload the clips you choose to publish. See “YouTube and Google user data” below.
  • Network proxy providers: fetching a public YouTube video may pass through a proxy network; it sees the video address, not your account.
  • Resend (United States): account emails and replies to your support messages.
  • pvuv.ai: privacy-focused visitor statistics, loaded only after you accept analytics. It sets a first-party cookie _pv_id (kept up to 13 months) and stores IP addresses only as truncated, hashed ranges together with a hashed browser fingerprint, so visits can be counted without identifying you. You can withdraw consent at any time in Privacy preferences, which deletes these cookies.
  • Stripe and PayPal: payments, subscriptions and fraud checks, under their own privacy policies.

We do not sell personal data or share it for advertising. Data may be transferred outside your country to the places listed above; where the law requires it, we rely on the providers’ standard contractual safeguards.

05

YouTube and Google user data

Publishing clips to your own YouTube channel is optional and separate from signing in. It uses the YouTube API Services, and only starts when you connect a channel on a finished video’s page.

  • What we ask Google for: one permission, to upload videos to your channel (youtube.upload). We cannot read, edit or delete your existing videos, comments, playlists, subscribers or analytics.
  • How we use it: we upload a clip only when you choose it and press Publish, with the title, description, visibility and audience setting you choose. Nothing is uploaded automatically.
  • What we store: an encrypted refresh token so uploads keep working, the channel ID and name that YouTube returns after your first upload, and a record of each publish (which clip, its title, visibility, status and the YouTube video ID).
  • What we do not do: we do not sell this data, use it for advertising, or share it with anyone except Google to carry out the upload. Wang Xiaochun’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
  • Disconnecting: use Disconnect above the clips on any finished video. We then revoke our access at Google and delete the stored token. You can also remove access in your Google security settings. Closing your account does both and deletes the publish records.

By using the YouTube features you also agree to be bound by the YouTube Terms of Service. Google’s handling of your data is described in the Google Privacy Policy.

06

How long we keep it

  • Uploaded and downloaded source videos are deleted within 2 days of the job.
  • Finished clips stay downloadable for 3 days on the free plan, 30 days on Starter and Plus, and 90 days on Pro and Ultra.
  • A YouTube connection is kept until you disconnect it or close your account; publish records are kept with the account.
  • Account data is kept while the account is open and deleted within 30 days after you ask us to close it.
  • Support chats are deleted 24 months after the last message, or with your account if you close it sooner.
  • Payment records are kept for as long as tax and accounting law requires, usually seven years.

07

Your choices and rights

You can download your account data from your settings, and ask us to correct or delete it. Depending on where you live, you may also have the right to object to or restrict processing and to complain to your data protection authority. Write to support@openshorts.io; we answer within 30 days.

The service is not meant for children under 16, and we do not knowingly collect their data.

08

Security

Traffic is encrypted, sign-in codes are stored only as hashes, file links are signed and expire, and access to production systems is limited to the operator. No system is perfectly secure; if a breach affects your data, we will tell you as the law requires.

09

Changes

When this policy changes, the date at the top changes too. For material changes we also email account holders before they take effect.