本《隐私政策》适用于 TelogFSD(下称「本 App」或「TelogFSD」)在 Apple App Store 分发的客户端及相关必要后台服务。
本 App 的产品运营者与个人信息处理者为温岭市新河壹嘉软件开发工作室(个体工商户)(非特斯拉、非 Apple)。
本 App 通过 Apple Developer Program(个人会员资格)上架 App Store;该个人开发者账户持有人与运营者(经营者)为同一自然人。运营者依法由经营者承担责任;该安排不改变运营主体与个人信息处理者身份,亦不减损该自然人作为个人开发者依法享有的合法权益。
本 App 面向中国大陆特斯拉车主设计与合规落地;即使同步上架海外 App Store,个人信息处理仍以中华人民共和国法律(含《个人信息保护法》)及本政策为准(法律另有强制规定的除外)。
请在使用前仔细阅读;同意、登录或继续使用即表示您已理解本政策。本政策与《用户协议》《最终用户许可协议(EULA)》共同构成您与运营者之间的约定。
com.jchen.TelogFSD本政策不约束特斯拉、Apple、Google 等第三方自行收集的信息;请另行查阅其隐私政策。
本 App 在特斯拉中国开发者平台(developer.tesla.cn)及/或特斯拉全球开发者平台(developer.tesla.com)注册为第三方应用,具备 Fleet API 接入资质。车主授权后,我们仅通过特斯拉官方开发者接口取得车辆相关数据。中国区车辆以中国开发者应用与 auth.tesla.cn 流程为准;海外车辆以对应区域开发者应用与官方认证页为准。
| 环节 | 说明 | 是否经 TelogFSD 业务服务器中转车辆遥测 |
|---|---|---|
| 开发者注册 | 运营者在特斯拉开发者平台注册 TelogFSD 第三方应用,取得 Fleet API 资质与 client_id(中国与海外为独立应用) |
— |
| 车主授权 | 您被引导至特斯拉官方认证页(如 auth.tesla.cn / auth.tesla.com)登录,并勾选 OAuth 授权范围 |
否 |
| Token 换票 | 授权码经 TelogFSD 专用 HTTPS 后端与特斯拉官方 token 端点交换 access / refresh token;client_secret 仅存于服务端,不含于 App 安装包;App 不长期明文保存 Tesla 令牌 |
仅令牌交换,不含车辆遥测内容 |
| Fleet API 元数据 | TelogFSD 后端代您调用特斯拉 Fleet API,获取车辆列表、状态等元数据(用于账户绑定与展示) | 否(非持续遥测流) |
| Fleet Telemetry | 在您完成 Virtual Key 配对并配置 Fleet Telemetry 后,车辆官方计数与行程等数据经特斯拉 Fleet Telemetry 推送至 TelogFSD 专用接收端,加密存储后供仪表盘、趋势、行程等功能使用 | 是(Live 功能所必需) |
| 派生分析 | 智驾占比、趋势、评分等 TelogFSD 派生指标在后端或 App 展示层计算,并标注为派生数据 | 派生结果可存储于 TelogFSD 后端 |
| 本机缓存 | 语言、区域、选中车辆、同意记录等偏好保存在设备安全存储 | 否 |
您可在特斯拉账户设置或本 App 内断开授权;断开并删除账号后,我们将停止新的 Tesla 数据拉取,并按本政策删除或匿名化相关数据(法律另有规定除外)。
openid、offline_access — 身份标识与离线刷新令牌vehicle_device_data — 车辆状态、里程、软件版本、Fleet API 元数据等vehicle_location — 车辆位置(Drive Hub 行程、驾驶分析地图、轨迹展示)本 App 不申请 vehicle_cmds、vehicle_charging_cmds 等远程控制类 scope;不会远程唤醒、预空调或下发充电指令。
(A)Fleet Telemetry 官方字段(车辆推送,App 展示为特斯拉官方计数/遥测时使用官方字段名):
| 官方字段名 | 用途(TelogFSD) |
|---|---|
MilesSinceReset | 自复位里程(官方计数器;仪表盘 / 趋势基础;见 §4.3 硬件/固件要求) |
SelfDrivingMilesSinceReset | 自复位智驾里程(官方计数器;智驾占比基础;见 §4.3 硬件/固件要求) |
Location / VehicleSpeed / Gear | 行程/Drive Hub、驾驶分析、路线展示 |
Odometer / Soc / RatedRange | 里程表、电量、续航估算 |
OutsideTemp / InsideTemp | 环境温度 / 车内温度(能耗与行程上下文) |
Version | 车辆软件版本(更新关联分析) |
(B)Fleet API 元数据(OAuth 授权后经 API 拉取):车辆 ID、脱敏 VIN、车型、在线/休眠状态等。
(C)TelogFSD 派生指标(标注为 TEL0G_FSD_DERIVED,非特斯拉官方算法):智驾占比、驾驶评分、长期趋势、多月对比、分享卡与 PDF 报告等。除非界面明确标注为特斯拉官方计数器,否则均为 TelogFSD 计算结果。
精确位置、行程轨迹、VIN 等可能构成敏感个人信息;我们仅在您连接车辆并开启相关功能所同意的范围内处理,不用于广告定向。
本 App 的完整 Live 功能与官方智驾计数(SelfDrivingMilesSinceReset 等)目前主要适用于同时满足以下条件的车辆:
不满足上述条件的车辆,可能无法收到 MilesSinceReset / SelfDrivingMilesSinceReset 等官方计数推送,仪表盘智驾占比、趋势等功能可能长期为 0 或不可用。OAuth 连接、车辆列表等基础能力不受此限,但不构成我们对非适用车辆提供相同统计能力的承诺。特斯拉后续若调整软件、硬件或字段支持范围,以特斯拉官方文档与 App 内实际表现为准。
| 类别 | 示例 | 说明 |
|---|---|---|
| 账户与标识 | Apple / Google 登录标识、可选显示名 / 邮箱 / 头像 | 用于创建与维护 TelogFSD 账号;不使用 Firebase 等第三方身份平台 |
| 特斯拉授权 | OAuth 令牌、车辆 ID、脱敏 VIN、车型 / 固件等元数据 | 经特斯拉开发者平台 OAuth 流程取得;令牌加密保存在 TelogFSD 专用后端;不写入 App 会话明文 |
| 车辆遥测与统计 | 官方计数器、行程、位置采样、派生智驾占比 / 趋势 / 评分 | 经 Fleet API / Fleet Telemetry 等特斯拉开发者接口在您授权后同步;派生指标标注为 TelogFSD 派生 |
| 订阅与权益 | App Store 订阅状态、Premium 权益 | 付款由 Apple 处理;我们不直接收集银行卡号 |
| 本机偏好 | 语言、区域、选中车辆、同意记录 | 保存在设备安全存储 |
| 支持沟通 | 您主动发送的邮件、截图、日志 | 仅用于客服与缺陷排查 |
我们不收集:特斯拉密码、通讯录、相册全文、生物识别模板、用于广告的跨应用标识。
我们不会出售个人信息,也不会将车辆数据用于广告定向。
| 第三方 | 角色 | 涉及信息 |
|---|---|---|
| Tesla / 特斯拉 | 车辆数据来源(特斯拉开发者平台官方接口) | 经您在 Tesla 账户或 OAuth 授权流程中明确授权的车辆与账户信息 |
| Apple | 登录、分发、订阅结算 | Apple ID 登录信息、购买记录 |
| 可选登录 | 您授权的 Google 账号基本资料 | |
| 云服务提供商 | TelogFSD 后端托管 | 加密后的令牌与业务数据 |
我们力争在 15 个工作日内答复;情况复杂时依法延长并说明理由。
本 App 面向成年车主及车辆管理人,不会主动面向未满 14 周岁未成年人收集个人信息。若监护人发现误收集,请联系我们删除。
我们可能因功能、法律或监管要求更新本政策,并在本页注明生效日期。重大变更将通过 App 内提示或显著方式告知。若不同意,可停止使用并删除数据。
This Privacy Policy applies to the TelogFSD mobile app and necessary backend services distributed via the Apple App Store.
The operator and personal-information processor is Wenling Xinhe Yijia Software Development Studio (sole proprietorship) (not Tesla, not Apple).
The app is listed under an Apple Developer Program (Individual) account. The individual Apple Developer account holder and the sole-proprietorship operator are the same natural person.
Unless mandatory local law provides otherwise, processing of personal information is governed by the laws of the People’s Republic of China (including the PIPL) and this Policy.
com.jchen.TelogFSDTelogFSD is registered as a third-party app on the Tesla China Developer platform (developer.tesla.cn) and/or the global Tesla Developer platform (developer.tesla.com) with Fleet API access. After your authorization, we obtain vehicle-related data only through Tesla’s official developer interfaces. China vehicles use the China developer app and auth.tesla.cn; overseas vehicles use the corresponding regional developer app and official auth endpoints.
| Stage | Description | Vehicle telemetry relayed via TelogFSD servers? |
|---|---|---|
| Developer registration | Operator registers TelogFSD on Tesla Developer, obtains Fleet API qualification and client_id (separate apps for China vs overseas) |
— |
| Owner authorization | You are redirected to Tesla’s official auth page (e.g. auth.tesla.cn / auth.tesla.com) to sign in and grant OAuth scopes |
No |
| Token exchange | Authorization code is exchanged for access / refresh tokens via TelogFSD’s HTTPS backend and Tesla’s official token endpoint; client_secret is server-side only and not bundled in the app; the app does not store Tesla tokens in plaintext long-term |
Token exchange only; no vehicle telemetry payload |
| Fleet API metadata | TelogFSD backend calls Tesla Fleet API on your behalf for vehicle list / status metadata (account binding and display) | No (not a continuous telemetry stream) |
| Fleet Telemetry | After Virtual Key pairing and Fleet Telemetry configuration, official counters and trip data are pushed via Tesla Fleet Telemetry to TelogFSD’s dedicated receiver, encrypted and stored for dashboard, trends, and trips | Yes (required for Live features) |
| Derived analytics | FSD ratios, trends, scores, etc. are computed by TelogFSD and labeled as derived data | Derived results may be stored on TelogFSD backends |
| On-device cache | Language, region, selected vehicle, consent flags in secure on-device storage | No |
You may revoke authorization in Tesla account settings or in-app. After unlinking and account deletion we stop new Tesla data collection and delete or anonymize related data as described in this Policy (unless law requires otherwise).
openid, offline_access — identity and refresh tokensvehicle_device_data — vehicle status, mileage, software version, Fleet API metadatavehicle_location — vehicle location (Drive Hub trips, driving analytics maps, route display)We do not request vehicle_cmds or vehicle_charging_cmds; we do not remotely wake, precondition, or control charging.
(A) Fleet Telemetry official fields (vehicle push; shown with official field names when labeled as Tesla counters):
| Official field | TelogFSD use |
|---|---|
MilesSinceReset | Official miles-since-reset counter (see §4.3 HW/firmware requirements) |
SelfDrivingMilesSinceReset | Official self-driving miles counter (see §4.3 HW/firmware requirements) |
Location / VehicleSpeed / Gear | Trips / Drive Hub, driving analytics, routes |
Odometer / Soc / RatedRange | Odometer, state of charge, rated range |
OutsideTemp / InsideTemp | Ambient / cabin temperature context |
Version | Vehicle software version (update-related analytics) |
(B) Fleet API metadata (after OAuth): vehicle ID, masked VIN, model, online/asleep status, etc.
(C) TelogFSD derived metrics (labeled TEL0G_FSD_DERIVED, not Tesla’s official algorithms): FSD share, driving score, long-term trends, multi-month comparisons, share cards, PDF reports. Unless explicitly labeled as an official Tesla counter, values are TelogFSD calculations.
Precise location, trip traces, and VIN may be sensitive personal information. We process them only within the scope of your vehicle connection and enabled features—not for ad targeting.
Full Live features and official self-driving counters (e.g. SelfDrivingMilesSinceReset) currently target vehicles that meet all of the following:
Vehicles that do not meet these requirements may not receive official counter telemetry; dashboard FSD share and trends may stay at zero. Basic OAuth / vehicle list may still work, but we do not promise parity for ineligible vehicles. Tesla may change software, hardware, or field support over time; in-app behavior prevails.
We do not collect Tesla passwords, contacts, full photo libraries, biometrics, or cross-app advertising IDs.
Provide dashboard, trends, trips, sharing, Tesla linking, Premium entitlement checks, customer support, and legal compliance. No sale of personal data; no ad tracking SDKs.
Access, correction, deletion, withdrawal of consent, and account deletion via in-app controls or email Drive-Analytics@telog.cn (subject “Privacy Request”). We aim to reply within 15 business days; complex cases may take longer as required by law.
Operator: see above. Apple listing: Individual Developer (same natural person). Email: Drive-Analytics@telog.cn. Support page: support.html.