Last Updated: August 15, 2026
Effective Date: August 15, 2026
Operator: Shenzhen Xingmotu Technology Co., Ltd. (深圳市星摩途科技有限公司) (hereinafter “ThinkMoto/we”)
Welcome to the 「MotoTrace」 APP under ThinkMoto. This document integrates the MotoTrace APP Privacy Policy and the SDK & Third-Party Library Usage Statement, fully describing required system permissions, third-party dependencies, personal information collection/use/storage/sharing rules, user data rights, and compliance terms.
1. Applicable entities: Shenzhen Xingmotu Technology Co., Ltd. (深圳市星摩途科技有限公司) and all its subsidiaries and affiliates;
2. Scope: All MotoTrace APP features, including account management, vehicle inspection, VCI diagnostic device connectivity, location maps, push notifications, online customer service, payments, diagnostic report export, app updates, etc.;
3. Not applicable: Third-party jump services, third-party ads, and external cooperative inspection services within the APP; data processing by third-party businesses is governed by their independent privacy policies;
4. Acceptance: Downloading, logging in, or using any APP feature means you have fully read, understood, and agreed to all terms of this privacy compliance document.
1. Collection principles: Strictly follow legality, legitimacy, necessity, and good faith; collect only information necessary for vehicle diagnosis, device connectivity, location push, and other business operations; do not collect redundant personal information unrelated to the service;
2. Use boundaries: All collected information is used only to ensure service operation, device security/risk control, online troubleshooting, and legal obligations; expanding to other uses requires a separate pop-up and your express consent—never without consent;
3. Storage rules: All user personal information is stored on servers in mainland China; retained only for the shortest period needed for business purposes; after account cancellation, cleared or anonymized per laws and regulations;
4. Security: Network transmission uses HTTPS/WSS encryption; local sensitive data is encrypted; tiered access control, real-time security monitoring, and regular audits; sensitive fields in online logs are masked;
5. User rights: You may query, correct, and delete personal business data at any time, freely withdraw granted system permissions, and apply to cancel your account;
6. Third-party control: All third-party SDKs come from official/open-source channels, are regularly updated for security fixes, fully disclose collection scope, and follow platform privacy compliance norms.
(1) Bluetooth-related Permissions (depends on flutter_blue_plus)
1. Android system permissions: BLUETOOTH, BLUETOOTH_ADMIN, BLUETOOTH_SCAN, BLUETOOTH_CONNECT, BLUETOOTH_ADVERTISE, ACCESS_FINE_LOCATION
2. iOS permission descriptions (Info.plist configuration text)
<key>NSBluetoothAlwaysUsageDescription</key>
<string>Bluetooth is required to connect to vehicle diagnostic devices</string>
<key>NSBluetoothPeripheralUsageDescription</key>
<string>Bluetooth is required to connect to vehicle diagnostic devices</string>
3. Use scenarios: Scan and pair VCI automotive diagnostic devices, rename Bluetooth devices, read diagnostic box IMEI/ICCID, sync device activation info to the server;
4. Location note: Android Bluetooth pairing mandatorily depends on location capability; location is enabled only temporarily during pairing and stopped immediately after; we do not continuously record or store your geographic location.
(2) Location and Map Permissions (geolocator, multi-map SDKs)
1. Android system permissions: ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, ACCESS_BACKGROUND_LOCATION
2. iOS permission descriptions
<key>NSLocationWhenInUseUsageDescription</key>
<string>Location access is needed to provide maps, geofencing, and trip track services</string>
<key>NSLocationAlwaysAndWhenInUseUsageDescription</key>
<string>Location access is needed for continuous positioning and geofence alerts</string>
<key>NSLocationAlwaysUsageDescription</key>
<string>Location access is needed for continuous positioning and geofence alerts</string>
3. Related SDKs: google_maps_flutter (overseas), amap_flutter_base_plus/flutter_map (domestic), geocoding, coordtransform
4. Use scenarios: Map display, vehicle geofence creation and entry/exit alerts, trip track recording, nearby riders, lat/long and address conversion;
5. Region logic: Domestic/overseas regions are distinguished by device SN; domestic defaults to Amap components; overseas loads Google Maps components.
(3) Camera, Photo Library, and Media Storage Permissions
1. Android system permissions: CAMERA, READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_VISUAL_USER_SELECTED, READ_EXTERNAL_STORAGE (Android 32 and below), WRITE_EXTERNAL_STORAGE (Android 32 and below)
2. iOS permission descriptions
<key>NSCameraUsageDescription</key>
<string>Camera access is needed to scan device QR codes and vehicle VIN codes</string>
<key>NSPhotoLibraryUsageDescription</key>
<string>Photo library access is needed to select images and videos for customer service feedback and chat</string>
<key>NSPhotoLibraryAddUsageDescription</key>
<string>Needed to save diagnostic report images and screenshots to the photo library</string>
3. Related SDKs: mobile_scanner, image_picker, wechat_assets_picker, video_player, video_thumbnail, file_picker
4. Scenario details:
① Camera: Scan VIN and OCR device activation codes; recognition runs fully on-device; original captured images are not uploaded; flashlight assists scanning in low light;
② Photos/files: Send images/videos in customer chat, upload fault feedback attachments, export PDF diagnostic reports locally, read local business resource files.
(4) Network Access Permissions
1. Android system permissions: INTERNET, ACCESS_NETWORK_STATE
2. iOS permissions: General network access
3. Related SDKs: dio, mqtt_client, geocoding, map SDKs, payment SDKs, push SDKs
4. Use scenarios: Business API interaction, real-time vehicle/device location reporting, map resource fetch, payment flows, push Token reporting, file upload/download, embedded H5 loading; all network channels use HTTPS/WSS encryption.
(5) Push Notification Permissions
1. Android system permissions: POST_NOTIFICATIONS, VIBRATE, RECEIVE_BOOT_COMPLETED
2. iOS permissions: System notification permission
3. Related SDKs: firebase_messaging (overseas FCM), jpush_flutter (domestic JPush), flutter_local_notifications
4. Use scenarios: Vehicle geofence entry/exit alerts, online customer messages, device status reminders; one push channel is enabled by SN region; APP language locale is uploaded with the push Token; the server sends localized notification copy.
(6) App Install and System App Query Permissions
Android system permissions: QUERY_ALL_PACKAGES, REQUEST_INSTALL_PACKAGES
Related SDKs: flutter_downloader, app_installer, open_file
Purposes: Background download of new APP packages, local APK install, open local diagnostic files; query installed apps for content-sharing jumps.
Category 1: No Personal Information Collection (basic tools / UI adapters)
flutter, cupertino_icons, flutter_screenutil, path_provider, permission_handler, url_launcher, bot_toast, package_info_plus, connectivity_plus, intl, provider, easy_refresh, extended_image, flutter_widget_from_html, card_swiper, flutter_datetime_picker_plus, google_api_availability, coordtransform, crypto, path, http_parser, lpinyin, transparent_image, ffi, flutter_localizations
Business purposes: Layout, screen adaptation, file paths, dynamic permissions, toasts, i18n, state management, image cache, coordinate conversion, crypto checks, and other low-level tools—do not collect user identity, location, device unique IDs, or similar personal information.
Category 2: SDKs That Collect/Store Personal Information
1. shared_preferences
Collected: Local cache of login state, user feature settings, system language preference, notification switches;
Purpose: Persist user config on device only.
2. dio
Collected: Account login credentials, vehicle diagnostic data, customer chat media/text, location coordinates, device-reported business data;
Purpose: Encrypted data exchange with backend business servers.
3. device_info_plus
Collected: Phone model, OS version, device hardware unique identifiers;
Purpose: Compatibility differentiation, online fault localization, version adaptation statistics.
4. mobile_scanner
Collected: Text after scan recognition (may include vehicle VIN, device serial numbers, etc.);
Purpose: VCI device activation and vehicle identification; recognition is local.
5. image_picker / wechat_assets_picker / file_picker / video_player
Collected: User album photos, local videos, custom documents;
Purpose: Customer fault feedback, chat media upload, diagnostic attachment reading.
6. flutter_blue_plus
Collected: Bluetooth device MAC, VCI device IMEI/ICCID, connection status;
Purpose: Pair diagnostic devices and sync activation info.
7. fluwx (WeChat SDK)
Collected: WeChat nickname, avatar, WeChat OpenID;
Purpose: WeChat quick login, content sharing, WeChat Pay.
8. tobias (Alipay SDK)
Collected: Payment order data, Alipay platform user identifiers (processing independently by Alipay SDK);
Purpose: In-APP Alipay payments.
9. geolocator / google_maps_flutter / amap_flutter_base_plus / flutter_map
Collected: Precise GPS lat/long, coarse network location, reverse-geocoded addresses;
Purpose: Maps, geofencing, trip tracks, nearby rider matching.
10. firebase_messaging / jpush_flutter
Collected: Device push Token, user account ID, APP language locale;
Purpose: Offline push and localized notification display.
11. mqtt_client
Collected: Real-time vehicle location coordinates, device IDs;
Purpose: Low-latency device status reporting (backend switchable on/off).
12. pdf
Collected: Vehicle inspection and fault data stored in diagnostic reports;
Purpose: Export PDF diagnostic reports locally to phone storage.
13. webview_flutter
Collected: Determined by the loaded third-party H5 page;
Purpose: Campaign pages, privacy agreements, partner business web pages.
14. logger
Collected: Runtime logs (including business debug data);
Control: In production, mask sensitive data in logs such as phone numbers, device serials, and location coordinates.
(1) Data Collected by Business Scenario
1. Device connectivity: Bluetooth MAC, VCI IMEI/ICCID;
2. Vehicle diagnosis: Vehicle VIN, fault detection data, full diagnostic reports;
3. Location services: GPS lat/long, reverse-geocoded addresses, trip tracks, geofence alert records;
4. Account login: Login credentials, WeChat/Alipay platform user identifiers;
5. Customer feedback: User-uploaded images, videos, local log files;
6. Push notifications: Device push Token, APP language;
7. Device statistics: Phone model, OS version.
(2) Lawful Use Scope
1. Core services: VCI Bluetooth connection, vehicle fault diagnosis, map location, geofence alerts, push, online payment, APP updates;
2. Product optimization & security: Online troubleshooting, feature iteration, device compatibility, abnormal behavior risk control;
3. Legal obligations: Provide necessary data upon lawful documents from judicial or regulatory authorities; protect public interest and lawful rights of users and third parties;
4. Supplement: Uses beyond the above require a separate pop-up and express consent; without consent, use will not be expanded.
(3) Data Storage Rules
1. Storage location: All user personal information is stored on servers in mainland China; without separate written consent, no personal data is transferred to overseas servers;
2. Retention periods:
① Account and bound diagnostic device data: Retained until the user actively cancels the account;
② Vehicle inspection records, location tracks, customer chat records: Users may delete individually; if not deleted, retained for the necessary business period;
③ After account cancellation: Only retain data for the minimum period required by law to handle potential disputes; destroy thoroughly after the period; not used for any commercial purpose during retention;
3. APP shutdown: If the APP ceases operation, all users will be notified 30 days in advance via APP pop-up and official website notice; within 15 days after shutdown, delete or anonymize all user personal information and permanently stop all collection.
(4) Sharing and Disclosure Rules
1. Personal information may be shared with third-party enterprises only after your separate, express authorization; third parties will be bound to strict data security duties;
2. When judicial or administrative regulators require data by lawful documents, necessary information will be provided per laws;
3. Without user express consent or legal compulsion, we never actively publish or disclose any of your personal information.
1. Access and correction: View device binding and historical vehicle inspection data on the APP “Me” page; apply for correction via official contacts if errors exist;
2. Deletion: Manually delete individual inspection/feedback records on “Me – Log Upload”; account cancellation clears all business-related data;
3. Permission withdrawal: In phone Settings – Apps – MotoTrace, turn off Bluetooth, location, camera, storage, notifications, etc. anytime; only related features fail; basic vehicle diagnosis remains available;
4. Account cancellation: Submit via customer service channels;
5. Inquiry and complaint: Feedback on privacy policy or data collection via website, customer phone, or dedicated email.
1. Bluetooth VCI vehicle diagnosis: Scan/pair devices, read onboard SIM info, sync activation data;
2. Dual-region maps: Amap domestically, Google Maps overseas; coordinate conversion, geofencing, tracks, nearby riders;
3. Dual-channel push: JPush domestically, FCM overseas; sync APP language for multilingual notification copy;
4. Online customer real-time chat: Dio API + MQTT long connection; images and video messages;
5. Dual-channel payments: WeChat quick login, WeChat Pay, Alipay;
6. File handling: Camera/album upload, local PDF diagnostic export, APP update package download/install;
7. Embedded web: Campaign pages, privacy agreements, partner H5.
1. Ordinary changes: Announced in-APP and on the official website for 7 days; effective automatically thereafter;
2. Material changes (collection scope, sharing rules, user rights, entity changes, etc.): Actively notify via APP pop-up, SMS, and email;
3. Acceptance: Continued use after changes take effect constitutes acceptance of the new Privacy Policy; if you disagree, stop using the APP and apply to cancel your account.
Official contacts
1. Official website: www.xthinkmoto.com (built-in online inquiry form)
2. Customer service Tel: +86 18002539865
3. Dedicated privacy email: service@thinkmotosys.com (please mark the subject “Privacy Policy Inquiry”)
4. Company address: 深圳市龙华区龙华街道景新社区梅龙大道999号壹成中心花园七区4栋B座5101
Response time
Within 15 business days after receiving privacy-related inquiries or complaints, we will provide a complete written reply; if unsatisfied, you may complain to the Longhua District Administration of Government Services and Data Management of Shenzhen.
Governing law
Formation, effectiveness, performance, interpretation, and all dispute resolution of this compliance document are governed by the laws and regulations of the People’s Republic of China (excluding conflict-of-law rules); if any single clause is held invalid or unenforceable, the remaining clauses remain in force; where multilingual versions conflict, the Chinese version prevails.