1. Who we are
EasyRemoveBG Team operates EasyRemoveBG and is the contact for information handled through this service. For privacy questions and requests, email support@easyremovebg.com.
2. Information we handle
- Images and results: files you choose to upload, image dimensions and format, processing settings, edits and resulting files.
- Account information: name, email address, profile image and verification status where provided. Google sign-in also supplies a provider account identifier and basic profile information; authentication records may include OAuth tokens and related expiry information.
- Account credentials: we do not receive your Google password. If you previously had an eligible email/password account, any password we retain is stored as a hash, never as plain text.
- Sessions and security: a signed device identifier used to prevent abuse, session identifiers, browser/user-agent information, network information such as IP addresses, request times and security or rate-limit records, as needed to operate the service.
- Task and support records: task IDs, processing status, error records and information you send when requesting help. Do not send passwords, private download links or unnecessary sensitive images.
- Website analytics: on public pages we send pageviews to Plausible hosted at app.pageview.app. Events include the public page URL, allowlisted campaign labels and an external referring site origin. The analytics service also receives network information such as IP address and user-agent with the request to produce visitor, device and approximate location statistics. We do not attach account identifiers, email addresses, image information, task identifiers or private download URLs to these events. Sign-in and My creations pages are excluded.
3. Why we use information
We use this information to provide image processing and downloads, maintain sessions, verify task ownership, recover submitted work, respond to requests, prevent abuse and diagnose failures. We also process information when required to meet legal obligations.
We use aggregate website analytics to understand which public pages people visit and how they find the service. This pageview integration does not set analytics cookies or create a persistent identifier in your browser.
Where a legal basis is required, processing depends on the purpose: providing the service you request, legitimate interests in security and reliability, compliance with law, or consent where required. We do not sell personal information or use your uploaded images for advertising.
4. Your device and cloud processing
Choosing an image opens a local preview. We upload the image for cloud processing when you start removal. Cloudflare provides hosting and private R2 file storage; database infrastructure stores account and task information. Replicate receives the image and processing parameters needed to run the background removal model.
Browser storage can contain task references, queued files and editing drafts to support batch recovery and Google sign-in handoff. These local copies are separate from cloud files. Clearing local storage may lose unsent files or edits and does not cancel submitted cloud work.
5. Retention and deletion
Original uploads and results expire 24 hours after upload is initiated. Expired files cannot be retrieved through the service. Daily cleanup permanently deletes expired cloud files, normally within the following 24 hours. Logging in does not extend that period.
The file expiry rule does not automatically delete account, task, security or support records. We retain those records only as needed for their service, security, dispute-handling or legal purpose. You can request access or deletion through the contact below; some records may need to be retained where law or an unresolved security issue requires it.
Replicate has its own retention policy. Its documentation states that API prediction inputs, outputs, files and logs are removed after about one hour by default. That policy is separate from our copies and is not a promise that every provider record is deleted at the same time.
Local task and draft references have validity limits, but browser-stored bytes can remain until later cleanup or until you clear site data. Downloaded files and copies held by others are not deleted by our cloud cleanup.
7. Security
We use private storage, authenticated ownership checks and limited-access downloads. Public service connections use HTTPS. Operational logs are designed to avoid image contents, passwords and signed storage URLs. No storage or transmission method is guaranteed completely secure.
If a personal data breach occurs, we will assess its effects and notify competent authorities and affected people where, and within the time limits, required by applicable law.
Avoid uploading highly sensitive documents or personal information that is not needed for background removal. Keep your device and account credentials secure.
8. Your choices and rights
Depending on applicable law, you may request access, correction, export or deletion of your personal information, object to certain processing, or withdraw consent where processing relies on consent. Email support@easyremovebg.com and describe the request. We may need to verify your identity and will respond within applicable legal time limits.
You can revoke Google account access in your Google settings. Revocation does not itself delete records held by EasyRemoveBG. You may also contact a competent data protection authority. Use browser controls to manage cookies and local storage.
9. Children and policy changes
The service is intended for adults aged 18 and over. If you believe a child has provided personal information, contact us so we can investigate and take appropriate action.
We update this page when our practices change and provide additional notice when required by law. The date at the top identifies this version.
Questions?
Contact EasyRemoveBG Team at support@easyremovebg.com.