Privacy Policy
Data controller: Cloudy NI (sole trader)
ICO data protection registration: ZC222090
This Privacy Policy describes how QR Forge ("the App", "we", "us") handles information when you use our Android application. We built QR Forge as a fully local, zero-server application. QR codes are generated on-device from data you type — the App never scans QR codes, never uses the camera, never reads your contacts, never tracks your location, and never uploads your QR content anywhere.
The short version
- No accounts. There is nothing to sign up for.
- No analytics. No Firebase, no telemetry, no tracking SDKs.
- No backend. The App has no server to send data to.
- Everything stays on your phone. QR content, history, colours and preferences are stored only in the App's private on-device storage.
1. Zero server-side storage
QR Forge does not transmit, upload, sync, or store any of your QR content or history on any developer-operated server. There is no backend API and no user account system. All persistence uses an on-device database (Android Room) and local preferences (DataStore) inside the App's private sandbox.
Data stored locally includes:
- QR code payloads you generate and choose to save to History
- Labels, colours, and any saved styling
- App preferences and premium status
2. No camera, no scanning
QR Forge is a generator-only app. It does not use the camera, does not request camera permission, and does not scan or read QR codes. It also does not read your device contacts — contact QR codes are built entirely from information you type yourself. This is a deliberate privacy choice.
3. Local sandboxed isolation
Android isolates each application's data. Other apps cannot access your QR Forge database or files without explicit user action. Uninstalling the App permanently deletes all locally stored QR history, styling and preferences.
4. Information we do not collect
- Name, email address, phone number, or postal address
- Precise GPS location
- Contacts, calendar, or SMS content (including SMS QR content you generate)
- Wi-Fi passwords you encode into QR codes
- Health, financial, or biometric data
- Any analytics telemetry
5. Google AdMob & advertising identifiers
The free version of QR Forge displays advertisements served by Google AdMob. When ads are enabled, Google and its advertising partners may process:
- Advertising ID (AAID / GAID): an anonymous, resettable device identifier used for ad delivery, frequency capping, fraud prevention, and aggregated conversion measurement.
- IP address (used to derive approximate geographic region)
- Device model, OS version, language, and screen characteristics
- Ad interaction events (impressions, clicks)
You may reset or limit ad personalization via Settings → Google → Ads → Opt out of Ads Personalization. Purchasing Premium removes all ads.
Google's privacy policy: policies.google.com/privacy
AdMob partner list: support.google.com/admob/answer/9012903
6. GDPR / CCPA consent (Google UMP)
Where required by applicable law — including the EU GDPR and the California CCPA/CPRA — the App presents a consent interface powered by Google's User Messaging Platform (UMP) on first launch. In regulated regions, ad loading is blocked until the consent flow completes successfully. Privacy options are also available from App Settings.
7. Google Play Billing
In-app purchases (Premium Monthly subscription / Premium Lifetime one-time) are processed entirely by Google Play. We receive only purchase confirmation tokens required to unlock premium features locally. We never receive your payment card number, bank account details, or billing address.
8. Children's privacy (COPPA)
QR Forge is not directed to children under 13 years of age. We do not knowingly collect personal information from children.
9. Data retention & deletion
Local data persists until you delete individual codes, clear App storage, or uninstall the App. Premium and preference flags are stored in DataStore on-device. No remote copies are retained by us.
10. Security
Android's sandbox model and filesystem permissions prevent routine cross-app access. We do not expose your data over any developer-controlled network endpoint.
11. Changes to this policy
We may update this Privacy Policy to reflect product, legal, or regulatory changes. Material updates will be indicated by revising the effective date above.
12. Contact
Privacy inquiries: support@cloudyni.com