J Shell 隐私政策
J Shell Privacy Policy
一句话版本：J Shell 是一个本地优先的 SSH 客户端。开发者不运营任何服务器，不收集、不上传、不存储你的任何数据，也不向第三方出售数据。你的主机配置、密钥和令牌只保存在你自己的手机里；只有在你主动使用 AI 助手或 GitLab 浏览时，相关请求才会由你的手机直接发往你自己配置的服务。
In one sentence: J Shell is a local-first SSH client. The developer runs no servers and does not collect, upload, store, or sell any of your data. Your host profiles, keys, and tokens stay on your own phone. Data leaves your device only when you actively use the AI assistant or GitLab browsing, and then it goes directly from your phone to services you configured yourself.
一、适用范围
本政策说明 J Shell Android 应用（下称“本应用”）如何处理与你有关的信息。本应用由个人开发者独立开发并发布，本政策中的“我们”指该开发者。
二、我们收集哪些信息
2.1 我们不收集任何信息
本应用没有账号系统，没有开发者运营的服务器或后端接口，也不接入任何统计分析、崩溃上报、广告或用户画像 SDK。具体来说，我们不会收集或上传：
- 你的姓名、邮箱、电话、账号等身份信息（本应用没有注册与登录）；
- 设备标识符（IMEI、Android ID、广告 ID、MAC 地址等）；
- 位置信息、通讯录、短信、通话记录、照片、日历；
- 剪贴板内容（只有你主动点击“粘贴”时，内容才进入终端输入）；
- 你在终端里输入的命令、终端输出、SFTP 浏览过的文件内容（这些只在你手机与你自己连接的服务器之间传输）；
- 应用使用行为、崩溃日志、性能数据（本应用不包含任何此类上报组件）。
2.2 仅保存在你手机上的信息
以下信息写入本应用的私有存储目录（Android app-private storage），其他应用无法读取，也不会上传给我们或任何第三方：
| 信息 | 具体内容 | 用途 | 是否加密 |
|---|---|---|---|
| 主机配置 | 别名、地址（IP/域名）、端口、用户名、认证方式（密码/私钥）、上次连接时间、跳板机、会话保持（tmux）设置 | 让你一键连接常用服务器 | 明文（其中不含任何凭据） |
| 已信任服务器指纹 | 用户名@地址:端口 与服务器公钥的 SHA-256 指纹 |
首次连接时让你核对指纹；指纹变化时阻止连接，防止中间人攻击 | 明文（公钥指纹不属于敏感信息） |
| 应用设置 | 主题、终端字号、指纹锁开关、会话保持默认开关、隐藏页面开关 | 记住你的界面偏好 | 明文 |
| AI 助手设置 | 服务商（OpenAI / DeepSeek）、模型名称、API Key | 调用你选择的 AI 服务 | API Key 使用 Android Keystore 的 AES-GCM 加密（密钥存放在系统密钥库中，不写入应用数据） |
| GitLab 设置 | 实例地址、登录用户名、服务端版本缓存、访问令牌与刷新令牌、你粘贴的内部 CA 证书、是否允许明文 http 的确认标记、令牌到期时间 | 免去每次重新登录 | 访问令牌与刷新令牌加密（同上）；地址、用户名、CA 证书为明文 |
| 端口转发规则 | 转发类型（-L/-R）、本地端口、目标地址与端口、监听范围 |
连接后自动建立隧道并在重连后恢复 | 明文 |
| 你从远端保存的文件 | 通过系统文件选择器保存的 SFTP 文件 | 把远端文件保存到本机 | 保存在你选择的位置，本应用不会保留访问权限 |
2.3 只在内存中短暂存在、绝不写入存储的信息
- SSH 登录密码、私钥口令、跳板机密码；
- 你选择或粘贴的 SSH 私钥内容（使用后立即在内存中清零）；
- GitLab 账号登录密码（仅用于向你自己的 GitLab 实例换取令牌，换取后立即丢弃）。
这些内容不会落盘、不会上传、也不会在应用重启后保留。
2.4 系统调试日志
本应用在开发调试中会写入 Android 系统日志（logcat）。这些日志只留在你的设备上，由 Android 系统管理并按系统策略轮转清除，不会被写入文件、不会发送给我们。日志中可能出现服务器地址或命令片段，若你与他人共享设备日志，请注意其中可能包含此类信息。
2.5 云备份与换机迁移
本应用已在清单中关闭 Android 自动备份（allowBackup=false），并在数据提取规则中排除了全部数据域。因此上述数据不会进入 Google 云备份，不会随换机迁移到其他设备——你的配置与令牌只存在于当前这台设备上。
三、这些信息用来做什么
我们使用上述保存在你设备上的信息，只用于实现应用功能本身：连接你指定的服务器、校验服务器身份、记住你的界面偏好、在你授权后调用 AI 服务、访问你的 GitLab 实例、建立你配置的端口转发隧道。我们不做用户画像、不做广告投放、不做与功能无关的任何用途。
四、你的数据会发送到哪里（是否分享给第三方）
我们不向任何第三方出售、出租或交换你的数据。数据只有在你主动使用相应功能时，才会由你的手机直接发往以下对象：
4.1 你自己指定的 SSH 服务器（必需功能）
你连接的主机地址、用户名与认证凭据，以及你输入的命令与终端输出，都会在你的手机与你自己填写的服务器之间通过 SSH 加密传输。这些数据由该服务器的管理者（通常就是你本人或你的公司）控制与留存，与我们无关。
4.2 AI 助手（默认关闭，需要你自行填入 API Key）
只有你在设置中填入 OpenAI 或 DeepSeek 的 API Key 并主动发起对话时，本应用才会把以下内容通过 HTTPS 发送给你选择的服务商：
- 你在对话框里输入的文本；
- 模型给出的命令（在你点击“执行”后于远端服务器上运行）；
- 这些命令的执行结果（标准输出、标准错误、退出码，超出长度上限的部分会被截断）。
发送的端点固定为 https://api.openai.com/v1/responses（OpenAI）或 https://api.deepseek.com/responses（DeepSeek），不经过我们的任何服务器。本应用不会把主机配置、密码、私钥、令牌、终端历史缓冲区发送给 AI 服务商。对话内容不会被本应用保存在设备上，仅在当前会话的内存中保留，退出会话即消失（这也是“停止”按钮会重置上下文的原因）。
这些内容一旦发送，即由该服务商按其隐私政策处理（可能包括存储与人工审阅），并可能被传输到你所处国家/地区以外的服务器。请在使用前阅读并确认你接受其政策：
- OpenAI：https://openai.com/policies/privacy-policy
- DeepSeek：https://cdn.deepseek.com/policies/zh-CN/deepseek-privacy-policy.html
如果你不希望任何数据离开设备，请不要配置 AI 助手——除此之外的功能都不需要它。
4.3 GitLab 浏览（需要你填写实例地址）
请求由你的手机直接发往你自己填写的 GitLab 实例（公司自建实例或 gitlab.com），并携带你提供的访问令牌。若你选择“用 GitLab 账号登录”，你的用户名与密码只会发送给该实例的 /oauth/token 接口，用于换取访问令牌；密码不会保存在本应用。本应用对 GitLab 的请求全部为只读的 GET 请求（唯一的 POST 是上述登录换取令牌）。
出于兼容内网自建实例的需要，本应用允许 http:// 地址，但必须由你在设置页显式勾选确认才会生效（明文传输意味着同一网络中的其他人可能看到这些请求，建议优先使用 https）。请求内容会进入该实例的服务器访问日志，由实例管理者控制。
4.5 应用内购买（Pro 一次性解锁）
本应用的 Pro 一次性解锁属于应用内购买，由 Google Play 完成全部交易与支付流程：
- 我们不接触、不存储你的任何支付信息（卡号、账单地址等都不经过本应用）；退款、税率、发票与账单问题由 Google Play 按其政策处理；
- 购买状态只以“是否已解锁”这一个布尔标记保存在你的手机本地（与主机配置同一个应用私有目录），不上传、不与任何账号绑定，我们也没有你的购买记录；
- 换机或重装后，用同一个 Google 账号可在应用内点「恢复购买」重新解锁（该查询由 Google Play 完成）；
- 免费版与 Pro 版的数据处理方式完全相同：无论是否购买，本应用都不收集、不上传你的任何数据（见第二节）。
除 Google Play 的内购结算外，本应用没有任何订阅、没有自动续费、也不接入任何第三方支付或广告 SDK。
4.4 应用分发渠道
本应用通过 Google Play 分发。Google 作为分发平台可能按其自身政策收集安装与设备相关信息（例如用于更新与安全）。这属于 Google 的行为，不在本应用的控制范围内，详见 Google 的隐私政策。
五、应用申请的权限及用途
| 权限 / 能力 | 用途 |
|---|---|
INTERNET | 连接你指定的 SSH/SFTP 服务器、AI 服务商与 GitLab 实例。这是本应用唯一必需的网络权限 |
ACCESS_NETWORK_STATE | 读取网络连通状态，用于断线后的自动重连与恢复端口转发 |
FOREGROUND_SERVICE、FOREGROUND_SERVICE_SPECIAL_USE | 在你切换到其他应用时保持 SSH 会话与隧道不被系统回收；同时显示一条常驻通知，通知中可返回终端或断开连接 |
POST_NOTIFICATIONS（Android 13+） | 显示上述会话通知。拒绝授权只影响通知可见性，不影响功能 |
生物识别（androidx.biometric） | 可选的应用锁。指纹或设备 PIN/密码的比对完全由 Android 系统完成，本应用只能收到“验证成功/失败”，无法接触、读取或存储任何生物特征数据 |
| 系统文件选择器（SAF） | 选择 SSH 私钥文件、导入 OpenVPN 配置、把远端文件保存到本机。本应用不需要也不申请存储权限，只能访问你明确选中的那个文件 |
com.android.vending.BILLING | 应用内购买 Pro 一次性解锁（由 Google Play 结算，见 4.5）。该权限只用于查询与发起购买，本应用不读取任何支付信息 |
BIND_VPN_SERVICE（当前版本未启用） | 见第八节 |
除上述权限外，本应用不申请任何其他权限。
六、数据如何保存与保护
- 不落盘原则：密码、私钥与私钥口令从不写入存储，使用后在内存中清零；
- 系统级加密：API Key、GitLab 访问令牌与刷新令牌使用 Android Keystore 中的密钥做 AES-GCM 加密，密钥不离开系统密钥库；
- 应用私有目录：配置文件只保存在本应用的私有存储中，其他应用无法访问；
- 关闭备份：不参与云备份与换机迁移，减少数据外泄面；
- 默认最小暴露：端口转发默认只监听
127.0.0.1（仅本机可访问），选择对同网络开放时界面会明确警告； - 传输加密：SSH、AI 服务商与 https 的 GitLab 通信均加密传输；明文 http 仅在你显式确认后可用；
- 不引入第三方 SDK：应用内没有广告、统计或跟踪组件，不存在第三方从应用内采集数据的通道。
同时请理解技术上的固有边界：本应用无法保护已经离开手机的数据——你在你自己服务器上的命令记录、你使用 AI 服务商时其留存的内容、你所在 GitLab 实例上的访问日志，都由对应服务的运营方控制。此外，已被 root 或植入恶意软件、或使用了不安全锁屏的设备，本应用的保护措施可能失效。连接凭据的安全性最终取决于你所连接服务器的安全性与你的设备安全。
七、数据保留多久、如何删除
保留期限：保存在你设备上的信息会一直保留，直到你主动删除或卸载应用。我们不做任何异地留存，因此没有“服务器端的你”。
你自己即可完成的删除方式：
| 想删除什么 | 在哪里删 |
|---|---|
| 某台主机的配置 | 首页该主机卡片右侧菜单（⋮）→ 删除 |
| 已信任的服务器指纹 | 首页顶栏“更多” → 信任服务器管理 → 逐个移除 |
| AI 的 API Key、模型设置 | 设置 → AI 助手 → 清空密钥并保存 |
| GitLab 访问令牌与刷新令牌 | GitLab 连接设置 → 清空「访问令牌」并保存（令牌即从设备删除，应用退回匿名浏览公共项目） |
| 某台主机的端口转发规则 | 会话工具 → 端口转发 → 点规则上的删除图标 |
| 全部数据 | 卸载应用，或在系统“应用信息”中执行“清除数据” |
卸载即彻底删除：由于本应用不参与云备份，卸载后上述数据不会在任何地方留下副本，也无法恢复。应用内没有单独的“清除全部设置”按钮；上表之外的非敏感本地数据（例如 GitLab 实例地址、内部 CA 证书、界面偏好）可在系统“应用信息 → 清除数据”或卸载应用时一并删除。
第三方侧的数据：若你要删除 AI 服务商或 GitLab 实例上留存的内容，需要按对应服务商的政策在其账号设置中操作；你也可以随时在服务商处吊销（revoke）API Key 或访问令牌，使本应用再也无法访问该服务。
八、关于 VPN（当前版本）
本版本不提供 VPN 功能，应用内没有 VPN 连接入口，也不会创建、转发或收集任何网络流量。为便于将来恢复该功能，安装包内保留了相关代码与系统声明（BIND_VPN_SERVICE），但在当前版本中它不会被启动、不会申请系统 VPN 授权，也不会处理你的任何流量。若未来的版本重新开放该入口，我们会在本政策中明确说明（届时隧道仍只在你自己的设备与你配置的目标网络之间建立，不经过我们的服务器），并在更新说明中告知。
九、儿童
本应用是面向开发者与运维人员的服务器管理工具，不面向儿童，也不会有意收集儿童（不满 14 周岁）的任何个人信息。由于本应用不收集任何个人信息，若你认为有儿童在未经监护人同意的情况下向我们提供了信息，请联系我们，我们会协助处理（实际上我们没有任何此类数据可删除）。
十、本政策的变更
我们可能随功能变化更新本政策。更新后的版本会发布在同一网址上，并更新顶部的“最近更新”日期。若变更涉及你数据的处理方式（例如未来开放 VPN 入口或引入新的第三方服务），我们会在应用内或商店更新说明中显著提示。继续使用更新后的应用，即表示你接受更新后的政策。
十一、联系我们
对本政策或你的数据有任何疑问、意见或删除请求，请联系：邮箱 mayuluck021@gmail.com（我们通常会在 7 个工作日内回复）。
1. Scope
This policy explains how the J Shell Android app (“the app”) handles information about you. The app is built and published by an individual developer; “we” below means that developer.
2. What we collect
2.1 We collect nothing
The app has no accounts, no developer-run server or backend, and no analytics, crash-reporting, advertising, or profiling SDK. In particular, we do not collect or upload:
- your name, email, phone number, or any account identity (there is no sign-up);
- device identifiers (IMEI, Android ID, advertising ID, MAC address);
- location, contacts, SMS, call logs, photos, or calendar;
- clipboard contents (text enters the terminal only when you tap Paste yourself);
- the commands you type, terminal output, or the contents of files you browse over SFTP — these travel only between your phone and the servers you connect to;
- usage analytics, crash logs, or performance data (the app contains no such component).
2.2 Information stored only on your phone
The following is written to the app’s private storage on your device. Other apps cannot read it, and it is never uploaded to us or to any third party:
| Information | Contents | Purpose | Encrypted? |
|---|---|---|---|
| Host profiles | Alias, address (IP/domain), port, username, authentication type (password/key), last-connected time, jump host, tmux settings | One-tap connections to your servers | Plain text (contains no credentials) |
| Trusted server fingerprints | user@host:port plus the SHA-256 fingerprint of the server’s public key |
Lets you verify a server on first connect and blocks a connection when the key changes (man-in-the-middle protection) | Plain text (a public-key fingerprint is not sensitive) |
| App settings | Theme, terminal font size, biometric-lock toggle, session keep-alive default, hidden-page toggle | Remembers your preferences | Plain text |
| AI assistant settings | Provider (OpenAI / DeepSeek), model name, API key | Calls the AI service you chose | API key encrypted with AES-GCM using a key held in the Android Keystore |
| GitLab settings | Instance URL, sign-in username, cached server version, access and refresh tokens, an internal CA certificate you pasted, your explicit acknowledgement of cleartext http, token expiry | Avoids re-authenticating every time | Access and refresh tokens encrypted as above; URL, username, and CA certificate in plain text |
| Port-forwarding rules | Type (-L/-R), local port, target address and port, bind scope |
Establishes tunnels on connect and restores them after a reconnect | Plain text |
| Files you save from a remote host | SFTP files saved via the system file picker | Store a remote file locally | Written to the location you pick; the app keeps no access to it |
2.3 Kept in memory only, never written to storage
- SSH passwords, private-key passphrases, and jump-host passwords;
- Any SSH private key you select or paste (zeroed in memory right after use);
- Your GitLab account password (used only to exchange for a token at your own GitLab instance, then discarded).
None of this is persisted, uploaded, or retained after the app restarts.
2.4 System debug logs
For development the app writes to the Android system log (logcat). Those logs stay on your device, are managed and rotated by Android, are never written to a file, and are never sent to us. They may contain server addresses or command fragments, so treat a shared device log accordingly.
2.5 Cloud backup and device transfer
The app disables Android auto-backup (allowBackup=false) and excludes every data domain in its data-extraction rules. Nothing listed above enters Google cloud backup or moves to another device during a transfer — your configuration and tokens exist only on this device.
3. What the information is used for
The information stored on your device is used solely to provide the app’s features: connecting to servers you specify, verifying server identity, remembering your preferences, calling an AI service you enabled, reaching your GitLab instance, and running the tunnels you configured. We do not profile you, serve ads, or use your data for anything unrelated to these features.
4. Where your data goes (third-party sharing)
We never sell, rent, or trade your data. Data leaves your phone only when you actively use a feature, and then it goes directly to:
4.1 Your own SSH servers (core feature)
The host address, username, and credentials you enter, along with the commands you type and the terminal output, travel between your phone and the server you configured, encrypted by SSH. That data is controlled and retained by the operator of that server (usually you or your employer), not by us.
4.2 AI assistant (off by default; requires your own API key)
Only after you enter an OpenAI or DeepSeek API key in Settings and start a conversation does the app send the following over HTTPS to the provider you selected:
- the text you type in the chat box;
- the commands the model proposes (run on the remote server after you tap Execute);
- the results of those commands (stdout, stderr, exit code; longer output is truncated).
Requests go to https://api.openai.com/v1/responses (OpenAI) or https://api.deepseek.com/responses (DeepSeek), never through a server of ours. The app does not send host profiles, passwords, private keys, tokens, or the terminal scrollback buffer to the AI provider. Chat content is not stored on your device by the app: it lives in memory for the current session only and disappears when the session ends (which is also why the Stop button resets the context).
Once sent, that content is handled under the provider’s own privacy policy (which may include storage and human review) and may be transferred to servers outside your country or region. Please read their policies before enabling this feature:
- OpenAI: https://openai.com/policies/privacy-policy
- DeepSeek: https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html
If you do not want any data to leave your device, simply do not configure the AI assistant — every other feature works without it.
4.3 GitLab browsing (requires your instance URL)
Requests go from your phone directly to the GitLab instance you enter (a self-hosted instance or gitlab.com) and carry the access token you supplied. If you choose “sign in with a GitLab account”, your username and password are sent only to that instance’s /oauth/token endpoint to obtain a token; the password is not stored by the app. All repository requests are read-only GET requests (the only POST is that sign-in exchange).
For self-hosted intranet instances the app permits http:// addresses, but only after you explicitly tick the acknowledgement in Settings (cleartext means others on the same network may see those requests; prefer https). Requests appear in that instance’s server access logs, which its administrator controls.
4.5 In-app purchase (the one-time Pro unlock)
The one-time Pro unlock is an in-app purchase, and Google Play handles the entire transaction and payment flow:
- We never see or store any payment information (card numbers and billing addresses never reach this app). Refunds, taxes, invoices and billing questions are handled by Google Play under its own policies;
- The purchase state is a single boolean flag (“unlocked or not”) stored locally on your phone, next to your host configuration. It is not uploaded and not tied to any account of ours — we hold no record of your purchase;
- After switching devices or reinstalling, tap “Restore purchase” in the app to unlock again with the same Google account (the lookup is performed by Google Play);
- The free and Pro versions handle data identically: purchased or not, the app collects and uploads nothing (see section 2).
Apart from Google Play billing, there are no subscriptions, no auto-renewals, and no third-party payment or advertising SDKs in this app.
4.4 Distribution channel
The app is distributed via Google Play. As the distributor, Google may collect install- and device-related information under its own policies (for example, for updates and security). That is Google’s processing, outside this app’s control; see Google’s privacy policy.
5. Permissions and why they are needed
| Permission / capability | Purpose |
|---|---|
INTERNET | Connect to the SSH/SFTP servers, AI providers, and GitLab instances you specify. The app’s only mandatory network permission |
ACCESS_NETWORK_STATE | Read connectivity so sessions and tunnels can recover after a network switch |
FOREGROUND_SERVICE, FOREGROUND_SERVICE_SPECIAL_USE | Keep an SSH session or tunnel alive while you use other apps, with a persistent notification that can return to the terminal or disconnect |
POST_NOTIFICATIONS (Android 13+) | Shows that session notification. Denying it only hides the notification; nothing else breaks |
Biometrics (androidx.biometric) | Optional app lock. Fingerprint or device PIN/password verification is performed entirely by Android; the app only learns success or failure and can never access, read, or store biometric data |
| System file picker (SAF) | Pick an SSH private key, import an OpenVPN profile, or save a remote file locally. The app requests no storage permission and can only access the exact file you select |
com.android.vending.BILLING | In-app purchase of the one-time Pro unlock, billed by Google Play (see 4.5). Used only to query and start a purchase; the app never reads payment details |
BIND_VPN_SERVICE (not active in this version) | See section 8 |
No other permissions are requested.
6. How data is stored and protected
- Nothing sensitive is persisted: passwords, private keys, and passphrases are never written to storage and are zeroed in memory after use.
- System-backed encryption: API keys and GitLab access/refresh tokens are encrypted with AES-GCM using a key held in the Android Keystore, which never leaves the system key store.
- Private storage: configuration lives in the app’s private directory, unreadable by other apps.
- Backup disabled: no cloud backup or device transfer, which shrinks the exposure surface.
- Minimal exposure by default: tunnels listen on
127.0.0.1only unless you deliberately expose one to your local network, and the UI warns you when you do. - Encrypted transport: SSH, AI providers, and https GitLab traffic are all encrypted; cleartext http requires your explicit acknowledgement.
- No third-party SDKs: there are no ads, analytics, or tracking components, so no third party can collect data from inside the app.
Please also note the inherent limits: the app cannot protect data that has already left your phone — command history on your own servers, content retained by an AI provider, and access logs on your GitLab instance are all controlled by those service operators. On a rooted or malware-infected device, or one with an insecure lock screen, these protections may fail. The security of your credentials ultimately depends on the security of the servers you connect to and of your device.
7. Retention and deletion
Retention: information on your device is kept until you delete it or uninstall the app. We keep no copy anywhere else, so there is no server-side “you”.
How to delete it yourself:
| To delete | Where |
|---|---|
| A host profile | Home screen → the host card’s menu (⋮) → Delete |
| Trusted server fingerprints | Home top bar → More → Trusted servers → remove each entry |
| AI API keys and model settings | Settings → AI assistant → clear the key and save |
| GitLab access and refresh tokens | GitLab connection settings → clear the access token field and save (the tokens are then deleted from the device and the app falls back to anonymous browsing of public projects) |
| A host’s port-forwarding rules | Session tools → Port forwarding → the delete icon on the rule |
| Everything | Uninstall the app, or use “Clear data” in Android’s App info |
Uninstalling deletes everything: because the app is excluded from cloud backup, no copy of this data survives anywhere, and it cannot be recovered. There is no single “clear all settings” button; the remaining non-sensitive local data (for example the GitLab instance URL, an internal CA certificate, and UI preferences) goes away with Android’s “Clear data” or by uninstalling the app.
Data held by third parties: to delete content retained by an AI provider or a GitLab instance, use that provider’s own account controls. You can also revoke your API key or access token at any time, after which the app can no longer reach that service.
8. About VPN (current version)
This version provides no VPN functionality: there is no VPN entry point in the app, and it does not create, route, or collect any network traffic. To make a future re-enablement easier, the related code and system declaration (BIND_VPN_SERVICE) remain in the package, but in this version they are never started, never request system VPN consent, and never handle your traffic. Should a future version re-open that entry point, we will say so explicitly in this policy (the tunnel would still run only between your device and the target network you configure, never through our servers) and in the release notes.
9. Children
The app is a server-management tool for developers and operators. It is not directed to children and does not knowingly collect any personal information from children (under 14). Because the app collects no personal information at all, there is nothing for us to delete; if you believe a child has provided us information, contact us and we will help.
10. Changes to this policy
We may update this policy as the app changes. The updated version will be published at the same URL with a new “Last updated” date. If a change affects how your data is handled (for example, re-enabling the VPN entry point or adding a new third-party service), we will highlight it in the app or in the store release notes. Continuing to use the updated app means you accept the updated policy.
11. Contact us
For any question, concern, or deletion request regarding this policy or your data: email mayuluck021@gmail.com (we normally reply within 7 business days).