Last updated: August 18, 2026
QuickTUI ("the App") respects and protects user privacy. The App does not use analytics, advertising SDKs, or telemetry.
Most features of the App work without any account. A QuickTUI Cloud account is only needed for the optional cloud subscription features described below.
Connection data stays on your device and on servers you choose. The iOS app stores server profiles locally and stores access tokens in the iOS Keychain. The browser client stores its verified session token and preferences in browser storage on that server origin.
When you use Quick Setup, the SSH password is used to connect to your server and run the installer. It is not saved by QuickTUI.
Your QuickTUI server may process terminal I/O, session metadata, logs, and update checks needed to provide the remote terminal service. That data remains under the server you operate.
If you choose to use QuickTUI Cloud, you sign in with your Apple Account (Sign in with Apple) or Google account. When you sign in, we collect and store:
This data is used only to create and authenticate your QuickTUI Cloud account, link your subscription to it, and prevent abuse.
Cloud subscriptions are purchased through Apple's App Store, and payment is processed by Apple. We never receive your payment card details. To provide the service, we store your subscription plan and status, together with a pseudonymous transaction token that links your App Store purchase to your QuickTUI Cloud account.
When your subscription includes the cloud relay service, we also store the data needed to operate it: your relay IDs, the public keys and fingerprints of the devices you bind to them, relay server assignments, and aggregate usage counters such as transferred bytes and connection counts, used to run the relay and enforce plan limits. Relay traffic itself is end-to-end encrypted between your devices; the relay cannot read your terminal content.
Agent notifications are off on a device until you opt in by granting the operating system notification permission and enabling that device's registration. These two device controls are separate. Each QuickTUI server also has server-wide preferences that separately control whether registered devices receive notifications, which event categories are sent, and which optional fields appear in the notification text.
A server can send notifications for an approval request, a completed task, an Agent error, or an ended Agent session. The notification title identifies QuickTUI and the default message only identifies the event category. If you enable them, the message can also include the Agent type, project name, session name, and a task or error summary. There are no notification-text options for sending full terminal output, source code, credentials, or full prompts or Agent responses. Names and summaries can still contain text supplied by you or an Agent.
Delivering and opening a notification also requires route-only data that is not controlled by the notification-text field switches. This includes the bound device ID, routing mode, event category, notification ID and revision, collapse ID, and sent time, plus Agent runtime, session, and interaction references when the event has them. Oversized session or interaction references are replaced with versioned, domain-separated SHA-256 locators, which the client resolves only against its authenticated server data. The internal Relay request also carries a request ID for retry and deduplication; that request ID stops at the Relay and is not included in the stable payload sent to the device. QuickTUI uses route-only values to address the selected device, deduplicate delivery, find the matching local server profile/session/interaction, and fail safely when the target is stale or ambiguous.
Your QuickTUI server stores its server-wide notification preferences and the push registration for each registered device in its own local state. For delivery, that server briefly sends the selected notification text, route-only data, and the device's push token through QuickTUI Relay to Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM). The Relay notification path does not persist device push tokens or notification payloads. During retries it may keep bounded, short-lived in-memory deduplication state, including Relay and request identifiers, a request hash, lifecycle metadata, and the Relay response; this state does not contain the push token or notification payload. APNs delivers an alert that iOS may display directly when the app is not running. FCM sends a data-only message that the QuickTUI Android app processes before displaying. Apple and Google process the push token and payload under their own platform terms and privacy practices.
You can revoke the operating system notification permission or disable that device's registration at any time. In QuickTUI, you can also disable notifications or individual categories and text fields in each server's server-wide preferences. Removing the last local profile that uses a paired-device credential causes the client to request revocation of that credential's remote push registration; provider-invalid tokens are also removed when reported. Delivery may already be in progress, so these controls cannot retract a notification already accepted by APNs or FCM.
只有你同时授予操作系统通知权限并启用该设备的通知注册后，这台设备上的 Agent 通知才会开启；这两项设备控制彼此独立。每台 QuickTUI server 另有 server-wide 偏好，分别控制已注册设备是否接收通知、发送哪些事件类别，以及通知正文显示哪些可选字段。
server 可以针对待审批、任务完成、Agent 错误或 Agent 会话结束发送通知。通知标题只标识 QuickTUI，默认正文只说明事件类别。你还可以选择在正文中加入 Agent 类型、项目名、会话名及任务或错误摘要。通知正文没有用于发送完整终端输出、源代码、凭据、完整提示词或完整 Agent 回复的字段；但名称和摘要仍可能包含你或 Agent 提供的文字。
投递及打开通知还需要不受正文显示字段开关控制的 route-only 数据，包括已绑定设备 ID、routing mode、事件类别、notification ID 与 revision、collapse ID、发送时间，以及事件具备时的 Agent runtime/session/interaction 引用。过长的 session 或 interaction 引用会替换为带版本且按用途隔离的 SHA-256 locator，客户端只会在已认证的 server 数据中解析它。内部 Relay 请求还会携带用于重试和去重的 request ID；该 ID 到 Relay 为止，不会进入发给设备的稳定 payload。QuickTUI 使用 route-only 数据把通知投递到所选设备、去重，并在本机找到对应的 server profile/session/interaction；目标过期或匹配不唯一时会安全失败。
你的 QuickTUI server 会在自己的本地状态中保存 server-wide 通知偏好及每个已注册设备的 push registration。投递时，该 server 会把所选通知正文、route-only 数据和设备 push token 经 QuickTUI Relay 短暂转发给 Apple Push Notification service（APNs）或 Firebase Cloud Messaging（FCM）。Relay 通知路径不会持久化设备 push token 或 notification payload；重试期间可能短暂保留有界的内存去重状态，包括 Relay 和 request 标识、请求哈希、生命周期元数据及 Relay 响应，但不包含 push token 或 notification payload。APNs 投递 alert，应用未运行时 iOS 也可能直接显示；FCM 投递 data-only message，由 QuickTUI Android 应用处理后显示。Apple 和 Google 会按各自的平台条款与隐私规则处理 push token 和 payload。
你可以随时撤销操作系统通知权限或关闭该设备的通知注册，也可以在 QuickTUI 中通过每台 server 的 server-wide 偏好关闭全部通知、单独类别或正文可选字段。删除使用同一已配对设备凭据的最后一个本地 profile 时，客户端会请求撤销该凭据对应的远端 push registration；provider 报告 token 失效时也会清除该注册。已由 APNs 或 FCM 接受的通知可能正在投递，以上操作无法撤回它。
Account and subscription data is used solely to provide the QuickTUI Cloud service. We do not sell your data or use it for advertising. We do not share it with third parties, except with the infrastructure providers that host the service, or where disclosure is required by law.
Like most online services, our servers keep technical access logs of requests to QuickTUI Cloud, including IP addresses and request metadata. These logs are used only for security, abuse prevention, and troubleshooting, are kept only for a limited time, and are not used for marketing or profiling.
Account and subscription data is retained while your account exists. You can delete your account at any time from within the App using the Delete Account option. Deleting your account permanently removes all data associated with it from our servers, including your account identifier, hashed email, subscription records, and relay data. We may retain minimal security and audit records where required for fraud prevention or legal compliance.
Deleting your account does not cancel an active App Store subscription. To stop billing, cancel the subscription in your Apple Account settings.
All communication with QuickTUI Cloud uses encrypted connections (TLS). Email addresses are stored only as one-way hashes, and authentication tokens are kept in the platform's secure storage on your device.
This privacy policy may be updated on this page.
For privacy questions or requests, visit the Support page or email dualface@gmail.com.