Privacy Policy Draft for QR & Barcode Studio

Developer: Aktyva konsaltynh technologies
Privacy contact: mateuszbednarski696@gmail.com

Scope

This policy describes how the Android application QR & Barcode Studio handles information. It reflects the inspected application source and supplied Store listing. It should be reviewed before publication and updated if the app’s data practices change.

Information accessed and stored

The app processes camera images when you start scanning, images you select for decoding, content you enter to create codes, and JSON backup files you choose to import. Scanning, decoding and code generation take place on your device. Camera images are not uploaded by the app, and the scanning implementation does not save camera photographs.

Code content can include text, website addresses, contact names, phone numbers, email addresses, Wi-Fi network names and passwords, or any other information contained in a scanned code or entered by you. The app does not request access to your device’s contacts; contact codes use the details you enter.

Scanned results, manual entries and generated codes are saved locally in history and collections. Saved records include the code content, format, collection name, an internal identifier and whether the record was scanned. Imported backups are merged with existing saved records.

The inspected application does not implement accounts, developer-operated cloud storage, advertising, analytics, tracking or automatic transmission of your saved content to the developer.

Purposes

The app uses this information to scan and decode codes, generate QR codes and barcodes, display results, search history, organize collections, customize output, save or share images, and export or restore backups.

Permissions and file access

Camera permission is requested when you start camera scanning. You may deny or revoke it through Android settings. Image import and manual entry provide alternatives.

The app uses Android’s document picker to access images and backup files you select and to save PNG images and JSON backups to a location you choose.

The Android manifest includes Internet permission. The inspected application does not implement uploads or background network collection. Website addresses are opened in an external app only after you choose to open them and confirm the action.

Sharing and external services

The app does not automatically share your saved information with the developer or third parties.

When you choose Share image, the app creates a PNG in its local cache and grants the receiving app access through Android’s sharing system. The image contains the encoded information, which recipients can decode.

PNG exports and JSON backups contain your code content. Backups may include contact details and Wi-Fi passwords. If you choose a cloud-backed storage location or share through another service, that provider handles the information under its own privacy practices.

When you confirm opening a website, the selected browser or other receiving app receives the URL. The destination website may collect information under its own policy. Links do not open automatically.

Third-party libraries

The app uses ZXing and ZXing Android Embedded to encode and decode codes on your device, together with Android and Jetpack Compose components. No advertising, analytics or remote crash-reporting SDK is identified in the inspected dependencies or application source.

Security

Saved history and collections are held in the app’s private Android storage. Android automatic app backup is disabled in the application manifest. Shared images are exposed through a non-public file provider with temporary read permission for the selected receiving app.

The app does not implement additional encryption for saved code records or exported backups. QR codes and barcodes are readable encodings, not encryption. Protect exported files and shared images, especially those containing passwords or personal details.

Errors may produce exception types and stack traces in Android’s local diagnostic logs. The inspected code does not send these logs to a remote reporting service.

No storage or sharing method can guarantee complete security. Because the app does not implement its own server transfers, it does not establish a separate encrypted upload channel. Connections made by external browsers, websites, storage providers or sharing apps depend on those services.

Retention and deletion

Saved codes remain on your device until you delete them or remove the app’s data. No automatic expiration period is implemented.

Use Settings, then Delete all local codes, and confirm Delete all to remove saved history and collections. You can also clear the app’s storage or uninstall it through Android settings to remove its local app data.

Images created for sharing may remain in the app’s cache until overwritten, cleared by Android or removed when app storage is cleared. No fixed cache retention period is implemented.

Deleting local codes does not delete exported PNG images, JSON backups or copies already shared with other apps or people. Delete those separately from their storage locations or request deletion from the relevant recipient. Importing a retained backup can restore previously deleted records.

For privacy or deletion questions, contact mateuszbednarski696@gmail.com. The developer cannot remotely access or delete records held only on your device. If you email the developer, your email address and the information you include become available to the recipient; a specific support correspondence retention period has not been established in the supplied information.

Children’s privacy

A target age range has not been established in the supplied information. The inspected app does not implement accounts, age verification or remote collection of children’s information. Information entered or scanned by a child is processed and stored locally in the same way as other code content. Children and their guardians should take care when encoding or sharing personal information and passwords.

Policy changes

This policy should be updated when changes to the app affect its data handling. Review the version made available with the app for current practices. No separate in-app policy-change notification mechanism was identified in the inspected source.

Contact

Developer: Aktyva konsaltynh technologies
For privacy questions or deletion guidance: mateuszbednarski696@gmail.com