Privacy Policy — Your Videos and Your Data
Privacy Policy for RemoveVideoBG, covering how uploaded videos are handled, what data we collect, how long it is kept, and how to delete your account.
2026/10/25
Last updated: October 25, 2026
At a glance
This policy explains what RemoveVideoBG collects when you use removevideobg.net, why we collect it, and how long we keep it.
- Where your video goes: it is uploaded to private cloud storage and sent to a third-party AI processing provider to remove the background. See Your videos and results.
- How long we keep it: a daily cleanup job removes source videos once they are older than 24 hours. Finished results stay while your account exists. See Keeping data and deleting your account.
- Training: we do not use your uploads to train our own models. See Your videos and results.
- Who else handles data: Cloudflare, Stripe, Google (if you use Google sign-in), a password-breach checking service and the AI processing provider. See Who else handles your data.
- Cookies: the full list, with lifetimes, is in the Cookie Policy.
- Deleting your account: you can do it yourself in Security settings. It removes your account details, videos and results, and a few limited records stay for a fixed time. See Keeping data and deleting your account.
- Questions: reach us through the contact page. See Contact.
Your videos and results
Videos you upload are stored in private cloud storage, processed by a third-party AI provider, and returned to you as a finished result that only your signed-in account can download.
- Upload: you need to be signed in to upload. The file goes into private storage that is not publicly readable.
- Processing: to run the background-removal model, we give our AI processing provider a temporary link, valid for 15 minutes, that lets it fetch the source video. We also send the processing settings, such as background color and output format. We do not send your name or email address, although the storage path inside the link contains an internal account identifier. The provider handles the video under its own terms, which we do not control.
- Results: we copy the finished result from the provider into our private storage. You download it from your History page, and only your account can access it.
- Source videos: a daily cleanup job removes source videos that are older than 24 hours, so a source file is normally gone within 48 hours of upload. The site also asks for the source file to be deleted when a submission fails or is cancelled.
- Review by us: when it is needed to fix a problem or keep the service secure, we may look at your uploads and results.
- Results stay until your account is deleted. There is no button yet to delete a single result. Deleting your account removes all of them, and the section Keeping data and deleting your account explains how.
- Training: RemoveVideoBG has no system that uses your uploads or results to train models, and we do not use them for that.
- Sale and publication: we do not publish or sell your uploads or results.
What else we collect
We collect the account, payment, activity and technical information below to run the service, keep accounts secure, take payments, answer your messages and prevent abuse. We do not use any of it for advertising.
| Information | What we use it for | How long we keep it |
|---|---|---|
| Account details. Your name, email address and a hashed password, or the name, email address and profile picture Google shares when you use Google sign-in. | Creating and securing your account, and sending account emails. | Until you delete your account. |
| Sign-in sessions. The IP address and browser details (user agent) recorded with each session. | Keeping your account secure. | Removed when you delete your account. |
| Credits and processing history. Your credit balance and credit history, plus the details of each processing job: settings, status and duration. | Showing your history, charging and returning credits, and keeping jobs reliable. | While your account exists. Technical job records have shorter schedules, shown in the retention table below. |
| Payment records. Stripe handles your card details. We keep Stripe reference IDs for your customer record, subscriptions and invoices, plus the plan, amount and status. | Taking payments, managing subscriptions and answering billing questions. | Anonymized financial records remain after deletion, as described below. |
| Messages you send us. The name, email address and message from the contact form. | Replying to you. | The form sends your message to our support mailbox as an email, where it is kept like any other email. |
| Emails we send you. Your name and email address, used for verification, password reset, deletion confirmation, welcome and payment notices. If you invite someone by email, the address you enter. | Delivering the messages. For invitations, we also keep a hashed form of the address to apply invitation limits. | Queued emails are cancelled and redacted when you delete your account. The hashed invitation address is kept while your account exists and is deleted with it. |
| Request records. The route name, method, status code, response time and a random request ID for each request to the site. They do not include your IP address, page parameters or query strings. | Fixing errors and keeping the service reliable. | 7 days. |
| Rate-limit counters. Counts of sign-in and form requests, which can include your IP address. The contact form uses one-way hashes of your IP address and email. | Blocking floods of requests and automated abuse. | Sign-in counters are cleared after about 1 hour. |
Reward fairness and anti-abuse records
Reward fairness records are the limited records we keep to apply the eligibility and anti-abuse rules of the welcome, daily and invitation rewards, which the Terms of Service describe.
If you take part in the daily or invitation reward program, we keep limited records needed to apply its eligibility and anti-abuse rules. These can include purpose-separated irreversible keyed hashes derived from your email address, network address, or a random browser identifier; the reward decision and reason; and anonymous invitation-graph nodes used to prevent invitation loops. When welcome credits are issued, we also record hashes of your browser details and email domain, and a two-letter country code. We do not store the raw email address, network address, or device characteristics in these reward records.
How long they last depends on the record:
- Sign-up signals recorded when welcome credits are issued (the hashes of your network address, browser details and email domain, and the country code) are cleared after 30 days.
- Most other signals expire within 90 days.
- Short-lived invitee network and repeated-attempt signals expire after 24 hours.
- A sign-up receipt records that a browser has already received welcome credits, so other accounts from that browser do not automatically receive another welcome reward for 90 days.
- An inviter's random browser anchor remains while the invitation is active, because removing it earlier would disable the self-invitation check. It is removed after the invitation is completed, revoked, or detached and the 90-day retention window has passed.
On account deletion, account-linked signup context is deleted and successful signup receipts are detached from the user. For up to 90 days from grant, the receipt retains only a purpose-separated keyed hash of a random browser identifier, key version, an irreversible grant-source digest and timestamps. Limited email hashes and de-identified invitation nodes may also remain for up to 90 days. No raw address, network address or browser fingerprint is retained in these fairness records. Expired records are removed automatically; they are not used for advertising or contacting you. If you sign up again with the same email address within 90 days of deleting an account, you may not receive welcome credits.
When you delete your account, required cleanup remains fail-closed: the account is not marked deleted if a required step fails. The limited, time-bound reward fairness records described above are deliberate exceptions. Reward eligibility rows that contain your account ID are deleted; financial ledger and lot records are retained only in anonymized form where required for balance integrity and audit.
Sign-in, passwords and security
You can sign in with Google or with an email address and password, and your email address must be verified first. We protect these steps and your data in the following ways:
- Passwords are stored as protected hashes, not readable text. New passwords must be 15 to 128 characters.
- Breached-password check: when you set a new password, we send only the first five characters of its SHA-1 hash to the Have I Been Pwned service to see whether the password has appeared in a known breach. If that service is unavailable, we do not accept the new password.
- Bot checks: Cloudflare Turnstile protects sign-up, password reset and resending verification emails, and sign-in after repeated failed attempts. It receives the challenge result, the site name and your IP address.
- Verification and reset requests: we keep limited security and delivery metadata. Verification links, reset tokens and passwords are not included in diagnostic logs.
- Sessions: your sign-in cookie is HttpOnly, Secure and SameSite, so page scripts cannot read it. Sign-in sessions last 7 days.
- Storage: uploaded videos and results sit in private storage and are served only to the account that owns them.
- Payments: card details go straight to Stripe, and our servers do not store them.
- Connections: the site is served over HTTPS.
No online service is perfectly secure, so please use a long, unique password.
Cookies and similar technologies
The site sets cookies to keep you signed in, protect sign-in, remember small preferences and apply reward fairness limits. The Cookie Policy lists the cookies and browser storage items that the site's own code sets, with their purpose and lifetime, including the two reward cookies.
Cloudflare Turnstile and Stripe can set their own cookies on their own domains when you use sign-up checks or payments.
Who else handles your data
We use the following services to run the site. Each entry lists the categories of data that the service receives.
- Cloudflare hosts the site and its database, stores files in private storage, delivers our emails, and provides the Turnstile bot check. It handles the traffic to the site (including IP addresses), the account data in our database, your stored videos and results, the emails we send, and Turnstile challenge results.
- A third-party AI processing provider receives your source video through a temporary link, together with the processing settings, so it can remove the background.
- Stripe processes payments, subscriptions and invoices. It receives your email address, name, a reference to your account, and the details of what you buy. Card details go directly to Stripe.
- Google provides sign-in if you choose it. It receives your sign-in request and shares your name, email address and profile picture with us.
- Have I Been Pwned receives only the first five characters of a password hash when you set a new password.
These companies handle data under their own terms and privacy policies.
Keeping data and deleting your account
You can delete your account yourself, and most of what we hold about you is removed when you do. To start, open Security settings and choose Delete Account. We email you a confirmation link, and the deletion runs only after you click it.
Before deleting, we stop renewals and close open checkouts with the payment provider. If we cannot confirm that those steps are complete, your account is kept and not deleted.
| Data | How long we keep it |
|---|---|
| Source videos | Removed by the daily cleanup once older than 24 hours (normally within 48 hours of upload), and removed at deletion. |
| Results | While your account exists. Removed when you delete your account. |
| Account details, sessions, profile picture and verification codes | Removed when you delete your account. |
| Your customer record at Stripe | Deleted when you delete your account. |
| Queued emails to you | Cancelled and redacted at deletion. |
| Technical processing records | Technical records of each processing run are archived after 30 days and deleted 90 days after archiving. Notification and webhook payloads are redacted after 30 days. Processing-related records are redacted as soon as you delete your account. |
| Request records | 7 days. |
| Sign-in rate-limit counters | About 1 hour. |
| Reward fairness records | Up to 90 days, with sign-up signals cleared after 30 days, as described above. These are an exception to deletion. |
| Financial records | Kept after deletion in anonymized form, where amounts, currency and billing periods stay but account, subscription and invoice IDs are removed. A hashed payment-deletion marker is kept for 400 days. |
Your choices and requests
You can manage most of your data yourself, and you can write to us about anything the settings do not cover.
- Delete your account in Security settings, as described above.
- Cookies: control them in your browser. The Cookie Policy explains the effects.
- Questions or requests about your data, such as a copy of what we hold, a correction, or removing something earlier than the schedules above: tell us through the contact page, using the email address on your account.
There is no self-service data export yet.
Changes to this policy
When this policy changes, we post the new version on this page and change the date. This version rewrites the policy in plainer language and adds a section on how uploaded videos and results are handled, a list of the information we collect, the services that handle your data, and a table of how long data is kept.
Contact
For privacy questions, use the contact page. Please do not send passwords or verification codes.