QR Code Generator
Privacy Policy
Effective date: July 14, 2026
This Privacy Policy applies to the QR Code Generator Android application (package name: com.tejan.qrcodegenerator) (the "App"). This Privacy Policy explains how information is accessed, processed, stored, and shared when you use the App.
1. Overview
The App is a QR code generation and scanning utility. The developer does not provide user accounts, registration, login, cloud storage, or a developer-operated backend server. The developer does not directly collect QR code content or other personal information entered into the App.
The App uses Google services, including Google Mobile Ads (AdMob) for advertising and Google ML Kit Barcode Scanning for QR code scanning. These third-party services may process certain information as described in this Privacy Policy and in Google's own policies.
2. Information Entered into QR Codes
The App allows users to generate QR codes for content such as text, website URLs, email details, phone numbers, SMS content, Wi-Fi information, location coordinates, contact information (vCard), UPI payment information, social media URLs, event text, and PDF URLs.
This information is provided by the user and is processed locally on the device to generate QR codes. QR code generation is performed on-device using the ZXing library. The App does not upload QR code content to a developer-owned server, and the developer does not receive the content of generated QR codes.
3. QR Code History and Favorites
The App stores QR history and favorites locally using Android SharedPreferences. Stored records may include an internal item ID, QR type, QR type label, full QR content, date and time information, timestamp, created or scanned source information, favorite descriptions, optional logo image data, QR color, and background color.
History and favorites are not uploaded to a developer-owned server and are not received by the developer. This locally stored data remains on the device until the user deletes it, clears the App's data, or uninstalls the App.
Users can delete individual history or favorite items, use available bulk deletion options, or clear all history or favorites from the relevant App screens.
4. QR Scanner and Camera Access
The App requests camera permission to scan QR codes in real time. Camera frames are analyzed on-device using CameraX and Google ML Kit Barcode Scanning. The App does not record camera video, save camera frames to disk, or upload camera frames to a developer-owned server.
When a QR code is detected, the decoded QR content is processed locally and may be saved to the App's local QR history.
The App also allows users to select an image from the device to scan a QR code. The selected image is processed locally for barcode detection. The App does not upload the selected image to a developer-owned server.
5. Gallery Images and QR Logo Customization
Users may select an image from their device to use as a logo overlay when customizing a QR code. The selected image is processed locally. The developer does not receive or upload the selected image to a developer-owned server.
If logo information is saved with a history or favorite record, optional logo image data may be stored locally on the device as part of that record.
6. Saving and Exporting QR Codes
The App allows users to save QR codes as PNG, JPG, and PDF files.
- PNG and JPG files may be saved to the public Pictures/QR Codes/ directory using Android MediaStore.
- PDF files may be saved to the public Documents/QR Codes/ directory using Android MediaStore.
Exported files are not uploaded to a developer-owned server. Files saved in public device storage may remain after the App is uninstalled and must be deleted by the user through the device's Gallery, Documents app, or file manager.
7. Sharing and Clipboard
When a user chooses to share a QR code, the App creates a temporary PNG file in the App's cache directory and uses Android FileProvider and the Android share sheet. The user chooses the external app or service that receives the shared file.
The developer does not receive the shared QR file. Once content is shared with a third-party app or service selected by the user, that third party's privacy practices apply.
The App also provides a copy function that places QR content on the Android system clipboard. Clipboard content may be accessible to the operating system and other apps according to Android's clipboard behavior and permissions. The copied content is not uploaded to a developer-owned server by this App.
8. Advertising and Google AdMob
The App uses the Google Mobile Ads SDK (AdMob) to display interstitial advertisements. The App does not currently use banner, rewarded, app open, or native ads based on the audited App implementation.
Google Mobile Ads may automatically collect, process, and share certain data for advertising, analytics, SDK performance, and fraud prevention purposes. Depending on Google services, device settings, applicable law, and advertising configuration, this may include:
- IP address, which may be used to estimate general or approximate location;
- Device and account identifiers, including the Android Advertising ID where available;
- Device and app information;
- User product interactions and advertising interactions, such as impressions, taps, clicks, and engagement information;
- Diagnostic and SDK performance information; and
- Information related to SDK errors or crashes.
The developer does not directly read or maintain a separate developer database of this advertising data. Advertising-related information is processed by Google through the Google Mobile Ads SDK.
For more information about Google's data practices, review:
- Google Privacy Policy
- How Google uses information from sites or apps that use its services
- Google Mobile Ads SDK data disclosure information
9. Google ML Kit Barcode Scanning
The App uses Google ML Kit Barcode Scanning to detect and decode QR codes. Camera frames and user-selected images used for scanning are processed for barcode detection. Based on the audited App implementation, QR scanning is performed on-device and camera frames are not stored or uploaded by the App.
ML Kit may use network access to obtain or manage required model components. The App does not send decoded QR content to a developer-owned server.
Google's privacy practices are described in the Google Privacy Policy.
10. Network Access and External Actions
The App uses internet and network-state access primarily for Google Mobile Ads and Google service components. The developer does not operate a backend API or server that receives user QR content.
Some actions are initiated by the user and may open external apps or services. For example, the App may open a website in a browser, open a phone dialer, email app, maps app, or another compatible application. Information passed to an external app as part of a user-requested action is then subject to the privacy practices of that external app or service.
11. Permissions
The App may use the following Android permissions:
- INTERNET: Used for Google Mobile Ads and Google service network access.
- ACCESS_NETWORK_STATE: Used to determine network connectivity for services such as advertising.
- CAMERA: Used to scan QR codes. Camera permission is requested at runtime.
- FLASHLIGHT: Used for the scanner torch or flashlight function.
- VIBRATE: Used to provide vibration feedback after successful QR scanning.
- ACCESS_WIFI_STATE: Used for Wi-Fi-related QR functionality.
- CHANGE_WIFI_STATE: Used to support user-requested Wi-Fi connection or network configuration actions from compatible Wi-Fi QR codes.
The App does not request device location or contacts permission. Location coordinates and contact details used in QR codes are entered by the user and processed locally.
12. Data the Developer Does Not Directly Collect
Based on the audited App implementation, the developer does not directly collect or maintain a developer-operated server database containing users' names, email addresses, phone numbers, postal addresses, account information, user IDs, precise location, contacts, photos, videos, audio files, QR code content, scanned QR code content, or local search history.
This statement does not mean that third-party SDKs collect no information. Google Mobile Ads may process the advertising, device, interaction, identifier, IP address, and diagnostic data described in the Advertising section above.
13. Local Data Retention and Deletion
The App does not enforce a fixed retention period for locally stored QR history or favorites. History and favorites remain on the device until deleted by the user, App data is cleared, or the App is uninstalled.
Exported PNG, JPG, and PDF files remain in public storage until the user manually deletes them. These public files may remain after the App is uninstalled.
Temporary sharing files are stored in the App's cache directory and may be cleared by Android, by clearing the App's cache or data, or when App-specific storage is removed.
Users can delete local App data by:
- Deleting individual history or favorite records;
- Using bulk delete or clear-all options where available;
- Deleting exported QR files through the device's Gallery, Documents app, or file manager;
- Clearing the App's cache or data through Android Settings; or
- Uninstalling the App.
Data managed independently by Google through its SDKs is subject to Google's applicable retention and privacy practices.
14. User Accounts and Account Deletion
The App does not provide user accounts, registration, login, or authentication. Therefore, there is no App account to delete. The developer does not operate a backend database of user accounts or QR code content.
15. Data Security
The App keeps QR history and favorites in local Android SharedPreferences. The audited App implementation does not encrypt these SharedPreferences. Because QR content can contain information chosen by the user, users should avoid storing highly sensitive information in QR history or favorites if they do not want that information retained locally on the device.
The App does not transmit QR content to a developer-owned server. Google SDK network communications are managed by Google and are subject to Google's security and privacy practices.
No method of electronic storage or transmission can be guaranteed to be completely secure.
16. Children's Privacy
The App is a general-purpose QR code utility and does not contain features specifically designed for children. The audited App implementation is not configured for child-directed treatment in Google Mobile Ads.
The developer does not knowingly operate a user account system or developer-owned server for collecting personal information from children. Parents or guardians with privacy questions may contact the developer using the email address below.
17. International Data Processing
Google may process information through AdMob and other Google services on servers located in different countries. Google's processing and international data handling are governed by Google's applicable privacy terms and legal safeguards.
18. Privacy Rights and Requests
Because the developer does not maintain a developer-operated server database of user personal data or QR content, there may be no developer-controlled server record to access, correct, or delete.
Users can manage and delete locally stored QR history, favorites, exported files, and App data using the controls described in this Privacy Policy.
Depending on where you live, applicable privacy laws may provide additional rights regarding personal data. For questions about data controlled by the developer, contact the developer using the email address below. For information processed independently by Google, users should review Google's privacy policy and privacy controls.
19. Changes to This Privacy Policy
This Privacy Policy may be updated when the App's features, permissions, SDKs, advertising implementation, or data practices change. The updated Privacy Policy will be posted on this page and the effective date will be revised.
20. Contact Us
If you have questions about this Privacy Policy or the App's privacy practices, contact:
Email: amittechinfohelp@gmail.com