Privacy Policy — QR Code Generator - Main
Last updated: September 16, 2026
1. Who is responsible
QR Code Generator - Main is published by Hamid Manafov, an individual developer based in Azerbaijan. In this policy, "I" and "my" refer to Hamid Manafov. I am the controller of personal information processed for the app and its support service. Contact: hamidmanafov7@gmail.com.
This policy explains local processing, subscription services and support communications. Your use of the app is governed by the Terms of Use. Services you choose to visit or share with have their own privacy policies.
2. Overview
Scanning and QR generation happen on your device. I do not operate a backend that receives your camera images, scan history or saved QR designs. You do not need an app account.
The app has no ads, advertising SDK or tracking across other companies' apps or websites. It does not use the advertising identifier (IDFA). It has no separate general-purpose usage analytics SDK; RevenueCat processes subscription information and provides subscription analytics, as explained in section 4.
Information can leave your device for subscription checks and purchases, when you contact support, or when you choose to share content or open a destination. Device backups are described below.
3. Information on your device
- Camera. With your permission, the app processes camera frames locally to recognise QR codes and barcodes. It does not record or upload the camera feed. Without camera permission you can still scan a selected photo or create codes. Change camera access in iOS Settings → Apps → QR Code Generator - Main → Camera.
- Selected photos. The system photo picker gives the app access to the images you select; it does not require general access to your photo library. A picture selected for scanning is processed locally and is not saved as an image in scan history.
- Logos. If you add a picture as a QR logo and save the design, a copy of the logo image is stored locally with that design so it can be reopened and edited.
- History and designs. Scan history contains decoded code content. Saved designs contain the encoded content, design settings and any logo. Content can include links, contact information or Wi-Fi credentials. The app does not send these records to me or RevenueCat.
- Preferences. Settings such as appearance and the scan-history toggle are stored locally.
Recognised scans are saved locally in History. You can delete entries in History; Settings also offers a separate confirmation to remove existing scans. Created designs are separate from scan history and can be deleted in History.
Local records remain until you delete them or delete the app and its data. Exporting or sharing a code can create copies outside the app; deleting its history entry does not remove those copies. Temporary files are also created for exports. Your device's backup settings may include app data in a device or iCloud backup. Deleting local data does not necessarily erase earlier backups; backup management is controlled by you and Apple.
4. Subscription services
Apple. The App Store handles payments, billing and subscription transactions under Apple's Privacy Policy. I do not receive your payment-card details or Apple Account credentials.
RevenueCat. RevenueCat, Inc. processes subscription information on my behalf. Its SDK creates a random app user ID and communicates with its servers to check subscription status, validate purchases and restore access. These checks can occur even if you have never purchased PRO.
This processing includes the SDK-generated ID; device, operating-system and app-version information; purchase and receipt records; last-seen information; and the request's IP address, from which country can be derived. The app does not supply a name or email address to RevenueCat.
The information supports subscription access, purchase restoration, fraud prevention and subscription reporting, such as revenue and renewal statistics. Although RevenueCat calls the ID "anonymous", it distinguishes an installation or subscription record; it is not a promise that all related records are legally anonymous.
RevenueCat does not receive your camera frames, selected photos or QR content from the app. Its Privacy Policy and Data Processing Addendum describe its role and safeguards.
Subscription records are held to administer and restore purchases, resolve billing issues and meet applicable record-keeping obligations. Deleting the app does not automatically delete records held by Apple or RevenueCat. Contact me about RevenueCat records as described in section 8; Apple's records are governed by its own retention rules.
5. Support and actions you choose
Support email. If you send a support or privacy request, I receive your email address, message and any attachments you include. The app prepares an editable message containing the app version, device model identifier and iOS version. You can review or remove these details before sending. Your email service and the support mailbox service process the correspondence.
I use this information to answer your request, investigate the reported issue and handle related follow-up. Correspondence is retained for those purposes and any applicable legal or dispute-related record-keeping needs. Do not send passwords, full payment-card details or unrelated sensitive data.
Sharing and destinations. Exporting a code or sending it through the iOS share sheet gives the chosen destination the content you select. Opening a scanned link or another action can send information to the website, app or service involved. Those recipients handle it under their own policies.
A detected web link opens when you choose the open action, or automatically in single-scan mode if you enable Auto-open detected link in Settings. Auto-open is off by default and does not apply to batch scans. The app does not verify the safety of scanned destinations.
6. Recipients, transfers and security
Apple handles App Store transactions; RevenueCat handles subscription processing and reporting. Support correspondence passes through email services, and user-initiated actions involve the recipients you choose. Service providers may use subprocessors to operate their services.
I do not sell personal information or share it for cross-context behavioural advertising.
RevenueCat processes data in the United States, and Apple and email services may process data in other countries. I handle support requests from Azerbaijan. Where applicable, international transfers require appropriate safeguards. RevenueCat's Data Processing Addendum includes Standard Contractual Clauses and provisions for UK and Swiss transfers. Contact me for information about safeguards relevant to your request.
App records are stored in the iOS app sandbox and benefit from the device's security protections. Subscription communications use HTTPS/TLS. Email and any exported content are also subject to the security of the services you use. No storage or transmission method is completely secure.
7. Legal bases
Where the GDPR or UK GDPR applies, I rely on:
- Contract: processing needed to provide and restore a subscription, and to respond to requests about that service.
- Legitimate interests: operating and securing the subscription service, understanding subscription performance, preventing fraud and addressing support issues, balanced against your rights and expectations.
- Legal obligations: keeping records or responding to requests when required by applicable law.
You control camera access through iOS permission settings and select individual images through the photo picker. These device controls determine access to those features; they are not blanket consent to unrelated processing. Where processing requires consent under applicable law, that consent must be obtained separately and can be withdrawn.
8. Your choices and rights
You can manage local data as described in section 3 and cancel a subscription through your Apple Account subscription settings. Deleting the app does not cancel a subscription.
Where the GDPR or UK GDPR applies, you may request access, correction, erasure, restriction or portability of your personal information, and object to processing based on legitimate interests. You may withdraw consent where processing relies on it, without affecting earlier lawful processing. You may also complain to the relevant data protection authority. These rights are subject to applicable conditions and exceptions.
If the CCPA or CPRA applies, the information described in this policy includes identifiers, commercial information, technical information and any support content you provide. The sources, purposes and recipients are described in sections 4–6. Subject to applicable law, you may request access, correction or deletion and exercise your rights without unlawful discrimination. An authorised agent may contact me with evidence of authorisation. I do not sell personal information or share it for cross-context behavioural advertising.
Send requests to hamidmanafov7@gmail.com. I cannot remotely retrieve or delete records held only on your device. For a subscription record, a transaction ID can help locate it if you have one; you can still contact me if you have never purchased. I may need additional information to verify a request and find the relevant record, and will explain if I cannot identify it. Do not send Apple Account passwords or payment-card details. Contact Apple directly about information it independently holds.
I respond within the time limits required by the law applicable to your request.
9. Children
The app is not directed at children under 13. I do not knowingly collect their personal information. If you believe a child has provided personal information through the app or support service, contact hamidmanafov7@gmail.com so I can investigate and arrange deletion of identifiable records where appropriate.
10. Changes and contact
The current policy is published at https://hamid207.github.io/qr-legal/privacy.html. Updates will have a new date at the top. Material changes will be highlighted in the app or App Store release notes. If a change requires consent or another step under applicable law, publishing an updated policy alone does not replace it.
For questions or privacy requests, contact Hamid Manafov at hamidmanafov7@gmail.com.