隐私政策
适用应用：蓝牙调试助手-SPP(串口)通信
Android 包名：com.zzf.bluetoothsmp
最后更新日期：2026-09-09
本政策说明本应用如何处理蓝牙通信数据、使用统计、故障诊断和应用内购买信息。您无需创建本应用的开发者账号即可使用蓝牙功能。隐私联系邮箱为 zhangfeidamo@gmail.com。
蓝牙通信和保存在设备上的信息
本应用使用蓝牙功能发现、连接附近设备，并发送和接收您指定的数据。在 2.8 及后续版本中，蓝牙扫描、监听、连接和收发仅在应用位于前台时运行；应用退到后台后会停止蓝牙通信。这些版本不再为蓝牙通信使用前台服务或请求通知权限。2.8 之前的版本可能使用前台服务和通知维持后台蓝牙通信。设备名称、蓝牙地址、服务 UUID、通信历史、快捷键、宏和相关配置用于显示连接、恢复设置和本地调试。
您发送的通信内容会传递给连接的蓝牙设备；对端设备如何保存和使用这些内容，由该设备及您选择的使用方式决定。本应用的分析事件使用收发数量、字节总数等统计，不把通信内容、宏内容、蓝牙地址或完整服务 UUID 作为分析事件字段上传。
您可以主动复制诊断报告、导出日志或宏。导出内容可能包含设备信息和通信数据；当您在系统文件选择器中选择其他应用或云存储位置时，该目的地会收到相应文件，并按自己的规则处理。请只向您信任的设备和目的地发送这些信息。
使用统计与近似位置
本应用使用 Google Analytics for Firebase 了解功能使用和运行情况。数据包括应用屏幕和会话、扫描和连接操作及结果、权限结果、导出或复制操作、收发统计，以及应用版本和设备相关信息。
Analytics 还会处理安装级标识，并在可用时使用 Android 广告 ID。它可以根据网络连接的掩码 IP 信息推导粗略地区，用于地区统计；这不同于读取 GPS 精确坐标。广告 ID 或安装标识不等于您的姓名，但可用于关联同一次安装的使用事件。
我们已关闭本应用 Analytics 资源的广告个性化设置。该设置不会停止本政策披露的使用统计、崩溃诊断或 Google 产品和服务数据共享。
相关技术说明见 Google Analytics 数据披露。
崩溃与诊断
本应用使用 Firebase Crashlytics 分析崩溃和部分非致命异常。诊断信息可能包括异常栈、发生时间、应用版本、操作系统、设备型号、内存或存储状态，以及发生问题时的连接状态和错误类型。
Firebase 的相关安装和会话组件还会处理随机安装/会话标识以及运行环境信息，用于计算受影响的安装数量和运行质量。这些标识可以将多个诊断报告关联到同一次应用安装。Crashlytics 的完整诊断报告用于提供崩溃诊断服务；发生崩溃的时间和是否为致命错误等有限信息，也会以崩溃事件进入 Analytics，并受下文的 Analytics 共享设置影响。Firebase SDK 数据披露
支持者购买
如果您使用“支持开发者”功能，付款由 Google Play 的付款界面处理。本应用查询购买结果、确认购买，并保存支持者权益状态以显示或恢复徽章。应用不读取您的银行卡号或银行卡验证码。
当您打开支持开发者入口时，本应用会把“已拥有/未拥有”支持者权益状态作为分析事件的一部分。Analytics 也可能记录 Google Play 完成的应用内购买事件，包括商品、价格、币种和数量等信息。这些购买统计用于了解支持者功能的使用；购买和权益结果也用于提供已购买的功能。
Google Play 的付款信息处理适用其自身条款。Google Play 付款说明、Analytics 自动购买事件说明
处理目的和服务提供方
本应用处理上述信息用于提供蓝牙通信与购买权益、统计功能使用、诊断问题和改进可靠性。统计和诊断数据通过 Google 的 Firebase/Analytics 服务处理；因此，即使没有上传到开发者自建服务器，也不表示数据从未离开您的设备。
Google/Firebase 为统计和诊断提供数据处理服务。本应用还启用了 Analytics 的“Google 产品和服务”数据共享：Google 可以分析这些 Analytics 数据，了解使用行为和趋势，并改进其产品及服务；对这一用途，Google 作为独立数据控制者处理数据。技术支持以及汇总模型和业务洞察也按相应 Analytics 设置处理。您自行选择的蓝牙设备、文件存储位置或分享接收方，也会收到您主动传递给它们的相应内容。Google 对其服务的处理说明见 Google 隐私政策、Analytics 数据共享说明 和 Firebase 隐私与安全。
权限与选择
- 附近设备/蓝牙权限：用于发现、连接、通信及使本机可被发现。拒绝或撤销相关权限会影响对应蓝牙功能。
- 较早 Android 系统的位置权限：Android 11 及以下的蓝牙发现可能需要该权限。本应用使用它完成附近蓝牙扫描；该权限用途与 Analytics 从网络信息推导粗略地区是两回事。
- 互联网：用于 Analytics、Crashlytics、Google Play 购买及更新服务。
- 广告 ID：系统支持时可在 Android 设置中管理。重置或删除广告 ID 不代表之前已经上传的统计记录被删除，也不等于关闭所有安装级分析。
当前 Google Play 版本在运行时启用上述分析和崩溃诊断，尚未提供独立的应用内遥测关闭开关。您可以在系统设置管理应用权限。停止使用或卸载应用会停止该安装继续运行，但不会自动清除已经传出的数据。
保存期限与删除
设备上的记录。您可在历史记录页面删除会话历史，在调试页面清空当前调试日志。Android 的“清除存储空间/清除应用数据”可移除本应用当前安装的本地数据。已导出的文件需在保存位置另行删除。若设备启用了系统备份或设备迁移，相关副本及恢复行为由系统和您选择的备份服务控制；仅卸载应用不一定删除这些副本。
Analytics 数据。本应用的 Analytics 资源将事件级数据保留设置为 2 个月，用户级数据保留设置为 14 个月，并开启了“有新的用户活动时重置”。新的活动会刷新相关用户标识的保留期限。上述设置不适用于标准汇总报告；到期数据的清理按 Google 的服务处理周期完成。删除本机数据不会自动发出对这些远端记录的删除指令。Analytics 数据保留说明
崩溃数据。根据 Firebase 的公开说明，Crashlytics 崩溃栈及相关标识保存 90 天后开始从在线和备份系统清除。这是开始清理的时间，不代表该时刻所有副本立即消失。Firebase 保存说明
购买数据。应用内的权益状态用于显示和恢复购买。Google Play 保存的交易记录由 Google Play 的规则管理；清除应用数据不等于退款或删除 Google Play 交易记录。
目前本应用没有开发者账号注销功能，也没有按安装删除云端遥测的应用内入口。我们不会将您的联系邮箱自动绑定到 Firebase 随机安装标识，因此仅凭邮箱通常不能定位某次安装的全部统计记录。如您希望了解某类数据的保存、可用删除方式或您的隐私权利，请联系 zhangfeidamo@gmail.com。我们会根据请求涉及的数据与可识别范围说明可采用的处理方式；本政策不承诺未具备的即时或全部远端删除能力。
安全、未成年人和政策更新
Firebase/Analytics 的数据传输使用 HTTPS/TLS。蓝牙通信的安全性还取决于设备、连接方式与使用环境；本应用不对任意蓝牙对端提供端到端加密保证。
如您是未成年人，请按照所在地法律及监护人的指导使用。监护人对有关数据处理有疑问时，可以通过上述邮箱联系。
本政策发生实质变化时，我们会在此页面更新内容和日期。联系方式：zhangfeidamo@gmail.com。
Privacy Policy
Application: 蓝牙调试助手-SPP(串口)通信 — Bluetooth SPP Assistant
Android package: com.zzf.bluetoothsmp
Last updated: September 9, 2026
This policy explains how the app handles Bluetooth communication, usage statistics, diagnostics and in-app purchase information. You do not need to create an account with the app's developer to use its Bluetooth features. Our privacy contact is zhangfeidamo@gmail.com.
Bluetooth communication and information on your device
The app discovers and connects to nearby Bluetooth devices and sends or receives the data you specify. In version 2.8 and later, Bluetooth scanning, listening, connections and data transfer operate only while the app is in the foreground; Bluetooth communication stops when the app goes into the background. These versions no longer use a foreground service or request notification permission for Bluetooth communication. Versions before 2.8 may use a foreground service and notifications to maintain background Bluetooth communication. Device names, Bluetooth addresses, service UUIDs, communication history, shortcuts, macros and settings support connections and local debugging.
The information you send is delivered to the connected Bluetooth device. Its subsequent handling depends on that device and how you use it. The app's analytics events use counts and byte totals; communication content, macro content, Bluetooth addresses and full service UUIDs are not added as analytics event fields.
You can copy diagnostic reports or export logs and macros. Exported files may contain device information and communication content. If you select another app or a cloud storage destination in the system file picker, that destination receives the file and handles it under its own rules. Send information only to devices and destinations you trust.
Usage analytics and approximate location
The app uses Google Analytics for Firebase to understand feature use and operation. This includes screens and sessions, scanning and connection actions and outcomes, permission results, export or copy actions, traffic counts, and app and device information.
Analytics also processes installation identifiers and the Android Advertising ID when available. It can derive a coarse region from masked IP information associated with the network connection. This is different from reading precise GPS coordinates. Advertising and installation identifiers are not your name, but can associate events with an app installation. Analytics data disclosure
We have disabled ad personalization in this app's Analytics property. This setting does not stop the usage analytics, crash diagnostics or Google products and services data sharing described in this policy.
Crash reports and diagnostics
Firebase Crashlytics helps diagnose crashes and some non-fatal exceptions. Reports may include stack traces, timestamps, app and operating-system versions, device model, memory or storage state, connection state and error types.
Related Firebase installation and session components process random installation/session identifiers and operating-environment information to measure reliability and affected installations. These identifiers can associate multiple reports with the same app installation. Full Crashlytics reports support the crash-diagnostics service. Limited information about a crash occurrence, such as its time and whether it was fatal, also enters Analytics as a crash event and is subject to the Analytics sharing setting described below. Firebase SDK disclosure
Supporter purchases
Google Play processes payments through its checkout interface. The app checks and acknowledges purchases and keeps an entitlement state to display or restore the supporter badge. The app does not read your card number or card security code.
When you open the support-developer entry, the app includes whether the supporter entitlement is owned in an analytics event. Analytics may also record completed Google Play in-app purchases, including product, price, currency and quantity. These statistics help understand use of the supporter feature; purchase results also provide purchased entitlements.
Google Play handles payment information under its own terms. Google Play payment information, automatically recorded purchase events
Purposes and service providers
We use this information to provide Bluetooth communication and purchase entitlements, understand feature use, diagnose problems and improve reliability. Google Firebase/Analytics processes analytics and diagnostics. The absence of a developer-operated upload server does not mean that no data leaves your device.
Google/Firebase provides processing services for analytics and diagnostics. We have also enabled the Analytics “Google products & services” data-sharing setting. Google can analyze this Analytics data to understand behavior and trends and improve its products and services; for this use, Google acts as an independent data controller. Technical support and aggregated modeling and business insights are also handled under the relevant Analytics settings. Bluetooth devices, file destinations and recipients you choose receive the information you send to them. See the Google Privacy Policy, Analytics data-sharing information and Firebase privacy information.
Permissions and choices
- Nearby devices/Bluetooth: discovery, connections, communication and making this device discoverable. Denying or revoking permission affects the corresponding features.
- Location on older Android versions: Android 11 and earlier may require location permission for Bluetooth discovery. The app uses it for nearby Bluetooth scanning. This is separate from Analytics deriving a coarse region from network information.
- Internet: Analytics, Crashlytics, Google Play purchases and app-update services.
- Advertising ID: you can manage it in Android settings where supported. Resetting or deleting it does not delete previously uploaded records or turn off every installation-based measurement.
The current Google Play version enables the analytics and crash diagnostics described above and does not have a separate in-app telemetry switch. You can manage app permissions in Android settings. Stopping use or uninstalling prevents that installation from continuing to run; it does not automatically remove data already transferred.
Retention and deletion
Local records. You can delete conversation history from History and clear current debugging logs from Debug. Android's clear-storage/clear-app-data control removes this installation's local app data. Delete exported files separately at their destination. System backup or device migration may retain or restore copies according to your device and chosen backup service; uninstalling may not delete those copies.
Analytics. Our Analytics property retains event-level data for 2 months and user-level data for 14 months, with reset-on-new-user-activity enabled. New activity refreshes the retention period of the associated user identifier. These settings do not apply to standard aggregated reports; expired records are removed according to Google's processing cycle. Clearing local app data does not itself request deletion of these remote records. Analytics retention
Crash data. Firebase states that Crashlytics keeps crash stack traces and associated identifiers for 90 days before beginning removal from live and backup systems. This does not mean every copy disappears immediately on day 90. Firebase retention information
Purchases. Local entitlement state supports displaying and restoring purchases. Google Play transaction records follow Google Play's rules. Clearing app data does not refund a purchase or delete its Google Play transaction.
The app has no developer account to close and currently has no in-app control for deleting cloud telemetry by installation. We do not automatically link a contact email address to Firebase's random installation identifiers, so an email address alone usually cannot identify all records from a particular installation. For information about retention, available deletion options or your privacy rights, contact zhangfeidamo@gmail.com. We will explain available handling based on the data concerned and the records that can be identified. This policy does not promise immediate or complete remote deletion where that capability is unavailable.
Security, minors and updates
Firebase/Analytics transmissions use HTTPS/TLS. Bluetooth security also depends on the devices, connection method and environment; the app does not guarantee end-to-end encryption for arbitrary Bluetooth peers.
Minors should use the app according to applicable law and guidance from their parent or guardian. Parents or guardians with privacy concerns may contact the address above.
Material changes will be reflected on this page with an updated date. Contact: zhangfeidamo@gmail.com.