本隐私政策(以下简称「本政策」)适用于本应用及其随附的网络扩展组件。本政策说明本应用在何种情形下处理何种信息、处理的目的与方式、信息的存储位置与留存期限,以及您就此享有的权利。请您在使用本应用前完整阅读本政策。
1.1 「本应用」指本网络代理客户端软件,包括其主程序与随附的网络扩展(NetworkExtension)组件。
1.2 「开发者」指本应用的开发与发布主体,即本政策项下信息处理活动的责任主体。开发者为本应用运营的服务端,仅有第 4.2 条第(12)项所述的识别码解析服务与第 1.6 条所述的演示服务商;本应用不会在您未作出相应选择的情况下主动连接它们。
1.3 「服务提供者」指向您提供代理或者网络接入服务的主体,即您在本应用中配置的订阅地址或者输入的服务商识别码所指向的主体。
1.4 「个人信息」指以电子或者其他方式记录的、能够单独或者与其他信息结合识别特定自然人身份或者反映特定自然人活动情况的各种信息。
1.5 「服务商识别码」指由服务提供者分发给其用户的一串字符,用于在本应用内查询该服务提供者的登录入口(面板地址)。
1.6 「演示服务商」指由开发者运营、仅供演示与审核使用的服务提供者,其对信息的处理方式见第 4.2 条第(13)项。
2.1 本应用不收集的信息
本应用不收集下列信息:
(1)姓名、出生日期、身份证件号码、电话号码等可直接或间接识别您身份的个人信息;
(2)用于广告投放或者跨应用跟踪的设备标识符;
(3)您经由本应用访问的网址、域名、目标服务器地址、连接发起时间、连接持续时长等访问记录与连接元数据;
(4)经由隧道传输的任何流量内容。
本应用不设置自有账户体系,不要求您向开发者注册或登录。除第 4.2 条第(12)项所述的识别码解析服务,以及您输入演示识别码时访问的第 1.6 条所述演示服务商外,本应用不与任何由开发者为本应用运营的服务器通信。本应用未集成任何第三方统计分析、广告或崩溃采集软件开发工具包(SDK)。
2.2 您在设备上提供或生成的信息
您在使用本应用的过程中可能输入、导入或生成下列信息:订阅地址、线路配置信息(包括您手动添加或扫码添加的单条线路),以及订阅地址与线路链接中通常内嵌的访问凭据(如令牌、UUID、密码等);您在设置中填写的受信任 Wi-Fi 名称、DNS 服务器与本地域名映射、规则集地址与分流规则。
上述信息由本应用在您的设备本地处理与存储,存储方式见第 5 条。其中,服务商识别码仅依第 4.2 条第(12)项发送至识别码解析服务;订阅地址、账号邮箱与密码等仅依第 4.2 条发送至您所选择的服务提供者。除此之外,本应用不向开发者传输上述信息。
若您选择以「服务商识别码」添加订阅,您还会输入该识别码,以及您在该服务提供者处的账号邮箱与密码。密码仅用于向该服务提供者的面板发起登录请求,本应用不保存密码;识别码、登录成功后由该面板签发的令牌、账号邮箱,以及该服务提供者对订阅内容加密时为您单独签发的订阅解密钥匙,存储于本设备的钥匙串,见第 5.1 条第(4)项。识别码的处理见第 4.2 条第(12)项,面板登录、账户信息与订阅解密钥匙的处理见第 4.2 条第(13)项。
本应用于「订阅」页订阅卡的菜单与「设置 → 当前订阅」页内提供「复制订阅地址」操作。该操作由您主动发起,本应用不会自动执行;经由该操作写入系统剪贴板的内容已被限定为仅在本机可用(不经由「接力」等功能同步至您的其他设备),并设定十分钟后自动失效。请注意,订阅地址通常内嵌访问凭据,效力等同于密码。上述操作不适用于以服务商识别码添加的订阅:此类订阅的订阅地址不在界面中显示。
2.3 本地诊断日志
为便于您自行排查连接故障,本应用会在您的设备本地写入运行日志。除隧道建立情况与内核错误信息外,该日志还包含由内核记录的逐条连接记录,其内容包括目标主机名或者 IP、端口、所使用的出站线路以及失败原因。该日志:
(1)仅存储于您设备的本地容器内,不会由本应用自动上传至开发者或者任何第三方;
(2)在本应用内查看或者导出该日志时,逐条连接记录中的目标主机名与 IP 将被替换为占位符,端口、出站线路与失败原因予以保留。即:您主动分享出去的内容不含前述目标地址,而设备本地留存的原始文件仍然包含;
(3)按写入方与内容分别清除:隧道进程写入的内核日志(含轮转产生的副本,其中包含逐条连接记录)在每次发起连接时删除;隧道进程自身的运行日志(仅记录隧道建立、网络切换、启动与停止等事件,不包含连接记录)在每次发起连接时滚存,设备上保留上一次连接的一份;本应用主进程写入的内核日志在每次重新开启日志(应用启动、以及每次连接前测速)时删除;连接前测速的记录每轮覆盖写入。即含连接记录的日志始终仅保留最近一次;移除任何一条订阅时,或者本机保存的订阅凭据文件损坏而无法解读时,上述日志一并删除;
(4)随本应用被卸载而一并删除。
本应用于「活动」页内提供「诊断日志」功能,供您查阅上述日志。您可在该页面主动执行下列操作,该等操作均由您发起,本应用不会自动执行:
(1)复制:日志文本将写入您设备的系统剪贴板。本应用已将该项内容限定为仅在本机可用(不经由「接力」等功能同步至您的其他设备),并设定十分钟后自动失效。
(2)导出:本应用在您设备的临时目录内生成一份日志文件,以供您通过系统分享功能发送。该文件在分享界面关闭后即由本应用删除。
若您为获得技术支持而主动将该日志发送给开发者,该行为属于您的主动提供,其内容与范围由您自行决定。日志内容可能包含您所配置的线路地址与服务器域名,建议您在发送前自行查阅。
2.4 相机与照片
本应用提供扫描二维码添加订阅或线路的功能:
(1)相机:仅在您打开扫码页面时使用,用于在设备本地识别二维码;画面不被保存、不被上传,本应用切到后台时即停止使用相机。
(2)照片:您可以选择一张图片识别其中的二维码。该功能使用系统提供的照片选择器,本应用无法访问您的相册,只能读取您选中的那一张图片;该图片在设备本地识别后即被丢弃。
(3)识别出的订阅或线路须经您在确认页面确认后才会添加,本应用不会因扫码而自动连接。
2.5 设备本地的记录与显示
为实现相应功能,本应用在您的设备本地保存或显示下列信息,均不向开发者传输:
(1)流量记录:隧道进程按天累计经由本应用的流量字节数(区分直连与经线路两类),最多保留 90 天,不含任何域名、地址或线路名称。您可在「活动」页的「流量记录」中「清除记录」。
(2)线路名单:最近使用与收藏的线路,以及测速最快的若干线路(用于「自动」线路的排序)。仅保存线路名称及其先后顺序;按订阅分开保存,以订阅地址的摘要值区分,不保存订阅地址本身;移除该订阅时一并删除。
(3)实时活动(默认关闭):开启后,连接建立的时刻、最近一次确认连接仍在的时刻以及线路名称(可设置为不显示)将显示在锁屏与灵动岛上,因而也可能显示在与本设备配对的 Apple Watch、Mac 或者车载设备上,且无需解锁即可看到。本应用在后台时无法得知连接的变化,因此该显示只写明最近一次确认的时刻;您在锁屏、控制中心、小组件或者快捷指令中断开连接时,它会更新为已断开。
(4)通知:本应用仅发送设备本地通知,包括订阅到期提醒,以及开启「断线提醒」(默认关闭)后,由隧道进程在连接意外断开或者自动重连被暂停时发出的提醒。通知内容不包含线路名称、服务器地址或者订阅地址;订阅到期提醒只显示到期日期。
(5)小组件与控制中心:您添加的主屏幕与锁屏小组件、控制中心控件会显示连接状态与线路名称(部分小组件还显示连接时长与流量)。锁屏小组件与控制中心无需解锁即可看到。
(6)最近一次测速结果:测速结束后,本应用在设备本地保存一份最近的测速结果,包括线路名称、测得的延迟(毫秒)与测得的时间,并以订阅地址的摘要值区分订阅,不保存订阅地址本身。该结果仅用于在您 30 分钟内再次打开本应用时先行显示上次的结果,不被上传;超过 30 分钟后不再用于该显示,并在本应用下次启动时删除;您更换或者移除订阅时一并删除。网络诊断测得的结果不在此列(见第 4.2 条第(8)项)。
3.1 第 2.2 条所述信息,仅用于在您的设备本地建立与维持网络连接、解析与更新您所配置的订阅内容、按您的设置选择线路,以及在界面中呈现线路与账户信息;其中服务商识别码仅用于第 4.2 条第(12)项所述查询,面板登录令牌仅用于第 4.2 条第(13)项所述请求,订阅解密钥匙仅用于在您的设备本地解密该服务提供者发来的订阅内容。第 2.4 条所述信息仅用于识别您扫描的二维码;第 2.5 条所述信息仅用于向您呈现相应内容。
3.2 第 2.3 条所述信息,仅用于您本人对连接故障的排查。
3.3 本应用不将上述任何信息用于自动化决策、广告投放或者跨应用跟踪,亦不将其用于本政策载明目的之外的用途。
4.1 第三方软件开发工具包
本应用未集成任何第三方统计分析、广告或崩溃采集 SDK,不因该等目的向任何第三方共享信息。
4.2 服务提供者
(1)订阅更新:当您导入订阅或者请求更新订阅时,本应用按您所配置的订阅地址向相应服务提供者发起请求。对开启了「自动更新」的每一条订阅,本应用在回到前台时按其更新间隔,逐条向其订阅地址发起请求,包括当前未在使用的订阅。该地址通常内嵌您的访问凭据,该服务提供者因此可获知您的 IP 地址、请求时间及客户端类型。上述信息流由订阅机制本身决定。
(2)流量传输:连接建立后,您的网络流量经由您所选择的服务提供者的服务器传输;本应用自身不设任何中转服务器。
(3)责任划分:服务提供者对其所获信息的处理适用其自身的隐私政策,不受本政策约束,开发者不就此作出任何陈述或者担保。请您仅配置您信任的服务地址。
(4)首次启动连通性探测:本应用在首次启动时,向 Apple 的连通性检测地址(captive.apple.com)发起一次 HEAD 请求。该请求不携带任何设备标识、账户信息或者您的配置内容,其唯一目的是让操作系统在此时弹出无线数据访问授权(部分机型),以免该授权在您首次导入订阅或者发起连接时中途弹出而导致该次操作失败。该探测在本应用的每次安装中仅执行一次,其结果不被记录、不被上报,亦不影响本应用的任何行为。
(5)设备时钟校正:部分线路协议要求客户端与服务器的时间相差在数十秒以内,设备时钟不准会使该等线路全部无法连接。为此本应用在下列三种情形下查询外部时间源,仅用于计算本设备时钟与标准时间的偏差:① 连接前测速与发起连接之前(以及开启第(7)项所述功能后的每次冷启动时),向公共 NTP 服务(默认 time.apple.com)查询一次;② 上述查询失败时,改向 cloudflare.com、apple.com、microsoft.com 三个站点发起 HEAD 请求,读取应答头中的标准时间并取一致值;③ 连接建立后,隧道进程按固定间隔(默认 30 分钟)以及在设备唤醒、网络切换或者系统时间变更时,再次向同一 NTP 服务查询。上述请求均不携带任何设备标识、账户信息或者您的配置内容;相应服务可获知您的 IP 地址与请求时间。查询结果仅在设备本地用于校正时间偏差,不被上报。
(6)线路测速与健康检查:您发起测速时,本应用经由每条线路访问测速目标(内核内置的检测地址,或者您在「设置 → 测速设置」中填写的第一条有效地址)以测量延迟。选择「自动」线路或者开启备用订阅后,隧道进程经由线路访问 http://www.gstatic.com/generate_204 进行健康检查:选择「自动」线路后,在有流量时约每 10 分钟对当前订阅中最多 25 条线路检查一次。为某一份订阅开启「主订阅不可用时使用」后,隧道进程在有流量时约每 2 分钟检查一次,并在当前线路不可用时经由该备用订阅的服务器转发您的流量,即您的流量可能经由另一家服务提供者的服务器传输。上述健康检查在发起连接或者重新载入配置时也各执行一次。
(7)启动时自动选线路(默认关闭):开启后,本应用在每次冷启动且未连接时,执行一次第(5)项所述的时钟校正,并对当前订阅的线路测速一次,以选出一条线路;本应用不会因此自动连接。
(8)网络诊断:仅在您点击「开始诊断」时,本应用向 Apple 的连通性检测地址(captive.apple.com)发起一次 HEAD 请求,并对当前所选线路测速一次。诊断结果仅保存在内存中,不写入设备存储,不被上报。
(9)规则集:仅在您添加或者更新规则集时,本应用向您填写的规则集地址发起请求,以下载规则列表;该地址的提供者可获知您的 IP 地址与请求时间。下载内容转换后仅保存在设备本地。
(10)域名解析:本应用使用的 DNS 服务器(默认 Cloudflare 与阿里 DNS,可在「设置 → DNS」中更改)在处理解析请求时,可获知被查询的域名与发出请求的 IP 地址。
(11)苹果推送线路探测:开启「包含苹果推送服务」(默认开启)时,连接建立后,隧道进程分别经由线路与直连向 Apple 的连通性检测地址(http://captive.apple.com/hotspot-detect.html)发起小型 HTTP 请求,以决定苹果推送走线路还是直连。该探测在发起连接或者重新载入配置时执行一次,此后仅在有推送连接发生时执行。请求不携带任何设备标识、账户信息或者您的配置内容;Apple 可获知发出请求的 IP 地址与请求时间。
(12)识别码解析:当您输入服务商识别码并点击「查询」时,本应用将该识别码发送至由开发者运营、托管于 Cloudflare 的识别码解析服务(Cloudflare 作为基础设施提供方会处理该请求),以查询该识别码对应的服务提供者的面板地址与名称,以及该服务提供者登记的接口路径与是否对订阅内容加密。查询成功后,若该服务提供者设有图标,本应用会随即向识别码解析服务请求一次该图标(同样只带识别码与 IP),此后不再重新请求;图标保存在本机。该服务仅收到识别码与发起请求的 IP 地址,不收到任何设备标识、账户信息或者您的配置内容。该服务不记录、不留存识别码与 IP 地址;IP 地址仅以哈希形式、在约一分钟的时间窗内用于限制查询频率以防滥用,该哈希值在约一至两分钟后即失效。该请求仅由您点击「查询」触发;本应用在其它任何时刻均不与该服务通信。
(13)面板登录与账户信息:您以服务商识别码添加订阅时,本应用将您输入的账号邮箱与密码发送至该服务提供者的面板以完成登录,并以登录后取得的令牌向该面板请求您的订阅地址,以及套餐、到期、流量、重置与公告信息。若该服务提供者对订阅内容加密,本应用还会以该令牌向其面板请求一把只发给您的订阅解密钥匙,并在之后该钥匙过期或者无法解开订阅内容时再次请求;更新这类订阅时,请求中附带每次随机生成的一串字符与该钥匙的版本号,仅用于在您的设备本地解密,不含任何个人信息。此后,仅在您打开「设置 → 当前订阅」页或者在该页点击「刷新账户信息」时,本应用再次向该面板请求上述账户信息;该服务提供者因此可获知您的 IP 地址与请求时间。第 1.6 条所述的演示服务商由开发者运营,仅用于比对演示账号,不记录、不保存您输入的内容。上述账户信息仅在本应用界面中以文字显示(公告中的链接不可点击、图片不加载),不写入设备存储,不传输给该服务提供者以外的任何一方。本应用不提供购买、续费或者充值功能。
4.3 依法披露
除依据法律法规的强制性规定或者有权机关依法定程序提出的要求外,开发者不向任何第三方转让或者公开披露信息。鉴于本应用不向开发者传输第 2.2 条、第 2.3 条所述信息,开发者无法经由本应用提供该等信息。
5.1 存储位置
(1)订阅地址、线路配置信息及其中内嵌的访问凭据(包括手动添加的线路),存储于本应用沙盒内 Application Support 目录下的一个文件中。该文件不参与 iCloud 备份与电脑备份,并在设备重启后首次解锁之前保持加密。当前或者最近一次连接所用的线路配置与凭据另有一份存于系统 VPN 配置内,见第(3)项。
(2)订阅名称、服务提供者返回的流量与到期信息、诊断日志,以及第 2.2 条、第 2.5 条所述的其他信息,存储于本应用在您设备上的沙盒目录及 App Group 共享容器内。受信任 Wi-Fi 名称还会写入系统 VPN 配置的按需连接规则(见第 6.3 条)。
(3)当前或者最近一次连接所用的内核运行配置,包括其中线路(含备用订阅的线路)的访问凭据,存储于系统设置中的 VPN 配置内,以便系统自行发起连接(例如自动连接,或者您在系统设置中打开 VPN)。该配置在您下次连接或者连接中配置更新时被替换;在「移除订阅」移除正在使用的订阅时一并删除。
(4)服务商识别码、面板登录令牌、账号邮箱与订阅解密钥匙,存储于本设备的系统钥匙串(Keychain),并设为仅本设备可用:不同步至 iCloud 钥匙串,不随备份迁移至其它设备。
(5)本应用不将上述信息存储于开发者或者其他任何一方控制的服务器;服务提供者以其自身身份持有的账户信息,不属于本应用的存储范围,适用其自身的隐私政策。
5.2 留存期限
第 5.1 条第(1)项至第(3)项所述信息随本应用被卸载而一并删除;其中诊断日志另受第 2.3 条第(3)项、流量记录另受第 2.5 条第(1)项、最近一次测速结果另受第 2.5 条第(6)项所述删除机制的约束。第 5.1 条第(4)项所述钥匙串信息在您「解除绑定」时全部删除,在您「退出登录」时删除其中的登录令牌与账号邮箱(订阅解密钥匙保留,以便该订阅继续自动更新;见第 7.2 条第(7)项),在您移除以识别码添加的那条订阅时删除其中的订阅解密钥匙;卸载本应用时,钥匙串中的该等信息由操作系统按其规则处理,可能在重新安装后仍然存在,建议您在卸载前先「解除绑定」。
5.3 安全措施
本应用依赖 iOS 提供的应用沙盒隔离与文件保护(Data Protection)机制保护上述本地存储。请您同时为设备设置锁屏密码,并避免在越狱设备上使用本应用。
5.4 iCloud 备份
若您在系统中启用 iCloud 备份或者进行本地加密备份,前述本地数据(第 5.1 条第(1)项所述包含访问凭据的文件除外)可能作为系统备份的组成部分被备份。该备份行为由 Apple 提供并控制,适用 Apple 的隐私政策,不构成本应用向开发者的传输。
6.1 本应用使用 Apple 提供的 NetworkExtension 框架,在系统「设置 — 通用 — VPN 与设备管理」中创建一项 VPN 配置。该配置的用途,是将设备的网络流量交由运行在您本机的隧道进程处理,并按您所配置的规则转发。iOS 因此在状态栏显示 VPN 标识。
6.2 开发者不利用该项权限进行流量分析、内容读取、内容修改或者注入,亦不记录访问记录。隧道进程运行于您的设备本地,其本身不向开发者回传任何数据(包括遥测、访问记录与流量内容);您的流量去向见第 4.2 条第(2)项。
6.3 若您在「设置 → 自动连接」中添加受信任的 Wi-Fi 或者选择自动连接的网络类型,本应用将相应的按需连接规则写入系统 VPN 配置,由系统按网络名称与网络类型决定何时连接或者断开。本应用不读取您当前所连 Wi-Fi 的名称。名称相同的 Wi-Fi 网络均会被视为受信任的网络。
7.1 查阅:您可在本应用界面内查阅当前所配置的订阅地址(以服务商识别码添加的订阅不显示订阅地址)、线路列表,以及订阅返回的流量与到期信息;以服务商识别码添加的订阅,在登录状态下还可在「设置 → 当前订阅」页查阅面板返回的套餐、到期、流量、重置与公告信息。
7.2 清除与更换:您可在本应用中执行下列操作:
(1)在「设置 → 当前订阅」页「移除订阅」,或者在「订阅」页订阅卡的菜单中「移除」(以服务商识别码添加且仍处于绑定状态的订阅,只在订阅卡的菜单中提供):清除该订阅的地址、已获取的线路列表、订阅返回的流量与到期信息,以及该订阅的线路名单(第 2.5 条第(2)项)、最近一次测速结果(第 2.5 条第(6)项)与订阅解密钥匙(第 5.1 条第(4)项)。移除的若是正在使用的订阅,本应用将断开当前连接,并移除本应用写入系统设置的 VPN 配置;移除的若是当前连接正作为备用的订阅,其线路将从当前连接中移除。移除任何一条订阅时,本机的诊断日志一并删除;
(2)「更换订阅地址」:以新的订阅地址替换当前配置(以服务商识别码添加的订阅不提供此项);
(3)「更新订阅」:按当前订阅地址重新获取线路列表;以服务商识别码添加且仍处于绑定状态的订阅,在「订阅」页点击「立即更新」,或者在登录状态下于「设置 → 当前订阅」页点击「刷新账户信息」,即完成同一操作;
(4)在「订阅」页的「手动添加的线路」中逐条「移除」您手动添加的线路;
(5)在「活动」页的「流量记录」中「清除记录」;
(6)在「设置 → 分流模式」中「删除」规则集,在「设置 → DNS」中「删除」本地域名映射或者「恢复默认 DNS」,在「设置 → 自动连接」中「移除」受信任的 Wi-Fi;
(7)以服务商识别码添加的订阅,在「设置 → 当前订阅」页「退出登录」:删除本机保存的面板登录令牌与账号邮箱(订阅解密钥匙保留,以便该订阅继续自动更新);「解除绑定」:删除本机保存的服务商识别码、面板地址、登录令牌、账号邮箱与订阅解密钥匙,该订阅保留,可照常使用、更新与移除,但仍不显示其订阅地址(若该服务提供者对订阅内容加密,此后该订阅将无法再更新)。
执行第(1)项所述操作而移除了 VPN 配置后,若您再次发起连接,操作系统将重新请求您授权添加 VPN 配置。
7.3 全部删除:卸载本应用将删除本应用存储在设备容器内的全部数据,包括订阅配置与诊断日志;钥匙串中的信息见第 5.2 条。本应用未提供单独清除诊断日志的入口;诊断日志按第 2.3 条第(3)项自动清除,移除订阅时也一并删除。
7.4 撤回同意:您可通过停止使用并卸载本应用撤回对本政策的同意。
7.5 鉴于本应用不向开发者传输、开发者亦不经由本应用存储您的个人信息,就本应用而言,向开发者提出的查阅、复制、更正、删除或者可携带请求不存在可执行的对象,相关操作均可由您在本设备上自行完成;就服务提供者以其自身身份处理的信息,请依其自身的隐私政策向其提出。
8.1 本应用不面向 13 周岁以下的儿童,开发者不会有意收集儿童的个人信息。鉴于本应用不收集任何用户的个人信息,亦不存在收集儿童个人信息的情形。
8.2 若您为未成年人,请在监护人的指导下决定是否使用本应用。监护人如对相关事项有疑问,可依第 10 条载明的方式联系开发者。
9.1 本政策变更时,其版本号将相应提升。现行文本可随时在本应用「设置」中的「关于」页查阅。本应用更新后您继续使用,即表示您接受变更后的本政策。
9.2 本政策的版本号与最后更新日期载于正文末尾的版本标注行。
就本政策的任何问题、意见或者投诉,您可通过下列方式联系开发者:hachiminemo@gmail.com
This Privacy Policy (the "Policy") applies to the Application and its bundled network extension. It describes what information is processed, for what purposes and by what means, where that information is stored and for how long, and what rights you have in relation to it. Please read this Policy in full before using the Application.
1.1 "Application" means this network proxy client software, including its main program and the bundled NetworkExtension component.
1.2 "Developer" means the entity that develops and distributes the Application, and the party responsible for the processing described in this Policy. The only servers the Developer operates for the Application are the Provider Code resolution service described in Section 4.2(l) and the Demonstration Provider described in Section 1.6; the Application never connects to them unless you have made a choice that leads there.
1.3 "Provider" means the party that provides you with a proxy or network access service, namely the party to which a subscription URL you configure, or a Provider Code you enter, in the Application points.
1.4 "Personal Information" means any information, recorded electronically or otherwise, that identifies an individual or reflects an individual's activities, whether on its own or in combination with other information.
1.5 "Provider Code" means a string issued to you by a Provider, used within the Application to look up that Provider's sign-in endpoint (panel address).
1.6 "Demonstration Provider" means the Provider operated by the Developer solely for demonstration and app review; its handling of information is described in Section 4.2(m).
2.1 Information Not Collected
The Application does not collect:
(a) your name, date of birth, government identification number, telephone number, or any other information that identifies you directly or indirectly;
(b) device identifiers for advertising or cross-application tracking purposes;
(c) the addresses, domains, or destination servers you reach through the Application, the times at which connections are initiated, their duration, or any other access records or connection metadata;
(d) the contents of any traffic carried through the tunnel.
The Application maintains no account system of its own and does not require you to register with or sign in to the Developer. Other than the Provider Code resolution service described in Section 4.2(l), and the Demonstration Provider described in Section 1.6 that is reached when you enter the demonstration code, it communicates with no server operated by the Developer for the Application. It integrates no third-party analytics, advertising, or crash-reporting software development kit (SDK).
2.2 Information You Provide or Generate on Your Device
In the course of using the Application you may enter, import, or generate subscription URLs, server configuration data (including individual servers you add manually or by scanning a QR code), and the access credentials such URLs and server links commonly embed (tokens, UUIDs, passwords, and the like); and, in Settings, the names of trusted Wi-Fi networks, DNS servers and local domain mappings, rule-set addresses, and routing rules.
This information is processed and stored locally on your device as described in Section 5. Of it, a Provider Code is sent only to the resolution service as described in Section 4.2(l), and subscription URLs, account e-mail addresses, and passwords are sent only to the Provider you selected as described in Section 4.2. Beyond that, the Application transmits none of this information to the Developer.
If you choose to add a subscription with a Provider Code, you also enter that code and the e-mail address and password of your account with that Provider. The password is used only to send a sign-in request to that Provider's panel and is not stored by the Application; the code, the token issued by the panel on successful sign-in, the e-mail address, and, where that Provider encrypts its subscription content, the subscription decryption key it issues to you individually are stored in your device's keychain, see Section 5.1(d). The processing of the code is described in Section 4.2(l), and that of the panel sign-in, account information, and subscription decryption key in Section 4.2(m).
The Application provides a "Copy subscription URL" action in the menu of each subscription card on the Subscriptions tab and on the Settings → Current subscription screen. You initiate it; the Application never performs it automatically. Content written to the system pasteboard by that action is marked local-only (it is not synchronised to your other devices via Handoff or Universal Clipboard) and is set to expire after ten minutes. Note that a subscription URL usually embeds access credentials and is equivalent in effect to a password. This action does not apply to a subscription added with a Provider Code, whose subscription URL is not shown in the interface.
2.3 Local Diagnostic Log
So that you can investigate connection problems yourself, the Application writes a runtime log on your device. In addition to whether the tunnel was established and what errors the core reported, that log contains a per-connection record written by the core, comprising the destination host name or IP address, the port, the outbound route used, and any failure reason. That log:
(a) is stored only within the local container on your device and is never uploaded automatically to the Developer or to any third party;
(b) when viewed or exported within the Application, has the destination host names and IP addresses in those per-connection records replaced with a placeholder, while ports, outbound routes, and failure reasons are retained. In other words, what you choose to share does not contain those destination addresses, whereas the original file retained on your device still does;
(c) is cleared according to which process wrote it and what it contains: the core log written by the tunnel process (including any copy produced by the core's log rotation, and containing the per-connection records) is deleted at the start of each connection; the tunnel process's own runtime log (which records only events such as tunnel start and stop and network changes, and contains no connection records) is rotated at the start of each connection so that one copy from the previous connection is kept on the device; the core log written by the Application's main process is deleted each time that log is reopened (at launch, and before each pre-connection speed test); the pre-connection speed-test record is overwritten on every round. Logs containing connection records therefore exist on the device only for the most recent connection; all of these logs are also deleted when you remove any subscription, or when the subscription credentials file stored on this device is damaged and cannot be read;
(d) is deleted when the Application is uninstalled.
The Application provides a "Diagnostic log" screen within the Activity tab for you to review that log. You may initiate the following operations there; the Application performs neither of them automatically:
(a) Copy: the log text is written to your device's system pasteboard. The Application marks that content local-only (it is not synchronised to your other devices via Handoff or Universal Clipboard) and sets it to expire after ten minutes.
(b) Export: the Application writes a copy of the log to a temporary directory on your device so that it may be sent through the system share sheet. The Application deletes that file once the share sheet is dismissed.
Should you choose to send that log to the Developer in order to obtain support, that is a disclosure you make deliberately and whose scope you determine. The log may contain the addresses and domain names of the servers you have configured. You are advised to review its contents before sending it.
2.4 Camera and Photos
The Application lets you add a subscription or servers by scanning a QR code:
(a) Camera: used only while the scanning screen is open, to recognise the QR code on your device. Images are neither stored nor uploaded, and the camera is released when the Application moves to the background.
(b) Photos: you may choose one image in which to recognise a QR code. This uses the photo picker provided by the system; the Application cannot access your photo library and can read only the single image you choose, which is discarded once it has been read on your device.
(c) A subscription or server recognised from a QR code is added only after you confirm it on a confirmation screen. Scanning never starts a connection.
2.5 Records and Displays on Your Device
To provide the features concerned, the Application keeps or displays the following on your device. None of it is transmitted to the Developer:
(a) Traffic records: the tunnel process adds up, per day, the number of bytes that passed through the Application (split into direct and through servers) and keeps up to 90 days. The records contain no domains, addresses, or server names. You can use "Clear History" on the "Traffic History" screen of the Activity tab.
(b) Server lists: recently used and favourite servers, and the fastest servers from your speed tests (used to order the "Auto" server). Only server names and their order are kept; they are kept per subscription, identified by a digest of the subscription URL rather than the URL itself, and are deleted when that subscription is removed.
(c) Live Activity (off by default): when turned on, the time the connection was established, the time it was last confirmed to be up, and the server name (which you can choose to hide) appear on the Lock Screen and in the Dynamic Island, and may therefore also appear on an Apple Watch, Mac, or vehicle paired with this device, without unlocking. The Application cannot learn of connection changes while it is in the background, so the display states only when it last confirmed the connection; if you disconnect from the Lock Screen, Control Center, a widget, or Shortcuts, it changes to disconnected.
(d) Notifications: the Application sends only local notifications on your device: subscription expiry reminders and, if you turn on "Disconnect alerts" (off by default), alerts sent by the tunnel process when the connection drops unexpectedly or automatic reconnection is paused. Notifications contain no server names, server addresses, or subscription URLs; an expiry reminder shows only the expiry date.
(e) Widgets and Control Center: Home Screen and Lock Screen widgets and the Control Center control, if you add them, show the connection state and the server name (some widgets also show connection time and traffic). Lock Screen widgets and Control Center can be seen without unlocking.
(f) Latest speed test results: after a speed test, the Application keeps one set of the latest results on your device: server names, the measured latencies (in milliseconds) and the time they were measured, identified by a digest of the subscription URL rather than the URL itself. These results are used only to show your previous results first when you open the Application again within 30 minutes, and are not uploaded. After 30 minutes they are no longer used for this and are deleted the next time the Application starts; they are also deleted when you change or remove the subscription. Results from the network check are not included (see Section 4.2(h)).
3.1 The information described in Section 2.2 is used solely to establish and maintain network connections locally on your device, to parse and update the subscriptions you configure, to choose servers according to your settings, and to display server and account information in the interface; a Provider Code is used only for the lookup described in Section 4.2(l), a panel token only for the requests described in Section 4.2(m), and a subscription decryption key only to decrypt, locally on your device, the subscription content sent by that Provider. The information described in Section 2.4 is used solely to recognise the QR codes you scan; that described in Section 2.5 is used solely to show you the corresponding content.
3.2 The information described in Section 2.3 is used solely for your own diagnosis of connection failures.
3.3 None of the above is used for automated decision-making, advertising, or cross-application tracking, or for any purpose beyond those stated in this Policy.
4.1 Third-Party SDKs
The Application integrates no third-party analytics, advertising, or crash-reporting SDK and therefore shares no information with any third party for those purposes.
4.2 Providers
(a) Subscription updates. Where you import a subscription or request a subscription update, the Application issues a request to the relevant Provider using the subscription URL you configured. For each subscription whose "Auto Update" switch is on, each time the Application returns to the foreground it requests that subscription's URL in turn according to its own update interval, including subscriptions not currently in use. That URL commonly embeds your access credentials, and the provider is accordingly able to observe your IP address, the time of the request, and the client type. This flow is inherent in how subscriptions operate.
(b) Traffic. Once a connection is established, your traffic passes through the servers of the Provider you selected; the Application itself operates no relay server.
(c) Allocation of responsibility. A Provider's handling of the information it receives is governed by that Provider's own privacy policy and not by this Policy, and is not the subject of any representation or warranty by the Developer. Configure only services you trust.
(d) Launch connectivity check. On first launch, the Application issues a single HEAD request to Apple's connectivity-check endpoint (captive.apple.com). The request carries no device identifier, account information, or configuration content. Its sole purpose is to have the operating system present its wireless-data authorization prompt (on device models that have one) at that moment, rather than mid-way through your first subscription import or connection, where it would cause that operation to fail. It runs once per installation; its result is neither recorded nor reported and does not affect the Application's behaviour.
(e) Device clock correction. Some line protocols require the client and server clocks to agree to within tens of seconds; a device whose clock is wrong cannot connect to any of those lines. The Application therefore queries external time sources in the following three situations, solely to compute the offset between this device's clock and standard time: (i) before a pre-connection speed test and before starting a connection (and, if the feature in item (g) is on, at each cold launch), it queries a public NTP service once (time.apple.com by default); (ii) if that query fails, it issues HEAD requests to cloudflare.com, apple.com, and microsoft.com and takes the agreed standard time from their response headers; (iii) once a connection is established, the tunnel process queries the same NTP service again at a fixed interval (30 minutes by default) and when the device wakes, the network changes, or the system time changes. None of these requests carries a device identifier, account information, or configuration content; the services concerned can observe your IP address and the time of the request. The results are used only on the device to correct the clock offset and are not reported.
(f) Speed tests and health checks. When you run a speed test, the Application reaches a test target through each server (the core's built-in check address, or the first valid address you entered under Settings → Speed Test Settings) to measure latency. When you choose the "Auto" server or turn on a backup subscription, the tunnel process performs health checks by reaching http://www.gstatic.com/generate_204 through servers: with "Auto", about every 10 minutes while there is traffic, checking up to 25 servers of the current subscription. When you turn on "Use when the main subscription fails" for a subscription, the tunnel process checks about every 2 minutes while there is traffic and, if the current server is unavailable, forwards your traffic through that backup subscription's servers; your traffic may therefore pass through the servers of a different Provider. These health checks also run once each time a connection starts or the configuration is reloaded.
(g) "Pick Server at Launch" (off by default). When turned on, at each cold launch while not connected the Application performs the clock correction described in item (e) once and runs one speed test of the current subscription's servers in order to select a server. It does not start a connection.
(h) Network check. Only when you tap "Run Check", the Application issues one HEAD request to Apple's connectivity-check endpoint (captive.apple.com) and runs one speed test of the currently selected server. The result is kept in memory only; it is not written to storage and not reported.
(i) Rule sets. Only when you add or update a rule set, the Application requests the rule-set address you entered in order to download the rule list; whoever operates that address can observe your IP address and the time of the request. The downloaded content is converted and kept only on your device.
(j) Name resolution. The DNS servers used by the Application (Cloudflare and AliDNS by default, changeable under Settings → DNS) can observe the domain names queried and the IP address from which each query is sent.
(k) Apple push check. When "Include Apple push" is on (the default), after a connection is set up the tunnel process sends small HTTP requests to Apple's connectivity-check endpoint (http://captive.apple.com/hotspot-detect.html), both through your server and directly, to decide whether Apple push traffic uses the server or a direct connection. This happens once when connecting or when the configuration is reloaded, and after that only while push connections are being made. The requests carry no device identifier, account information, or configuration content; Apple can observe the IP address each request comes from and its time.
(l) Provider Code resolution. When you enter a Provider Code and tap "Look Up", the Application sends that code to a resolution service operated by the Developer and hosted on Cloudflare (Cloudflare processes the request as the infrastructure provider), in order to look up the panel address and name of the Provider it belongs to, together with the interface paths that Provider has registered and whether it encrypts its subscription content. If the lookup succeeds and that Provider has set an icon, the Application immediately requests that icon from the resolution service once (again sending only the code and the IP address) and does not request it again afterwards; the icon is stored on this device. That service receives only the code and the IP address the request comes from, and no device identifier, account information, or configuration content. It does not log or retain the code or the IP address; the IP address is used only in hashed form, within a time window of about one minute, to limit the rate of lookups and prevent abuse, and that hash expires after about one to two minutes. The request is made only when you tap "Look Up"; the Application does not communicate with that service at any other time.
(m) Panel sign-in and account information. When you add a subscription with a Provider Code, the Application sends the e-mail address and password you entered to that Provider's panel in order to sign in, and uses the resulting token to request from that panel your subscription URL together with your plan, expiry, traffic, reset, and notice information. Where that Provider encrypts its subscription content, the Application also uses that token to request from its panel a subscription decryption key issued to you only, and requests it again later when that key expires or the subscription content cannot be decrypted; when such a subscription is updated, the request carries a string generated at random each time and the key's version number, which are used only for decryption locally on your device and contain no personal information. Afterwards, the Application requests that account information from the panel again only when you open the Settings → Current subscription screen or tap "Refresh Account Info" there; the Provider can accordingly observe your IP address and the time of the request. The Demonstration Provider described in Section 1.6 is operated by the Developer; it only compares what you entered against its demonstration account and neither logs nor stores it. The account information is shown as text within the Application's interface only (links in notices cannot be tapped and images are not loaded), is not written to storage, and is not transmitted to any party other than that Provider. The Application offers no purchase, renewal, or top-up function.
4.3 Disclosure Required by Law
Except where required by mandatory provisions of law or by a competent authority acting through lawful process, the Developer transfers and discloses no information to any third party. As the Application does not transmit the information described in Sections 2.2 and 2.3 to the Developer, the Developer is not in a position to produce it through the Application.
5.1 Where Information Is Stored
(a) Subscription URLs, server configuration data, and the access credentials they embed (including servers you added manually) are stored in a single file in the Application Support directory of the Application's sandbox. That file is excluded from iCloud and computer backups and remains encrypted until the device is first unlocked after a restart. The server configuration and credentials used for the current or most recent connection are also kept in the system VPN configuration; see (c).
(b) Subscription names, the traffic and expiry information returned by your Provider, the diagnostic log, and the other information described in Sections 2.2 and 2.5 are stored within the Application's sandbox directory and App Group shared container on your device. The names of trusted Wi-Fi networks are also written into the on-demand rules of the system VPN configuration (see Section 6.3).
(c) The core configuration used for the current or most recent connection, including the access credentials of its servers (and of any backup subscription's servers), is stored in the VPN configuration in system settings, so that the system can start the connection itself (for example through Auto Connect, or when you turn on the VPN in system settings). It is replaced the next time you connect or the configuration is updated while connected, and is deleted when you use "Remove Subscription" on the subscription in use.
(d) The Provider Code, the panel token, the account e-mail address, and the subscription decryption key are stored in your device's system keychain, marked for this device only: they are not synchronised to iCloud Keychain and do not migrate to another device through a backup.
(e) The Application stores none of this information on any server controlled by the Developer or by any other party; account information held by a Provider in its own capacity is outside the Application's storage and is governed by that Provider's own privacy policy.
5.2 Retention
The information described in Section 5.1(a) to (c) is deleted when the Application is uninstalled; the diagnostic log is additionally subject to the deletion behavior described in Section 2.3(c), traffic records to that described in Section 2.5(a), and the latest speed test results to that described in Section 2.5(f). The keychain items described in Section 5.1(d) are deleted in full when you use "Unlink Provider", and the token and e-mail address among them when you use "Sign Out" (the subscription decryption key is kept so that the subscription can continue to update automatically; Section 7.2(g)); the subscription decryption key is deleted when you remove the subscription added with the Provider Code; when the Application is uninstalled, the operating system handles those keychain items according to its own rules and they may still exist after a reinstall, so you are advised to use "Unlink Provider" before uninstalling.
5.3 Security
The Application relies on the application sandbox and Data Protection mechanisms provided by iOS to protect the local storage described above. You are encouraged to set a device passcode and to avoid using the Application on a jailbroken device.
5.4 iCloud Backup
If you enable iCloud Backup or create an encrypted local backup, the local data described above (other than the file containing access credentials described in Section 5.1(a)) may be included in that backup. Backup is provided and controlled by Apple and is governed by Apple's privacy policy; it does not constitute a transmission from the Application to the Developer.
6.1 The Application uses Apple's NetworkExtension framework to install a VPN configuration under Settings — General — VPN & Device Management. The purpose of that configuration is to hand the device's network traffic to a tunnel process running on your own device, which forwards it according to the rules you configured. iOS displays the VPN indicator in the status bar as a consequence.
6.2 The Developer does not use this permission to analyze traffic, to read, modify, or inject content, or to record access history. The tunnel process runs locally on your device and itself reports nothing back to the Developer (no telemetry, access history, or traffic content); where your traffic goes is described in Section 4.2(b).
6.3 If you add trusted Wi-Fi networks or choose the network types for automatic connection under Settings → Auto Connect, the Application writes the corresponding on-demand rules into the system VPN configuration, and the system decides when to connect or disconnect based on network names and types. The Application does not read the name of the Wi-Fi network you are connected to. Any Wi-Fi network with the same name is treated as trusted.
7.1 Access. You may view the subscription URL (not shown for a subscription added with a Provider Code), the server list, and the traffic and expiry information returned by your subscription within the Application's interface; for a subscription added with a Provider Code, while you are signed in you may also view the plan, expiry, traffic, reset, and notice information returned by the panel on the Settings → Current subscription screen.
7.2 Clearing and replacement. The Application provides the following operations:
(a) "Remove Subscription" on the Settings → Current subscription screen, or "Remove" in the menu of a subscription card on the Subscriptions tab (for a subscription added with a Provider Code that is still linked, only the latter is offered), which clears that subscription's URL, the server list already obtained, the traffic and expiry information returned by the subscription, and that subscription's server lists (Section 2.5(b)), latest speed test results (Section 2.5(f)), and subscription decryption key (Section 5.1(d)). If the subscription removed is the one in use, the Application also disconnects the current session and removes the VPN configuration it wrote to system settings; if it is serving as a backup for the current connection, its servers are taken out of that connection. Removing any subscription also deletes the diagnostic logs on this device;
(b) "Change subscription URL", which substitutes a new subscription URL for the current configuration (not offered for a subscription added with a Provider Code);
(c) "Update subscription", which retrieves the server list again using the current subscription URL; for a subscription added with a Provider Code that is still linked, "Update Now" on the Subscriptions tab, or "Refresh Account Info" on the Settings → Current subscription screen while you are signed in, does the same;
(d) "Remove" for each server you added manually, under "Manually Added Servers" on the Subscriptions tab;
(e) "Clear History" on the "Traffic History" screen of the Activity tab;
(f) "Delete" for a rule set under Settings → Routing mode, "Delete" for a local domain mapping or "Restore Default DNS" under Settings → DNS, and "Remove" for a trusted Wi-Fi network under Settings → Auto Connect;
(g) for a subscription added with a Provider Code, "Sign Out" on the Settings → Current subscription screen, which deletes the panel token and account e-mail address held on this device (the subscription decryption key is kept so that the subscription can continue to update automatically), and "Unlink Provider" there, which deletes the Provider Code, panel address, token, e-mail address, and subscription decryption key held on this device while the subscription itself is kept and can still be used, updated, and removed, although its subscription URL remains hidden (if that Provider encrypts its subscription content, that subscription can then no longer be updated).
If the operation described in (a) removed the VPN configuration, the operating system will ask you to authorise a VPN configuration again the next time you start a connection.
7.3 Deletion of everything. Uninstalling the Application deletes all data it holds in the device container, including subscription configuration and the diagnostic log; keychain items are treated as described in Section 5.2. The Application provides no separate facility for clearing the diagnostic log; it is cleared automatically as described in Section 2.3(c) and is also deleted when you remove a subscription.
7.4 Withdrawal of consent. You may withdraw your acceptance of this Policy by ceasing to use the Application and uninstalling it.
7.5 Because the Application transmits none of your Personal Information to the Developer and the Developer stores none of it through the Application, a request to the Developer for access, portability, rectification, or erasure in respect of the Application has no subject matter to operate on, and all such operations can be carried out by you on your own device; for information processed by a Provider in its own capacity, please address your request to that Provider under its own privacy policy.
8.1 The Application is not directed to children under 13, and the Developer does not knowingly collect personal information from children. As the Application collects personal information from no user, no collection of children's information arises.
8.2 If you are a minor, please decide whether to use the Application under the guidance of your guardian. Guardians with questions may contact the Developer as provided in Section 10.
9.1 When this Policy changes, its version number is raised. The current text is always available on the About page in the Application's Settings. If you continue to use the Application after an update, you accept the changed Policy.
9.2 The version number and date of last update appear in the version line at the end of this text.
Questions, comments, or complaints regarding this Policy may be directed to the Developer at: hachiminemo@gmail.com