Summary
TL;DR What we do — and don't do
- We do not require an account, login, advertising ID, or tracking profile.
- QR/barcode scanning, code generation, and history storage run locally on your device.
- Authenticity Check sends only the cropped photo you explicitly submit to LeadSphere's analysis service so the app can return a visual report.
- We request two iOS permissions: Camera (to scan codes and capture authenticity-check photos) and Add to Photos (used solely when you tap "Save"). Nothing else.
Effective date: June 1, 2026 · Version 1.0
Details
1. Information you provide to the app
When you generate a QR code or barcode you type information (URL, Wi-Fi password, contact details, etc.) into the app. This information is used only to render the symbol you requested and to optionally store it in the on-device history.
If you use Authenticity Check, you may capture or select one product photo, crop it, and tap submit. Only that cropped image is sent to LeadSphere's analysis endpoint to produce the authenticity report shown in the app.
Code-generation inputs and scan history are stored exclusively in a local Realm database inside the app's sandbox container. They are removed when you delete the app.
2. Information we never collect
- Account credentials, advertising profiles, or tracking identifiers
- Device identifiers (IDFA, IDFV) — we do not link any SDK that reads them
- Crash logs, analytics events, or usage statistics
- Contacts, calendar entries, or photo-library contents beyond the single image you explicitly choose to scan or submit
3. iOS permissions we use
Camera Requested only when you open the scanner or Authenticity Check camera. QR/barcode frames are analysed on your device with Apple AVFoundation and Vision. Camera preview frames are never recorded or uploaded automatically. For Authenticity Check, a still image is captured only when you tap the shutter, then the cropped image is uploaded only after you confirm submission. If you use the library instead, the system photo picker hands us only the single image you choose — we never browse your photo library.
Photos · Add Only Requested only when you tap "Save" on a generated code. We save the PNG to your Photos library and immediately release the handle. We never read your existing photos.
4. Children's privacy
QBCode is rated 4+. We do not knowingly collect any information from anyone, including children. If you believe a child has somehow shared information with us, please contact us — we will be very surprised, since we don't collect any data, but we will investigate.
5. Third parties
QBCode is built with open-source libraries including SnapKit, RealmSwift, Alamofire, and lottie-ios. We do not use advertising or analytics SDKs. Alamofire is used only to submit the cropped Authenticity Check photo after you confirm the request.
6. Changes to this policy
If we ever change what QBCode does with your data (for example, adding optional iCloud sync), we will update this page and the effective date above. Material changes will be highlighted on the home screen of the app.
7. Contact
Questions or concerns? Email support@leadsphere.app. We typically reply within two business days.