BEGODE Android · com.begode.app

隐私政策 / Privacy Policy

生效及最后更新:2026-08-25 · Effective and last updated: 2026-08-25

适用于 BEGODE Android 0.1.3(versionCode 5)及其后续更新,除非更新版本另有说明。

1. 谁负责处理数据

本政策适用于由东莞市比高德智能科技有限公司(Dongguan Begode Intelligent Technology Co., Ltd.)提供的 BEGODE Android 应用。隐私问题或权利请求可发送至 bgd002@begode.com。官网:https://www.begode.com/

App 首次启动时会显示隐私选择;用户同意后才进入主界面并初始化联网功能。拒绝后 App 会退出。系统权限可在设备设置中随时撤销。

2. 我们处理哪些数据

功能数据用途与处理位置
账号与资料邮箱、验证码、密码的安全表示、用户 ID、昵称,以及用户选择填写的头像、姓名、简介、性别、生日、地址、电话和地区注册、登录、找回账号、展示和编辑资料;通过 HTTPS 发送至 BEGODE 社区服务
粉圈与社区安全帖子、图片、视频、评论、点赞、关注、拉黑、举报、时间和关联账号提供公开社区、互动、内容管理、安全审核与申诉;媒体保存在 BEGODE 的社区文件服务
客服随机会话 ID、消息、语言、工单、订单查询信息和客服处理记录自动回复、转人工、解决问题和查询订单;需要人工处理时可能发送至飞书/Lark 客服通道
商城IP、WebView User-Agent、Cookie、浏览和会话数据,以及用户在结账时主动提交的联系、收货、订单与支付信息在 App 内展示由 Shopify 提供的 BEGODE 商城并完成用户发起的交易;支付信息由结账页所示的支付服务商处理
技术与安全日志IP、转发 IP 头、请求路径和方法、时间、状态、来源页、User-Agent、Cookie、语言及内容协商头运行 API、故障排查、防滥用和安全审计

3. 主要在设备本地处理的数据

4. Android 权限

App 可能请求附近蓝牙(扫描与连接)、精确/大致位置、相机和麦克风权限;屏幕录制期间使用媒体投影及麦克风类型的前台服务。网络、网络状态和振动权限用于联网与本地提醒。App 不声明广告 ID、联系人、短信、电话状态、日历或读取全部照片库的权限。

5. 接收方、共享与跨境

BEGODE 主要 API 当前运行于香港云基础设施;Shopify、飞书/Lark、支付和网络服务可能在其运营地区处理数据,因此可能发生跨境传输。我们仅为提供相应功能、安全运营或履行法律义务而传输必要数据。原生 App 不使用广告 ID,也未集成第三方行为广告 SDK。我们不以出售个人数据获取对价。

6. 保存期限

我们按数据用途、账号状态、安全需求和适用法律确定保存期限:

7. 账号与数据删除

App 内路径:我的 → 账号安全 → 删除账号。无法登录时,可从注册邮箱联系 bgd002@begode.com。公开说明:账号与数据删除页

当前删除接口会使账号失效并删除或去标识化部分账号及关联数据;它不应被理解为立即清除所有公开内容、举报、安全日志、客服、商城、第三方记录或备份。用户可在邮件中明确要求处理帖子、评论、媒体、客服或其他数据,我们会按可验证身份、实际系统能力和适用法律处理。

8. 其他权利和选择

用户可编辑资料、删除自己的帖子和评论、管理关注与拉黑、撤销系统权限、清除车辆/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

FeatureDataPurpose and destination
Account and profileEmail, verification code, secured password representation, user ID, nickname, and optional avatar, name, bio, sex, birth date, address, phone and regionRegistration, authentication, recovery and profile services over HTTPS
Community and safetyPosts, photos, videos, comments, likes, follows, blocks, reports, timestamps and linked accountsPublic community, interactions, moderation, safety and appeals
SupportRandom session ID, messages, language, tickets, order-query information and support recordsAutomated support, human handoff and order assistance; related content may be processed through Feishu/Lark for human support
StoreIP, WebView user agent, cookies, browsing/session data, and contact, shipping, order and payment data entered during checkoutEmbedded BEGODE store provided through Shopify and the payment provider shown at checkout
Technical logsIP and forwarded-IP headers, request path/method, time, status, referrer, user agent, cookies, language and content-negotiation headersService operation, troubleshooting, abuse prevention and security auditing

3. Data primarily processed on the device

4. Permissions

The app may request nearby Bluetooth, precise/approximate location, camera and microphone permissions. Screen recording uses media-projection and microphone foreground-service types. 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

Recipients may include BEGODE API/database/community-media and mail infrastructure; Feishu/Lark for human support; Shopify, store CDN/cookie services and checkout payment providers; and recipients the user deliberately chooses through Android sharing or a user-configured HTTPS 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

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, withdraw permissions, and clear ride statistics or blackbox files. Requests to access, correct, copy, 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.