Privacy Notice
How Remove Zero handles image, account, authentication, and security data.
Last updated August 24, 2026
1. Who controls your data
The Remove Zero service operator is responsible for personal data processed through the service.
This notice applies to the website, free image tool, accounts, and related support interactions.
2. Data we use
- Images and image URLs you submit, plus requested output settings and generated results.
- Account, authentication, session, and security metadata.
- Theme and language choices may be stored in the browser so the interface can remember them.
- Technical logs may include request identifiers, IP address, device details, timing, errors, and abuse signals, but must not contain passwords or internal service secrets.
3. Data categories
- Account data such as name, business email, authentication records, and organization membership.
- Processing data such as requested output, request status, timestamps, and technical result metadata.
- Customer images and generated results for the limited time needed to process and deliver them.
- Security and usage data such as IP address, device information, request metadata, and abuse signals.
- Support and privacy-request correspondence.
4. Why we use data
- Provide and secure accounts, image processing, and downloads.
- Prevent fraud, abuse, and unauthorized access.
- Troubleshoot failed requests and improve reliability using minimized technical data.
- Comply with applicable security and legal obligations.
5. Images, model training, and retention
Customer images are processed to complete the requested job and are not used to train a general model by default.
Source and result bytes are retained only as long as needed to process and deliver the request. Minimized security records may be retained longer where needed for service integrity or legal obligations.
6. Service providers and transfers
Remove Zero may use providers for hosting, GPU inference, authentication, email, error monitoring, and support. Providers process data only for their assigned role and under appropriate safeguards.
No provider should receive more data than needed for its role.
7. Cookies and local storage
Remove Zero may use local storage for language, theme, session, and security preferences. Advertising or analytics technologies are disclosed and consent is requested where applicable law requires it.
8. Retention and deletion
Retention periods differ for images, processing metadata, security logs, account records, and support messages.
Deletion requests must be authenticated. Backups may retain protected copies for a limited recovery period, during which they should not be restored except for disaster recovery.
9. Privacy rights
Depending on location, individuals may have rights to access, correct, delete, restrict, object, withdraw consent, or receive a portable copy of personal data, and may complain to a regulator.
We may verify identity and authority before acting on a privacy request.
10. Security, children, and changes
Security measures are summarized on the Security page, but no method is perfectly secure. The service is intended for business users and is not designed for children. A minimum age and any parental-consent process must be set based on launch markets.
Material changes to production data use should be explained before they take effect. A date change alone is not meaningful notice.