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.
01
Who is responsible
The controller of your personal data under the EU General Data Protection Regulation (GDPR) is Wang Xiaochun (“we”), an individual, Warschauer Straße 33, 10243 Berlin-Friedrichshain, Germany. Email: w.xchun1982@gmail.com.
For any privacy question or request, write to support@openshorts.io or to w.xchun1982@gmail.com. We have not appointed a data protection officer, because the law does not require one for a service of this size.
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.
- Basic visit counts, no cookies: page address, referrer, country, device and browser type and page speed, counted by Cloudflare Web Analytics without cookies, without local storage and without a personal profile.
- Analytics, only if you agree: pages viewed, referrer, device and browser type, and a coarse location, collected by pvuv.ai, Google Analytics 4 and Microsoft Clarity (clicks, scrolls and session replays, with inputs and email addresses masked) 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.
- Country: the country your IP address belongs to, as Cloudflare reports it with each request. See “Country from your IP address” below.
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. Product updates and offers only if you tick the box at sign-in or turn them on in Settings → Notifications; each has a one-click unsubscribe link.
- To answer support requests and to find and fix outages.
The legal bases under Article 6(1) GDPR are:
- (b) contract: running your account, your jobs, your plan and any publishing you ask for, and answering your support requests;
- (c) legal obligation: keeping invoices and payment records for tax and accounting law;
- (f) legitimate interests: security, stopping abuse of free minutes (for example by comparing sign-up IP addresses and blocking disposable email addresses), country checks, and monitoring the service so failures are noticed. You can object to processing based on legitimate interests at any time;
- (a) consent: visitor statistics by pvuv.ai, Google Analytics 4 and Microsoft Clarity, only after you accept analytics, and product update and offer emails, only if you opt in. You can withdraw consent at any time in Privacy preferences, in Settings → Notifications, or with the unsubscribe link.
04
Who processes data for us
We use these providers only to run the service. Each one receives just what its task needs, and processes it on our behalf under a data processing agreement, except where noted as an independent controller:
- Cloudflare (United States, global network): hosting of the website on Cloudflare Workers, storage of uploads and clips in Cloudflare R2, bot checks with Turnstile, and the country lookup from your IP address.
- Neon (Postgres database hosted on Amazon Web Services in the United States, region us-east-2): account, job, support and billing records.
- Hetzner (Germany): the servers that download videos, transcribe them and render clips.
- Modal (United States): GPU servers that render clips, and may transcribe the audio, for jobs on paid plans and minute packs. They receive the source video and its transcript for the duration of the job.
- 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. We use the paid API, under which Google does not use the transcripts to improve its products.
- Anthropic (United States): the AI assistant in the support chat receives your recent chat messages and, if you are signed in, your plan; it does not receive your email address. Our internal outage alerts also send job statistics and error messages to Anthropic for a short diagnosis.
- Residential proxy networks (Evomi, DataImpulse and MiyaIP): fetching a public video, for example from YouTube, may pass through one of these networks. They see the address of the video being fetched, not your account or IP address.
- Resend (United States): account emails and replies to your support messages.
- WeCom (Tencent, China): notifications to the operator’s phone about new support and contact messages, with the email address you left and the start of your message, and about outages.
- Cloudflare Web Analytics (Cloudflare, Inc., USA): a script that counts visits and page speed without cookies, without local storage and without a personal profile. It does not track you across sites, so it loads without the consent banner (legitimate interest in knowing how many people use the site and how fast it is).
- 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. - Google Analytics 4 (Google Ireland and Google LLC, USA) and Microsoft Clarity (Microsoft, USA): page and event statistics and session replays, loaded only after you accept analytics. Google Consent Mode keeps advertising storage and ad personalisation off; Clarity masks form inputs and email addresses.
- Stripe and PayPal: payments, subscriptions and fraud checks. For payment processing they act as independent controllers under their own privacy policies.
- 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.
- TikTok: only if you connect a TikTok account, to show your display name and to post the clips you choose. See “TikTok user data” below.
We do not sell personal data or share it for advertising.
05
Transfers outside the EU
Several of the providers above process data in the United States, and WeCom in China. Those countries do not have the same data protection law as the EU, so the law requires an extra safeguard for these transfers.
- For US providers that are certified under the EU-U.S. Data Privacy Framework, the European Commission has decided that transfers to them are adequately protected.
- For the others, we rely on the European Commission’s standard contractual clauses, which are part of the providers’ data processing terms.
You can ask us for a copy of the safeguard that applies to a given provider.
06
Country from your IP address
Cloudflare tells us the country your IP address belongs to with each request. We use it for two things: to decide whether free minutes are available in your region (paid minutes work everywhere), and to decide whether the support chat is offered to visitors without a paid plan. We store the country of your latest sign-in with your account. We do not use it to locate you more precisely than the country.
07
Support chat
The chat on the site stores your messages, the email address you leave for a reply, the page you wrote from, your account if you are signed in, and your IP address for rate limits. An AI assistant (Anthropic, see above) answers common questions and hands the conversation to the operator when needed; the operator can read the whole conversation and replies in the chat and by email. If you use the chat without signing in, a cookie keeps your conversation in this browser for up to 12 months.
08
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.
09
TikTok user data
Publishing clips to your own TikTok account is optional and separate from signing in. It uses TikTok’s Login Kit and Content Posting API, and only starts when you connect an account on a finished video’s page.
- What we ask TikTok for: two permissions: to see your TikTok display name and avatar (
user.info.basic), and to post videos to your account (video.publish). We cannot read your videos, followers, messages or analytics. - How we use it: we show your TikTok name before you post, and we send a clip only after you have previewed it, chosen who can see it and which interactions to allow, declared any commercial content, and pressed Publish. Nothing is posted automatically.
- What we store: encrypted access and refresh tokens so posting keeps working, your TikTok open ID, and a record of each post (which clip, the caption, the choices you made, its status). TikTok’s tokens expire: access tokens after 2 hours and refresh tokens after 180 days.
- What we do not do: we do not sell this data, use it for advertising, or share it with anyone except TikTok to carry out the post.
- Disconnecting: use Disconnect above the clips on any finished video. We then revoke our access at TikTok and delete the stored tokens. You can also remove access in the TikTok app under Settings, Security & permissions. Closing your account does both and deletes the post records.
By using the TikTok features you also agree to TikTok’s Terms of Service and Privacy Policy.
10
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 or TikTok 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.
11
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, to data portability, and to withdraw consent with effect for the future. Write to support@openshorts.io; we answer within one month.
You can also complain to a data protection authority, for example the one where you live or the authority responsible for us: the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit).
The service is not meant for children under 16, and we do not knowingly collect their data.
12
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.
13
Changes
When this policy changes, the date at the top changes too. For material changes we also email account holders before they take effect.