Wellcode · QR Generator
Privacy Policy
Last updated: October 20, 2026
This policy explains what personal data QR Generator handles, why, who processes it, how long it is kept and what your rights are. It covers the QR Generator app for iPhone and Android, listed as "QR Generator—Fast Code Maker" on the App Store and on Google Play (the "app").
In short: there is no account and no sign-in. The codes you scan and create are read and generated on your phone, and the ones you save stay on your phone. They are not sent to us or to anyone else unless you share them yourself, apart from what an error report can occasionally contain (section 2). What leaves your phone is technical: crash reports, which reach us, and, on Android, usage metrics of the code reader built into the app, which reach Google. We do not show ads, we do not sell your data and we do not track you across other companies' apps and websites.
1. Who is responsible for your data
The data controller is:
Wellcode S.r.l.s.
Via Reggio 5/A, 42015 Correggio (RE), Italy
VAT no. IT02956860353
Email: support@wellcode.it
Write to that address for any question about this policy or to exercise your rights (section 10).
2. What the app does with your data
Scanning with the camera
To scan a code the app asks for access to the camera. The camera images are analysed on your device as they arrive — by Apple's Vision framework, which works on the device, on iPhone, and by Google's ML Kit barcode reader, which is built into the app, on Android. They are not recorded, saved or sent anywhere: once the code is read, only its content is kept in memory to show it to you.
Scanning from a photo
You can also read a code from a picture in your library. The app opens the system's picker, so it only ever receives the picture you choose, not the rest of your library. That picture is analysed on your device in the same way; the app works on a temporary copy in its private storage and never sends it anywhere.
Creating codes
To create a code you type its content: a web address, a text, or the name, password and security type of a Wi-Fi network. The code is generated on your device.
Saved codes, on your phone
A code you scan or create is saved only if you tap Save. The app then keeps, on your device only, the content of the code, its format and the date you saved it. Keep in mind that the content is stored as it is: a saved Wi-Fi code includes the network's password. You can delete a saved code at any time by swiping it away in the Saved list; uninstalling the app deletes them all. Like any other app data, saved codes may be included in your phone's own backup (iCloud or Google), depending on your device settings.
The app also keeps a few settings on your device: your theme, when you first opened it, whether you have already seen the rating screen shown at first launch, and when and how many times it asked the store to show you a rating prompt.
Sharing, copying and opening
Your codes leave your phone only when you choose to send them, apart from what an error report can occasionally contain (see "Crash and error reports" below). When you tap Share, the app creates an image of the code and hands it, with its content as text, to your phone's share sheet; what happens next depends on the app or person you pick, under their own terms. For a Wi-Fi code, both the image and the text can include the network's password. You can also copy the content to your phone's clipboard.
When the app recognises a code as a web address, Open opens it outside the app, in your browser or in the app that handles that address: from then on you are on that website or app, which receives what any visit sends it, such as your IP address, under its own privacy policy. The app does not check addresses with any online service before opening them. The links in Settings lead to websites in the same way, except that the store pages of our other apps and these pages on wellcode.it open in a browser view inside the app.
Ratings and reviews
The app asks the App Store or Google Play to show you their rating prompt, and the Settings screen can open the app's page on the store or share links to it through your share sheet. Ratings and reviews are handled by Apple or Google under their own terms: we only see what the store publishes, and the store decides whether to show the prompt at all.
Crash and error reports
When the app crashes or something goes wrong, the versions of the app distributed through the stores send a report to Firebase Crashlytics with technical details such as the device model, operating system and its version, app version, free memory and disk space, battery and orientation state, whether the app was in the foreground, whether the device is rooted or jailbroken, the technical details of the error, and random identifiers of the installation. To tell how often the app crashes, the same service also records when the app is opened, with those device details and identifiers. Reports are not linked to you, and they are not meant to include the codes you scan, create or save; but the technical message of an error can sometimes contain part or all of the content the app was handling at that moment — for example a web address it could not open, or the first characters of a code it could not save.
The code reader on Android
On Android, the code reader built into the app (Google ML Kit) sends Google metrics about how it is used and how it performs: device manufacturer and model, operating system version and build, the hardware available for machine learning, the app's package name and version, the reader's version and settings, the format and resolution of the images it analyses, how long it takes, the type of event, error codes, and a random identifier of the installation. Under ML Kit's terms, the images it analyses and the codes it reads are not sent to Google; the reader may also contact Google from time to time to receive fixes and updated compatibility information. On iPhone this part does not apply: the app uses Apple's Vision framework instead.
When you contact us
If you write to us, we receive your email address and whatever you write, including any information you choose to add.
What the app does not collect
There is no account, so we do not have your name, email address or phone number unless you write to us. The app does not collect your location, your contacts or your device's advertising identifier. It contains no analytics service and we do not analyse how you use it: the only usage data are the app-launch records and the ML Kit metrics described above. It does not show ads and has no in-app purchases. It never uses the microphone.
3. Why we use your data and on what legal basis
| Purpose | Data | Legal basis (GDPR) |
|---|---|---|
| Reading and creating codes, and keeping the ones you save | Camera images, the photo you pick, the content of your codes — all processed on your device | Performance of our contract with you (art. 6(1)(b)) |
| Finding and fixing crashes and errors, keeping the app working | Crash and error reports, records of app launches, installation identifiers | Legitimate interest in a reliable app (art. 6(1)(f)) |
| Using a code reader that works on the device, without sending images anywhere (Android) | The ML Kit metrics described in section 2 | Legitimate interest in a fast, private and reliable reader (art. 6(1)(f)) |
| Answering your messages | Email address, what you write | Legitimate interest in replying to you (art. 6(1)(f)) |
| Complying with the law and defending our rights | Any data needed in the specific case | Legal obligation (art. 6(1)(c)); legitimate interest (art. 6(1)(f)) |
4. Who processes your data
We do not sell or rent personal data. We have no servers of our own: the app talks directly to the providers below. Unless the table says otherwise, they process the data on our behalf and under contracts that bind them to use it only to provide their service to us.
| Provider | What it does | Where |
|---|---|---|
| Google Ireland Ltd / Google LLC — Firebase Crashlytics | Crash and error reports | United States and other countries where Google has facilities |
| Google LLC — ML Kit (Android only) | Receives the code reader's usage metrics, which ML Kit's terms say Google uses to measure performance, debug, maintain and improve ML Kit and to detect misuse. For that use Google acts as an independent controller under its own privacy policy | Any country where Google has facilities, including the United States |
| Apple Inc. / Apple Distribution International; Google (Google Play) | Distributing the app; ratings and reviews. They act as independent controllers under their own privacy policies | EU and United States |
We may also disclose data when the law requires it, for example to a court or a public authority, and to a buyer if Wellcode or the app is ever sold, in which case this policy will continue to protect your data.
5. Transfers outside the European Union
The providers above may process data in the United States and in other countries outside the European Union. Those transfers are covered by the EU-U.S. Data Privacy Framework, where the provider is certified under it, or by the Standard Contractual Clauses approved by the European Commission. You can ask us for a copy of the safeguards that apply.
6. How long data is kept
- Saved codes and settings: on your device, until you delete them or uninstall the app.
- Camera images and picked photos: not kept. They are analysed and discarded; the temporary copy of a picked photo stays in the app's private storage until the system or the app clears it.
- Crash and error reports and their identifiers: 90 days, as stated by Firebase.
- ML Kit metrics (Android): kept by Google under its own policies.
- Emails you send us: for as long as needed to answer you and follow up on the same issue.
7. Deleting your data
Since there is no account, there is no account to delete. To delete a saved code, swipe it away in the Saved list; to delete everything the app keeps on your phone, uninstall it. Crash reports are not linked to you, so we cannot pick out yours; they are deleted automatically after 90 days.
8. Cookies
The app does not use cookies. These pages are hosted on Firebase Hosting (Google), which receives your IP address to deliver them; they set no cookies and load nothing from other websites.
9. Security
Crash reports and the reader's metrics travel encrypted (HTTPS/TLS). Saved codes stay inside the app's private storage on your device, protected by your phone's own security; the app does not encrypt them separately, so protect your phone with a passcode, especially if you save Wi-Fi passwords. No system is perfectly secure: if a breach affecting your data occurs, we will notify you and the authorities as the law requires, as far as we are able to reach you.
10. Your rights
Under the GDPR you have the right to:
- access your data and receive a copy of it;
- rectify data that is inaccurate or incomplete;
- erase your data (see section 7);
- restrict processing in certain cases;
- data portability: receive the data you gave us in a structured, machine-readable format;
- object at any time to processing based on our legitimate interest.
To exercise them, write to support@wellcode.it. We reply within one month, free of charge. Because the app has no account and keeps your codes on your phone, we hold very little that can be traced back to you, and may be unable to find data that is not linked to you.
You also have the right to lodge a complaint with a data protection authority — in Italy, the Garante per la protezione dei dati personali — or with the authority of the country where you live or work.
11. Children
QR Generator is suitable for all ages. It has no account, asks for no personal details and sends out only the technical data described above, which is not linked to anyone. We do not knowingly collect personal data from children under 13; if you believe a child has given us personal data, for example by writing to us, tell us and we will delete it.
12. Changes to this policy
We will update this policy when the app changes the way it handles personal data, and publish the new version on this page with its date. If the changes are significant — in particular, if we want to use your data for a new purpose — we will tell you in the app before they take effect, and ask for your consent where it is required.