Welcome to ScanMan! We are well aware that QR codes may contain sensitive information. Therefore, when designing, we follow the principle of "local first, privacy first" to minimize the collection and reliance on your personal data to the greatest extent.

I. What information do we collect?

By default, ScanMan does not require users to register or log in, nor does it automatically upload any scanned content. We only collect a very small amount of information when necessary to support the operation of the function:

1.1 Camera Access Permissions

Used for real-time scanning of QR codes or barcodes

No background shooting, recording or uploading of any images will be conducted

The scanned content is processed locally on the device in real time without going through the server

1.2 Optional Data (if enabled)

Historical records (saved locally on the device for easy review)

The QR code generation data manually entered by the user (processed locally, not uploaded)

The clipboard read and write permissions when using the QR code sharing function (only when triggered by the user)

1.3 Diagnostic Data (Optional to agree or not)

Application crash logs, basic device information (such as operating system, model)

It is used to improve product stability and does not contain any scanning content

Use third-party SDKS such as Firebase Crashlytics. For details, see below

Ii. How do we use this information?

The data we collect is only used for the following purposes:

Realize core functions such as scanning codes, QR code generation, and historical record display

Let users voluntarily save the scanning results for easy review or sharing

Improve product quality and stability (if you agree to send anonymous crash logs)

We will not analyze or upload the content of your QR code, nor will we use the scanning records for marketing or advertising.

Iii. Data Storage and Security

All scanned contents are saved locally on the device by default

Serverless upload or cloud synchronization (unless you actively enable a certain cloud service)

If synchronization or backup functions are introduced in the future, clear notification and consent will be sought before the functions are enabled

Iv. Description of Third-party Services

We may integrate the following services to ensure product quality:

Firebase Crashlytics: Collecting Crash Information and Performance Analysis (Anonymous)

Google ML Kit or open-source QR code scanning engines (such as ZXing) : used for local QR code recognition, running locally and not connected to the network

All third-party services comply with their respective privacy policies, which you can review separately.

V. User Control Rights

You can do it at any time

Clear the historical scan records

Deny access to the camera (Some functions of the App will not be available)

Disable or restrict notification permissions

Diagnostic data upload is prohibited (control switches are provided in the Settings interface)

We respect users' autonomy and do not forcibly bind permission requests.

Vi. Protection of Children's Privacy

This application is not intended for children under the age of 13. We do not intentionally collect any information about children. If you find that the data of minors has been wrongly collected, please contact us for deletion.

Vii. Policy Update Explanation

We may adjust the privacy policy due to functional updates. If there are significant changes to the policy, we will notify you either within the app or through the update log. You have the right to choose whether to continue using this application.

Viii. Contact Us

If you have any privacy-related questions, suggestions or complaints, please contact us