QR & Barcode Mediet Studio Privacy Policy

App: QR & Barcode Mediet Studio
Developer: Devs Kiwi Power
Privacy contact: contact@kiwipowersp.com

About this policy

This policy describes how QR & Barcode Mediet Studio processes information based on its current application source and supplied Store description.

Developer: Devs Kiwi Power
Privacy contact: contact@kiwipowersp.com

Information accessed and processed

The app processes information you enter, paste, or scan to create, display, and organize QR codes and barcodes. This may include text, website addresses, contact names, organizations, phone numbers, email addresses, Wi-Fi network names and passwords, and other content encoded in a scanned code.

Contact details and Wi-Fi information are supplied by you or decoded from codes. The inspected implementation does not read your address book or retrieve saved Wi-Fi passwords from your device.

Camera access is used for QR-code and barcode scanning. The scanner processes camera images on your device and returns decoded content to the app. The inspected implementation does not save or upload camera photographs or video. You can manage camera permission through Android settings and use manual entry instead of scanning.

Local storage and purposes

Code generation, decoding, searching, and library organization take place on your device. No account or developer-operated cloud synchronization is implemented in the inspected source, and no upload of your code content to the developer was identified.

The app stores library and activity records in private Android app preferences. Records can include code content, names, code formats, whether an entry was generated, scanned, or manually entered, timestamps, saved status, collection assignments, and appearance and export settings. It also stores collection names and preferences for history and scanner sound.

Activity history is enabled by default. When enabled, new generated, scanned, and manual entries are retained automatically. Turning it off stops automatic retention of new activity, but does not delete existing records. Codes you explicitly save are retained, and batch generation saves successful results to the library even when activity history is off.

This information is used to generate and render codes, show decoded results, maintain your library and collections, support search and filters, and apply your preferences.

Sharing and actions you control

The inspected implementation does not automatically share your code library with the developer or integrate an advertising or analytics service.

Copying content places it on the system clipboard. Access to clipboard content is governed by your device and operating system.

Exporting a PNG writes a code image to a destination you select through Android's document picker. If you choose a cloud-backed storage provider, that provider may receive and store the exported file under its own practices. Anyone who can read the exported code may be able to recover its encoded content, including contact details or Wi-Fi passwords.

Website links are not opened automatically. After you confirm that you want to open a website, the app passes the address to an external app such as your browser. That app and the destination website handle the resulting request under their own privacy policies and may receive information such as your IP address and the requested URL.

Third-party libraries and network access

The app uses ZXing and ZXing Android Embedded for local code generation and camera scanning. No transmission of code content by these integrations is shown in the inspected implementation.

The Android manifest declares Internet access and advertising-ID permission. No advertising SDK, ad display, advertising-ID access, analytics integration, or tracking code was identified in the inspected source and declared dependencies. The permission declaration alone does not establish that an advertising identifier is collected.

The app also contains a WebView for displaying a configured terms and privacy page. If displayed and successfully loaded, that page would involve a network request to its host. The inspected startup state currently opens the code tools directly. Data handling by a remotely hosted page could not be established from the local source.

Android backup

The app allows Android backup and does not define custom backup exclusions in the inspected manifest. Depending on your device, Android version, and backup settings, app data may be backed up or restored by the operating system or its backup provider. This can include locally stored library information. Such backups are separate from any app-operated cloud synchronization and are governed by the provider's practices and your device settings.

Security

The app uses Android's private app storage for its library and preferences. The inspected implementation does not add application-level encryption to those stored records. Password masking in an input field does not encrypt the password stored in a code or record.

No app-operated transfer of your code library was identified, so encryption in transit for such a transfer is not applicable to the inspected local workflow. Security of browser requests, hosted pages, exports to storage providers, and operating-system backups depends on the relevant service and configuration. No method of storage or transmission can be guaranteed secure.

Retention and deletion

Local records and preferences have no automatic expiration period in the inspected implementation. They remain until you delete them or remove the app's local data.

You can delete an individual stored code using Delete record. Settings → Clear activity history removes unsaved activity while retaining saved codes and collections. Deleting a collection removes the collection but keeps its codes. Turning off history does not erase earlier activity.

You can use Android's app storage controls to clear the app's local data. Uninstalling ordinarily removes local app data, but operating-system backups may remain or later restore data according to your backup settings. Exported images, clipboard copies, and copies held by other apps or storage providers are not deleted when you remove a record from this app. Manage those copies separately.

No in-app mechanism for submitting a deletion request to the developer is implemented. The inspected source does not show a developer-held copy of your code library that could be remotely deleted. No response time or remote deletion capability is established by the supplied information.

Children's privacy

The supplied information does not establish an intended age range or a child-directed audience. No separate child account, age-verification system, or child-specific data collection is shown in the inspected implementation. The local processing and storage described in this policy apply to all users.

Changes to this policy

This policy should be updated when the app's functionality, permissions, integrations, or data practices change. Review the policy accompanying the version you use for updated information.

Contact

App: QR & Barcode Mediet Studio
Developer: Devs Kiwi Power
Privacy contact: contact@kiwipowersp.com