Why accounts appear
Accounts can synchronize work, store cloud projects, meter server credits, support teams, or connect a web and mobile workflow. Those can be legitimate features. They are not inherently required to select a local photo, create a foreground mask on the device, and save a local result.
For a single-image utility, an account also creates a password, recovery flow, user database, and new category of personal information. A focused local app can avoid all of that.
Look beyond the sign-in screen
“No account required” does not automatically mean “no upload.” A website or app can accept an anonymous upload. Check the privacy policy for clear answers to four questions:
- Where is the foreground mask generated?
- Is the source image sent to a developer or third-party server?
- Does the app include analytics or advertising SDKs?
- What information is required for purchases and support?
What Background Remover does
Background Remover uses Apple frameworks to generate and edit the foreground mask on iPhone and iPad. It does not operate a photo backend, require an account, include advertising, or include app analytics. Apple StoreKit handles purchases, and Apple’s photo picker controls selection.
Purchases without a developer account
An App Store purchase is tied to the Apple Account managed by Apple. The developer receives verified entitlement status rather than payment-card details. Restore Purchases lets a user ask the App Store to restore qualifying access without making a Background Remover account.
The tradeoff
Without a developer cloud account, projects do not automatically synchronize between devices and there is no web editing history. That is intentional for this app: import one image, make the result, export it, and keep ownership of the files in your existing photo and document workflow.