「毛豆仪表盘」（以下简称"本应用"）非常重视您的隐私。本政策说明我们在提供实时仪表、车辆蓝牙连接、行程记录、订阅和问题诊断等功能时如何收集、使用、存储和保护您的数据。
| 数据类型 | 用途 | 存储位置 |
|---|---|---|
| GPS 位置信息 | 计算实时速度、累计里程、记录行程起终点和轨迹采样、获取道路限速与地点名称 | 行程数据保存在本机；为获取地点名称，可能将起终点经纬度发送至 Apple 地理编码服务或我们的自建反查接口 |
| 蓝牙通信数据 | 读取并显示车辆速度、档位、里程、电量、导航状态等车辆数据，生成行程统计 | 主要在本机处理和保存；部分汇总统计可能用于订阅权益、功能分析和故障排查 |
| 蓝牙配对密钥 | 维持与车辆的加密通信 | iOS Keychain（本地加密存储） |
| 行程记录 | 展示历史行程、起终点、距离、均速、最高速度、驾驶事件和能耗等信息 | 保存在本机数据库；行程汇总指标可能作为分析事件上传，原始轨迹采样不用于广告追踪 |
| 设备与使用数据 | 统计功能使用情况、订阅状态、主题下载、连接状态和问题定位 | 通过 Firebase Analytics、友盟统计及我们的自建统计接口处理 |
| 崩溃日志和诊断数据 | 排查应用闪退、异常和兼容性问题 | 通过 Firebase Crashlytics 处理，可能包含设备型号、系统版本、应用版本、设备标识符及相关诊断上下文 |
| 用户主动提交的日志 | 仅在您手动触发应用内日志上传入口时，用于排查连接、行程记录或应用异常问题 | 本应用不会自动上传日志；您手动上传后，日志会发送至我们配置的日志接收接口。日志文件名可能包含车辆标识符，日志内容可能包含设备、车辆连接、位置或诊断上下文 |
| 订阅状态 | 管理付费功能的访问权限 | 通过 RevenueCat SDK 处理 |
| 车辆标识符 | 识别车辆连接状态、订阅权益状态、问题诊断和崩溃定位 | 保存在本机；在启用相关功能时可能随统计或诊断数据由 Firebase、友盟、RevenueCat 或我们的自建接口处理 |
| 运动传感器、媒体播放和相册权限数据 | 用于判断静止状态、在仪表盘显示当前播放音乐、保存分享图片或联系二维码 | 主要在本机处理；保存图片时由 iOS 相册服务处理 |
本应用使用 iOS 位置服务获取实时速度、海拔、道路限速和行程位置信息。开启行程记录功能时，本应用会在本机保存行程起终点、轨迹采样和驾驶事件对应的位置，用于历史行程展示、路线回看和统计计算。
为了将经纬度转换为可读地点名称，本应用可能调用 Apple 地理编码服务；当坐标位于中国区域时，也可能通过我们的自建反查接口请求地点名称。该请求通常包含经纬度，不包含您的姓名、手机号或车辆账号登录凭据。
您可以随时在 iPhone 的「设置 → 隐私与安全 → 定位服务」中关闭本应用的位置权限。关闭后，GPS 测速和限速提醒功能将不可用，但蓝牙车辆数据功能不受影响。
本应用通过蓝牙低功耗（BLE）与车辆通信，读取行驶数据。所有通信均经过 AES-256-GCM 加密，配对密钥存储在 iOS Keychain 中。
蓝牙连接需要您在车辆端主动授权。本应用仅读取用于仪表显示和行程统计的数据，不执行任何车辆控制操作（如解锁、启动等）。为统计功能稳定性和排查故障，车辆连接状态、授权结果、订阅状态、行程汇总指标等可能作为分析事件处理。
本应用可能请求运动传感器权限，用于判断设备是否静止并提升速度、驾驶事件判断的稳定性。传感器数据主要在本机实时处理，不用于识别您的身份。
本应用可能读取当前播放的媒体标题、艺术家、封面和播放状态，用于在仪表盘界面显示当前播放信息。这些媒体信息主要在本机显示，不用于广告追踪。
当您选择保存驾驶报告图片或联系二维码时，本应用会请求相册写入权限。除非您主动保存图片，本应用不会修改您的相册内容。
本应用集成了以下第三方 SDK：
| SDK | 提供方 | 用途 |
|---|---|---|
| Firebase Analytics | Google LLC | 应用使用统计、功能分析和事件分析 |
| Firebase Crashlytics | Google LLC | 崩溃统计、异常上报和诊断分析 |
| 友盟统计 | 友盟同欣（北京）科技有限公司 | 应用使用统计、功能分析和事件分析 |
| RevenueCat | RevenueCat, Inc. | 订阅管理与内购验证 |
上述 SDK 可能会处理设备标识符、应用版本、系统版本、设备型号、购买和订阅状态、崩溃日志、诊断信息及使用事件。具体处理方式请参阅各 SDK 提供方的隐私政策。
本应用不面向未满 18 周岁的未成年人。我们不会主动收集未成年人的个人信息。
我们可能会不时更新本隐私政策。重大变更将通过应用内通知告知您。继续使用本应用即表示您接受更新后的政策。
如您对本隐私政策有任何疑问，请通过应用内「联系开发者」功能与我们联系。
"Model Dash" (the "App") respects your privacy. This policy explains how we collect, use, store, and protect data when providing real-time dashboard, Bluetooth vehicle connection, trip history, subscription, and diagnostic features.
| Data Type | Purpose | Storage |
|---|---|---|
| GPS location information | Calculate real-time speed and distance, record trip start/end points and route samples, obtain speed limits and place names | Trip data is stored on your device. To obtain place names, start/end coordinates may be sent to Apple geocoding services or our own reverse-geocoding endpoint |
| Bluetooth communication data | Read and display vehicle speed, gear, mileage, battery level, navigation state, and other vehicle data, and generate trip statistics | Mainly processed and stored locally. Some aggregated metrics may be processed for subscription entitlement, feature analytics, and troubleshooting |
| Bluetooth pairing keys | Maintain encrypted communication with the vehicle | iOS Keychain (local encrypted storage) |
| Trip records | Display historical trips, start/end places, distance, average speed, max speed, driving events, and energy-related statistics | Stored in the local database. Aggregated trip metrics may be uploaded as analytics events. Raw route samples are not used for advertising tracking |
| Device and usage data | Measure feature usage, subscription state, theme downloads, connection state, and diagnose issues | Processed through Firebase Analytics, Umeng Analytics, and our own analytics endpoint |
| Crash logs and diagnostic data | Diagnose crashes, exceptions, and compatibility issues | Processed through Firebase Crashlytics and may include device model, OS version, app version, device identifiers, and related diagnostic context |
| Logs you voluntarily submit | Only when you manually trigger the in-app log upload entry, diagnose connection, trip recording, or app issues | The App does not upload logs automatically. After you manually upload them, logs are sent to our configured log receiving endpoint. Log file names may include vehicle identifiers, and log contents may include device, vehicle connection, location, or diagnostic context |
| Subscription status | Manage access to paid features | Processed through the RevenueCat SDK |
| Vehicle identifiers | Identify vehicle connection state, subscription access eligibility, troubleshooting, and crash diagnosis | Stored locally. When related features are used, they may be processed with analytics or diagnostic data by Firebase, Umeng, RevenueCat, or our own endpoints |
| Motion sensor, media playback, and photo library permission data | Detect stationary state, show currently playing music on the dashboard, and save share images or contact QR codes | Mainly processed locally. When saving images, the data is processed by iOS Photos services |
The App uses iOS Location Services to obtain real-time speed, altitude, road speed limits, and trip location information. When trip recording is enabled, the App stores trip start/end points, route samples, and driving-event locations locally for trip history, route review, and statistics.
To convert coordinates into readable place names, the App may call Apple geocoding services. For coordinates located in China, the App may also request place names through our own reverse-geocoding endpoint. These requests usually include coordinates but do not include your name, phone number, or vehicle account login credentials.
You may disable location permission for the App at any time in iPhone Settings > Privacy & Security > Location Services. After location permission is disabled, GPS speed measurement and speed limit alerts will be unavailable, while Bluetooth vehicle data features will not be affected.
The App communicates with the vehicle through Bluetooth Low Energy (BLE) to read driving data. All communication is encrypted with AES-256-GCM, and pairing keys are stored in the iOS Keychain.
Bluetooth connection requires authorization from the vehicle side. The App only reads data used for dashboard display and trip statistics, and does not perform any vehicle control actions, such as unlocking or starting the vehicle. To measure feature reliability and diagnose issues, vehicle connection state, authorization result, subscription state, and aggregated trip metrics may be processed as analytics events.
The App may request motion sensor permission to determine whether the device is stationary and improve the reliability of speed and driving-event detection. Sensor data is mainly processed locally in real time and is not used to identify you.
The App may read the currently playing media title, artist, artwork, and playback state to show now-playing information on the dashboard. This media information is mainly displayed locally and is not used for advertising tracking.
When you choose to save a driving report image or contact QR code, the App requests photo library write access. The App does not modify your photo library unless you actively save an image.
The App integrates the following third-party SDKs:
| SDK | Provider | Purpose |
|---|---|---|
| Firebase Analytics | Google LLC | App usage statistics, feature analytics, and event analytics |
| Firebase Crashlytics | Google LLC | Crash reporting, exception reporting, and diagnostic analysis |
| Umeng Analytics | Umeng Tongxin (Beijing) Technology Co., Ltd. | App usage statistics, feature analytics, and event analytics |
| RevenueCat | RevenueCat, Inc. | Subscription management and in-app purchase validation |
These SDKs may process device identifiers, app version, OS version, device model, purchase and subscription status, crash logs, diagnostic information, and usage events. Please refer to the privacy policies of the respective SDK providers for details.
The App is not intended for minors under the age of 18. We do not knowingly collect personal information from minors.
We may update this Privacy Policy from time to time. Material changes will be communicated through in-app notifications. Continued use of the App means you accept the updated policy.
If you have any questions about this Privacy Policy, please contact us through "Contact Developer" in the App.