English

Photo Background Remover: Privacy Policy

Last updated 2026-10-02.

Photo Background Remover collects the following, and nothing else.

What	Specifically	Why	Shared
App activity	A credit balance per app and Zaparo ID user id: the credits held, the actions they were spent on by the app's own action name, when a rewarded ad was last credited, and a ledger of every change; App interactions, as AdMob measures them: that an ad was requested, shown, watched or dismissed; Which applications within this one tenant the account has been seen in. Recorded when an application registers a device or completes a sign-in under its own application id, so `me().apps` can answer it back to the person.	Account management, Advertising or marketing, Analytics, App functionality, Fraud prevention, security, and compliance	Yes
App info and performance	App sessions, as Firebase Sessions reports them to Crashlytics: when the app came to the foreground and started a session, with the package name, OS and SDK versions, network type, and device manufacturer and model; Crash stack traces, ANRs and breadcrumbs; Diagnostics the SDK reports on the app and on itself: app launch time, hang rate and energy usage; Telemetry about each run of the on-device model: device manufacturer, model, OS version and build; the package name and app version; latency; the format and resolution of the image passed in; and events such as feature initialization, model download, detection and resource release	Advertising or marketing, Analytics, App functionality, Fraud prevention, security, and compliance	Yes
Device or other IDs	A per-installation identifier, which Google states is not intended to uniquely identify a user or a physical device; Advertising ID (AD_ID), used by AdMob to serve and measure ads; An identifier for the phone, sent with an ad request and with the report that an ad was shown or tapped. It is the advertising identifier only where the app has been declared for it in Play; everywhere else it is an identifier this SDK generates for that install alone, which no other app can read and which dies when the app is removed. Neither is stored as it arrives: the server keeps a keyed hash of it, so the ads cannot be traced back to the identifier.; Crashlytics installation UUID; Firebase installation ID, from the Firebase Installations SDK that Crashlytics brings in; it is sent with each app session and used to renew the Crashlytics installation UUID; The account identifier, the public half of a key generated in the device key store, and what registered it: the kind of client (phone app, browser, desktop app), its operating system and the app version	Account management, Advertising or marketing, Analytics, App functionality, Fraud prevention, security, and compliance	Yes
Financial info	Purchase history: the Play purchase token, product id and order id of each credit pack, Unlimited or subscription purchase, verified with Google Play and kept so a purchase is granted once; for a subscription also the expiry Play reports, re-read on each renewal	App functionality	No
Location	Approximate location, derived by AdMob from the IP address an ad request arrives on	Advertising or marketing, Analytics, Fraud prevention, security, and compliance	Yes
Personal info	Email address, and the name a provider reported, from the sign-in the person chose. Those two and nothing else: a browser provider is asked for `openid email profile` and only the address and the name are read out of what comes back.	Account management	No

How long your data is kept

Who holds each kind of data listed above, and when it is deleted:

Device or other IDs: Our ad server keeps each ad view and tap for 35 days, linked only to a one-way code made from the device identifier with a secret key (a keyed hash), never to the identifier itself. Then that whole day's records are deleted, and the totals that remain identify no phone. A record of which ads a phone has already been shown is kept for 30 days, so the same ad is not shown to it again.
App activity, Device or other IDs, Personal info: Zaparo ID, our sign-in service, keeps it for as long as your Zaparo ID exists. Your Zaparo ID is shared by every Zaparo app you use, so deleting your data in one app removes only that app's link to it.
App activity, Financial info: Our credits service keeps it until your account is deleted. Deleting it removes your credit balance, any credits held back for something not yet finished, and the record of every change. The Google Play token of a purchase is kept with nothing linking it to you, so a credit pack that was already granted cannot be granted a second time.
App info and performance, Device or other IDs: Google (Firebase Crashlytics) keeps crash reports, minidumps (snapshots of memory at the moment of a crash), the installation IDs and the session data sent with them for 90 days, then removes them from its live and backup systems. We keep none of it on our own servers.
App info and performance, Device or other IDs: Google holds it under its own retention rules. It carries no name, account or advertising ID, only an identifier for the app installation, which Google says is not meant to identify a person or a phone.
App activity, App info and performance, Device or other IDs, Location: Google holds it under its own retention rules for advertising data, published at policies.google.com/technologies/retention. You can reset or delete the advertising ID at any time in your phone's settings.

Deleting your data

You can ask for your data to be deleted at any time, at the address below.

Email privacy@kbsoap.com with the subject “Delete my data” and the app's name, Photo Background Remover.
Your data in Photo Background Remover listed above is deleted within 30 days of your request, except what the list above says is kept, for as long as it says.
Your Zaparo ID is shared by every Zaparo app you use, so it is not deleted: only its link to Photo Background Remover is removed, and your data in other Zaparo apps stays.

Contact

Questions about this policy, or a deletion request: privacy@kbsoap.com