Privacy

Last updated: 3 October 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. You can then post or schedule those clips to TikTok, Instagram, YouTube or Discord accounts you connect. 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 needs no account, and nothing it records is uploaded unless you choose to send a recording, or an export to be posted, to your Cliporium account.

They are independent unless you connect them. The Windows app does not require a web account. If you sign in to your web account in the app, you can send a recording from your PC to be clipped here, and schedule posts through your account; nothing is sent until you press Send or Schedule on a particular recording or export, and once it arrives it is an upload like any other, covered by Part one. The web service cannot read anything on your PC. If you use only one of them, only that part applies to you.

Who we are

Cliporium is run by Nexiora Ltd, a company registered in the United Kingdom. Nexiora Ltd decides how and why the data on this page is used, which makes it the data controller under UK data protection law. You can reach us at info@nexiorastudio.com.

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.

Cliporium for Windows signs in differently: it opens this website in your browser, you sign in and press Allow here, and the app then holds a token of its own. It never sees your password. That token is refused the moment you sign the PC out, change your password, or leave the PC unused for 60 days, and it lasts 90 days at most.

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 a mode: general, gaming, tutorial or podcast. 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 (Cloudflare R2). The video does not pass through the Cliporium website itself. It is kept there for 30 days, then deleted automatically - see how long things are kept.
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, transcribes the speech on that machine, finds the interesting moments, renders the clips - with one still picture of each, to show in your library - and writes them back to storage. Your video and its audio are not sent to any third-party AI provider. For podcast clips, the text of the transcript is sent to Google’s Gemini API to choose the moments worth clipping - see Google Gemini below. General, gaming and tutorial clips are chosen on that machine with no AI provider; only if that fails is their transcript text sent to Gemini instead.
5. The finished clips are recorded against your account and your credit balance is reduced by two credits for each clip 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.

A recording sent from Cliporium for Windows follows the same path, with three differences. It can be up to 6 GB, and goes up in pieces, each through its own link valid for an hour, so a large recording can carry on after an interruption. The app sends the choices you made - mode, framing, caption style, how many clips - and the recording’s own file name, and nothing else about your PC. And until the last piece has arrived it is an unfinished upload: discarded at once if you cancel it or delete your account, and within a week if it is simply never finished.

Your plays, only if you ask. With “Use my game events to find my plays” turned on in the app, a gaming recording also carries your own plays in it, as the game itself reported them to the app: the times of your kills, multikills, aces, first bloods and objective steals, and what each was. Nothing else about them - no player names, no scores, not your deaths, nothing another player did. We use them only to choose which moments of that recording to clip, keep them with that upload so that asking for more clips uses them too, and delete them with it. We are never told which of your clips holds which play; the app works that out on your PC.

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. They only leave it when you post them to a platform you connected.

Google Gemini

This section applies if you generate reels or motion graphics, or make clips: the sound of every clip is sent to Gemini to score it. Podcast clips also send their transcript; general, gaming and tutorial clips send theirs only if choosing their moments on our own machine fails.

If every Gemini model is unavailable - an outage or a used-up quota - the same text is sent to Groq instead, so your clips or reel can still be made. Groq receives only that text, never your video, audio or brand images, and Groq states that it does not use it to train models.

For podcast clips, the transcript text of your video - the words, not the video or audio - is sent to Gemini, which returns the moments worth clipping. The same happens for a general, gaming or tutorial video only if choosing its moments on our own machine fails.

Each clip’s score in My clips - how likely it is to do well, from 0 to 100, with a few words on why - is Gemini’s judgement from hearing it. The clip’s sound is sent, up to its first minute and a half, as low-quality mono audio; its picture never is. The score is an estimate, not a forecast of how a post will do.

Writing a reel script, or the words for a motion-graphics video, is also done by Gemini. Your brand profile - the name, what the business does, your tone notes, your offer wording and your CTA keyword - and up to four of the pictures you added to it are sent to Google’s Gemini API, which returns the dialogue, or the video’s text and voiceover lines. Your uploaded videos are never part of this; only your brand profile, its pictures, and what 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, the scripts written from it and the sound of your clips may be used to train Google’s models, and may be read or heard 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, and do not clip a video whose sound you would not want a person at Google to hear. Put nothing confidential in a brand profile; it is meant to hold the things you would say in public anyway.

Connected social accounts

This section applies only if you connect a TikTok, Instagram, YouTube or Discord account to post or schedule your clips. You never have to: every clip can be downloaded and posted by hand instead.

