Privacy

Last updated: 9 September 2026.

Cliporium is two separate things, and this page covers both because they handle your data very differently:

• The Cliporium web service at cliporium.com. You create an account, upload a long video, and our processing infrastructure finds clips in it. This part necessarily involves an account, an upload and a payment provider.
• Cliporium for Windows, a local recorder that keeps the last few minutes of your game. It has no account, and by default nothing it records is uploaded anywhere.

They are independent. The Windows app does not require a web account and does not send your recordings to the web service. The web service cannot read anything on your PC. If you use only one of them, only that part applies to you.

Part one - the Cliporium web service

This is a hosted service. Being honest about the shape of that up front: it holds an account for you, your uploaded video is stored on our cloud storage, and it is processed by machines we run. That is how it works, and there is no version of it that keeps everything on your computer.

What an account holds

Signing up asks for two things: an email address and a password. That is the whole form.

Your session is a signed token held in a cookie. There is no third-party sign-in provider wired up today - email and password is the only way in.

What happens to a video you upload

This is the part worth reading closely, so here is the whole path, in order:

1. You pick an MP4 (up to 2 GB) and choose podcast or gaming mode. Our server records a row for it - a generated storage key, the original filename so you can recognise it later, the mode, and the time - and hands your browser a short-lived upload link, valid for ten minutes.
2. Your browser uploads the file straight to our cloud storage (Amazon S3). The video does not pass through the Cliporium website itself.
3. When you start generation, a background job is queued through Inngest, our job queue. The message it carries is three identifiers - which upload, which user, which mode. No video, no filename, no email.
4. The job sends the storage key and the mode to our own GPU processing infrastructure over an authenticated HTTPS request. That machine reads the video from storage, finds the interesting moments, renders the clips and writes them back to storage. Your video is not sent to any third-party AI provider.
5. The finished clips are recorded against your account and your credit balance is reduced by the number of clips produced. If you have no credits when the job runs, it stops there and the upload is marked no credits - nothing is processed and nothing is charged.
6. Playing or downloading a clip generates a private link to that one file, valid for one hour. Your videos and clips are not publicly readable, and there is no public URL for them.

Your original upload is kept as well as the clips, so that clips can be regenerated and so you can see what a clip came from.

Payments

Payments are handled by Stripe. Card numbers are entered on Stripe’s own checkout pages and never reach our servers or our database. We could not show you your own card number if you asked.

A Stripe customer record is created for you when you sign up, using your email address, so that a later purchase has something to attach to. What we store against your account is the identifiers listed above and nothing more.

Plans are Starter at £9.99, Pro at £24.99 and Ultimate at £69.99 per month, granting 50, 150 and 500 credits respectively. Credits do not expire and are not removed when a subscription ends.

Who else handles your data

Running a hosted service means other companies necessarily process parts of it. This is all of them:

Your data is not sold and not shared for advertising. Your uploaded videos and the clips made from them are never used to train any model, by us or anyone else, and never leave our own infrastructure for processing.

Reel generation, and the one place this is different

This section applies only if you use the reel generator. If you only upload videos and get clips back, none of it touches you.

Writing a reel script is the one step we do not run ourselves. Your brand profile - the name, what the business does, your tone notes, your offer wording and your CTA keyword - is sent to Google’s Gemini API, which returns the dialogue. Your uploaded videos are never part of this; only the text you typed into a brand profile, and the script that comes back.

We use the free tier of that API, and Google’s terms for it are materially different from every other provider on this page. Google states that content submitted to the unpaid tier, and the responses it generates, are used “to provide, improve, and develop Google products and services and machine learning technologies”, and that human reviewers may read and annotate that content. So your brand profile and the scripts written from it may be used to train Google’s models and may be read by a person at Google.

We are telling you this plainly because it is the kind of thing that should not be discovered later. If that is not acceptable for your business, do not create a brand profile - the clip pipeline does not use this API and is unaffected. Put nothing confidential in a brand profile; it is meant to hold the things you would say in public anyway.

Cookies, analytics and telemetry

There is no analytics on this website. No Google Analytics, no advertising pixels, no session recording, no third-party trackers, and no profile of how you use the site.

