WinKit Privacy Policy
How WinKit for Android and iOS uses device permissions, processes your content and collects usage and diagnostic data.
Effective and last updated:
Developer: Chu Nam Thang. Ho Chi Minh City, Vietnam. Support and privacy contact: namthangdev@gmail.com.
On this page
Content on your device
WinKit does not require an account and does not display ads. QR and barcode contents, recognized text, document images, Wi-Fi details entered to create a QR code, and values entered into tools are processed on your device. We do not send this content to a developer-operated server or include it in our custom analytics events.
Settings and some tool state, such as counters and timers, are stored locally. You choose when to copy, save, export or share content. Files saved outside WinKit, clipboard contents, and device or cloud backups are managed by your operating system and the services you choose.
Device permissions
- Camera and photos
- Used to scan codes, text and documents, or process an image you select. Saving an image may require photo or storage access on some OS versions. Picking an image does not require unrestricted access to your photo library.
- Microphone
- Used while the noise meter is active to calculate sound levels on-device. The tool does not save or upload audio recordings.
- Location
- The compass uses location, when permitted, to calculate true north. This location is not sent in our custom events. Separately, analytics services may derive a coarse region from connection information.
- Notifications and alarms
- Used for timers you start, including supported iOS Live Activities. You can manage these permissions in device settings.
You can revoke supported permissions in device settings. A tool that needs a denied permission may be unavailable; other tools remain accessible.
Usage and diagnostic data
Production versions use the following Google Firebase services. On-device processing of your content does not mean that the app collects no technical data.
- Firebase Crashlytics
- Collects crash and non-fatal error reports, stack traces, device and OS information, app version, installation-related identifiers and diagnostic context such as the current screen. We use this data to investigate faults and improve stability.
- Google Analytics for Firebase
- Collects screen views, tool opens, predefined actions and results, tab selections, settings changes and permission outcomes. The SDK also processes app-instance identifiers, device and app information and coarse regional information. We use this data to understand feature usage and prioritize improvements.
- Firebase Performance Monitoring
- Collects performance measurements, device and connection information (including IP addresses), installation identifiers and supported network-request metadata. Measurements include startup, rendering and custom operation durations, such as decoding a QR photo or creating a PDF. We use this data to identify slow operations.
Our custom events use predefined categories, not raw QR contents, Wi-Fi passwords, OCR text, images, document contents, filenames, user-entered URLs, tokens or bill amounts. We do not link analytics identifiers to an app account or use them for personalized advertising. Android advertising-ID collection is disabled; the iOS integration does not include IDFA support.
Android scanning uses Google ML Kit and Google Play services. ML Kit may send Google device and app information, performance metrics and installation-related identifiers for diagnostics and usage analysis. iOS scanning uses Apple frameworks such as Vision and VisionKit.
Disclosure to others
Google processes the technical and usage data described above to provide Firebase and ML Kit services. We do not sell your data. We may disclose information where required by law or necessary to protect users and investigate abuse. If you contact support, we receive the email address and information you choose to send.
We require service providers to protect data consistently with this policy and applicable data-protection obligations. Google's handling is subject to its applicable data-processing and security terms and the service privacy disclosures linked above.
Retention and deletion
- Local app data
- Remains until you reset or delete it, clear app data where supported, or uninstall WinKit. Exported files and backups outside the app must be deleted separately.
- Analytics
- Our Analytics property is configured to retain event data for 2 months and user-level data for 14 months. Reset on new user activity is enabled: new activity refreshes the expiry of the user identifier to 14 months from that activity; this does not extend the event-data retention period. Standard aggregated reports are not subject to these retention settings. Google's processing and deletion schedules apply.
- Crashlytics and Performance
- Google documents 90 days for Crashlytics crash data, 30 days for IP-associated Performance events, and 60 days for installation-associated or de-identified performance data before deletion starts. Deletion from active and backup systems may take additional time.
- Support emails
- Kept while needed to resolve your request and meet applicable legal obligations. You can contact us to request deletion.
Your choices and privacy requests
You control device permissions and whether to export or share content. Production versions currently do not provide an in-app switch to disable the three Firebase services. Revoking camera, microphone or location permission does not disable technical collection. Uninstalling stops future collection from that installation, but does not automatically delete information already sent.
To request access, correction, deletion or restriction of personal data, contact the privacy email listed on this page. These rights depend on applicable law. WinKit has no user accounts, and we do not associate SDK identifiers with your name or email, so your email alone may not identify every technical record. We will explain what we can locate and process. Do not send passwords or private scanned documents with your request.
Children
WinKit is not directed to children under 13. We do not intentionally request their personal information. Contact us if you believe a child has provided personal information through the app or support so we can review and address it.
Security and international processing
Firebase and ML Kit diagnostic communications use encrypted transport. We restrict custom telemetry to predefined technical categories rather than scanned content. No storage or transmission method is completely secure. Google may process information outside your country under its service terms and applicable transfer safeguards.
External services and this page
Links you open and apps you share to have their own privacy practices. This policy page is hosted on Vercel, which processes connection information such as IP address and browser details to serve and protect it. We do not add analytics or advertising scripts to this page. Language and theme choices may be saved in your browser's local storage.
Updates and contact
We update this policy and the date above when our data practices change. Material changes may require additional notice or consent. For questions or privacy requests, contact Chu Nam Thang at namthangdev@gmail.com.