Third-Party Personal Information Sharing List
StationHub Third-Party Personal Information Sharing List
Updated: October 20, 2026
The StationHub mobile app uses selected open-source components and third-party services for notifications, media playback, scanning, crash diagnostics, product analytics, and remote connections. This list describes what each component does, when it runs, what it may process, and whether information leaves the device. Versions and provider policies may change; use the provider’s latest public policy as the reference.
1. Components that run locally
The following components mainly run on the phone and do not send personal information to the component maintainer’s servers:
| Component | Scenario | Information it may access | Handling |
|---|---|---|---|
flutter_local_notifications 19.4.1 / com.dexterous.flutterlocalnotifications | Backup progress, remaining items, and completion alerts | Notification permission and notification text | Creates notifications on the device |
audio_service / com.ryanheise.audioservice | Background playback or keeping a backup task alive | Notification and background-run permissions | Local integration; no transfer to third-party servers |
flutter_vlc_player 7.4.2 / MobileVLCKit 3.6.1b1 | Play NAS videos and change orientation | Playback state, accelerometer, and gyroscope | Plays on the device; video is not uploaded to the maintainer |
flutter_scankit 2.0.3 / com.huawei.hms:scanplus:2.12.0.301 | Add a device, QR sign-in, or binding | Camera image and basic device information needed to run HMS | Codes are preferably recognized on-device; see the Huawei HMS Core Privacy Statement |
mobile_scanner 6.x / iOS GoogleMLKit/BarcodeScanning 7.0.0 / Android com.google.mlkit:barcode-scanning 17.3.0 | iOS scanning and Android fallback scanning | Camera image and device or diagnostic information described by the provider | Images are recognized on-device; see the Google Privacy Policy |
2. Components that transmit information to providers
| Service or SDK | Trigger | Information transmitted or processed | Purpose and policy |
|---|---|---|---|
Sentry (sentry_flutter 8.14.2 / Sentry HybridSDK 8.46.0) | App crash or error | Device model, system version, device identifier, error/crash logs, IP and other network information | Troubleshooting and stability analysis; Sentry Privacy Policy |
PostHog (posthog_flutter 5.0.0 / PostHog iOS 3.30.1) | App use that generates an analytics event | Device identifier (ulid/device SN), device and network information, feature events | Understand feature use and paths; session replay is off; PostHog Privacy Policy |
peergine P2P tunnel (pg_lib_tunnel, Android pgjnitunnel.jar / native iOS library) | You enable remote access through P2P or a relay | Device SN/identifier (SN, UDID), IP, port, and link-negotiation network data | Establish an overlay or relay path; relay addresses are p2p.t-firefly.net and us.p2prelay.t-firefly.net; no separate public privacy policy |
Sentry, PostHog, and peergine process information only when the related feature is enabled or an event occurs. Installing the app does not make us read private NAS files; whether file content is transmitted depends on the feature, your authorization, and the destination provider’s rules.
3. Sharing boundaries and your choices
- Third-party components process only the information needed for the functions listed here and not for unrelated independent commercial purposes.
- You can turn off notifications, product analytics, remote connections, or system permissions; the related feature may then be unavailable.
- Providers may change processing because of versions, regions, infrastructure, or policy updates. Their official notices then apply.
- For rights requests about a provider, review its public policy first. For StationHub accounts, devices, or app features, contact us at
service@spcnasos.com.
4. Related documents
How is this guide?