The only cookies set are the ones that sign you in and keep the sign-in form safe from cross-site submission. They are strictly necessary for the site to work, which is why you are not being asked to consent to anything - there is nothing optional to consent to.

Fonts are bundled with the site when it is built, so your browser does not fetch them from Google or anyone else. The page you are reading now runs no JavaScript at all.

How long things are kept

Your account, your uploads and your clips are kept until you ask for them to be deleted. There is no automatic expiry today, and we would rather say so plainly than publish a retention period we do not actually enforce.

You can delete everything yourself, at any time, from Settings → Delete your account in your dashboard. It cancels any active subscription, removes every uploaded video and clip from storage, and deletes the account record. It takes effect immediately and cannot be undone. Deleting your data explains exactly what goes, and what to do if you cannot sign in.

Your rights

You can ask for a copy of what we hold about you, ask for it to be corrected, ask for it to be deleted, or object to how it is being used. Email info@nexiorastudio.com and you will get an answer within 30 days. Because your email address is the identifier for the account, please write from the address the account uses, or tell us what it is.

Part two - Cliporium for Windows

Cliporium for Windows is a local recorder. It has no account of its own, and by default nothing it records is uploaded anywhere. This part of the page says precisely what it records, where that lives, and what leaves your machine. Nothing below is affected by whether you also have a web account.

What instant replay keeps, and why that deserves a warning

While instant replay is on, Cliporium keeps a rolling buffer of everything shown on the captured monitor - not just the game. If a Discord conversation, a browser tab, an email notification or your bank statement is on that screen, it is in the buffer for as long as your buffer length allows (two minutes by default).

That is not a side effect; it is how a replay buffer works. Every product of this kind does it. We say so plainly because the alternative - letting you discover it later - is worse.

Three things bound it:

• The buffer is continuously deleted. Older segments are removed as new ones arrive, so at any moment it holds roughly your configured buffer length and no more.
• It lives only on the drive you chose, in <your drive>\Cliporium\buffer\. It is never written to a network share and never to a roaming profile.
• It never leaves your machine.

If you would rather it not run continuously, turn instant replay off and use the Record button when you actually want a recording, or set “only while a game is in the foreground” in Settings.

A recording keeps more, for longer. Pressing Record holds everything from that moment until you press Stop - up to thirty minutes - instead of the last two minutes, and saves it as one ordinary clip in your library. The warning above therefore applies to that whole span. Cliporium stops and saves a recording early if your drive starts running out of space, and tells you that is why.

What is kept permanently

Uninstalling removes the program. It deliberately does not delete your clips or your library - those are your files, and an uninstaller that silently took away a year of recordings would be doing the wrong thing. Remove those folders yourself if you want them gone.

Microphone

Off by default. It stays off until you turn it on. When it is on, your voice is recorded as a separate audio track in the clip, so you can mute it later without losing the game audio.

Windows’ own microphone privacy setting applies as usual; if Windows blocks microphone access, Cliporium reports that rather than recording silence and pretending.

Window titles

Cliporium records the title of the foreground window to label clips from games it does not recognise. Window titles can be revealing - they often contain document names, page titles or server names.

This is controlled by Settings → General → Remember window titles. Turn it off and only the executable name is stored.

Telemetry and crash reports

The Windows app has no telemetry. It counts nothing about how you use it and sends nothing about it anywhere.

Crash reports are local, and off by default. If you turn on Keep local crash reports in Settings → General, and Cliporium’s background service crashes, it writes a text file into %LOCALAPPDATA%\Cliporium\crash\ with the version, the error message, where in the code it happened and a backtrace. That file stays on your PC. Nothing reads it but you, and sending it to us is a thing you would have to do by hand.

If you never touch these settings, the Windows app makes no network requests at all except the update check, which you can also turn off, and the one download described under Captions, which happens only when you press the button.

Sharing

In Settings → Sharing you can connect a Discord webhook: a URL you create in a Discord server you run. That URL is the key to the channel, so Cliporium keeps it encrypted for your Windows account (Windows Data Protection, in %LOCALAPPDATA%\Cliporium\secrets.bin) and never shows it again, never puts it in the database, and never puts it in a log. When you connect it, Cliporium asks Discord once what the webhook is called, and nothing else.

