Privacy Policy

What we collect

The video file you choose to upload and a record of the processing job (status, credits consumed, timestamps). If you buy credits, we also keep the purchase records described under Credit purchases and payments. Processing a clip requires an account — we use Google sign-in, so there is no password for us to store, and card details are never sent to us.

You sign in with Google to process a clip. We store the email address on that Google account, the name and profile picture Google shares with us, and a session record that keeps you signed in. Google tells us whether the address is verified; we never receive your Google password.

If you sign in

Account data is used to recognise you on your next visit, to attach purchased credits (and the one-time trial allowance) to you, and to enforce your balance. It is not used for advertising and not shared with the analytics providers described below. Signing in is required in order to process a clip.

Sessions expire, and you can sign out at any time from the account page, which ends the session on our side as well as in your browser.

To have your account and its data deleted, email us at the address in the contact section below and we will remove the account record. Credits are purchased once, so there is no subscription to cancel. The videos you uploaded are deleted automatically after the retention period regardless, because retention is enforced by a storage lifecycle rule.

Credit purchases and payments

Credit packs are sold through Stripe, a third-party payment processor. Your card details are entered on Stripe’s own page and are never sent to or stored by us; we could not charge a card even if we wanted to.

What we do store is purchase metadata, in our own database: a Stripe customer reference, the checkout session identifier, which pack was bought, how many credits it granted, the amount paid, and when. We use it for one purpose — keeping your credit balance correct and showing it on the account page. It is not used for advertising or profiling.

Stripe also receives the billing details it needs to process the payment and to meet tax and anti-fraud obligations, as a controller in its own right. Their handling of that data is described in Stripe’s privacy policy.

Credits are purchased once and do not renew, so there is nothing to cancel. Refunds are described in the terms of service.

Usage limits and credits

To enforce your balance, we keep a per-account record of the credits each processing job consumed (one credit is one second of video), and of the credits each purchase added. Because processing now requires an account, this record is keyed by your account rather than by your network address.

We also store an irreversible hash (HMAC-SHA256) of the request IP alongside each job — the raw IP address itself is never stored. That hash is used only to investigate abuse. It does not enforce any limit, is not used for cross-site tracking, profiling or advertising, and is not shared with the analytics tools described below.

Analytics and cookies

We use two third-party analytics tools to understand how the tool is used: Google Analytics 4 for traffic and conversion analysis, and Microsoft Clarity for heatmaps and session replays. Both set cookies in your browser and send usage data to their operators, Google and Microsoft.

A session replay can capture what a page looked like while you used it. The area that shows your file name, upload keys and video preview is masked before anything leaves your browser, so it never reaches Clarity — masked content is not uploaded at all.

Visitors in the EU/EEA, the UK and Switzerland are not tracked until they accept. Visitors elsewhere are tracked by default until they decline. Declining stops further reports and reloads the page if analytics have already started; anything already sent for that page view cannot be recalled.

You can change or withdraw your choice at any time with the control below.

Where your files are stored

Uploaded videos and the transparent results generated from them are stored in third-party object storage (Cloudflare R2). Video bytes are uploaded directly from your browser to that storage and are not kept on this site's own servers.

Processing by a third-party AI service

Removing the background requires running a segmentation model, so your video is passed to a third-party AI inference provider that performs that step and returns the transparent result. The provider processes the file on our behalf for this purpose.

How long we keep them

Uploads and their results are deleted automatically 24 hours after they are created. Deletion is enforced by a storage lifecycle rule rather than a scheduled job, and once a file is deleted, any previously issued download link stops working.

What we do not do

We do not sell the videos you upload and we do not publish them. We have no advertising or profiling system, so there is no commercial profile of you to build. For the analytics described above, the only thing we keep about a visit is the aggregate usage data those tools report.

Terms of Service

This policy covers what we store and for how long. Using the service is also governed by our Terms of Service, which cover the account requirement, your responsibility for the content you upload, acceptable use and the limits of our liability. Where the two overlap, this policy governs the handling of your data.

Contact

Questions about this policy, or a request to delete a file before its automatic expiry, can be sent to hi@videobackgroundremoval.com.