Privacy Policy

Effective date: February 1, 2026

This Privacy Policy explains how Cleanbox ("we", "us", or "our") collects, uses, and protects information when you use our app and services.

1. Information We Collect

Device information (model, OS version, app version, language).
Identifiers needed for account/session management (e.g., device ID).
Usage data such as feature usage and error logs (if enabled).

We do not upload your photos or contacts for analysis. All scanning and analysis happen locally on your device unless a feature explicitly requires cloud processing.

2. How We Use Information

Provide core features and maintain app functionality.
Improve performance, stability, and user experience.
Prevent abuse and ensure service security.

3. Data Sharing

We do not sell your personal data. We may share limited information with service providers to operate the app (e.g., analytics or crash reporting), but only as necessary and with appropriate safeguards.

4. Data Retention

We retain data only as long as needed to provide the services and comply with legal obligations. You can request deletion where applicable.

5. Security

We use reasonable technical and organizational measures to protect your information. No system is 100% secure, but we continuously improve our safeguards.

6. Your Choices

You can manage permissions in your device settings.
You can uninstall the app to stop data collection.

7. Children

Our services are not intended for children under 13. We do not knowingly collect personal information from children.

8. Changes to This Policy

We may update this policy from time to time. Changes will be posted on this page with a new effective date.

9. Contact Us

If you have questions about this Privacy Policy, please reach out via the app or support channels made available to you.

AI and Data Processing

This app does not use any third-party AI service.
Photos, videos, and contacts are processed on-device only and are not sent to any third-party AI provider.
Data is sent to our own backend only when necessary (such as authentication, subscription verification, feedback submission, and basic usage reporting), with appropriate security safeguards.