YouTube. Cliporium uses the YouTube API Services to upload to a channel you connect. By connecting YouTube you agree to be bound by the YouTube Terms of Service, and Google’s handling of your data is covered by the Google Privacy Policy. You can remove Cliporium’s access at any time from your Google Account’s security settings.

What we receive, and what we keep

Access and refresh tokens are encrypted (AES-256-GCM) before they are stored. Tokens and webhook URLs are never sent to your browser and never passed to our job queue. The names and pictures in the last column are kept in our server’s cache for up to an hour, so that every page load does not ask the platform again, and are then discarded. While an account stays connected, we renew its tokens with the platform so scheduled posts keep working.

What we use it for

Only these:

• Showing you which account is connected, on the Connections page and wherever you choose an account to post to.
• Publishing what you choose to post: a clip you post now, a post you schedule, or new clips sent to an account by an automation you set up on the Calendar. Nothing is posted any other way.
• Keeping what we hold up to date: for YouTube, the channel’s handle is read again every night, and the videos Cliporium uploaded are checked every 25 days to see whether they are still there. YouTube requires anything an app keeps from it to be refreshed or deleted within 30 days.

We do not read your other posts, followers, likes, comments, messages or analytics - for YouTube, only whether the videos Cliporium uploaded are still there - and we never edit or delete anything on your account. Data from TikTok, Meta and Google is not sold, not used for advertising or marketing, not used to train any model, not shared with other Cliporium users, and not used for anything other than the things above.

What is sent when you post

• TikTok. Our server uploads the video file to TikTok. Where Cliporium posts directly, it also sends the caption and the privacy, interaction and commercial content settings you chose, and TikTok publishes it. Until TikTok approves Cliporium for direct posting, the video is instead delivered to your TikTok inbox as a draft, with no caption, for you to finish and post in the TikTok app.
• Instagram. Instagram fetches the video itself from a private link to that one file, valid for two hours, together with the caption and cover frame you chose, and publishes it as a reel.
• YouTube. Our server uploads the video file to your channel with the title, description, tags, visibility and made-for-kids answer you chose, exactly as you wrote them. The one addition is the one the form tells you about: your tags are also added to the end of the description as hashtags. An automation titles each video with its reel’s opening line.
• Discord. The video is sent to your webhook with your title and caption. If it is too large for Discord to accept, a private download link valid for seven days is sent instead.

Once posted, the content is on that platform under its own terms and privacy policy - see TikTok’s and Instagram’s and the YouTube Terms of Service. Cliporium keeps a record of each post on your Calendar - the platform, account, time, caption, tags, status and a link to the post - until you delete it or your account. A link to a YouTube video is checked with YouTube every 25 days, and removed once the video, or the connection to its channel, has gone. If you tick delete the video after posting, the clip file is removed from our storage once it has gone out.

Disconnecting, and deleting this data

• In Cliporium: Connections → Disconnect, beside the account. The stored tokens, IDs and username for that account are deleted immediately - for YouTube, with the links to the videos Cliporium uploaded - and Google or TikTok is asked to cancel Cliporium’s access. Deleting your Cliporium account does the same for every connected account.
• At the platform: on TikTok, Settings and privacy → Security and permissions → Manage app permissions; on Instagram, Settings → Website permissions → Apps and websites; on YouTube, your Google Account’s third-party access page. Removing Cliporium there stops its tokens working straight away. For YouTube, Cliporium notices when it next checks the connection, which it does nightly: the Connections page asks you to reconnect, and if you do not within a week, everything it held for that channel is deleted. For TikTok and Instagram, disconnect in Cliporium as well to delete them from our database.

Deleting your data covers this in full, including what to do if you cannot sign in.

If you apply to the partner programme

The form on our partner programme page sends us what you type into it - your name, your email address, where you would share Cliporium, your links, the audience size if you give one, and what you write about how you would introduce it. It is not stored in our database: it arrives as an email to info@nexiorastudio.com, and we use it to consider your application and to reply to you. Nothing is sent to the address on the form except that reply, and applying does not create a Cliporium account or sign you up to anything.

If you arrive from a partner’s link, nothing is stored on your device. Their code travels in the address bar - the ?ref= you can see there - and is sent with the sign-up form if you create an account, which is the only moment we record it. There is no affiliate cookie and no tracking script. The same happens if you use a partner’s discount code at checkout: we note which partner it belongs to so we can pay them. What the partner is told is that somebody subscribed - never who you are, what you upload, or what you make with it.