Nothing is sent unless you press Send on an export. Then exactly one file goes: that export, with the title you typed, to the one channel you chose. No clip is ever sent on its own, no detector sends anything, and nothing is scheduled. Uploads wait until no game is in front, the same as exports, and you can cancel one while it is queued or in progress.

What you send is then on Discord under Discord’s terms, not ours. Removing the connection in Settings forgets the key; what was already sent stays where you sent it.

YouTube connects through Google’s own consent screen in your browser. The refresh token Google issues goes into the same encrypted store as the Discord webhook, and only the export you press Send on is uploaded, private by default. Nothing about the upload passes through any server of ours: your PC talks to Google directly.

TikTok and Instagram cannot be posted to from a desktop app on its own. TikTok’s token endpoint requires the app’s secret on every refresh, and Instagram does not accept an upload at all - it is given a link and fetches the file itself. So both go through Cliporium’s posting service, and this is exactly what it holds:

• The platform tokens for the account you connected, encrypted, so it can post on your behalf when you press Send. They are deleted the moment you remove the connection in Settings, and the platform is told to revoke them.
• The clip you are sending, for the minutes it takes. TikTok’s bytes never reach the service at all: your PC uploads them straight to TikTok. An Instagram reel goes to a storage slot the service signs a short-lived link for, because Meta will only fetch a reel from a link; that slot is deleted the moment Meta reports it has finished, and swept within half an hour regardless.
• The title you typed, for as long as the send is in flight, and nulled the moment it finishes. It was only ever there to hand to the platform.
• An opaque install id - a random identifier Cliporium generates once per data folder - used to rate-limit and to let you disconnect. It is not a device fingerprint and is not tied to a name, an address, or to your Cliporium web account; the Windows app never asks for one.

What the service records of a send - which platform, when, whether it worked - is deleted after seven days. Its logs carry the ids of a send and never a clip’s title, a token, or a byte of video.

While TikTok has not finished auditing the app, TikTok itself only permits posting privately, to a private TikTok account. Cliporium does not hide that: the Sharing panel says it before you connect, and the library says “posted privately: only you can see it on TikTok” on the clip afterwards.

A licence key, if you ever enter one, is checked on your PC against the issuer’s public key and kept in the encrypted store. It never phones home.

Captions

Exports can carry captions of what was said. The speech recognition runs on your PC, in a separate program (whisper.cpp) that ships with Cliporium, on the audio of the one clip you are exporting. No audio, text or anything else leaves the machine for it.

It needs a speech model, which is not included. Pressing Download model in Settings → Export fetches one file (57 MB or 181 MB, your choice) from Hugging Face over HTTPS; that request carries no identifier and Cliporium checks the file byte for byte against a hash recorded in the release before keeping it. Nothing is downloaded until you ask, and deleting %LOCALAPPDATA%\Cliporium\models\ removes it again.

A captioned export also gets a small .srt text file beside it with the same words, so you can see and edit exactly what was recognised.

Update checks

If Check for updates is on, Cliporium periodically asks a server whether a newer version exists. That request carries the current version and nothing else - no identifier, no usage data. Turning it off stops the requests entirely; you will need to update manually.

Admin mode

If you enable Admin mode, Cliporium registers a Windows scheduled task so its recorder can start with administrator rights without prompting you every time. Windows asks for your permission once, when you turn it on.

This is a convenience, not a security boundary - Microsoft’s own position is that elevation within a single user account is not one. The task’s permissions are left at the Windows default, so only an administrator can change what it launches. Turning Admin mode off removes the task.

Your data, in one place

Everything the Windows app knows lives in two folders: %LOCALAPPDATA%\Cliporium and the Cliporium folder on the drive you chose. Delete those and nothing of yours remains on your PC.

The one exception is the posting service, and only if you connected TikTok or Instagram: it holds the tokens for that account, and a record of what you sent for seven days. Removing the connection in Settings → Sharing deletes the tokens and tells the platform to revoke them. Deleting your data says how to have the rest removed, and what to do if the app is not to hand.

Changes to this page

If a future version starts sending something it did not send before, that will be stated in the release notes and will be off by default. A recorder that quietly changed its mind about this would not deserve to be trusted with a rolling capture of your screen.

Contact

info@nexiorastudio.com