Privacy Policy

Last updated: October 16, 2026

Background removal happens in the cloud. Your finishing touches and saved editing session stay in your browser. Here is what that means for your data.

1. Scope

This policy covers removebackground.me. Google sign-in stores your name, email, profile image and session information to manage your account and credits. Guest and login cookies are used for access control. Payments are not enabled.

2. Images sent for background removal

When you start automatic removal or reprocess an image, the image is sent to our server, hosted on Cloudflare, and forwarded to fal.ai to generate a cutout. An image may contain personal information, including faces or embedded metadata. Only submit images you are authorized to share for this purpose.

Processed images are stored privately on Cloudflare for three hours from receipt of the upload. Access stops at expiry and deletion is scheduled; physical deletion may be delayed by scheduling or failures. Editing, signing in and unlocking do not extend this period. Credit records are retained without image contents. See fal.ai’s privacy policy and Cloudflare’s privacy policy.

We ask fal not to store request JSON and set its media lifecycle to one hour. These controls are separate from our three-hour limit and do not guarantee the same deletion period for OpenRouter or downstream model providers.

To suggest backgrounds, a thumbnail up to 256px is sent through fal.ai and OpenRouter to Google Gemini for subject classification. The category is saved with your image on this device.

3. Editing data stored on your device

Originals, low-resolution previews and editing operations may be saved in this browser until the image expires. Expired records are cleared while the page is open, or before showing saved work on your next visit. Uploaded backgrounds expire within three hours, or earlier with their associated image. Clearing site data removes local copies; downloaded files are unaffected. Manual edits are performed on this device.

4. Background photo searches

When you search for a background photo, your search text, page number, and a language setting derived from the query are sent through our server to Pexels. Search results may be cached on our server for up to 24 hours. Avoid entering sensitive personal information in searches.

Photo previews and selected photos load from Pexels, which receives standard connection information such as your IP address and browser request headers. Selected backgrounds may be saved with your local editing session. See the Pexels privacy policy.

5. Technical information and storage

Our hosting and processing providers handle technical information needed to deliver and protect the service, such as network addresses, request times, and error information. Provider logs may have separate retention periods from local editor data.

The application uses necessary login and guest cookies and local editing storage. We use a self-hosted Plausible instance for cookieless pageview and feature-use statistics. Your browser sends these events to our site; our server removes URL parameters and unapproved data before forwarding them. Plausible receives your IP address and User-Agent to count unique visitors. With your optional consent, we also load Google Analytics 4 for page views and selected feature events, and Microsoft Clarity for usage metrics, heatmaps, and session replay. These services may use analytics cookies and receive standard connection details. Google Analytics receives page paths without query parameters; we do not deliberately send image contents, file names, image URLs, search text, account details, or form inputs as analytics events. Clarity is configured to mask all page content in recordings, and its advertising storage is denied. The optional scripts do not load before consent. Your choice is saved locally; use Analytics settings in the footer to change it. Infrastructure providers may use separate security and delivery technologies. Microsoft privacy statement.

For signed-in accounts, we store the first known referral or UTM source, Cloudflare country code, and a limited history of page views and feature actions linked to the account. Administrators can also see image processing status and credit transactions. We do not store image contents, file names, search text, or URL parameters in this activity history. Activity events are deleted after 365 days; attribution remains while the account exists.

6. Purposes and providers

Data is handled to process the images you request, restore your editing session, deliver background search results, and operate and protect the service. Our application does not publish your uploads or run a training pipeline using them. Provider handling is subject to the applicable provider agreements; this policy does not promise a particular provider deletion time or training restriction.

Providers may process information outside your country. Where data protection law requires a legal basis, processing to deliver your requested service is based on performance of that service, and necessary security processing on legitimate interests where permitted. Consent will be requested where required.

7. Your choices and rights

You can stop uploading images, avoid optional background searches, and clear local site data at any time. Download any work you wish to keep before clearing it. Removing local data does not withdraw a processing request that has already been sent.

Depending on your location and applicable law, you may have rights to access, correct, delete, or receive a copy of personal data, restrict or object to processing, and withdraw consent where processing relies on consent. You may also raise a concern with your local data protection authority.

8. Policy updates

We update this policy when data handling changes. The revision date appears above.

9. Contact and privacy requests

For privacy questions or to exercise your rights, email support@removebackground.me. Describe your request and the relevant interaction with the service; please do not attach sensitive images. We may need information to verify your request. We cannot access editing data stored only in your browser, but you can remove it using the steps above.