隐私政策 / Privacy Policy
生效及最后更新:2026-10-13 · Effective and last updated: 2026-10-13
适用于 BEGODE Android 0.1.13(versionCode 15)及其后续更新,除非更新版本另有说明。
1. 谁负责处理数据
本政策适用于由东莞市比高德智能科技有限公司(Dongguan Begode Intelligent Technology Co., Ltd.)提供的 BEGODE Android 应用。隐私问题或权利请求可发送至 bgd002@begode.com。官网:https://www.begode.com/。
App 首次启动时会显示隐私选择;用户同意后才进入主界面并初始化联网功能。拒绝后 App 会退出。系统权限可在设备设置中随时撤销。
2. 我们处理哪些数据
| 功能 | 数据 | 用途与处理位置 |
|---|---|---|
| 账号与资料 | 邮箱、验证码、密码的安全表示、用户 ID、昵称,以及用户选择填写的头像、姓名、简介、性别、生日、地址、电话和地区 | 注册、登录、找回账号、展示和编辑资料;通过 HTTPS 发送至 BEGODE 社区服务 |
| 粉圈与社区安全 | 帖子、图片、视频、评论、点赞、关注、拉黑、举报、时间和关联账号 | 提供公开社区、互动、内容管理、安全审核与申诉;媒体保存在 BEGODE 的社区文件服务 |
| 在线状态、附近车友与实时共享 | 账号标识、随机在线/共享会话 ID、在线时间、查询半径、四舍五入到 0.01° 网格的位置,以及用户在实时共享中选定的车辆/骑行参数(每组最多 5 项);只有另行开启默认关闭的“共享 GPS 精准位置”后,才会额外处理新鲜精确经纬度、定位时间和精度 | 提供在线状态、附近查询、地图展示及用户主动开启的实时共享;通过 HTTPS 发送至 BEGODE 社区服务,活动共享数据可向附近范围内符合条件的已登录车友显示 |
| 客服 | 随机会话 ID、消息、语言、工单、订单查询信息和客服处理记录 | 自动回复、转人工、解决问题和查询订单;需要人工处理时可能发送至飞书/Lark 客服通道 |
| 商城 | IP、WebView User-Agent、Cookie、浏览和会话数据,以及用户在结账时主动提交的联系、收货、订单与支付信息 | 在 App 内展示由 Shopify 提供的 BEGODE 商城并完成用户发起的交易;支付信息由结账页所示的支付服务商处理 |
| 技术与安全日志 | IP、转发 IP 头、请求 URL/路径、查询参数(附近查询可包含 0.01° 网格位置和半径)、请求方法、时间、状态、来源页、User-Agent、Cookie、语言及内容协商头 | 运行 API、故障排查、防滥用和安全审计 |
登录账号且 App 在前台时,App 会向社区服务维持短期在线状态,启动会话本身不含位置。只有用户按账号单独同意“附近查询”后,在线心跳和附近查询才会发送四舍五入到 0.01° 网格的位置。附近查询同意不会自动开启实时共享。
3. 主要在设备本地处理的数据
- 蓝牙与车辆:附近车辆名称和蓝牙地址、车辆别名、遥测、车辆设置、骑行统计和按车辆保存的续航估算通常在设备本地处理。只有用户主动确认实时共享时,当前选定参数组的数据(例如速度、里程、电压、电流、温度、PWM 或状态,每组最多 5 项)才会发送至 BEGODE 社区服务。
- 手机位置:经授权后,位置用于本机计算 GPS 速度、距离和海拔。登录用户单独同意附近查询后,App 在前台会发送四舍五入到 0.01° 网格的位置,用于在线状态与附近查询。用户再次确认开启实时共享后,App 会持续发送该网格位置;如另行开启默认关闭的“共享 GPS 精准位置”,还会发送新鲜精确经纬度、定位时间和精度。实时共享可在切换应用、回到桌面或锁屏后继续,直到用户停止共享、退出账号、切换或断开车辆、撤销位置权限或会话失效。
- 相机、麦克风和屏幕录制:只在用户主动开启并完成 Android 权限或投屏确认后使用。生成的 MP4 保存在设备,App 不会自动上传。
- 黑匣子:车辆诊断 CSV 默认保存在设备。只有用户主动通过系统分享时,所选接收应用才会收到文件。
- 设置与缓存:语言、主题、单位、提醒、登录令牌、车辆别名、统计、按账号保存的附近查询同意和精准位置共享选择、媒体缓存、商城 Cookie 和固件缓存会保存在 App 私有存储或相应媒体目录。
4. Android 权限
App 可能请求附近蓝牙(扫描与连接)、精确/大致位置、相机、麦克风和通知权限。屏幕录制期间使用媒体投影及麦克风类型的前台服务。用户主动开启实时共享后,App 使用位置及已连接设备类型的前台服务、持续通知和局部唤醒锁,以便在切换应用、回到桌面或锁屏时继续获取位置、维持车辆连接并发送共享更新;通知可用于返回 App 或停止共享。网络、网络状态和振动权限用于联网与本地提醒。App 不声明广告 ID、联系人、短信、电话状态、日历或读取全部照片库的权限。
5. 接收方、共享与跨境
- BEGODE API、数据库、社区媒体服务器和邮件投递基础设施,用于账号、社区、在线状态、附近车友、实时共享和服务功能;
- 用户主动开启实时共享时,附近范围内符合条件的已登录车友可看到活动共享中的位置、选定参数、昵称和头像;
- 飞书/Lark,在用户转人工或客服运营需要时处理相关会话和工单信息;
- Shopify、商城 CDN、Cookie 服务和结账页所示支付服务商,用于商城浏览、订单与支付;
- 用户主动选择的系统分享目标或用户自行填写的 HTTPS 固件/诊断服务。
BEGODE 主要 API 当前运行于香港云基础设施;Shopify、飞书/Lark、支付和网络服务可能在其运营地区处理数据,因此可能发生跨境传输。我们仅为提供相应功能、安全运营或履行法律义务而传输必要数据。原生 App 不使用广告 ID,也未集成第三方行为广告 SDK。我们不以出售个人数据获取对价。
6. 保存期限
我们按数据用途、账号状态、安全需求和适用法律确定保存期限:
- 账号和社区资料通常在账号有效期间保存;账号删除后,账号标识会被删除、软删除或去标识化。为社区连续性、反滥用、争议处理或法律义务所必需的帖子、评论、举报、安全日志和备份副本可能继续保存,但不再用于账号日常服务。
- 社区媒体保存至用户删除内容、删除账号请求按实际范围处理,或运营、安全、缓存和备份周期结束。
- 在线状态和实时共享在活动列表中的有效租约约为 15 秒,需要持续更新;用户停止共享或更新停止后,相关数据不再作为活动在线/共享记录返回。该有效期只表示实时展示期限,不表示相关 API 访问记录、安全日志或备份会被立即删除。
- 客服会话、工单和订单查询记录在解决问题、质量审计及履行法律义务所需期间保存;商城订单和支付记录由商城及支付服务商依其政策和法律义务保存。
- 访问与安全日志仅在运行、排障、防滥用和依法配合所需期间保存;备份中的副本在正常轮换或法律保留期结束后处理。
- 本地数据通常保留到用户在功能中清除、系统清除 App 数据或卸载;共享媒体目录中的录屏可能需用户单独删除。
7. 账号与数据删除
App 内路径:我的 → 账号安全 → 删除账号。无法登录时,可从注册邮箱联系 bgd002@begode.com。公开说明:账号与数据删除页。
当前删除接口会使账号失效并删除或去标识化部分账号及关联数据;它不应被理解为立即清除所有公开内容、举报、安全日志、客服、商城、第三方记录或备份。用户可在邮件中明确要求处理帖子、评论、媒体、客服或其他数据,我们会按可验证身份、实际系统能力和适用法律处理。
8. 其他权利和选择
用户可编辑资料、删除自己的帖子和评论、管理关注与拉黑、按账号撤销附近查询同意、关闭精准位置共享,并可从 App 或持续通知立即停止实时共享。用户还可撤销系统权限、清除车辆/GPS 统计和黑匣子,并通过系统清除 App 数据。关闭本机同意或停止共享不等于删除服务器已经处理的记录;查阅、更正、复制、删除、限制处理或申诉请求可发送至上述邮箱。为保护账号,我们可能通过注册邮箱核验身份;请勿发送密码或一次性验证码。
9. 安全、未成年人和政策更新
客户端禁止明文网络流量,社区、客服和固件请求使用 HTTPS;Android 权限、系统投屏确认和临时文件分享权限用于限制访问。任何系统均不能保证绝对安全。
本 App 面向电动独轮车骑行者和车主,并非面向儿童设计。未达到所在地区可独立同意数据处理年龄的用户,应在监护人指导和当地法律允许的情况下使用。
重大处理方式变化会通过 App、官网或本页面通知;必要时会重新请求同意。页面顶部日期代表当前版本。
1. Controller and scope
This policy applies to the BEGODE Android app provided by Dongguan Begode Intelligent Technology Co., Ltd. Contact bgd002@begode.com for privacy requests. Website: https://www.begode.com/.
The app presents a privacy choice on first launch. Network-enabled features initialize after consent; declining exits the app. System permissions can be withdrawn in device settings.
2. Data processed
| Feature | Data | Purpose and destination |
|---|---|---|
| Account and profile | Email, verification code, secured password representation, user ID, nickname, and optional avatar, name, bio, sex, birth date, address, phone and region | Registration, authentication, recovery and profile services over HTTPS |
| Community and safety | Posts, photos, videos, comments, likes, follows, blocks, reports, timestamps and linked accounts | Public community, interactions, moderation, safety and appeals |
| Online status, nearby riders and live sharing | Account identifier, random presence/share-session IDs, online timestamps, search radius, location rounded to a 0.01° grid, and up to five user-selected vehicle/ride metrics per live-sharing group; fresh precise coordinates, observation time and accuracy are additionally processed only when the default-off “Share precise GPS location” option is separately enabled | Online presence, nearby search, map display and user-initiated live sharing; sent to BEGODE community services over HTTPS, with active sharing data visible to eligible signed-in riders nearby |
| Support | Random session ID, messages, language, tickets, order-query information and support records | Automated support, human handoff and order assistance; related content may be processed through Feishu/Lark for human support |
| Store | IP, WebView user agent, cookies, browsing/session data, and contact, shipping, order and payment data entered during checkout | Embedded BEGODE store provided through Shopify and the payment provider shown at checkout |
| Technical logs | IP and forwarded-IP headers, request URL/path, query parameters (nearby queries may include a 0.01° grid location and radius), method, time, status, referrer, user agent, cookies, language and content-negotiation headers | Service operation, troubleshooting, abuse prevention and security auditing |
While a signed-in user keeps the app in the foreground, the app maintains a short-lived presence session; starting that session does not include location. Only after the user separately grants account-scoped Nearby consent do presence heartbeats and nearby queries send location rounded to a 0.01° grid. Nearby consent does not automatically enable live sharing.
3. Data primarily processed on the device
- Bluetooth and vehicle data: nearby vehicle names/addresses, aliases, telemetry, settings, ride statistics and per-vehicle range estimates are generally processed on the device. Only after the user explicitly confirms live sharing is the currently selected metric group—such as speed, distance, voltage, current, temperature, PWM or status, up to five metrics—sent to BEGODE community services.
- Phone location: with permission, location is used locally for GPS speed, distance and altitude. After a signed-in user separately grants Nearby consent, the foreground app sends location rounded to a 0.01° grid for presence and nearby queries. After a separate confirmation to start live sharing, that grid location is sent continuously; if the default-off precise-location option is also enabled, fresh precise coordinates, observation time and accuracy are sent. Live sharing may continue when switching apps, returning home or locking the screen until the user stops sharing, signs out, changes or disconnects the vehicle, withdraws location permission, or the session becomes invalid.
- Camera, microphone and screen recording: used only after user action and Android permission/capture approval. Generated MP4 files remain on the device and are not uploaded automatically.
- Blackbox: diagnostic CSV files remain local unless the user shares them through Android.
- Settings and caches: preferences, tokens, aliases, statistics, account-scoped Nearby consent and precise-location sharing choices, media cache, store cookies and firmware cache remain in app-private or relevant media storage.
4. Permissions
The app may request nearby Bluetooth, precise/approximate location, camera, microphone and notification permissions. Screen recording uses media-projection and microphone foreground-service types. After the user starts live sharing, the app uses location and connected-device foreground-service types, an ongoing notification and a partial wake lock so that it can continue accessing location, maintaining the vehicle connection and sending sharing updates when switching apps, returning home or locking the screen; the notification can reopen the app or stop sharing. Internet, network-state and vibration permissions support network features and local alerts. The app does not declare the advertising ID, contacts, SMS, phone state, calendar or broad photo-library permissions.
5. Recipients and international processing
- BEGODE API, database, community-media and mail infrastructure for account, community, presence, nearby-rider, live-sharing and support features;
- Eligible signed-in riders nearby, who may see the location, selected metrics, nickname and avatar included in an active share initiated by the user;
- Feishu/Lark for human support;
- Shopify, store CDN/cookie services and checkout payment providers for store browsing, orders and payment;
- Recipients deliberately selected by the user through Android sharing or a user-configured HTTPS firmware/diagnostic service.
The primary BEGODE API currently runs on cloud infrastructure in Hong Kong. Shopify, Feishu/Lark, payment and network providers may process data in their operating regions, so international transfers may occur. Transfers are limited to service delivery, security and legal obligations. The native app does not use the advertising ID or a third-party behavioral-advertising SDK. We do not sell personal data for monetary consideration.
6. Retention
- Account/profile data is generally kept while the account is active. After deletion, identifiers are deleted, soft-deleted or de-identified. Public content, moderation evidence, security logs and backups may remain where necessary for continuity, abuse prevention, disputes or law, but are not used for ordinary account service.
- Community media remains until content deletion, account-deletion processing within the actual supported scope, or the end of operational, security, cache and backup cycles.
- Presence and live-sharing entries have an active lease of approximately 15 seconds and require continuing updates. After sharing is stopped or updates cease, the data is no longer returned as an active presence/share. This active-display period does not mean related API access records, security logs or backups are deleted immediately.
- Support, ticket and order-query records remain as needed to resolve cases, audit quality and meet legal duties. Store and payment providers retain transaction records under their policies and applicable law.
- Access/security logs remain only as needed for operation, troubleshooting, abuse prevention and legal requests. Backup copies are handled at the end of normal rotation or legal holds.
- Local data generally remains until cleared in the feature, app data is cleared, or the app is uninstalled. Screen recordings in shared media may require separate deletion.
7. Deletion and other rights
In-app path: Me → Account security → Delete account. If sign-in is unavailable, email bgd002@begode.com from the registered address. See the public account and data deletion page.
The current endpoint disables the account and deletes or de-identifies part of the account and associated data. It does not mean immediate removal of all public content, reports, security logs, support, store, third-party or backup records. A user may identify posts, comments, media, support or other data in an email request; requests are handled subject to verified identity, actual system capability and applicable law.
Users can edit profiles, delete their posts/comments, manage follows/blocks, revoke account-scoped Nearby consent, switch off precise-location sharing, and immediately stop live sharing in the app or ongoing notification. Users can also withdraw system permissions and clear ride statistics or blackbox files. Revoking local consent or stopping a share does not itself delete records already processed by the server. Requests to access, correct, copy, delete, restrict or appeal may be sent to the contact above. Never send a password or one-time code.
8. Security, children and changes
The client blocks cleartext network traffic, uses HTTPS for community/support/firmware requests, and relies on Android permission, capture-confirmation and temporary file-grant controls. No system can guarantee absolute security.
The app is designed for electric-unicycle riders and owners and is not directed to children. A person below the age at which they may independently consent in their region should use it only with guardian guidance and where local law permits.
Material changes will be notified through the app, website or this page, and renewed consent will be requested where required. The date at the top identifies the current version.