Last updated 16 September 2026
AGclip turns long videos into short vertical clips. This page explains what we hold, why we hold it, and what you can make us do about it. It is written to be read rather than to be survived.
AGclip is an independent service operated by Raza Sarwar, a sole trader in the United Kingdom trading as AGclip. For data protection purposes the controller for everything described on this page is Raza Sarwar, reachable at contact@agclip.com. There is no company behind this and no team: one person runs it, answers this address, and is accountable for what follows. A postal address is provided on request to anyone exercising the rights set out below.
| What | Why | Where |
|---|---|---|
| Your email address | To identify your account and send account-related email | Supabase |
| Video you upload, and the clips made from it | It is the thing the product makes. Kept so you can come back to it | Our server, plus Cloudflare R2 for durability |
| Transcripts, face-tracking data, thumbnails | Working files produced while making your clips | Our server. Rebuildable, and not backed up |
| Your settings, brand kits, presets | So the studio looks the same next time | Our server, plus Cloudflare R2 |
| Access tokens for social accounts you link | Only to post the clips you tell us to post | Our server, in a database separate from your work |
Sign-in goes from your browser straight to Supabase, our authentication provider, over an encrypted connection. Our servers never receive it, and there is nothing for us to leak. We receive only a signed token proving who you are, and we store only the account identifier inside it.
You can sign in to AGclip with a Google account instead of a password.
The sign-in runs through Supabase, our authentication provider; the consent
screen Google shows you names AGclip, and the only scopes
it is ever asked for are openid, email and
profile. There are no others. None of them is one of Google's
sensitive or restricted scopes.
What we receive. From those three scopes, and nothing beyond them:
sub claim — which is how we know you are the same
person who signed in last time.What we do with it. One thing: it signs you in, and it tells your uploads, clips and settings apart from everybody else's. The identifier is what names the folder your work lives in. The email address is also what account email goes to — a password reset, or a notice that this policy has changed. We do not build a profile from it, we do not use it for advertising, we do not use it to train any model, and we do not use it to work out anything about you.
What we do not receive. We never see your Google password. We have no access to Gmail, Drive, Calendar, Contacts, Photos or anything else in your Google account, and we cannot acquire any without sending you back to Google to approve a scope that Google would name to you on screen.
Where it is stored, and for how long. The email address, name and identifier are held by Supabase, our authentication provider. Our own servers store the identifier, and the email address where you have given us one. All of it is kept for as long as your account exists and is destroyed when you delete your account — see Deleting your data, and deleting your account.
What we share. Nothing. Information received from Google APIs is not sold, not transferred to anybody, and not disclosed to any third party for any purpose, other than to the authentication provider named above, which is the thing that performs the sign-in, or where we are compelled to disclose it by law.
Limited Use. AGclip's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google will know that you signed in to AGclip, in the same way it knows about any site you use it on. What Google does with that is covered by their privacy policy, not ours. If you would rather Google was not involved, use the email and password form — it does exactly the same thing, and it is not a lesser account.
Your video is processed on our own machines and is not sent to any third-party AI service. Transcription, face detection, framing and rendering all run on servers we control, using software installed on them.
The one exception is optional and never automatic: if you choose to use the Pro editor's audio-cleanup feature and it is configured to use a hosted speech service, the audio for that clip is sent to that provider to be processed. Nothing is sent anywhere until you press the button.
We do not use your video to train models — not ours, not anybody else's. We do not sell it, license it, or show it to anyone. Staff do not watch it except where you have asked for support and given permission, or where we are legally required to.
Two, both strictly necessary, and no others:
Both are HttpOnly, which means scripts running in the page cannot read them, and both are marked Secure over HTTPS. There are no advertising cookies, no analytics cookies and no third-party trackers on this site. That is also why you are not asked to dismiss a cookie banner: there is nothing to consent to.
If you connect TikTok, YouTube, Instagram, Facebook or Snapchat, we store the access tokens those services give us. We use them for exactly two things: posting the clips you ask us to post, and — where the platform offers it — reading back how a clip you published performed, so the studio can show you.
We never post anything you have not asked us to post. You can unlink an account at any time in Settings, which deletes the stored tokens.
If you use the Analytics dashboard to track a public account, we read that account's public profile and recent posts — the same information the platform shows anybody — about once a day, and cache it. We do not access anything private, and we do not track individuals.
Each is used for that purpose alone. We do not share your data with anyone else, and we do not sell it to anyone under any circumstances.
Our servers are in Falkenstein, Germany. Object storage is provided by Cloudflare R2. If you are outside that region, your data will be transferred there in order to provide the service.
Your work stays until you delete it, or until you ask us to close your account.
Deleting a video or a clip in the Library moves it to the Bin, and there it stays: we do not empty it on a timer, and what is in it still counts against your storage. Emptying the Bin is what actually erases — the file leaves our disk, and the copy in object storage is deleted with it. Until you do that it has not been deleted, and this page is not going to tell you otherwise.
Working files — transcripts, thumbnails, tracking caches — may persist a little longer while caches are cleared, and are deleted with the source they were made from.
Anything you made, you can delete yourself, now. Delete a video or a clip in the Library and then empty the Bin: that is what takes it off our disk and out of object storage. Brand kits, presets, logos and saved fonts each delete from where you made them, and unlinking a social account in Settings destroys the tokens we hold for it.
Deleting the whole account is a request, not a button — and we would rather say so than imply a control that is not there yet. Email contact@agclip.com from the address the account uses, or from the Google account you sign in with, and ask. You do not have to give a reason and you will not be talked out of it.
What that removes: the uploads, the clips made from them, the transcripts, thumbnails and tracking caches, your brand kits and presets, the tokens for any social account you linked, and the sign-in record itself — including the email address, name and identifier Google told us about you. Copies held in object storage go with them.
We aim to do it within 30 days, which is what UK GDPR allows us, and in practice it is the same day. Object storage keeps its own copies for a short window after a delete and those expire on their own schedule inside that period; nothing reads them in the meantime.
You can ask us to:
Email us and we will do it. We will not make you justify the request. If you are in the UK or EU and think we have handled your data badly, you have the right to complain to your data protection regulator — in the UK that is the Information Commissioner's Office at ico.org.uk.
Connections are encrypted. Sign-in tokens are held in cookies that scripts cannot read. Each account's files are kept in a separate area and requests are checked against the account making them.
No service can promise it will never be breached. If yours is affected by one, we will tell you, and we will tell you what actually happened.
If this policy changes in a way that matters, we will say so on this page and, for anything significant, by email. The date at the top is always the date of the current version.
Questions, requests, or complaints: contact@agclip.com. We answer these ourselves.