生效日期：2026 年 9 月 6 日
QBittorrent Client 是用于管理用户自行配置的 qBittorrent 与 Transmission 服务器的独立第三方远程客户端。本应用不提供公共搜索、资源索引、媒体目录、云存储或文件分享服务，也不会将服务器上的任务内容下载到 iOS 设备。
用户添加服务器时，本应用会在设备本地保存服务器地址、显示名称、账号类型、用户名、密码或 API Key 及连接偏好，以便再次连接。上述信息不会发送给应用开发者；只有在登录或执行用户要求的服务器管理操作时，才会传输到用户配置的服务器地址。
本应用可能展示或缓存界面所需的服务器响应，其中可能包括任务名称、文件名、传输统计、Tracker、Peer、分类和标签。下载任务的内容文件保留在用户自己的服务器上并由该服务器处理，不会保存到 iOS 设备。开发者不运营接收上述管理信息的中转服务。
用户应妥善保护设备，并在服务器支持时优先使用 HTTPS。开启自签名证书选项会降低常规证书校验强度，仅应连接用户控制且信任的服务器。
本应用使用 Google Mobile Ads 展示横幅广告和激励广告。根据用户所在地区、同意选择、设备设置及 Google SDK 的当前行为，Google 及其广告合作伙伴可能处理设备和广告标识符、IP 地址、由 IP 推断的大致位置、广告互动、产品互动及诊断信息。
在适用地区，本应用通过 Google User Messaging Platform（UMP）在请求广告前征求同意；当 Google 要求时，设置页会提供“广告隐私选项”入口。无需同意消息的用户可以直接看到广告，不需要额外确认。
本应用目前不会请求 App Tracking Transparency（ATT）权限，也不会主动访问 IDFA。请参阅 Google 隐私政策和 Google Mobile Ads 数据披露说明。
为排查请求和错误，本应用可能向 Apple 统一日志系统写入仅保存在设备上的运行日志。应用的请求日志会隐藏密码、Cookie、Token、API Key 和会话标识符。本应用不会将这些日志上传到开发者运营的分析或崩溃报告服务。
Apple 和 Google SDK 仍可能依据其政策及用户的设备设置独立处理诊断信息。
开发者不会出售服务器账号信息或服务器任务数据。本应用不会将这些信息发送到开发者运营的后端。Google Mobile Ads 处理的数据受 Google 条款及用户适用的同意选择约束。
服务器配置会保留在设备上，直至用户删除对应服务器条目或卸载应用。服务器任务数据的保留与删除由用户自己的 qBittorrent 或 Transmission 服务器控制。Google 保留的广告数据遵循 Google 的相关政策。
当应用中显示“广告隐私选项”入口时，用户可以通过该入口查看或修改适用的广告数据使用选择。
本应用并非面向儿童。用户应达到适用法律及获取本应用所使用的 App Store 账号规定的最低年龄。
qBittorrent 和 Transmission 名称仅用于说明兼容的服务器协议。本应用与相关项目不存在隶属、授权或官方认可关系。
应用功能、SDK 或法律要求发生变化时，本政策可能更新；如有重大变更，将同步更新顶部生效日期。
Effective Date: September 6, 2026
QBittorrent Client is an independent third-party remote administration client for user-configured qBittorrent and Transmission servers. It does not provide public search, a content index, a media catalog, cloud storage, or file-sharing services, and it does not download task content from the server to the iOS device.
When a user adds a server, the app stores the server address, display name, account type, username, password or API key, and connection preferences locally on the device so that it can reconnect to that server. This information is not sent to the app developer. It is transmitted only to the server address configured by the user when needed to authenticate or perform a requested server-management action.
The app may display or cache server responses required for its interface. These responses can include task names, file names, transfer statistics, trackers, peers, categories, and tags. Downloaded payload files remain on and are processed by the user's server and are not saved to the iOS device. The developer does not operate an intermediary service that receives this management information.
Users should protect access to their device and use HTTPS whenever their server supports it. Enabling a self-signed-certificate option weakens normal certificate validation and should be limited to servers the user controls and trusts.
The app uses Google Mobile Ads to display banner and rewarded advertisements. Depending on the user's region, consent choices, device settings, and Google's current SDK behavior, Google and its advertising partners may process device and advertising identifiers, IP address, approximate location derived from IP address, ad interactions, product interactions, and diagnostic information.
Where required, the app uses Google's User Messaging Platform (UMP) to request consent before ads are requested and provides an advertising privacy-options entry in Settings when Google requires it. Users for whom no consent message is required can see ads directly without an additional confirmation.
The app does not currently request App Tracking Transparency (ATT) permission and does not intentionally access the IDFA. See the Google Privacy Policy and Google Mobile Ads data disclosure.
The app may write local operational logs to Apple's unified logging system to help diagnose requests and errors. Passwords, cookies, tokens, API keys, and session identifiers are redacted by the app's request logger. These logs are not uploaded to a developer-operated analytics or crash-reporting service by the app.
Apple and Google SDKs may independently process diagnostics according to their policies and the user's device settings.
The developer does not sell server account information or server task data. The app does not send that information to a developer-operated backend. Data processed by Google Mobile Ads is governed by Google's terms and the user's applicable consent choices.
Server configurations remain on the device until the user deletes the corresponding server entry or removes the app. Server task data remains subject to the retention and deletion controls of the user's own qBittorrent or Transmission server. Advertising data retained by Google is governed by Google's policies.
When the Advertising Privacy Options entry is available in the app, users can use it to review or change applicable advertising data-use choices.
The app is not directed to children. Users must meet the minimum age required by applicable law and by the App Store account used to obtain the app.
The qBittorrent and Transmission names are used only to identify compatible server protocols. The app is not affiliated with, authorized by, or endorsed by either project.
This policy may be updated when app features, SDKs, or legal requirements change. The effective date above will be revised when material changes are made.