We keep an application while we are considering it and, if you join the programme, for as long as you are a partner and as long as we need the records of what we paid you. If you would rather we deleted it sooner, email us and we will. Applying is not a purchase, so the lawful basis is our legitimate interest in answering people who ask to work with us, and the steps taken at your request before any agreement.

Cookies, analytics and telemetry

There are no third-party 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.

We do count page views, in the simplest form that is still useful: for each page and each day, how many times it was opened, and, when you arrive from another website, that site’s name (for example youtube.com - never the page you came from). Nothing else is recorded: no cookie, no IP address, no account, no device or browser details. A count cannot be traced back to you or linked to anything else you do here. The counts are kept in our own database and are not shared with anyone.

The only cookies Cliporium sets 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.

The demo video on the home page is hosted on YouTube. Until you press play, the only thing loaded from YouTube is its thumbnail picture, which reaches your browser from Google’s servers, so they see your IP address, as for any image. Pressing play loads YouTube’s own player, in its privacy-enhanced mode. From then on YouTube may store information on your device and collect data about the playback, under the Google Privacy Policy. That is Google’s processing, not ours, and nothing from it reaches us.

There is a chat widget on every page, for sales questions. It is ours: the same people run Cliporium and Nexiora AI, the chat product behind it, so your messages are not being handed to an unrelated business. It does run on other people’s infrastructure, though. Loading any page here fetches the widget and its settings from servers hosted by Supabase and delivered through Cloudflare, which means your IP address and browser are visible to them whether or not you ever open the chat, in the same way they are to any site you visit.

It sets no cookies. It stores one flag in your browser’s session storage so its greeting does not reappear on every page, and that is gone when you close the tab. If you do start a conversation, what you type is stored so the conversation can continue and we can answer it, and it is sent to an AI model provider to write the reply - so please do not put anything sensitive into it. Conversations are kept indefinitely, though inactive ones may be deleted after thirty days, and none of it is used to train a model. To have a conversation removed, write to us.

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

How long things are kept

The video you upload is kept for 30 days, then deleted automatically. It is only needed while more clips might be made from it, and it is by far the largest thing we hold for you. A video added from a link is kept the same way, counted from when we fetched it. After those 30 days the clips made from it are unaffected, but no more can be made from that upload - to carry on, upload the video again. Deleting an upload yourself removes it at once.

Everything else - your account, your clips, your scheduled posts and your connected accounts - is kept until you delete it or ask for it to be deleted.

Two more things expire, because they are only ever halfway: a PC’s sign-in ends after 60 days without use and 90 days at most, and an upload from the Windows app that is never finished is discarded within a week.

Anything you type into the chat widget is kept separately from your account, in the chat service’s own database: indefinitely, though an inactive conversation may be deleted after thirty days. Ask us and we will remove it.

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.

Why we are allowed to use it

Under UK data protection law, we rely on performing our contract with you for your account, uploads and clips, and for connecting and posting to TikTok, Instagram, YouTube or Discord accounts you connect - they are the service you signed up for; on legal obligation for payment and tax records; and on our legitimate interests in keeping the service secure and preventing abuse, for server logs and the sales chat widget. You can object to processing based on legitimate interests by writing to us. If we ever want to use your data for something optional, such as marketing emails, we will ask for your consent first.

Where it is processed

Some of the providers listed above, including Vercel, Neon, Inngest and Groq, process data in the United States. Where data leaves the UK, it is protected by the safeguards UK law requires, such as the UK International Data Transfer Addendum or, for a certified provider, the UK-US data bridge.

Children

You must be at least 13 to create an account, and old enough to hold an account on any platform you connect. If you are under 18, you need a parent or guardian’s permission to use Cliporium, and they must agree to any paid plan. We do not knowingly collect data from anyone under 13; if you believe we have, write to us and we will delete it.

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.

If you are unhappy with how we handle your data, you can also complain to the UK Information Commissioner’s Office at ico.org.uk.

Part two - Cliporium for Windows

Cliporium for Windows is a local recorder. It needs no account, and nothing it records is uploaded unless you sign in to your Cliporium web account in the app and press Send on a recording, or schedule an export to be posted. This part of the page says precisely what it records, where that lives, and what leaves your machine. Signing in takes nothing away: everything below works the same without it.

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. Nothing sends the buffer anywhere; what you can send is a clip or recording you have already saved, and only when you press Send on it.

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. If you send a recording to Cliporium, everything in it goes, including anything that was on screen besides the game. Watch it first if you are not sure.

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.

