Optional one-time purchase
All QR features remain free. An optional Google Play purchase supports development and permanently removes ads; it is not a subscription. Google Play processes payment and manages purchase history according to its policies. The developer does not receive your card or bank account details. The app queries Google Play for purchase status and keeps a signed purchase receipt and signature in app-private storage to verify ad removal and restore it. These records are not added to app logs or custom analytics events and are not sent to a developer server. App-private records are removed when you clear app data or uninstall. Google Play retains its own transaction records. Restore using the same Google Play account while online after reinstalling or changing devices. A completed refund or revocation removes the entitlement when Google Play next reports that it is no longer owned. Settings reset does not cancel or erase your purchase.
Optional Firebase analytics remains off by default. If you enable it, Google Analytics for Firebase may automatically record in-app purchase events. This is separate from the purchase verification described above. Payment does not opt you into analytics.
QR cards, PDFs and printing in 0.7.0
You select Wi-Fi QR images through the system picker, and QRTransfer reads them on your device. QR content, card headings and notes are used to create card images and PDFs. Edits saved in the library are stored in encrypted app-private storage on your device. Previously exported images, PDFs and printed copies do not update automatically. Replace them yourself after changing a Wi-Fi password or other details.
PDFs are temporarily generated in the app cache. Saving copies a PDF to the location you choose in the system file picker. Sharing grants temporary read access to the receiving app you select. Printing passes the document to the Android print service; the receiving app or print service has its own processing policies. QRTransfer card generation does not send QR content or PDFs to a developer server.
Exported PNGs, PDFs and printed copies are not encrypted. Anyone who can see them may read information in the QR, including Wi-Fi passwords. Copies saved outside QRTransfer or shared with another app are not removed when you uninstall QRTransfer; delete them in their saved location or receiving app. The app does not confirm whether a guest actually connects to Wi-Fi.
Optional analytics introduced in 0.6.2 remains off by default in 0.7.0. The consent, data processing and retention information below continues to apply.
Optional analytics in 0.6.2
Optional analytics in 0.6.2
Google AdMob/UMP advertising and Nearby device transfer processing described for 0.6.0 remain separate services. Version 0.6.2 adds optional Google Analytics for Firebase to understand feature use and improve reliability. Optional analytics described here applies to 0.6.2; it was not included in 0.6.0. Korean and English features remain available.
Analytics is OFF on fresh installation and upgrade. It is not required to use QRTransfer. The privacy policy is available in Settings before choosing Allow analytics. Firebase is not initialized for optional analytics before consent. Turn off and reset analytics in Settings, or reset all app settings, stops future measurement, denies analytics consent and resets local analytics data and the local analytics installation identifier. The choice remains OFF after restart. This does not promise immediate deletion of previously transmitted server data; existing aggregate reports may remain. Google controls processing and deletion timing, and server retention depends on the Analytics property's settings.
Our custom events contain only fixed categories: new/return app use (derived locally), transfer mode and result, QR tool category and error stage/code. There is no developer-assigned user ID. We do not send QR payloads, text, contacts, names, email, phone, URLs/URIs, paths, filenames, bytes, sizes, titles, Wi-Fi SSID/password/BSSID, EXIF/GPS, user input or exception text/stack/cause in custom analytics events. QR display is not reported as confirmed delivery. Crashlytics and raw fatal/error collection are not used.
Allowing analytics is not a no-data choice: Google's SDK may collect automatic events (such as first open, sessions and engagement), pseudonymous installation identifiers, device/app/network details, and approximate location derived from IP addresses. Analytics uses internet and encrypted transport. Google operates globally and may process data outside Korea. No exact server country or retention period is promised without confirmed cloud settings.
AdMob and UMP remain separate services with their own data processing and choices described below. Analytics consent never grants advertising storage, advertising user data or ad personalization; those analytics consent categories remain denied, and Analytics advertising ID collection and automatic screen reporting are disabled. Linking Analytics with AdMob, if configured by the operator, does not change this user choice. This implementation does not rely on Google signals or personalized advertising. Operator: gagadodo; contact: kmymgd@gmail.com. The existing support route is https://wekinu.github.io/.
Transfer limits
Photos for QR transfer are limited to 3MB. Galaxy fast file transfer is limited to 1MB and depends on device compatibility and permissions. Large QR photo transfers may take several minutes. Ordinary and continuous QR transfer are not encrypted: someone who sees the screen can read the content. Nearby device transfer uses an encrypted connection after both devices approve the displayed confirmation code. Analytics does not change the protocol or these limits.
QR sharing and advertising
Share content by QR without an account. QR transfer works without internet. Text, contacts, photos, and camera footage are not sent to a developer server. This content and file names are not included in ad requests or personalized advertising keywords.
This version uses the Google AdMob advertising SDK and Google's User Messaging Platform (UMP). Internet is used to load ads and check consent information, and a banner ad may appear on Home. QR transfer remains available if ads cannot load.
Google SDK data processing
Fast file transfer uses the Nearby Connections SDK in Google Play services. Your selected file is sent directly to the connected device, and the Nearby connection is encrypted. Google's Nearby SDK collects usage diagnostics such as performance, connection latency, reliability, throughput, device model, country, build version, and app package name to improve the user experience. You can allow or refuse this collection in Android Settings under Google > Usage & diagnostics. Details: https://developers.google.com/nearby/connections/overview#data_collection
Google's advertising SDK may collect or share IP addresses (which can estimate approximate location), app launches and ad interactions, diagnostic information, advertising IDs, app set IDs, and applicable device or account identifiers to serve and analyze ads and prevent fraud. SDK communication uses TLS encryption. This communication is separate from unencrypted QR transfer. UMP checks consent status according to the applicable region and choices and provides privacy choice screens when needed.
Whether ad requests are allowed follows UMP's result. If privacy choices need to be available, Change ad privacy choices appears in the app settings. You can reset or delete your advertising ID in Android settings. Google Privacy Policy: https://policies.google.com/privacy
SDK processing details: https://developers.google.com/admob/android/next-gen/privacy/play-data-disclosure
Information processed on your device
Text, contacts, and photos you enter or select are processed on your device to display or read QR codes. Camera footage is used for QR recognition and is not itself recorded or saved. The app does not request permission to read all contacts or access all photos. Only items you choose in the system picker are read.
Storage and deletion
Photos selected in QR tools are used for QR recognition on your device. Photos and scanned content are not sent to a developer server, and no scan history is saved automatically. Wi-Fi QR codes are generated from a network name selected from the list or entered manually and a password you enter. Choosing Save to library stores QR content and names, and QR card titles and instructions, encrypted with an Android Keystore key in app-private storage. You can delete individual entries in the library or remove them by clearing app data or uninstalling the app.
Tapping Allow location permission in the Wi-Fi list requests precise location permission. Once allowed, the app reads the currently connected Wi-Fi name and nearby network names, security types, and signal strengths on your device. Access point identifiers (BSSID) are compared temporarily to identify the connection. Scan lists and BSSIDs are not saved to files or servers or included in ad requests. Location coordinates and saved Wi-Fi passwords are not read. Location must be turned on, and the app waits for scan results only while the list screen is active. You change settings and permissions yourself.
Save as image or Save image and share saves QR codes and QR cards as PNG files in the QRTransfer album in your gallery. Exported images are not encrypted, and information such as passwords in the QR can be read. They remain after uninstalling the app and must be deleted in your gallery.
Choosing Save my card stores the name, company, job title, phone number, and email you enter in app-private storage. Delete saved card removes it. Transfer settings and diagnostic records for continuous QR receiving, including file names, sizes, times, device information, and success status, are stored on your device. Transfer content itself is not included in diagnostic records.
Clear app data in the app's storage settings or uninstall the app to remove app-private data. Automatic backup is not used. Files received through continuous QR and exported result CSV files remain in the QRTransfer folder in Downloads and must be deleted separately with the system files app. Temporary sharing files are stored in app cache; old files and files beyond the size limit are removed on the next share. Clearing system cache or uninstalling the app also removes them.
Sharing you choose
When content is displayed as regular or continuous QR, nearby people who can see the QR can read it. These QR transfers are not encrypted. A fast transfer connection QR contains only a temporary connection identifier, not file content. After comparing verification codes and approving the connection on both phones, the file is transferred over an encrypted wireless connection. Original photos may contain metadata such as photo location. JPEG files made with Resize to send do not copy original metadata. After sharing with another app or choosing to add a contact, that app's storage and processing policies apply.
Permissions
Camera permission is used to receive QR and scan fast transfer connection QR. Nearby device permissions (Bluetooth and Wi-Fi) are requested when you select fast transfer. Android 10–12 versions need location permission and Location turned on for nearby device discovery; the app does not read or record location coordinates. Full file access is not requested; only files chosen in the system picker are read. Internet and network state permissions are used by advertising SDKs and Nearby's network connection between devices. Advertising identifier permissions are used by advertising SDKs. You can change app permissions in Android settings.
Fast transfer file storage
A temporary copy of the file selected for sending is made in app cache and removed on completion or cancellation. It may remain if the app is forcibly stopped; clear system cache or uninstall the app to remove it. Received files are saved to the QRTransfer folder in Downloads and remain after uninstalling the app, so delete them yourself in a files app.
Contact
Use the developer contact shown on the QRTransfer Google Play listing, or email kmymgd@gmail.com.
Current service settings: user-level and event-level Analytics retention is 2 months, with retention reset on new activity off. This setting does not limit all standard aggregate reports or promise immediate server deletion. Detailed device/location data, Google signals, advertising personalization and enhanced Firebase audiences are off. Basic SDK device/network processing and pseudonymous identifiers are still described above. QRTransfer AdMob is linked to its Firebase project for qrx.app only; this linkage does not replace optional analytics consent or grant analytics advertising consent. Account-wide impression revenue is off.
All four optional Google Analytics account data-sharing settings are off.