Privacy Policy
English / 中文Updated: October 16, 2026
Effective: October 16, 2026
The LiteLink app (also known as 轻连 and 跃然轻连) and related website are provided by Beijing Wentian Lanyue Technology Co., Ltd. (北京问天揽月科技有限公司, “we”). This policy explains how we process information when you sign in, browse and play content, manage compatible devices or view device conversations, and how to exercise your choices. Personal information does not include irreversibly anonymized information.
On first opening LiteLink, we prompt you to read this policy and the Terms of Service and offer two explicit choices: “Disagree” and “Agree and continue”. Choosing “Disagree” still lets you browse public content. That choice is stored only as a local notice decision, is not consent, and keeps error reporting off for that app session. Signing in, binding devices and related features request the corresponding terms and permissions. Baidu Maps is not initialized at app startup. After choosing “Disagree”, first opening a Baidu map separately explains the map service processing and asks for consent. General policy acceptance, system permissions and guardian viewing-permission confirmations for each device binding have their own scopes. Accepting this policy does not authorize every function, sensitive-information processing or international transfer.
1. Information and purposes
Device connection and management: We process scanned QR code contents, device names, models, identifiers, Bluetooth identifiers (such as supported Android MAC addresses or Apple UUIDs), connection status and necessary authentication information to identify devices, verify access and perform requested operations. Bluetooth or Nearby Devices permission enables discovery and connection. Some older Android versions associate Bluetooth scanning with location permission; this does not mean Bluetooth scanning is used to track your location.
Camera: The QR page explains the purpose first and requests camera access only when you tap Enable camera to scan, to recognize a device QR code. The purpose remains visible on that page during system authorization. The scan result is used to add the device. This feature does not provide photo uploads or photo sharing. Refusing camera access prevents QR scanning without affecting public content or Bluetooth Wi-Fi setup.
Android QR service: The scan page separately explains Google ML Kit and initializes it only after you choose Enable camera to scan. Images and QR contents are recognized on this device and are not sent to Google. Google processes device, app and scan diagnostics as described below. You can instead return to Bluetooth Wi-Fi setup.
Play microphone (optional): Using Light Core recording or voice interaction in Play requests microphone access for recording playback and voice features. Online voice interactions connect through the selected firmware to GizClaw services to process the required audio and connection state; the AI-service explanation below also applies. You may refuse or revoke microphone access in system settings. Recording-dependent onboarding or interaction may then be unavailable; ordinary content browsing and model viewing do not require microphone access.
Network setup: The device picker explains Bluetooth or Nearby Devices access and starts discovery only when you tap Search for nearby devices or Scan again. Android 11 and earlier also require location permission for Bluetooth discovery; this search finds setup devices without reading your phone's position. The purpose remains visible during system authorization. The Wi-Fi name you select and password you enter configure the device's network. Returned network status displays setup results. Device passwords, tokens and keys verify your authority to operate the device; keep these confidential.
Map sensor information: When you use Baidu Maps, its SDK reads orientation-sensor types and the available sensor list, and processes orientation values received through system sensor events to display the map compass and direction. Reads follow map operation and system sensor callbacks; processing includes system sensor API access and calculation and updates of map direction by the SDK. This is separate from phone location permission and is not used for personalized advertising. Provider identity and other map processing are described under Third-party services and components below.
Account sign-in and sessions (optional): Phone sign-in processes your phone number, SMS verification results, send times and information needed to prevent abuse. Apple sign-in processes your Apple account identifier, any email supplied by Apple and necessary verification information. We retain account identifiers, linked sign-in identities, sessions and access credentials for authentication, account management and security. SMS and verification services also process information needed for their respective functions. Public content and network setup that do not require an account remain available without sign-in.
Playback and content interactions: Browsing, searching and playback process content identifiers, language, progress, playback time and completion status to display content, resume playback and maintain listening history. Signed-in likes, content reports and report-status views also process like records, content references, the feedback you submit and necessary request information. Do not include children's identities, contact details or other personal information unrelated to your feedback.
Operational content: Announcements and promotions use shared public configuration. They are not targeted using personal profiles or personal information from third parties. LiteLink does not offer personalized advertising or targeted marketing pushes.
Account synchronization: Signing in automatically synchronizes local device cards and listening history with your account. Synchronization continues during sign-in, foreground and background transitions, playback changes and related page operations. Synced information includes device identifiers, names, icons, service addresses and credentials used to restore device access, together with content identifiers and playback progress. Device credentials are held in system secure storage on the phone; the server retains them under account access controls and provides them when you restore device access. Signing out clears the session; local device cards and listening history may remain for separate management.
Background and silent operation: In an already running app, background transitions trigger the account synchronization described above. Audio you started can continue using the media foreground service and save/sync progress. Find Device stops scheduled location requests outside the foreground and discards late results without adding location caches; requests already sent can still complete. Android map views follow Activity pause events. Map requests, enabled Sentry error reports and scan diagnostics may finish, queue or retry in the background or on a later run, with the scopes and purposes stated for each service. LiteLink has no continuous background phone tracking, marketing keep-alive or remote marketing push service.
Device conversations and recordings: Compatible devices using GizClaw cloud AI services process device identifiers, interaction audio, speech transcripts, character replies and conversation times for speech recognition, response generation, continued interactions and conversation history. Some entries include recordings for replay. Viewing saves or conversations and replaying recordings in LiteLink requests this information under device-management permissions. Recent conversation text may be cached for offline viewing. Information may be linked to the device user, including a child; it is not all anonymous or processed only in real time.
Long-term memory: Device services may extract explicitly supplied preferences, facts or conversational context into long-term memories and memory-change records for later interactions and updates. They are stored separately from original conversations and recordings and have different retention and deletion scopes. The conversation-history page is not a complete inventory of long-term memories.
Device contacts: Names, phone numbers and other supported fields you view or edit are used to manage the device's communication contacts and synchronized over supported connections. These are device contacts, not your phone's system address book. Only provide information you are authorized to manage.
Device location: Find Device retrieves device-reported coordinates, accuracy, address and update time from the associated service. The most recent location may be cached for display during network failures. Device location can reveal the whereabouts of its wearer or user and requires special protection. Only locate devices you own or are authorized to manage; inform their users and obtain necessary authorization. Location may be delayed or inaccurate.
Optional phone location: LiteLink requests location access while in use only after you choose Show my location in Find Device and confirm its purpose, to display your own position as a blue dot on supported maps. The Baidu version has no phone blue-dot entry. You can refuse and still view the device-reported location. LiteLink does not request Always location access or provide continuous background phone tracking. Location is sensitive information; permission is a separate system choice, not automatically granted by accepting this policy.
Local records and operation: The app stores device lists, preferences, listening history, necessary access credentials and location and conversation caches to reconnect, resume playback and restore the interface. Network requests may involve IP addresses and request results; local troubleshooting uses error and connection logs. Distributions with error reporting enabled send only OS names and versions, app versions, error types and code stacks, excluding account identities, device names, activity trails, conversation content and performance data. Identifiable logs and device information are not treated as anonymous merely because they are technical data.
2. Third-party services and components
2.1 Client third-party SDK inventory
Each entry identifies the SDK/component, developer or open-source provider, purpose, data, collection method, usage trigger, permissions and privacy rules. Versions refer to the locked dependencies; system components come with the OS. Map providers depend on platform, distribution and configuration, so not every distribution enables every listed map. SDKs use permissions granted to LiteLink rather than automatically gaining all permissions. System authorization, personal-information processing and international processing remain separate decisions.
Network services link to official privacy policies. Local open-source components without an independent data recipient link to their processing rules and official projects; a project page is not described as a separate privacy policy. Permissions describe LiteLink's actual configuration rather than unused library capabilities. Choosing external navigation passes the target device coordinates to the map service you open, whose subsequent processing follows its rules.
SDK name: 百度Android地图SDK（基础版） / Baidu Android Map SDK (Basic Edition)
Developer: 北京百度网讯科技有限公司 (Beijing Baidu Netcom Science Technology Co., Ltd.).
Package and versions: com.baidu.mapapi.map; flutter_baidu_mapapi_map/flutter_baidu_mapapi_base 3.9.6; Android Map/Search/Util support libraries 7.6.6.
Purpose: Map display, device-location markers and compass in Baidu-configured Android distributions.
Data: Viewport coordinates, device model/configuration, OS version, app name, network type/status, carrier/signal information, IP and map requests; Android ID for troubleshooting; directory paths/cache for map caching; orientation-sensor types, the available sensor list and direction values.
Collection and trigger: After map consent, opening a Baidu map uses system APIs, sensor callbacks and map requests. Android ID is read at SDK startup; device/network data follow map use and direction values update with callbacks. This version does not enable Baidu phone positioning or cycling/walking navigation. These purposes differ from LiteLink reading the target device's reported location.
Permissions: INTERNET and ACCESS_NETWORK_STATE. This distribution has no phone blue dot and requests no background phone location, phone-state or external-storage permissions for this map. Orientation-sensor reads have no separate system permission prompt.
SDK privacy policy: https://lbs.baidu.com/index.php?title=openprivacy
SDK name: Google Maps SDK for Android / Google Maps SDK for iOS
Developer: Google LLC; the Flutter integration is provided by the Flutter open-source project.
Versions: google_maps_flutter 2.6.1; Android integration 2.19.13 with native Maps SDK 20.0.0; iOS integration 2.5.2.
Purpose: Map display and location markers in Google-configured distributions.
Data: Map coordinates/requests, IP, device/OS metadata, app/SDK versions, SDK identifiers, map pan/zoom events and SDK crash information; authorized phone location when the blue dot is enabled.
Collection, trigger and permissions: Corresponding map/network APIs when the map opens; phone location only after Show my location and confirmation, using ACCESS_FINE_LOCATION on Android. Baidu distributions do not enable Google map display; packaged components do not enable every feature.
SDK privacy policy: https://policies.google.com/privacy
Official data disclosure: https://developers.google.com/maps/documentation/android-sdk/play-data-disclosure
SDK name: Apple Maps / MapKit
Developer: Apple Inc.; the apple_maps_flutter integration is provided by Luis Thein and open-source contributors.
Versions: MapKit comes with the Apple OS; apple_maps_flutter 1.4.0.
Purpose: Maps and location markers in Apple-map configurations.
Data: Viewport coordinates, map requests, network connection information and authorized phone location.
Collection, trigger and permissions: Opening the corresponding map loads its base map through system services. The optional blue dot uses location while in use only after your choice and confirmation, without requesting Always location.
SDK privacy policy: https://www.apple.com/legal/privacy/data/en/apple-maps/
Integration project: https://github.com/LuisThein/apple_maps_flutter
SDK name: mobile_scanner
Developer/provider: Julian Steenbakker and mobile_scanner open-source contributors.
Version: 7.4.0.
Purpose: Connect the camera and recognition engine for local device QR recognition.
Data: Live camera frames, recognition results and scan state; the maintainers are not independent recipients of images or QR contents. Android uses CameraX and Google ML Kit as listed below, including ML Kit diagnostics. Apple platforms use system AVFoundation/Vision for local recognition.
Collection, trigger and permissions: Enable camera to scan starts it and uses CAMERA on Android; closing scanning stops recognition. This entry does not import gallery images or request READ_MEDIA_IMAGES or all-files access.
Processing rules/project: https://github.com/juliansteenbakker/mobile_scanner
SDK name: Google ML Kit Barcode Scanning
Developer: Google LLC.
Package and versions: com.google.mlkit:barcode-scanning 17.3.0 through mobile_scanner; ML Kit common 18.11.0.
Purpose: On-device QR recognition and SDK diagnostics/usage analysis.
Data: Camera images and QR contents stay on-device and are not sent to Google. Diagnostics include manufacturer/model, OS, available ML hardware, package/app/SDK versions, installation-scoped identifiers, scan latency, image format/resolution, input/output sizes, initialization/detection/release events and error codes.
Collection, trigger and permissions: Enable camera to scan initializes the SDK and uses CAMERA. HTTPS diagnostics use INTERNET/ACCESS_NETWORK_STATE and may be scheduled or retried in the background. Closing scanning does not delete queued diagnostics. These diagnostics are not used for LiteLink personalized advertising.
SDK privacy policy: https://policies.google.com/privacy
SDK privacy/data disclosure: https://developers.google.com/ml-kit/terms ; https://developers.google.com/ml-kit/android-data-disclosure
SDK name: AndroidX CameraX
Developer/provider: Google LLC and Android Open Source Project contributors.
Versions: camera-lifecycle/camera-camera2 1.6.1 through mobile_scanner.
Purpose: Manage Android camera sessions and image frames for QR recognition.
Data: Local camera frames, configuration, lifecycle and image parameters needed for recognition. CameraX does not separately upload these frames to its maintainers.
Collection, trigger and permissions: Enable camera to scan followed by CAMERA authorization; frame processing ends when scanning/camera stops.
Processing rules/project: https://developer.android.com/media/camera/camerax
SDK name: Google DataTransport
Developer: Google LLC.
Package: com.google.android.datatransport, indirectly included by Google ML Kit.
Purpose: Queue, deliver and retry the scan diagnostics described above.
Data: The above ML Kit diagnostic payloads, queue and transport state; camera images and QR contents are not additional diagnostic uploads.
Collection, trigger and permissions: After scanning generates diagnostic events, system jobs/alarms and HTTPS use INTERNET/ACCESS_NETWORK_STATE. Queued records may send/retry in the background, after scanning closes or on later runs; system scheduling may also wake the process.
SDK privacy policy: https://policies.google.com/privacy
Diagnostic scope/project: https://developers.google.com/ml-kit/android-data-disclosure ; https://github.com/firebase/firebase-android-sdk
SDK name: Sentry SDK (sentry_flutter/sentry)
Developer: Functional Software, Inc. (Sentry).
Versions: 10.0.0-alpha.6; Android Sentry 8.56.0.
Purpose: Troubleshoot failures in distributions with error reporting enabled.
Data: OS name/version, app version, error type and stack trace. Reports filter account IDs, device names, device/installation identifiers, operation logs, network requests, chats and raw error input; the IP field is a fixed non-user address. Performance, session, screen-replay and unused shake-feedback collection are disabled. The receiving service still sees the connection's source IP.
Collection, trigger and permissions: Initialization follows general agreement in enabled distributions; errors/retries use INTERNET/ACCESS_NETWORK_STATE without requesting camera, microphone, location, phone-state or storage access for diagnostics. Location/retention depend on project configuration; the default project is in the US. International processing requires applicable notice, separate consent and safeguards; policy acceptance is not blanket authorization.
SDK privacy policy: https://sentry.io/privacy/
SDK name: flutter_blue_plus
Developer/provider: flutter_blue_plus open-source maintainers, including Charles Weinberger and contributors.
Versions: 1.36.8; Android implementation 7.0.4.
Purpose: Discover/connect compatible devices and write Wi-Fi setup data.
Data: Advertised names, Bluetooth identifiers, signal strength, service identifiers, connection state and setup data sent to the device; processed locally with the selected device, not separately sent to maintainers.
Collection, trigger and permissions: Search for nearby devices/Scan again uses system Bluetooth APIs. Android 12+ uses BLUETOOTH_SCAN/BLUETOOTH_CONNECT; Android 11 and earlier use BLUETOOTH/BLUETOOTH_ADMIN and ACCESS_FINE_LOCATION required for scanning, without reading phone coordinates here.
Processing rules/project: https://github.com/chipweinberger/flutter_blue_plus
SDK name: geolocator
Developer/provider: Baseflow and flutter-geolocator open-source contributors.
Versions: 13.0.4; Android implementation 4.6.2.
Purpose: Check/request location authorization for the optional phone blue dot on supported maps.
Data: Local location-service/permission state. LiteLink does not start a continuous location stream through this component, and it has no independent location-upload destination.
Collection, trigger and permissions: Only Show my location followed by confirmation requests location while in use, ACCESS_FINE_LOCATION on Android. Baidu distributions have no such entry.
Processing rules/project: https://github.com/Baseflow/flutter-geolocator
SDK name: Cronet / cronet_http
Developer/provider: Google LLC, Chromium and Dart open-source contributors.
Versions: cronet_http 1.9.0; embedded Android Cronet 143.7445.0.
Purpose: Android HTTP for content, accounts, synchronization and device control.
Data: Destination addresses, headers, necessary credentials, request/response data, connection state, network type and available network-environment information. The corresponding feature's service receives requests and sees the source IP; business content is not separately submitted to the component's maintainers.
Collection, trigger and permissions: Online features and the background sync/playback described here use INTERNET/ACCESS_NETWORK_STATE. LiteLink does not enable library Wi-Fi-switch testing or system-account authentication features.
Processing rules/project: https://github.com/dart-lang/http/tree/master/pkgs/cronet_http
SDK name: cupertino_http
Developer/provider: Dart open-source contributors; the underlying URLSession networking is supplied by Apple Inc. with the OS.
Version: 2.4.0.
Purpose: Apple-platform HTTP for content, accounts, synchronization and devices.
Data: Destination addresses, headers, necessary credentials, requests/responses and connection information. The selected feature's service receives data and sees the source IP; maintainers do not receive a separate upload.
Collection, trigger and permissions: Online features and described background sync/playback use system networking, without adding camera, location, contacts or external-storage permissions.
Processing rules/project: https://github.com/dart-lang/http/tree/master/pkgs/cupertino_http
SDK name: http (Dart HTTP client)
Developer/provider: Dart open-source contributors.
Version: 1.6.0.
Purpose: A common HTTP interface for the above transports and other supported platforms.
Data: Feature URLs, headers, necessary credentials and request/response data, received by the destination service rather than this project's maintainers.
Collection, trigger and permissions: Platform networking for online features, including INTERNET on Android, without independent location, camera or storage permission requests.
Processing rules/project: https://github.com/dart-lang/http/tree/master/pkgs/http
SDK name: webview_flutter (system web component)
Developer/provider: Flutter open-source project, the Android system WebView provider and Apple Inc.'s WKWebView.
Versions: webview_flutter 4.14.1; webview_flutter_android 4.14.1; webview_flutter_wkwebview 3.27.0.
Purpose: Sign-in/verification, support and Play web pages.
Data: Page addresses, necessary sessions, web storage and interactions; page services receive online requests. Authorized Play recording is supplied only to the current supported page and corresponding voice service. Web third-party components are listed in section 2.4.
Collection, trigger and permissions: Online pages use INTERNET. A Play recording request without existing authorization first explains its purpose and requests RECORD_AUDIO only after Allow. Ordinary web display does not need microphone access.
Processing rules/project: https://github.com/flutter/packages/tree/main/packages/webview_flutter
SDK name: mpv_audio_kit
Developer/provider: Alessandro Di Ronza and open-source contributors.
Version: 0.4.5.
Purpose: Integrate audio playback and system media controls.
Data: Selected audio addresses, media, titles, playback state/progress passed to local mpv decoding and system media sessions. Online audio requests its content service rather than a separate upload to plugin maintainers.
Collection, trigger and permissions: Playback you start uses INTERNET for online content and FOREGROUND_SERVICE/FOREGROUND_SERVICE_MEDIA_PLAYBACK. POST_NOTIFICATIONS concerns media notifications whose presentation depends on OS/settings. Audio output does not require RECORD_AUDIO.
Processing rules/project: https://github.com/ales-drnz/mpv_audio_kit
SDK name: mpv
Developer/provider: mpv open-source contributors.
Version: 0.41.0 through mpv_audio_kit.
Purpose: Local audio decoding and playback.
Data: Selected media addresses, audio bytes, decoding state and playback progress. Online media accesses the corresponding content address rather than uploading to mpv maintainers.
Collection, trigger and permissions: Your playback/control actions read media and output sound; online playback uses INTERNET and audio output does not request recording permission.
Processing rules/project: https://mpv.io/ ; https://github.com/mpv-player/mpv
SDK name: AndroidX Media3
Developer/provider: Google LLC and Android Open Source Project contributors.
Versions: media3-session/media3-common 1.10.1 through mpv_audio_kit.
Purpose: Android background audio, notifications, headset and lock-screen media-session controls.
Data: Media title, playback state/progress and control commands exchanged locally with system media interfaces, without separate listening-history uploads to maintainers.
Collection, trigger and permissions: User-started playback uses FOREGROUND_SERVICE/FOREGROUND_SERVICE_MEDIA_PLAYBACK; POST_NOTIFICATIONS concerns media notifications, not marketing pushes.
Processing rules/project: https://developer.android.com/media/media3
SDK name: flutter_pcm_sound
Developer/provider: Charles Weinberger and flutter_pcm_sound open-source contributors.
Version: 3.3.3.
Purpose: Interface sound effects and local PCM audio output.
Data: PCM audio bytes and output state, processed locally without separate transmission to maintainers.
Collection, trigger and permissions: Corresponding effects/playback use system audio output without requesting microphone access for output.
Processing rules/project: https://github.com/chipweinberger/flutter_pcm_sound
SDK name: Rive Flutter Runtime (rive/rive_native)
Developer/provider: Rive, Inc. and Rive open-source contributors.
Versions: rive 0.14.11; rive_native 0.1.11.
Purpose: Decode/display interactive animations and embedded audio locally.
Data: Loaded animations, embedded images/fonts/audio, playback progress and interaction state. Local rendering does not separately upload accounts, devices or listening history to Rive.
Collection, trigger and permissions: Opening/using animations processes verified resources. LiteLink networking downloads content from the corresponding service; this animation entry does not automatically fetch unverified Rive CDN assets or add system permissions.
Processing rules/project: https://github.com/rive-app/rive-flutter ; https://github.com/rive-app/rive-native
SDK name: package_info_plus
Developer/provider: Flutter Community Plus Plugins open-source contributors.
Version: 9.0.1, indirectly included by error reporting.
Purpose: Read this app's metadata for diagnostic version information.
Data: This app's name, package, version/build, installation/update times and source. The reporting SDK fills missing version parameters; normal builds already provide them. There is no independent upload destination; diagnostic uploads retain the Sentry filtering scope above.
Collection, trigger and permissions: System queries when this app's metadata is needed, without installation, all-packages or other dangerous permissions. Installation-source queries do not install software.
Processing rules/project: https://github.com/fluttercommunity/plus_plugins/tree/main/packages/package_info_plus
SDK name: shared_preferences
Developer/provider: Flutter open-source contributors.
Version: 2.5.5.
Purpose: Store local display preferences, agreement decisions and settings.
Data: Corresponding preference keys/values in private app storage, without separate transmission to maintainers.
Collection, trigger and permissions: Saving/reading/deleting settings uses system preferences without gallery, external-storage or all-files permissions.
Processing rules/project: https://github.com/flutter/packages/tree/main/packages/shared_preferences
SDK name: flutter_secure_storage
Developer/provider: German Saprykin (mogol) and open-source contributors.
Version: 9.2.4.
Purpose: Protect account sessions and device-access credentials in secure system storage.
Data: Account tokens, device credentials and storage keys read/written in local encrypted/secure storage without separate transmission to maintainers. LiteLink account synchronization is described in section 1.
Collection, trigger and permissions: Sign-in, device access, credential restoration/deletion use system secure storage without external-storage permissions.
Processing rules/project: https://github.com/mogol/flutter_secure_storage
SDK name: path_provider
Developer/provider: Flutter open-source contributors.
Version: 2.1.6.
Purpose: Locate private database, cache and temporary app directories.
Data: App directory paths returned by the OS, without separate path/file-content uploads to maintainers.
Collection, trigger and permissions: Related storage/cache operations query local directories; this app's private-directory use does not request gallery, external-storage or all-files access.
Processing rules/project: https://github.com/flutter/packages/tree/main/packages/path_provider
SDK name: Drift (drift/drift_flutter)
Developer/provider: Simon Binder and Drift open-source contributors.
Versions: drift 2.35.0; drift_flutter 0.3.1.
Purpose: Manage local device cards, listening history and related cache databases.
Data: The device cards, progress and database records described here, read/written in private app directories without separate transmission to maintainers. LiteLink account synchronization is a separate function.
Collection, trigger and permissions: Corresponding record saves, queries, migrations/deletions use local databases without external-storage or all-files permissions.
Processing rules/project: https://github.com/simolus3/drift
SDK name: SQLite / sqlite3
Developer/provider: SQLite developers; Dart integration by Simon Binder and sqlite3.dart open-source contributors.
Version: sqlite3 Dart integration 3.5.2.
Purpose: Store/query the above local databases.
Data: Related database files, query parameters and results in private app directories, without an independent upload destination.
Collection, trigger and permissions: Database reads/writes without external-storage or all-files permissions.
Processing rules/project: https://sqlite.org/ ; https://github.com/simolus3/sqlite3.dart
SDK name: share_plus
Developer/provider: Flutter Community Plus Plugins open-source contributors.
Version: 12.0.2.
Purpose: Pass selected QR codes, images or text to the system share interface.
Data: Selected content and necessary temporary files, delivered only to the recipient app you choose rather than separately uploaded to maintainers.
Collection, trigger and permissions: Your Share choice uses system sharing and temporary grants for selected files, without reading the whole gallery/all external files. Recipient processing follows its rules.
Processing rules/project: https://github.com/fluttercommunity/plus_plugins/tree/main/packages/share_plus
SDK name: pdf (Dart PDF)
Developer/provider: David PHAM-VAN (DavBfr) and dart_pdf open-source contributors.
Version: 3.13.0.
Purpose: Generate printable PDFs of selected picture books/articles locally.
Data: Selected text, illustrations, layout and PDF bytes, processed locally without separate upload to maintainers.
Collection, trigger and permissions: Your Print choice; LiteLink downloads illustrations from its content service and uses system fonts for text, without gallery or all-files access for PDF generation.
Processing rules/project: https://github.com/DavBfr/dart_pdf/tree/master/pdf
SDK name: printing
Developer/provider: David PHAM-VAN (DavBfr) and dart_pdf open-source contributors.
Version: 5.15.0.
Purpose: Pass the selected PDF to the system print interface.
Data: Selected document, print name and paper settings supplied to the local OS and selected print service, without separate upload to maintainers.
Collection, trigger and permissions: Your Print choice uses system printing and temporary access to selected files, without reading the whole gallery/all files. The print service's subsequent processing follows its rules.
Processing rules/project: https://github.com/DavBfr/dart_pdf/tree/master/printing
SDK name: url_launcher
Developer/provider: Flutter open-source contributors.
Version: 6.3.2.
Purpose: Open external pages, support or map navigation you choose.
Data: Selected links/parameters, including target device coordinates for navigation, passed to the selected browser/app without separate transmission to maintainers.
Collection, trigger and permissions: Your external-link/navigation choice invokes the OS without requesting phone contacts, SMS-reading, phone-state or location permissions for this handoff. Recipient services follow their rules.
Processing rules/project: https://github.com/flutter/packages/tree/main/packages/url_launcher
SDK name: sign_in_with_apple (Apple sign-in integration)
Developer/provider: ABOUT YOU and sign_in_with_apple open-source contributors; identity service by Apple Inc.
Version: 8.2.0.
Purpose: Verify the Apple identity you choose to sign in with.
Data: Authorized Apple account identifier, email if supplied and verification credentials exchanged between the system authorization page, LiteLink and Apple sign-in; no separate uploads to plugin maintainers.
Collection, trigger and permissions: Your Apple sign-in choice and authorization on Apple's page, without reading phone contacts, SMS or phone state.
Service privacy policy: https://www.apple.com/legal/privacy/
Integration processing rules/project: https://github.com/aboutyou/dart_packages/tree/master/packages/sign_in_with_apple
Other local foundations: flutter_riverpod 3.4.3 (Remi Rousselet/Riverpod contributors, state management), go_router 14.8.1 (Flutter project, routing), intl 0.20.3 (Dart project, language/date formatting), flutter_svg 2.3.0 (Flutter/Dan Field and contributors, SVG) and crypto 3.0.7 (Dart project, checksums/cryptography) process corresponding state, text, graphics or verification inputs locally without independent collection/uploads to maintainers or new system permissions. Processing rules/projects: https://github.com/rrousselGit/riverpod ; https://github.com/flutter/packages/tree/main/packages/go_router ; https://github.com/dart-lang/i18n/tree/main/pkgs/intl ; https://github.com/flutter/packages/tree/main/third_party/packages/flutter_svg ; https://github.com/dart-lang/crypto
LiteLink's own device-interface component gizclaw_control 0.23.2 sends necessary device identifiers, access credentials and control commands to the selected device service. Its processing is described in sections 1 and 2.3, rather than a separate disclosure to third-party SDK maintainers.
2.2 Android permissions and purposes
CAMERA: Requested only after Enable camera to scan for device QR recognition. Refusing affects scanning, not public content or Bluetooth Wi-Fi setup.
RECORD_AUDIO: Requested for Play recording/voice use after the purpose and an explicit Allow choice. Refusing affects that recording/voice feature.
BLUETOOTH_SCAN/BLUETOOTH_CONNECT (legacy BLUETOOTH/BLUETOOTH_ADMIN): User-initiated device discovery, connection and network setup.
ACCESS_FINE_LOCATION while in use: Required for Android 11-and-earlier Bluetooth scanning. Supported phone-blue-dot maps use it only after an explicit choice and confirmation. Baidu distributions offer no phone blue dot and request no background phone-location permission.
POST_NOTIFICATIONS/FOREGROUND_SERVICE/FOREGROUND_SERVICE_MEDIA_PLAYBACK: Audio you start, playback notifications and background media controls, not marketing pushes.
INTERNET/ACCESS_NETWORK_STATE: Selected online content, sign-in, device services, sync and enabled third-party service requests. These are normal manifest permissions without individual runtime prompts.
Orientation sensors: Baidu Maps processes the direction data described above. This access is not one of the location/camera runtime permissions and is still disclosed for its specific purpose and scope.
This Android manifest does not declare background location, contacts, SMS, calendar, phone state, system accounts, all-packages queries, installing other apps, external-storage read/write, gallery-reading or all-files management permissions. These are not permissions requested for current LiteLink features. Generic API references found by static scanning do not mean the app requested the associated permission and do not replace verification of actual data processing. Manage revocable permissions in system settings; refusal affects only dependent functions.
2.3 Accounts, cloud and other third-party services
The following account, SMS, verification and device-cloud services process data for the features you select. Not every service is a native SDK embedded in the app, and using it does not grant unrelated phone permissions.
Baidu account sign-in and Netdisk (optional, China account region): When you choose Baidu sign-in or link your Baidu account, Baidu shows the requested authorization. LiteLink stores the Baidu account identifier, display name, and encrypted OAuth credentials on its server to verify sign-in and access authorized files when you use a Netdisk feature. Signing in with a previously linked Baidu account returns to the same LiteLink account; a first sign-in with an unlinked Baidu account creates a new LiteLink account. The app saves the last visited folder and recently opened files locally per LiteLink account. Playing a file saves its name, stable redemption address, and progress in listening history, which syncs with your account when signed in. Complete audio downloads may be cached on this device and cleared in Settings. Audio is downloaded directly from Baidu Netdisk by the phone or device. You may unlink Baidu in Account to delete its stored credentials. If Baidu is your only sign-in method, first link another method. You may also revoke authorization in your Baidu account. Privacy policy: https://pan.baidu.com/disk/privacy
SMS and verification services: Mainland phone sign-in uses Volcengine SMS to send verification codes; other enabled phone services may use Twilio. Entry points with Alibaba Cloud human verification enabled also process verification tickets and necessary network, device and verification-interaction information to prevent automated abuse. Providers depend on the selected account region, entry point and enabled configuration.
Device AI services and model providers: GizClaw is the cloud service system used by compatible devices. Depending on the selected function and model configuration, necessary audio, text and context are processed by the actual model or speech provider. Current mainland services use Volcengine / Doubao speech recognition, real-time interaction or model capabilities, DeepSeek text generation and memory extraction, and Alibaba Cloud Qwen / DashScope text embeddings and model capabilities. A self-hosted memory service may still call these model APIs. Processing serves the respective interaction and memory functions. Model training, human quality review or other uses outside the disclosed scope require additional notice and any consent required by law.
DeepSeek privacy information: https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html
Alibaba Cloud Model Studio privacy information: https://help.aliyun.com/zh/model-studio/privacy-notice
Volcengine privacy information: https://www.volcengine.com/docs/6256/64902
Remote device services and infrastructure providers process device identifiers, authentication information, operation requests and responses as needed to provide the requested functions. We require processors acting on our behalf to use necessary information for agreed purposes with appropriate protections. We do not sell personal information or arbitrarily provide it to others outside your authorization, necessary service delivery or lawful requirements.
2.4 Third-party components in the website and embedded pages
Website device space, support and Play pages enable the following components for their corresponding functions. Loading a web component does not grant all app system permissions. Manage web storage in your browser; recording requests in app web pages still follow the Play authorization described above.
SDK name: Baidu Maps JavaScript API
Developer: 北京百度网讯科技有限公司 (Beijing Baidu Netcom Science Technology Co., Ltd.).
Version: JavaScript API 4.0, a different integration from the Android Basic Edition above.
Purpose: Maps, location markers and coordinate conversion in website device-location dialogs.
Data: Viewport/marker coordinates, map/conversion requests, IP and browser-provided device, OS and network information.
Collection and trigger: Opening a device-location dialog with coordinates and an allowed map configuration loads Baidu's API and map requests in the browser, without requesting phone location, camera or microphone access here.
SDK privacy policy: https://lbs.baidu.com/index.php?title=openprivacy
SDK name: Leaflet
Developer/provider: Vladimir Agafonkin and Leaflet open-source contributors.
Version: 1.9.4.
Purpose: Website global fallback maps and device-location markers.
Data: Viewport, marker coordinates and interaction state processed locally in the browser without independent uploads to Leaflet maintainers. Tiles come from the OpenStreetMap service below.
Collection and trigger: Using the global fallback base map, without a separate phone-location request.
Processing rules/project: https://leafletjs.com/ ; https://github.com/Leaflet/Leaflet
Map service name: OpenStreetMap standard map tiles
Provider: OpenStreetMap Foundation.
Purpose: Base tiles for website global fallback maps.
Data: Tile coordinates/zoom, IP, browser/device type, OS, referring page and access time; the requested area may relate to a device's location.
Collection and trigger: Browsers request tile.openstreetmap.org when the fallback map is used; the service receives those requests without requesting phone location.
Service privacy policy: https://osmfoundation.org/wiki/Privacy_Policy
SDK name: Rive Web Runtime (@rive-app/webgl2)
Developer/provider: Rive, Inc. and Rive open-source contributors.
Version: 2.40.1.
Purpose: Animations on the website and related web pages.
Data: Loaded animations, embedded assets and playback/interaction state rendered locally in the browser without separate account/device-record uploads to Rive. Corresponding content services handle resource downloads.
Collection and trigger: Opening/using animations without additional camera, microphone or phone-location authorization.
Processing rules/project: https://github.com/rive-app/rive-wasm
SDK name: WeChat JS-SDK
Developer/provider: 深圳市腾讯计算机系统有限公司 (Shenzhen Tencent Computer Systems Company Limited, WeChat).
Version: 1.6.0.
Purpose: Navigate from the shared support page within a WeChat Mini Program to its Mini Program support page.
Data: Mini Program environment, destination page address and navigation results exchanged between the page and WeChat host. This entry does not submit account signatures/device credentials or enable contacts, location or camera interfaces.
Collection and trigger: Clicking support in the Mini Program host loads/calls miniProgram APIs; ordinary app support pages do not enable this Mini Program navigation.
SDK privacy policy: https://weixin.qq.com/cgi-bin/readtemplate?lang=zh_CN&t=weixin_agreement&s=privacy
Official SDK source: https://res.wx.qq.com/open/js/jweixin-1.6.0.js
SDK name: Alibaba Cloud CAPTCHA 2.0 Web component (AliyunCaptcha.js)
Developer/provider: 阿里云计算有限公司 (Alibaba Cloud Computing Co., Ltd.).
Purpose: Prevent automated abuse and SMS flooding in enabled web sign-in flows.
Data: IP, browser/device environment, verification-scene identifiers, device verification tokens, click/slide interactions, verification parameters and results.
Collection and trigger: Entering a sign-in function with configured CAPTCHA loads it as configured. The browser verifies with the CAPTCHA service and LiteLink's server checks the receipt. Networking does not grant app contacts, camera, recording or phone-location permissions.
Service privacy policy: https://terms.aliyun.com/legal-agreement/terms/suit_bu1_ali_cloud/suit_bu1_ali_cloud202107091605_49213.html
Official integration documentation: https://help.aliyun.com/zh/captcha/captcha2-0/user-guide/server-access
Local web foundations: React/react-dom 19.3.0 (Meta Platforms, Inc. and React contributors), Radix UI (WorkOS and Radix contributors), cmdk 1.1.1 (Paco Coursey and contributors) and related style utilities render pages and controls. Page content/UI state stays local to these components, with no independent upload to maintainers or additional system permissions. Processing rules/projects: https://github.com/facebook/react ; https://github.com/radix-ui/primitives ; https://github.com/pacocoursey/cmdk
3. Storage and protection
Settings, caches and credentials are stored in app storage or system secure storage on your phone. Device configuration and contacts may also be stored on the device and connected services. Account and synced data are retained as needed for their respective functions; records can be deleted or the account closed. Security and operation logs are managed separately according to their purposes and legal requirements.
Conversation text, replay recordings and associated interaction-history logs in the current mainland GizClaw service are retained for 30 days from their cloud write time and cleaned according to server and object-storage rules. Conversation-text caches on the phone are used for at most 30 days; expired cache files are removed on subsequent reads. These rules do not mean save metadata, long-term memories, memory-change records, account data or security logs all expire after 30 days.
Save metadata supports continued interactions and save management. Long-term memories and their change records support later interactions and updates and remain for the period necessary for those purposes; they currently do not expire with the 30-day conversation history. Delete a save or use the contact channel below to request access, correction or deletion of long-term memories and other information, identifying the device and requested scope.
Deleting a save submits a background cleanup request for that save and its associated conversations and recordings. It does not delete every device-level shared memory, local cache or server copy. Removing a device card, signing out and uninstalling the app also have different effects and do not delete all device information. Information that must lawfully be retained should have restricted uses and be handled according to the applicable retention period.
Maps and remote services you connect to may operate in different countries or regions; processing locations depend on the selected service and deployment. Where additional notice, separate consent or international transfer safeguards are required, we will follow applicable requirements. General acceptance of this policy is not blanket authorization for every international transfer.
We use appropriate access controls, credential protection and security procedures to reduce loss, misuse and unauthorized access. No network or device system is completely secure. We will investigate incidents, take remedial steps and provide legally required notices.
4. Your choices and rights
Manage Bluetooth, camera, microphone and location permissions in your phone's settings. Refusing or withdrawing a permission affects the functions that depend on it, without invalidating earlier lawful processing. Manage device cards and supported device contacts in the app. Both this policy and the Terms remain available in Settings. Open Agreements & Consent from About in the sidebar to see each scope and its most recent agreement time. Open an item to view its version, scope and related terms, and to withdraw that agreement individually. The original agreement time is kept locally with the withdrawal status and time; other agreement records are unaffected. Withdrawing the general agreement stops error reporting and shows the notice on the next app launch. Sign-in, device-record viewing and map-service agreements are requested again at the corresponding next sign-in or feature use. Earlier agreements without a saved time are not assigned a new timestamp. All these records stay on the phone; they are not uploaded or synchronized with your account. Withdrawal does not delete your account, unbind devices or delete device data. System permissions remain separately managed in system settings.
Manage linked sign-in methods and close your account in Account, or delete listening-history entries, supported contacts or saves on their respective pages. Closing a LiteLink account deletes that account's identities, sessions, synced device cards, listening history, likes and related data from the LiteLink server; local device cards and listening history may remain. Account closure does not automatically reset hardware or erase all GizClaw device conversations, long-term memories or other device information. Content reports may remain for feedback handling or legal obligations and should be managed within their necessary scope and retention period.
To request access, copies, correction, deletion, withdrawal of consent or help with an unavailable operation, email legal@haivivi.com and identify LiteLink, the relevant device and requested information. We may verify identity, guardianship or device-management authority before disclosing or deleting data. Requests covering cloud conversations, recordings, long-term memories, memory-change records, local caches or backups should identify the required scope; processing should cover the relevant storage locations and explain any lawful basis and period for necessary retention.
We generally reply within fifteen working days and handle requests within applicable legal deadlines, explaining any need for additional verification or time. You may also contact the competent supervisory authority. Additional rights provided by applicable law remain available.
5. Minors and guardian viewing permissions
Before each binding of a device used by a child, confirm that you are the child's parent or other lawful guardian and have authority to view, replay and manage that device's conversations through LiteLink. Explain the information you can view to the child, respect their privacy and rights, and protect device credentials and conversation information.
This confirmation covers a guardian's access to and management of children's records through the app. It is not blanket permission for a child to use hardware and does not replace notice and consent required for hardware or cloud collection of audio, transcription, response generation, memory storage or other processing. Before processing information about children under fourteen, the guardian should receive clear notice of information types, purposes, processors, storage location and retention, refusal consequences and ways to exercise rights, and provide the required consent. Changes that require renewed consent must be separately notified and authorized.
If you do not confirm the app's viewing permission, do not access the child's conversations through the app. Network setup or public content that does not depend on this information can be used separately. System permissions, guardian viewing permissions and other sensitive-information processing have their own scopes; accepting this policy does not authorize them all.
Guardians may use the functions and contact channels above to request access, copies, correction or deletion of children's information or withdraw relevant consent. Requests are verified and handled within their respective scope. Do not use location features for unauthorized surveillance of another device user; contact us if children's information has been processed without required consent.
6. Changes
We update this policy as functions and processing change and identify the date. Where material changes require renewed consent under applicable law, we will provide additional notice and obtain the required consent. Updated documents remain available in Settings.
7. Contact
Beijing Wentian Lanyue Technology Co., Ltd. (北京问天揽月科技有限公司)
Email: legal@haivivi.com
Address: Room 1306, Floor 13, Building 1, No. 186 Beiyuan Road, Chaoyang District, Beijing, China.