If you send a recording that has a microphone track to Cliporium, Include my microphone in the Send dialog decides whether your voice goes with it. Off, the microphone track is left out of what is uploaded entirely. On, it is mixed with the game sound into one track, because that is what the clip service listens to - your commentary is what its captions are made of.

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. A window title is never sent to Cliporium: a recording you send is named after its own file (the game and the date).

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 and never sign in, 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.

Your Cliporium account in the app

Signing in happens in your browser, on cliporium.com. The app opens the page; you sign in there (or create an account) and press Allow; the browser hands a one-time code back to the app on your own PC. The app never sees your password, and nothing changes on the PC until you press Allow.

Afterwards the app keeps a sign-in token and your account’s id, name and email in the encrypted secrets.bin, and a short-lived access token in memory only - nothing in its database, settings or logs. Tokens are only ever sent back to the address that issued them. Your PC’s name is not sent: it appears here as “Windows PC” in Settings → Devices, where you can sign it out from anywhere.

While signed in, the app asks this website for your plan, credit balance and limits (so the Send dialog can say what a send will cost before you press it) and the progress of recordings you sent. When you open its Cliporium screen, it also reads the lists behind it: your clips, reels, brands, automations, scheduled posts, and the names and status of your connected accounts - never their tokens. It tells us nothing about your PC, your games or your library. Sign out in the app’s Settings → Account forgets the sign-in on the PC and ends it here.

The pictures on that screen, and a clip or reel you press play on, are downloaded into the app’s cache on your PC through the same one-hour private links the website uses; signing out clears that cache. Import to library copies a clip into your library, where it stays as one of your own clips until you delete it there - deleting it here, or signing out, does not reach into your PC. Pausing or resuming an automation from the app is the same switch as the one on the Calendar.

Sending a recording to be clipped. Nothing is sent unless you press Send on a clip or recording in your library. Then exactly that one goes: its video and its game sound; your microphone only if you include it; with Faster upload on, a smaller copy the app makes on your PC first; its own file name; the choices you made in the Send dialog; and, only with “Use my game events to find my plays” on (it is off until you turn it on), the times of your own kills, multikills, aces, first bloods and objective steals in that recording and what each was. Nothing else goes with it - no window titles, no player names, no other detected moments, no other clips, nothing from the buffer.

The upload goes straight from your PC to our storage, in pieces, each through a link valid for an hour. It runs only while no game or fullscreen window is in front, pauses when one comes to the front, and carries on after a restart from what storage already holds. A prepared copy may sit in <your library drive>\Cliporium\Uploading\ while it runs; it is deleted when the upload finishes or is cancelled. Cancel stops the upload and discards what had arrived. Once the whole recording has arrived, it is an upload like any other, and Part one applies to it.

Scheduling a post. TikTok, Instagram and YouTube are posted to through your Cliporium account, with the accounts you connected on the Connections page, exactly as Part one describes; the app holds no token for any of them. Schedule on Cliporium on a clip or reel from your account sends this website the post you made: which video, the account and the time, and the title, description, tags, cover frame and platform choices you entered. On an export from your library it first uploads that one file, whole, through a link valid for ten minutes, as one of your own videos, which then belongs to your account like any upload made here; with “Delete it from Cliporium once it has posted” on (the default for these) it is deleted once the post has gone out, and the post stays on your Calendar. Nothing is scheduled that you did not schedule, uploads wait until no game is in front, and calling a post off in the app removes it from your Calendar, together with a video the app uploaded for it. A post that fails before it is made takes that video with it too, since nothing would ever post it.

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 cannot be posted to from Cliporium for Windows itself: the app does not connect to YouTube or use YouTube’s API. To post to YouTube from the app, schedule it on your Cliporium account, as above.

TikTok and Instagram are the same: they post through your Cliporium account (above), and the app holds nothing for them. An earlier version of the app was built with a posting service of its own for these two; it never went live, and it is gone.

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. (A recording you send to Cliporium is captioned here instead, as Part one describes.)

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.

Two things can live elsewhere, and only if you chose them. Recordings you sent to Cliporium, and the clips made from them, are here under your web account (Part one) - deleting the folders on your PC does not touch them. So are posts you scheduled from the app, and any export it uploaded for one: they are on your Calendar and among your clips. 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

When this page changes, the date at the top changes with it. If a change affects how data from a connected account is used, we will also tell you in the dashboard or by email.

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