KayingCode Mobile 隐私政策
简要说明：KayingCode Mobile 是连接到你主动配对的 KayingCode 桌面工作区或 Node 的远程客户端。应用没有账号注册、广告或分析 SDK。为建立连接，它会处理设备标识和配对凭据；你发出的消息及主动选择的附件会经 Relay 转发到你授权的目标。应用不会将聊天内容或崩溃报告自动提交给 KayingAI 的分析服务。
1. 运营者与适用范围
本政策适用于由北京零点八度科技有限公司（KayingAI）提供的 KayingCode Mobile。它说明移动客户端及其连接 Relay 服务如何处理个人信息。桌面端、你自行部署或配置的 Relay、配对的桌面工作区 / Node，以及你在这些环境中配置的模型或其他服务，可能各自有独立的数据处理方式。
2. 我们处理的数据
- 设备与配对信息：设备标识、设备名称和平台、配对请求/完成状态、Relay 地址、授权的 Node / 工作区标识，以及访问和刷新令牌。令牌与设备身份凭据保存在设备的安全存储中（Android Keystore / iOS Keychain，由系统及插件提供保护）。
- 连接与会话数据：为显示工作区、会话、任务状态和审批请求，客户端会收发相应的会话标识、标题、状态、消息、提示词、回复和交互数据。这些内容会发送给你扫描配对或明确选择的桌面工作区 / Node。
- 你选择的文件和照片：只有在你主动使用文件或图片选择器并发送时，应用才读取所选项目。文件或图片内容通过已配对的连接传给目标工作区 / Node。扫描配对二维码时，相机画面用于设备端识别配对信息；二维码图像不会因扫描行为而被上传。
- 本地设置与日志：应用在设备上保存必要的连接配置、偏好和有限的会话界面状态。协议日志由应用在本地运行时产生，可在应用中查看、复制、导出或清除；日志可能包含连接信息或部分设备凭据片段，导出后请妥善保管。应用还会在本地保留最近一次崩溃诊断（错误、堆栈、时间和应用版本），用于你查看和排查问题，不会自动上传。
- 通知内容：若你允许通知，任务运行状态可能显示运行任务数；审批、完成或失败通知可能包含任务标题、预览文本或审批标题。通知由设备本地系统展示，内容来源于你连接的工作区。
3. 数据如何传输和由谁接收
客户端通过你配置的 Relay 与已授权的桌面工作区 / Node 通信。Relay 处理设备授权、配对、路由和连接所需的元数据，并转发实时会话或附件数据。Relay 会保存运行授权所需的设备、配对、令牌和授权记录；吊销可使相应设备/授权失效。具体服务器存储、备份及删除期限取决于该 Relay 的运营者和部署配置。
工作区 / Node 会收到你通过应用发送的消息、会话交互及所选附件。它们可能按其自身的存储和运行方式保存或进一步处理这些内容。如果该工作区配置了 AI 模型提供商或其他第三方服务，相关内容可能由这些服务接收；其处理受对应服务条款和隐私政策约束。KayingCode Mobile 本身不会直接把聊天内容发送给广告、分析或崩溃报告 SDK。
应用支持 HTTPS/WSS，也允许使用你自行配置的 HTTP/WS 地址。TLS 仅在连接使用 HTTPS/WSS 时提供传输加密。应用没有为会话内容提供端到端加密，Relay 和所配置的连接服务可能处理转发中的数据。请优先使用可信的 HTTPS/WSS Relay，并谨慎选择目标工作区和附件。
4. 使用目的与法律依据
我们仅为提供配对、身份验证、连接维护、会话交互、附件转发、通知、故障排查和服务安全所需而处理上述数据。必要数据基于提供你主动请求的服务而处理；非必要的权限和通知由你通过系统授权或应用设置控制。
5. 权限
- 相机：扫描桌面端显示的配对二维码。你也可选择从相册读取二维码图片。
- 照片 / 文件：通过系统选择器访问你明确选中的项目，以发送给配对目标；应用不会扫描整个图库或文件系统。
- 通知、前台服务和网络：用于显示你授权的任务提醒、后台运行状态并维持远程连接。你可在系统设置中关闭通知或撤销权限；撤销后部分后台提醒或连接能力可能不可用。
6. 保留与删除
设备上的连接令牌和凭据会在你移除相应连接、应用清除数据或卸载应用时按平台行为删除；设备安装身份可能为后续重新配对而保留，直至应用数据被清除或应用卸载。应用内移除设备会尝试向 Relay 吊销设备及其授权并清除本地凭据。Relay 的历史设备或配对记录是否以及何时物理删除，取决于 Relay 管理方；部分部署提供管理员删除已吊销设备历史记录的能力。
你可以在应用设置中清除可清除的日志和崩溃记录。聊天、文件和会话记录通常由配对的工作区 / Node 或其配置的服务管理；请在相应环境中删除。应用没有用户账号系统，因此没有账号注销流程。若需咨询或提出请求，请联系 service@kayingai.com，并说明所用 Relay；请勿在邮件中发送访问令牌或其他秘密凭据。
7. 儿童与年龄
KayingCode Mobile 面向 13 岁及以上用户，不面向 13 岁以下儿童。我们不会有意收集 13 岁以下儿童的个人信息。如你认为儿童向我们提供了个人信息，请通过下方邮箱联系我们。
8. 安全
应用使用平台安全存储保存设备凭据，并提供设备/授权吊销机制。互联网传输的安全性取决于你配置的 Relay、工作区和协议；使用非 TLS 的 HTTP/WS 地址会使网络传输缺少 TLS 保护。请保护设备锁屏和 Relay 管理凭据，并及时吊销不再使用的设备。
9. 政策更新
当产品的数据处理方式或适用要求发生变化时，我们会更新本页面并修改生效日期。重大变化会通过适当方式提示。
10. 联系我们
运营者：北京零点八度科技有限公司（KayingAI）
隐私与支持邮箱：service@kayingai.com
网站：https://kayingai.com
KayingCode Mobile Privacy Policy
In brief: KayingCode Mobile connects to a desktop workspace or Node that you choose to pair. It has no account registration, advertising, or analytics SDK. It processes device identifiers and pairing credentials to establish a connection. Messages and attachments you choose to send are relayed to your authorized destination. The app does not automatically upload chat content or crash reports to a KayingAI analytics service.
1. Who we are and scope
This policy applies to KayingCode Mobile provided by Beijing Lingdian Badu Technology Co., Ltd. (KayingAI). It describes data handling by the mobile client and its Relay service. The desktop app, a Relay you self-host or configure, the paired desktop workspace / Node, and any model or other service configured there may have separate data practices.
2. Data we process
- Device and pairing data: device identifier, device name and platform, pairing request/completion status, Relay address, authorized Node/workspace identifiers, and access and refresh tokens. Credentials are stored in platform secure storage (Android Keystore / iOS Keychain, as provided by the platform and plugin).
- Connection and session data: to show workspaces, sessions, task status, and approval requests, the client sends and receives related session identifiers, titles, status, messages, prompts, replies, and interaction data. This data is sent to the desktop workspace / Node that you pair or select.
- Files and photos you select: the app reads an item only when you choose it through the system picker and send it. Its contents are transferred to the paired workspace / Node. When scanning a pairing QR code, the camera image is used on-device to recognize pairing information and is not uploaded because of scanning.
- Local settings and logs: the app stores necessary connection settings, preferences, and limited session UI state on your device. Runtime protocol logs are generated locally and can be viewed, copied, exported, or cleared in the app; logs may contain connection details or partial device credential fragments, so protect exported logs. The app also stores the most recent crash diagnostic locally (error, stack, time, and app version) for your review and troubleshooting; it is not automatically uploaded.
- Notifications: if enabled, task status notifications may show the number of running tasks. Approval, completion, or failure notifications may include a task title, preview text, or approval title. They are displayed by the device and originate from your connected workspace.
3. How data is transferred and who receives it
The client communicates with your authorized desktop workspace / Node through the Relay you configure. The Relay processes metadata needed for device authorization, pairing, routing, and connectivity, and forwards live session or attachment data. It stores device, pairing, token, and authorization records needed to operate authorization; revocation can invalidate the relevant device or authorization. Server storage, backups, and deletion periods depend on the Relay operator and deployment configuration.
Your workspace / Node receives messages, session interactions, and attachments you send through the app. It may store or further process them according to its own operation. If it is configured to use an AI model provider or another service, that service may receive relevant content under its own terms and privacy policy. KayingCode Mobile itself does not send chat content to advertising, analytics, or crash-reporting SDKs.
The app supports HTTPS/WSS and also permits HTTP/WS addresses that you configure. TLS protects transport only when HTTPS/WSS is used. The app does not provide end-to-end encryption for session content, and the Relay and configured connection services may process data while forwarding it. Prefer a trusted HTTPS/WSS Relay and carefully choose your destination and attachments.
4. Purposes and legal basis
We process the data above only as needed to provide pairing, authentication, connectivity, session interaction, attachment transfer, notifications, troubleshooting, and service security. Necessary data is processed to provide the service you request. Optional permissions and notifications are controlled through your system authorization or app settings.
5. Permissions
- Camera: scans a pairing QR code displayed by the desktop app. You may instead choose a QR image from your photo library.
- Photos and files: system pickers provide access to items you explicitly select for transfer to the paired destination; the app does not scan your entire photo library or file system.
- Notifications, foreground service, and network: support authorized task alerts, background status, and remote connectivity. You can disable notifications or revoke permissions in system settings; some background alerts or connectivity features may then be unavailable.
6. Retention and deletion
Device tokens and credentials are removed according to platform behavior when you remove the relevant connection, clear app data, or uninstall the app. An installation identity may remain for future pairing until app data is cleared or the app is uninstalled. Removing a device in the app attempts to revoke the device and its authorizations on the Relay and clears local credentials. Whether and when historical device or pairing records are physically deleted depends on the Relay administrator; some deployments provide administrators with a way to delete history for revoked devices.
You can clear logs and crash records that the app exposes for clearing in Settings. Chat, files, and session records are generally managed by the paired workspace / Node or services configured there; delete them in those environments. The app has no user account system and therefore no account closure flow. For questions or requests, contact service@kayingai.com and identify the Relay you use. Do not send access tokens or other secret credentials by email.
7. Children and age
KayingCode Mobile is intended for users aged 13 and older and is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child has provided us with personal information, contact us using the email below.
8. Security
The app uses platform secure storage for device credentials and provides device/authorization revocation. Internet transport security depends on the Relay, workspace, and protocol you configure; HTTP/WS connections do not have TLS transport protection. Secure your device and Relay administrator credentials, and revoke devices you no longer use.
9. Changes to this policy
We will update this page and its effective date when product data practices or applicable requirements change. We will provide notice of material changes through appropriate means.
10. Contact
Operator: Beijing Lingdian Badu Technology Co., Ltd. (KayingAI)
Privacy and support: service@kayingai.com
Website: https://kayingai.com