This list describes third-party SDKs and services that LATICX products may use. Whether a service applies depends on the product, operating system, region and features you use; Android-only push channels do not apply to iOS.
Contents
1. Disclosure Principles
2. Third-Party Services and Data Disclosure
3. Notes
4. Your Rights
1. Disclosure Principles
- We integrate third-party services only where necessary for product features, security operations, notifications, analytics, crash diagnostics, SMS, or email delivery.
- We require third parties to process data only for agreed purposes and not to use, sell, or disclose it beyond the permitted scope.
- If a third-party SDK reads device identifiers, initializes at app startup, or involves cross-border transfer, we disclose it in this list.
2. Third-Party Services and Data Disclosure
| Third party | Provider / region | Scenario | Shared or collected data | Device identifiers | Initialization / trigger | Sharing method | Third-party privacy policy |
|---|---|---|---|---|---|---|---|
| Sentry Flutter SDK / GlitchTip | Sentry Software, Inc. (United States); GlitchTip may be self-hosted, with node location depending on LaticX deployment | App exceptions, crashes, error logs, page breadcrumbs, and runtime diagnostics | Exception stack, error message, page visit record, event properties, app version, runtime environment, device model, OS version, app-generated session ID / anonymous ID, hashed user ID | No. It does not read hardware identifiers such as IMEI or IDFA. It uses app-generated anonymous identifiers for error attribution. | Enabled according to actual product configuration and applicable privacy settings | The SDK reports crash and error diagnostic data subject to user settings. | Sentry; GlitchTip |
| PostHog Flutter | PostHog, Inc. (United States / EU cloud region or self-hosted node depending on actual configuration) | App behavior analytics, page view statistics, feature usage statistics, and user funnel analysis | Page name, event name, event properties, app version, runtime environment, device model, OS version, app-generated anonymous ID / distinctId, hashed user ID | No. It does not read hardware identifiers such as IMEI or IDFA. It uses app-generated anonymous identifiers. | Enabled according to actual product configuration and applicable privacy settings | The SDK reports analytics events according to configuration and user settings, which may include app-generated identifiers. | PostHog |
| Huawei Push Kit / HMS Core Push (Android only) | Huawei Software Technologies Co., Ltd. / Huawei Device Co., Ltd. (China) | Message push, notification delivery, and push token management on Huawei devices | AppID, package name, Push Token, AAID, device model, device type, system version, push status, notification-related information | Yes. Uses AAID, Push Token, and other app-level device identifiers. | Yes. Initialized at app startup; Push Token is obtained after login. | Necessary push information is transmitted through the system push channel. | Huawei Consumer Business Privacy Statement |
| Honor Push SDK (Android only) | Honor Device Co., Ltd. (China) | Message push, notification delivery, and push token management on Honor devices | AppID, package name, Push Token, AAID, device information, system version, push status, notification-related information | Yes. Uses AAID, Push Token, and other app-level device identifiers. | Yes. Initialized at app startup on devices supporting Honor push. | Necessary push information is transmitted through the system push channel. | HONOR Privacy Policy |
| OPPO / HeyTap OPUSH SDK (Android only) | Guangdong HeyTap Technology Corp., Ltd. (China) | Message push, notification delivery, and RegisterId management on OPPO, OnePlus, and realme devices | AppKey, AppSecret, package name, app version, OPUSH SDK version, RegisterId, device type, system version, push status, notification-related information | Yes. Uses RegisterId and other app-level device identifiers. | Yes. Initialized at app startup on devices supporting OPPO push; RegisterId is obtained after login. | Necessary push information is transmitted through the system push channel. | OPUSH SDK Privacy Policy |
| vivo Push SDK (Android only) | Vivo Mobile Communication Co., Ltd. (China) | Message push, notification delivery, and regId management on vivo devices | AppID, AppKey, package name, app version, vivo Push SDK version, regId, device type, system version, network information, push status, notification-related information | Yes. Uses regId, Android ID / OAID / VAID, and other device or app-level identifiers. | Yes. Initialized at app startup on devices supporting vivo push; regId is obtained after login. | Necessary push information is transmitted through the system push channel. | vivo Privacy Policy |
| Apple APNs / UserNotifications | Apple Inc. (United States and global operating entities) | System push notifications, notification permission request, and push token management on iOS devices | APNs Device Token, Bundle ID, notification permission status, notification metadata and delivery status, notification tap events | Yes. APNs Device Token is a device-and-app-level push identifier. | Registers for remote notifications when the user enables notification features and grants iOS notification permission. | Necessary notification information is sent through Apple's system push channel. | Apple Privacy Policy |
| Google ML Kit Barcode Scanning / mobile_scanner | Google LLC (United States) / mobile_scanner open-source component | QR code and barcode scanning | QR/barcode content in camera view, device information, app information, performance metrics, diagnostic information, installation-level identifiers | Yes. It may use installation-level identifiers for diagnostics and service improvement; it does not read IMEI or IDFA. | No. Used only when the user opens the scanning feature. | The recognition capability is called when the user opens the scanning page. Diagnostic information processed by Google services is governed by Google's policy. | Google Privacy Policy |
| WebRTC SDK / flutter_webrtc | flutter_webrtc open-source component; signaling, relay, or STUN/TURN node locations depend on LaticX deployment | Remote access, device connection, DataChannel data transfer, audio/video preview, and network traversal | Signaling information, ICE candidates, network addresses, device connection information, audio/video streams, DataChannel transmitted data | No. It is not known to actively read hardware identifiers such as IMEI or IDFA. Network addresses and session information are used during connection. | No. The SDK may be loaded with the app, but actual WebRTC connections are established after login or when the user enters a related feature. | Used to establish connections between user devices and the NAS or relay nodes. Transmitted content depends on the user's actions and connection method. | LaticX Privacy Policy |
| Google Calendar | Google (processing regions depend on Google services) | After authorization, read and display selected third-party calendar events; currently read-only | Selected calendar and event details, account identifier, token and sync state | Uses account and service identifiers | After the user authorizes and selects a calendar | The NAS connects directly to Google to synchronize the selected calendars | Google Privacy Policy |
| Microsoft Calendar / Microsoft Graph | Microsoft (processing regions depend on Microsoft services) | After Outlook.com / Hotmail authorization, read and display selected calendars; currently read-only | Selected calendar and event details, account identifier, token and sync state | Uses account and service identifiers | After the user authorizes and selects a calendar | The NAS connects directly to Microsoft to synchronize the selected calendars | Microsoft Privacy Statement |
| Google Drive | Google (processing regions depend on Google services) | After authorization, back up files between NAS and Google Drive according to the selected direction | Selected files, necessary metadata, account identifier, token and backup status | Uses account and service identifiers | After the user authorizes and creates a backup task | Transfers between the NAS and Google Drive according to the selected backup direction | Google Privacy Policy |
| Third-party weather service (if used) | Weather service provider, depending on the service used | Display weather city and conditions on Smart Calendar | City, weather query parameters and information needed for the network connection, which may include an IP address | Network requests may involve an IP address | When the weather feature is used | Necessary query information is sent and weather results are received | See the applicable weather service provider’s privacy policy |
3. Notes
Different services or push channels may be used depending on the device, operating system and region. Some third-party services process information only when you use a relevant feature, sign in, enable notifications, scan a device code or an error occurs. We update this list when third-party services or information processing practices change.
4. Your Rights
If you have questions about third-party data disclosure, or wish to access, correct, or delete related personal data, contact privacy@laticx.com. We will process your request after verifying your identity.