Português: transparência de dados em português
Data Transparency
This page is an explanatory transparency page. The official Google Play “Data safety” form must be completed in Play Console and must match the exact build distributed to users.
| Data / access | How it is used | Where |
|---|---|---|
| Camera frames | QR/barcode recognition | Processed for scanning; not intentionally stored on developer servers |
| User-selected image | Scan a code contained in an image | Selected by the user; intended for local recognition |
| Scan history / favorites | Convenience and app functionality | Local device storage |
| Device/app identifiers | Analytics, attribution, fraud prevention and advertising where enabled | May be processed by third-party SDK providers |
| App interactions | Analytics and product improvement | May be processed by analytics/attribution providers |
| Crash logs / diagnostics | Reliability and troubleshooting | May be processed by Firebase/diagnostic providers |
| IP/network information | Networking, security, ads/analytics; approximate location may be inferred | Third-party service infrastructure |
Third-party technologies observed in the supplied app bundle
Google/Firebase services, Google Mobile Ads, AppsFlyer, and Meta/Facebook advertising/mediation components. Actual collection/sharing depends on the final app build, configuration, consent flow, region and device settings.
Important
If SDKs are removed or added before publication, update both this website and the Google Play Data safety answers. Do not claim “no data collected” if active SDKs collect diagnostics, identifiers, analytics or advertising data.
Questions: fernandoprodutormusical@gmail.com