Last updated:2026.7.14
iNFCi is an application provided by Weigan Technology (Shenzhen) Co., Ltd. (hereinafter referred to as "we" or "us") for NFC read/write and related device connectivity features. This Privacy Statement applies to iNFCi on iOS and Android.
We attach great importance to the protection of your personal information and privacy. We will provide appropriate security measures for your personal information in accordance with legal requirements and industry-standard security practices.
Depending on how you obtain the app, which operating system you use, and your device language environment, advertising and billing features may differ: the Google Play Android build always uses Google AdMob and Google Play Billing, regardless of device system language; on the iOS App Store build, when your device system preferred language is not Simplified Chinese, Google AdMob and Apple In-App Purchase are used, and when your device system preferred language is Simplified Chinese, Pangle GroMore mediation (including Pangle and Tencent Ads) is used and VIP is still offered through Apple In-App Purchase; the mainland China app-store Android build also uses GroMore mediation and does not include Google Play Billing.
We will only use your personal information where we have a lawful basis to do so. Under applicable law, we may process your information based on lawful grounds such as your consent, where necessary to perform or enter into a contract with you, or where necessary to comply with legal obligations.
1.1 Core app features. To provide NFC read/write, Bluetooth device connection, firmware updates, QR code scanning, and LAN-based device updates, we invoke NFC, Bluetooth, camera, and network capabilities through system APIs only when you use the related features. NFC tag data, device communication payloads, and files you choose to read or write are processed on your device or between your device and the peripherals you connect. We do not use this data to build a profile that identifies you.
1.2 Local preferences. We store certain settings on your device (such as theme, usage quota counters, and VIP status flags) to operate the app. This information remains on your device unless otherwise described in this Statement.
1.3 What we do not do. We do not require you to create an account to use iNFCi. We do not provide, include, or distribute copyrighted game files or other third-party content through the app.
1.4 Personal information inventory. To meet applicable privacy laws and app-store compliance requirements, we disclose below the categories of personal information that iNFCi may involve. The purpose, method, and scope described for each category apply only to the versions or scenarios noted. Categories marked as "not collected" mean that neither our app nor the third-party SDKs we have configured to restrict collection will actively collect, read, or upload that type of information.
Collection by third-party advertising SDKs listed above occurs only after you tap Agree on the first-launch privacy dialog (mainland China Android build) or when you use the relevant ad services (other builds). If you choose Decline and use core features only, we do not initialize advertising SDKs and the related collection does not occur.
This section does not apply to the mainland China app-store Android build. That build does not use Google AdMob, and we do not collect Android ID through AdMob on that build. See Section 2.2 below.
In these scenarios, the app integrates the Google Mobile Ads SDK (AdMob) to display ads (including app-open, banner, and rewarded formats), measure ad performance, and prevent fraud. AdMob is provided by Google LLC and may automatically collect information such as:
Where required by law (for example, in the European Economic Area, the UK, or Switzerland), the Google Play Android build may use Google's User Messaging Platform (UMP) to request your consent before serving personalized ads. You can review or change your ad privacy choices on that build in the app under Settings → Ad privacy settings when available for your region.
On iOS in the AdMob scenario described above, the app does not use UMP and does not currently present an App Tracking Transparency (ATT) prompt before showing AdMob ads. You can limit personalized ads or reset advertising identifiers in iOS system settings (for example, Settings → Privacy & Security → Apple Advertising).
Google's privacy policy: https://policies.google.com/privacy
VIP subscribers do not see ads for features covered by their active subscription.
In these scenarios, the app does not use AdMob. It initializes third-party advertising SDKs through Pangle GroMore mediation, which may serve ads from the following ad networks we have integrated:
GroMore selects and fills ad requests across these networks for the ad placements you trigger in the app. After you agree to this Privacy Statement, the SDKs automatically collect information such as:
SDK providers and privacy policies:
Pangle and Tencent Ads each maintain independent privacy disclosures for their SDKs. Beyond the common categories listed above, whether an SDK processes additional personal information, and details such as retention periods or cross-border transfers, are governed by the relevant provider's privacy policy.
Privacy controls configured in our app (by platform):
Mainland China Android build. To follow a data-minimization approach, we configure Pangle SDK privacy settings and GroMore mediation privacy settings to disable or restrict collection and use of the following. We do not initialize advertising SDKs until you tap Agree on the first-launch privacy dialog:
If you choose Decline and use core features only on that Android build, we do not initialize advertising SDKs and you may continue using core NFC features without ads.
iOS (system preferred language is Simplified Chinese). We configure the Pangle SDK privacy provider to disable use of location for advertising. Before initializing the Pangle SDK, if the system has not yet recorded your choice, the app may present an App Tracking Transparency (ATT) prompt to determine whether IDFA may be used. If you deny or restrict tracking, we configure the SDK to limit IDFA use. Unlike the mainland China Android build, iOS does not currently show the same first-launch Agree/Decline privacy dialog; VIP subscribers do not see ads. iOS does not involve Android-specific identifiers such as Android ID, OAID, or IMEI.
Third-party SDKs may transmit the above information to their servers for processing and storage. Please refer to each provider's privacy policy for details.
The iOS (App Store) build offers optional VIP subscriptions and a lifetime purchase through Apple In-App Purchase (StoreKit) regardless of system language environment. The Android (Google Play) build offers comparable benefits through Google Play Billing. Payment flows are handled by Apple or Google; we do not collect or store your full payment card numbers or other sensitive payment credentials.
We receive only purchase confirmation, subscription status, and product identifiers to unlock VIP features (such as ad-free experience, theme access, and expanded usage) on your device. You can manage or cancel subscriptions in your Apple or Google account settings.
Apple's handling of payment data is governed by Apple's policies: https://www.apple.com/legal/privacy/
Non-VIP users may be subject to daily free usage limits and can earn additional uses by watching rewarded video ads (this may apply on iOS and on Android builds where monetization is enabled).
The mainland China Android build does not use Google Play Billing. Free usage quotas on that build are governed by in-app rules and may include rewarded video ads.
Google's handling of payment data is governed by Google's policies: Google Payments Terms of Service
This service may request the following permissions on iOS and/or Android. We ask for your consent through the system permission dialog before using sensitive capabilities. Permissions you deny will limit only the related features.
Used to read from and write to NFC tags and cards when you use NFC features (iOS and Android).
Used to discover and connect to external Bluetooth devices (such as Pixl.js) for data transfer and firmware updates (iOS and Android). On Android 12 and above, Bluetooth scan is declared as not used for location purposes.
Android: On Android 11 and below, the operating system may require location permission before Bluetooth device scanning. This permission is not requested on Android 12 and above for Bluetooth scanning in this app. It is unrelated to ad targeting on the mainland China build, where coarse location permission declarations for the ad SDK have been removed from the manifest.
iOS: Location permission may be requested when you use map or tag-coordinate related features. Such data is used only for features you actively invoke and is not used directly for ad targeting.
Used when you actively choose an image from your library to decode a QR code, or when you save a QR code to your library from a related feature. Access occurs only when you trigger the related feature; we do not read your entire photo library in the background.
Used for local authentication when you enable app lock or related security features. Biometric data is processed by the system; we do not collect or store your biometric templates.
Used for QR code scanning when you choose that feature. Camera images are processed locally for decoding and are not uploaded to our servers (iOS and Android).
Used for ads, store billing, firmware or content downloads you initiate, and LAN-based device updates (iOS and Android).
Used to show optional status notifications related to background device operations (such as Bluetooth connections or updates), when you grant notification permission.
Used to keep Bluetooth or device-connection tasks running reliably while you are actively using related features.
You can manage permissions for this app at any time in your device Settings.
Depending on your location, you may have rights to access, correct, delete, restrict, or object to certain processing of your personal information, and to data portability where applicable.
For data processed by Google (AdMob, Play Billing, or UMP on the Google Play Android build), Apple (App Store In-App Purchase on the iOS build), or by Pangle, Tencent Ads, and GroMore on the iOS Simplified Chinese ad scenario and the mainland China Android build, you may also exercise choices through the relevant provider's settings and policies.
To exercise rights relating to data we control, contact us using the details in Section 7. We will respond within a reasonable time as required by applicable law.
6.1 Core NFC and Bluetooth data you process through the app is handled on your device or directly with connected peripherals, unless you explicitly initiate a network transfer.
6.2 Advertising and billing-related data processed by Google, Apple, Pangle, Tencent Ads, and their service providers is stored and processed according to each provider's policies and infrastructure, which may involve servers outside your country of residence.
6.3 We retain information only for as long as necessary to fulfill the purposes described in this Statement, unless a longer retention period is required by law.
You may contact us through the following methods to exercise your relevant rights. We will respond as soon as possible.
Email: weigantechnology@outlook.com
If you are not satisfied with our response, especially where applicable law grants you additional remedies, you may lodge a complaint with a data protection authority in your country or region. You may also seek resolution through a court of competent jurisdiction where permitted by law.