Updated: 10 November 2026. This policy describes the data used by Background Remover. Questions and account deletion requests: [email protected].
Uploaded images
Images travel to our Java API and private background-removal worker to perform the requested processing. Temporary upload files are removed after the request. The worker uses temporary memory or temporary files during a request and does not maintain a photo gallery. Our background-removal code does not use submitted photos to train a model. Downloaded results and editor changes are handled in your browser and are not saved as a cloud project.
Accounts and sign-in
We store your email address and account identifier. If you use Google, we also store the Google subject identifier after verifying the ID token; Google supplies account information under its own privacy policy. For non-Google email domains, additional mailbox verification may be required. One-time email codes are stored as salted hashes, expire after 10 minutes and are consumed once. Netcore delivers sign-in emails and processes the recipient address and delivery metadata.
Sessions, cookies and usage limits
Essential HttpOnly cookies keep you signed in and protect Google sign-in. Session tokens are stored as hashes on the server and expire after 30 days or logout. We store hashed network identifiers, account identifiers and processing and download counts to enforce limits. Download records contain timestamps and photo counts, not exported image contents; they are deleted in the hourly cleanup after their rolling-hour window expires. Network addresses may also appear in operational access logs. Successful processing records are kept for up to 65 days to enforce monthly usage; expired sessions, codes and challenges are cleaned periodically.
API keys
We store key hashes, labels, short prefixes, usage and revocation dates, and API processing counts. A full key is shown only when it is created. The lifetime 100-image counter and hashes of successful Idempotency-Key values remain with the account; image results are not cached for replay. Unfinished reservations expire after five minutes. Batch edits and ZIP files are generated locally in your browser.
Subscriptions
We store order references, amounts, currency, subscription dates, cancellation state and transaction-verification events. WayForPay processes payment and card information. Our application does not store full card numbers or card security codes. Billing records are retained for payment support, reconciliation and applicable recordkeeping obligations.
Tracking and external services
The refreshed application does not load the former advertising analytics or session-replay scripts. It loads Google Identity Services when you open sign-in. Font files are loaded from Google Fonts. External providers receive the connection information needed to deliver their services and apply their own privacy policies. Essential cookies are used for authentication; no optional marketing cookie is required.
Your choices
You may use the free tool without an account, sign out to end your session, cancel renewals from your account and request access, correction or deletion of account data by email. Identity verification may be necessary to protect your account. Certain payment records may need to be retained for applicable obligations. Download your images before closing the editor; we cannot retrieve a closed browser project.