Privacy Policy

Images you upload. Your browser sends images directly to api.removebg.help, not through Vercel or analytics services. The API keeps temporary image bytes in bounded VPS storage; each authorized access may renew the expiry, and the periodic cleanup normally removes them about 10 minutes after the most recent authorized access. When the PhotoRoom provider is enabled, the API sends the image to PhotoRoom solely to perform background removal; PhotoRoom states that images processed through its API are not used for model improvement. We do not use your images to train models.

Anonymous service identifiers. When you first visit, api.removebg.help sets two HTTP-only cookies containing random UUIDs. rbg_uid tracks purchased credits and temporary uploads while you are signed out; if you later sign in, we use it during account linking to move that balance and any staged upload to your account subject. rbg_qid tracks only the current UTC day's signed-out free quota and is not moved or rotated when you link an account.

Optional account and authentication data. If you choose to sign in, Clerk collects and processes your email address, a Clerk user ID, authentication and session data, required identity cookies, and the verification or sign-in emails needed to access the account. Our interface may display your account email. Our API verifies Clerk's session token, reads its user ID, and deterministically derives a UUID-shaped account subject for quota, credit, checkout, and upload records; our backend does not store your full account email.

Technical metadata. Like every website, our server and proxy logs can include your IP address, user agent, request path, status, and timing. We use these for operations, debugging, abuse prevention, and rate limiting. Logs are size-rotated under our hosting configuration and deleted when no longer needed for those purposes; we do not promise a fixed day-based retention period.

Analytics data. We use privacy-focused Vercel Web Analytics to understand aggregate usage such as visited pages, device type, approximate region, and referral source. Uploaded images and account emails are not sent as analytics events. Before the payment success page is rendered, provider query parameters are redirected to a clean URL so they are not included in the analytics page URL. Google Analytics and Microsoft Clarity are disabled and are not loaded until an explicit analytics-consent flow is implemented. Product diagnostics use the closed events upload_started, processing_started, removal_succeeded, download_clicked, paywall_seen, checkout_started, and purchase_completed. Each event has only context and attribution. Safe first-touch attribution is stored for the current tab session under rbg_attribution_v1 in sessionStorage. localStorage key rbg_auth_subject_revision_v1 stores only a PII-free positive safe integer used to invalidate checkout attribution when the browser's authentication subject changes; it stores no user ID, email, anonymous cookie, or derived account subject. During checkout, this tab may store rbg_checkout_attempt_v1 in sessionStorage with a random attempt ID, mode, timestamp, paid-balance baseline, PII-free auth revision, safe context, and safe attribution. localStorage key rbg_checkout_lease_v1 contains only the random attempt ID, mode, and timestamp. A return tab may briefly write then remove rbg_checkout_signal_v1 containing only type checkout_returned and the matching random attempt ID. Checkout records are logically valid for two hours and stale records are removed on the next site visit, not automatically at an exact wall-clock instant. purchase_completed means only that a checkout-return flow later observed a paid-balance increase; it is conversion diagnostics, not a payment record or reconciliation source.

Payment information. Creem.io handles checkout and card processing. We do not receive or store your card number. A signed checkout-completed webhook can include customer fields supplied to Creem, such as email, name, or country, together with order and product data. Our backend processes the signed event to grant credits, redacts webhook bodies from application logs, and persists only the event identifier, service subject, and resulting credit state rather than those customer profile fields.

To run the background removal service and return your processed image.

To authenticate optional accounts, send requested verification or sign-in messages through Clerk, and link an rbg_uid session to a derived account subject so credits can be restored across devices.

To enforce the daily free quota and credit balance.

To detect and prevent abuse, fraud, and automated scraping.

To improve the service through aggregate, non-personal usage patterns (e.g., which pages and workflows are most useful).

We do not train AI models on your uploaded images.

We do not sell, rent, or share your data with advertisers or data brokers.

We do not use analytics to identify you personally or fingerprint you across sites.

We do not send marketing email. If you choose email-based sign-in, Clerk sends the transactional verification or sign-in messages you request.

Creem.io — payment processing. They store payment and basic identity information you provide at checkout under their own privacy policy.

Clerk, Inc. — optional account authentication and user management. When you sign in, Clerk acts as our service provider and processes your account email, Clerk user ID, authentication/session data, required cookies, and verification or sign-in email delivery. Clerk's handling of customer data is governed by its agreement with us; questions or requests about this account data should be sent to us.

PhotoRoom — optional image processing provider. When PhotoRoom mode is enabled, our API sends your uploaded image to PhotoRoom for background removal under PhotoRoom's data-processing terms. PhotoRoom states that API images are not used to improve its models.

Upstash — Redis storage. We store the random rbg_uid, the daily rbg_qid, or a derived account subject together with quota, credit, and related service records. We do not store your full Clerk account email in Upstash.

Google Analytics and Microsoft Clarity — currently disabled and not loaded. We will not enable them without updating this policy and implementing explicit analytics consent.

Vercel Web Analytics — cookie-free, aggregated page analytics. Vercel also serves the web interface but does not receive uploaded image bodies; our VPS provider hosts api.removebg.help and has access to network traffic in the normal course of operating the infrastructure.

rbg_uid — HTTP-only service identifier, lifetime 1 year. It is used for signed-out purchased credits and temporary-upload ownership and is involved when you link that session to an account.

rbg_qid — HTTP-only free-quota identifier, lifetime 1 year. It remains stable when you sign in, sign out, or rotate rbg_uid; the associated free allowance resets through a separate UTC-day record in Redis.

Clerk authentication cookies and browser storage — required only for optional sign-in, session continuity, and fraud/security controls. Depending on the environment and session state these include Clerk client or session identifiers; clearing them signs you out but does not by itself delete the Clerk account.

rbg_locale — a one-year preference cookie that remembers whether you selected English or Chinese.

Google Analytics and Microsoft Clarity cookies are not set because both services are disabled and not loaded. Vercel Web Analytics does not use cookies.

You can clear rbg_uid or rbg_qid at any time. Clearing rbg_uid can disconnect purchased credits held only by that anonymous session. Clearing rbg_qid resets the signed-out daily quota identity. Clearing Clerk authentication cookies signs you out; none of these actions alone deletes server-side or Clerk account data.

To access, correct, export, or delete account data, or to delete data tied to a derived account subject, rbg_uid, or rbg_qid, email support@removebg.help. If possible, write from the account email and include the relevant identifier for an anonymous-session request. We will handle the request and, where necessary, coordinate deletion of the Clerk account and associated service records. End-user requests about data Clerk processes for our authentication service should come through us; Clerk's own privacy contact details are at https://clerk.com/legal/privacy.

Depending on where you live, you may also have rights to access, rectification, erasure, portability, restriction, objection, or withdrawal of consent. Contact support@removebg.help to exercise them; we may need to verify your identity before acting.

The service is not directed to children under 13. We do not knowingly collect data from children. If you believe a child has used the service or created an account, contact us so we can remove the relevant service and Clerk account data.

We may update this policy. The 'Last updated' date at the top reflects the latest revision. Material changes will be highlighted on the homepage for at least 7 days.

Questions about this policy, or requests about your data, can be sent to support@removebg.help.