Privacy Policy for ScanGrid QR

Developer: It as a service
Privacy contact: info@itservice.fun

Scope

This policy describes how ScanGrid QR handles information when you scan, create, organize, export, or share QR codes and barcodes. It reflects the current application source and supplied app listing.

Information accessed and stored

ScanGrid QR processes code content on your device. The inspected application does not send scanned or entered content to the developer and does not implement accounts, cloud uploads, advertising, analytics, or remote crash reporting.

Camera scanning uses camera access to read QR codes and barcodes locally. Camera frames are processed on your device; the inspected code does not upload them or save them as image files. You can manage camera permission in Android settings. You can also choose an image through the system picker for local decoding. The selected image may be displayed temporarily as a preview; the app stores the decoded content in history when automatic history is enabled, rather than storing a copy of the original image in its library.

Information you scan or enter may include text, web addresses, Wi-Fi network names and passwords, and contact-card details such as names, organizations, phone numbers, email addresses, postal addresses, and websites. The app processes the fields you provide; it does not access your address book or automatically change contacts or connect to Wi-Fi networks.

Saved records include code content, format, name, date and time, collection, a locally generated record identifier, and output settings such as size, color, and error correction. Collection names and preferences for automatic history, scan sound, and vibration are also stored locally.

Purposes

The app uses this information to decode and display codes, generate code images, organize saved codes and scan history, search local records, remember preferences, and prepare PNG images or ZIP files for export or sharing. Sound and vibration provide scan confirmation when enabled.

Automatic scan history is enabled by default. You can disable it in settings. Disabling it stops future automatic history entries; it does not erase existing records.

Sharing and external services

The inspected application does not automatically transmit your code content to the developer or to analytics or advertising services. Information can leave the app when you choose an external action:

• Sharing sends the generated PNG or ZIP file to the app you select through Android’s sharing interface. The receiving app handles it under its own privacy practices.
• Exporting saves a file to the destination you choose. If you select a cloud-backed document provider, that provider may upload or synchronize the file.
• Copying places decoded content on the system clipboard, where it is handled under Android’s clipboard access rules.
• Opening a web link launches an external app or browser with the selected address. That app and the destination website may receive the address and ordinary connection information. Links are opened only after you choose to open them.

Code images encode the underlying content, including any Wi-Fi passwords or personal details you include. Anyone with access to an image may be able to read that content.

Third-party libraries

The Android app uses ZXing Core and JourneyApps ZXing Android Embedded for local code generation and scanning, along with AndroidX, Jetpack Compose, and Kotlin libraries. No advertising, analytics, or remote crash-reporting SDK was identified in the inspected dependencies or application code.

The app declares internet permission, but the inspected Android code does not implement a developer-operated data upload service. User-selected external apps and services may use the internet independently.

Local storage, security, and backup

On Android, saved records and preferences use app-private storage. Files prepared for export or sharing are written to the app’s cache. Sharing uses Android’s FileProvider with temporary read permission for the selected recipient.

The inspected code does not add encryption to saved code content or exported files. Protection of local data depends on Android’s app isolation, device security, and your device settings. No security measure can guarantee complete protection. Take care when storing or sharing sensitive code content.

Android backup is enabled in the application configuration. Depending on your device and system settings, Android or a device backup service may back up or restore app data under that service’s privacy practices. This is separate from an app-operated cloud service.

Retention and deletion

Saved codes, history, collections, and preferences remain in local storage until you remove them or clear the app’s data. No automatic expiry period is implemented for these records.

You can delete individual saved or history records from their details screen. You can clear all scan history through the app while keeping saved codes and collections. To remove all locally stored collections and preferences as well, use Android’s clear-storage controls. Uninstalling generally removes app-private data, but exported files and system backups may remain separately.

Prepared export and sharing files remain in the app’s cache until cleared by Android or through device storage controls; the inspected code does not set a fixed deletion schedule for them. Deleting a record or clearing history does not delete exported files, clipboard content, recipient copies, or backups. Manage those copies through the relevant device, storage provider, or receiving app.

For privacy or deletion questions, contact info@itservice.fun. The inspected app provides no account or server-side record store for the developer to search or erase, and the developer cannot directly remove data stored only on your device or with a service you selected.

Browser preview

If you use the browser preview, records and preferences are stored in that browser’s local storage. Clear the preview site’s browser data to remove them. The preview uses the qrcode library for local QR generation; camera scanning, image decoding, export, and sharing are unavailable in that preview.

Children’s privacy

A specific intended age group has not been established in the supplied information. The inspected app does not implement age collection, accounts, or a separate data-collection system for children. Children’s personal information entered or scanned into a code is handled locally in the same way as other code content and may be disclosed if the user exports or shares it.

Policy changes

This policy may be updated to reflect changes to the app’s features or information handling. Review the policy made available with the app for updates.

Contact

For questions about this policy or ScanGrid QR’s privacy practices, contact:
It as a service
info@itservice.fun