← 9F VPN · English · 简体中文

Effective Date: October 6, 2026
Last Updated: November 20, 2026

9F Technologies LLC ("we", "us", "our"), a company registered in the United States, operates the 9F VPN apps and related services (the "Service"). This policy explains exactly what information the Service collects, why, how long we keep it, and how you can delete it.

In short: we do not log the websites you visit, your DNS queries, or the content of your traffic, and we do not store your IP address. We do not sell your data and the Service contains no advertising or tracking SDKs. To run accounts, subscriptions and the network, we keep a small amount of device, account and connection-session information, described below.

1. What we never collect

Our VPN servers are configured with traffic/access logging disabled, and their system logs are kept in memory only.

2. What we collect and why

2.1 Device information

An identifier for your device, which is not your hardware serial number: on iPhone and iPad, a random identifier generated by the app; on Android, the Android ID that the system provides to our app (on Android 8 and later it differs from the one other developers' apps see; it changes after a factory reset), or a random identifier generated by the app if no usable Android ID is available; older versions of our app used the phone's firmware build number, which phones of the same model and firmware share. We also collect the device model, operating system version, app version, language, time zone and (on iOS) App Store country or region. We use this information to recognise your device, enforce the device limit of your account (5 devices for VIP), troubleshoot, prevent abuse, and produce aggregated statistics. For each device we also keep a VPN connection credential, which our VPN servers use to let the device connect and to apply its membership and the free plan's limits, and the device key the app uses to sign its requests, with the result of checking it. We use them, and records of security actions on a credential (for example replacing a credential that is in use on many networks at the same time), to prevent abuse; we also use when a credential was last used to compare the groups of the new-user trial (2.12).

2.2 Approximate location and network

When the app contacts our API, we derive your country, city and network provider (ISP / ASN) from the request. We use this to recommend nearby servers and for aggregated statistics. This is stored with your device record; the IP address itself is not.

2.3 Connection sessions

When a VPN connection starts and ends, the app reports the server region you connected to and how long the session lasted. We use this to show whether a device is online, to apply subscription and device limits, and to measure service reliability. We do not record what you do during a session.

Our VPN servers also count how much data each device transfers per day (a byte total only, not what the data was). We use it to apply the free plan's daily high-speed allowance, to show you today's usage and, for new devices in the trial test, to compare the groups (2.12).

When you connect, the app also reports whether the connection succeeded, how many attempts it took, the general reason for a failure, which server and connection type were used, how long it took, and whether you were on Wi-Fi or mobile data, and may include a carrier group (such as Telecom, Unicom or Mobile, inferred from the network provider described in 2.2). Some devices, while not connected to the VPN, test whether a few ports on our servers can be reached (opening a connection only, sending no data) and report the result. We keep these only as daily totals, without device identifiers, accounts or IP addresses, and use them to improve connection success.

2.4 Account information (optional)

You can use the Service without an account. If you create one, we store your account ID, creation date, the list of devices bound to the account, and details from the sign-in method you choose:

If Apple, or Google for a Gmail or Google Workspace address, confirms an email address that already belongs to a 9F VPN account, we link the sign-in to that account so your membership carries over. For other addresses we ask you to sign in with an email code first and then link Google on the Account page. Telegram does not share an email address, so a Telegram sign-in is never linked by email; you can link Telegram to an existing account on the Account page in the app.

Information we receive from Google is used only to sign you in, to manage your account and to send you the service emails described above; we never use it for advertising. Our use of it complies with the Google API Services User Data Policy, including the Limited Use requirements. We never sell it, use it for advertising, or share it with third parties, apart from the service providers in section 3 that process data on our behalf.

2.5 Subscription information

Subscription status, product and expiry date, received from Apple via RevenueCat. Payments are processed by Apple; we never receive your card details.

2.6 Support messages

If you contact us by email, Telegram or Facebook, we receive the information you choose to send.

2.7 Stored only on your device

App settings and favourite servers are stored locally on your device and are not uploaded.

If you turn on blocking, the block lists are downloaded to your device and matching happens on your device; the number of blocked requests is kept only on your device and is not uploaded.

2.8 App usage statistics

After you agree to data collection, the app reports a small set of in-app events so we can understand whether the app and the subscription screen work: the app being opened for the first time, the first successful connection, a free-plan limit or locked server notice being shown, the subscription screen being shown (and which screen it was opened from), a plan being selected, a purchase being started, completed, cancelled, blocked or failing (with a general error category), restoring purchases, a trial starting or ending, the result of the app's update check and whether an update prompt was shown or tapped, whether the notification reminder card was shown or accepted, whether notifications were allowed, and which kind of reminder was opened, taps on the "rate the app" entry, whether the app asked the system to show its rating prompt (or why it did not), and whether malicious-site blocking and ad and tracker blocking are switched on (on or off only, never which sites were blocked or how many).

We do not store these events one by one. We only add them up into daily totals per event, platform, app version and approximate country (the country recorded when your device first registered). The totals do not contain your device identifier, account or IP address. We may show slightly different screens to different devices (for example, whether the subscription screen appears when the app is first opened); these daily totals are then counted separately for each version.

To measure how many new devices come back after 1, 7 and 30 days, we also keep, for each device, a one-way keyed hash of the device identifier from section 2.1, the first day we saw the device, and which days (up to 64) the app was opened. Because we hold the key, this record can be linked back to your device record, so we treat it as personal data. It contains no account, location, server or usage details.

2.9 Apple Ads attribution

If you installed the app after tapping or viewing an ad on the App Store (Apple Ads), Apple can tell us which ad campaign, ad group and keyword led to the download. The app asks Apple's AdServices framework for an attribution token. Our subscription provider RevenueCat uses this token to get that information from Apple and keeps it with your subscription record. On your device, the app keeps only whether the download came from an ad and, if so, the ad group number. This does not use the advertising identifier (IDFA), does not ask for permission to track, and is not used to track you across other companies' apps or websites. We use it only to measure which of our App Store ads work.

2.10 Optional in-app question

After you have connected on two different days, the app may ask once what you mainly use a VPN for. Answering is optional and you can skip it. We keep only daily totals of the answers, grouped by platform, App Store country or region, a broad time-zone group (for example UTC+7) and the Apple Ads ad group (or "not from an ad"). We do not store your device identifier, account or IP address with your answer.

2.11 Web payment orders

For payments made on our website rather than through an app store (where web payment is offered, for example for the Android app), we keep an order record: the order number, your account ID and account email (if the account has no email address of its own, for example one created with Sign in with Telegram, or with Apple or Google without an email address we can use, this is an internal placeholder address that contains the ID of that sign-in account or your account ID), the plan and number of days, the amount and currency (and its value in US dollars), the payment method, our receiving address or wallet account, the order status and its times (created, payment deadline, paid, refunded), and the membership end date the order gives your account. For the payment we keep the payment reference and the amount received: for a blockchain transfer, the transaction hash, the sending address and when the transfer arrived; for a mobile wallet, the transaction number, the note you enter (for example the payer's name or the last digits of a phone number) and when you submitted them. For a refund we keep the amount refunded, its time and the refund transaction number. We also keep links between related records (for example a payment added to an order) and short notes our staff add while handling an order, such as the reason an order was declined.

If a blockchain transfer reaches our receiving address but does not match any order, we keep its transaction hash, sending address, amount and time, so that we can credit it to the right order or account, or send it back.

We use these records to add VIP to your account, handle refunds and questions, keep our accounts, make sure one payment is not counted twice, and email you an order receipt and VIP expiry notices. Blockchain transfers are public; we look up transfers to our receiving address through a blockchain data service (TronGrid). Wallet payments are processed by the wallet provider; we never receive your wallet password or PIN. When a payment needs checking by hand, we may send ourselves a notice by Telegram or email (see section 3). Subscriptions bought through the App Store do not create these records (see 2.5).

2.12 New-user trial

We may offer newly installed devices a free trial of VIP for a few days. To make sure each device and each account gets the trial only once, to prevent bulk abuse, and to understand whether the trial helps people use the Service and subscribe, we keep a record on our servers, linked to the device identifier (2.1), for each new device that is placed either in the trial group or in a comparison group that does not get the trial. It contains: which group the device is in and the name of the test; the country (as seen from the network when the device was checked for the trial), platform and app version; when the trial started and when it was due to end; when and why it ended; the result and method of the check that the device is a genuine device running our app (2.1); and whether, within 7 days of the trial starting (for the comparison group, of the check), the device had a paid membership, when we first saw it, and how that membership was bought (App Store, or on our website and with which payment method). To compare the groups, we also look at whether each device used the VPN, from its daily data totals (2.3), and whether the app was used again after the first day, from when its connection credential was last used (2.1). If you are signed in when the device is checked for the trial, or sign in during the trial, the record may be linked to that account; signing out or unbinding the device does not remove this link, but deleting your account does (section 4). We also count trial checks, starts and ends in daily totals that contain no device identifier (see 2.8).

We do not store your IP address with this record. To limit bulk claims, we count trials per day for each network: the network block (the first part of the IP address, usually shared by many users, not your full address) is stored only as a keyed one-way hash, and the network provider's number (ASN) as is. So that each device is counted only once in these counts and in our daily totals of trial checks, we also keep a keyed one-way hash of the device identifier together with the outcome of the check (for example, why a device was not eligible). These counters and hashes are deleted within 3 days.

3. Service providers

ProviderPurpose
AppleApp Store distribution, in-app purchases, Sign in with Apple, Apple Ads attribution
GoogleSign in with Google (confirms your Google account)
TelegramSign in with Telegram (confirms your Telegram account); when enabled, notices to our staff about web payment orders that need checking (order number, payment method, amount, the transaction number or the first characters of the transaction hash, and for wallet payments the note you entered and your account email)
RevenueCatSubscription status and receipt validation; Apple Ads attribution (which ad, if any, led to the download)
CloudflareHosting of our API, website and content delivery
ResendSending emails for us: sign-in codes and service emails (receipts, VIP expiry notices, security notices); when enabled, web payment order notices to our own mailbox. Receives: your email address, the email content and its language
TronGridLooking up blockchain transfers to our receiving address, for web payment orders
Server hosting providersData-centre hosting for our VPN servers

These providers process data only to deliver their service to us. We do not sell, rent or trade your information.

4. How long we keep data

5. Your choices and rights

6. Legal requests

We may disclose the limited information described in section 2 if we are legally required to. We cannot disclose browsing history, DNS queries, traffic content or stored IP addresses, because we do not have them.

7. Security

Traffic between the app and our servers is encrypted. Our API is served over TLS, and access to our systems is restricted to authorised personnel.

8. Children

The Service is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has provided us data, contact us and we will delete it.

9. Changes

If we change this policy, we will post the new version here and update the date above. Material changes will also be announced in the app.

10. Contact

For privacy questions or requests, including data deletion, email support@9fvpn.com.

9F Technologies LLC · 30 N Gould St, Sheridan, WY 82801, USA


生效日期:2026 年 10 月 6 日
最后更新:2026 年 11 月 20 日

9F Technologies LLC(以下称"我们")是一家在美国注册的公司,负责运营 9F VPN 应用及相关服务(以下称"本服务")。本政策说明本服务具体收集哪些信息、用途、保存多久,以及您如何删除这些信息。

简而言之:我们不记录您访问的网站、DNS 查询或流量内容,也不保存您的 IP 地址。我们不出售您的数据,本服务不含任何广告或追踪 SDK。为了运行账户、订阅和网络,我们会保存少量设备、账户和连接会话信息,详见下文。

1. 我们从不收集的信息

我们的 VPN 服务器已关闭流量 / 访问日志,系统日志只保存在内存中。

2. 我们收集的信息及用途

2.1 设备信息

设备标识(不是硬件序列号):iPhone 和 iPad 上是应用生成的随机标识;安卓上是系统提供给我们应用的 Android ID(安卓 8 及以上与其他开发者的应用看到的不同;恢复出厂设置后会改变),系统给不出可用的 Android ID 时改用应用生成的随机标识;旧版应用用的是手机的固件构建号(同型号、同固件的手机相同)。此外还有设备型号、系统版本、应用版本、语言、时区和 App Store 国家或地区(仅 iOS)。这些信息用于识别您的设备、执行账户的设备数上限(VIP 为 5 台)、排查问题、防止滥用和生成汇总统计。我们还会为每台设备保存 VPN 连接凭证(我们的 VPN 服务器用它允许设备连接,并执行会员和免费版的限制),以及 App 用来给请求签名的设备密钥及其校验结果。我们用它们以及对凭证采取的安全处置记录(例如某个凭证同时在很多网络上使用时更换它)来防止滥用;还会用凭证最近的使用时间比较新用户体验的两组(2.12)。

2.2 大致位置与网络

应用访问我们的接口时,我们会根据该请求推断您所在的国家、城市和网络运营商(ISP / ASN),用于推荐就近的服务器和汇总统计。这些信息会与设备记录一起保存,但 IP 地址本身不保存。

2.3 连接会话

VPN 连接开始和结束时,应用会上报您连接的服务器地区和本次连接的时长。用于显示设备是否在线、执行订阅和设备数限制、衡量服务的稳定性。我们不记录您在连接期间做了什么。

我们的 VPN 服务器还会统计每台设备每天传输的数据量(只有字节总数,不包括数据内容)。用于执行免费版每日高速流量额度、向您显示今日用量,以及在新用户体验测试中比较两组(2.12)。

连接时,应用还会上报这次连接是否成功、尝试了几次、失败的大致原因、所用服务器和连接方式、耗时,以及当时用的是 Wi-Fi 还是移动网络,并可能附上运营商类别(例如电信、联通、移动,由 2.2 所述的网络运营商推断)。部分设备在没有连接 VPN 时,会测试能否连上我们服务器的几个端口(只建立连接、不发送数据)并上报结果。这些信息只按天汇总成总数,不含设备标识、账户或 IP 地址,用于提高连接成功率。

2.4 账户信息(可选)

您无需账户即可使用本服务。如果您创建账户,我们会保存账户 ID、创建日期、绑定到该账户的设备列表,以及您所选登录方式提供的以下信息:

如果 Apple 确认的邮箱,或 Google 确认的 Gmail / Google Workspace 邮箱已属于某个 9F VPN 账户,我们会把这次登录关联到该账户,您的会员权益随之保留;其他邮箱需要您先用邮箱验证码登录,再在"账户"页面绑定 Google。Telegram 不提供邮箱,因此 Telegram 登录不会按邮箱关联;您可以在应用的"账户"页面把 Telegram 绑定到已有账户。

我们从 Google 获得的信息只用于为您登录、管理账户和发送上述服务邮件,绝不用于广告。其使用遵守《Google API 服务用户数据政策》,包括其中的"有限使用"要求。我们绝不出售这些信息,不将其用于广告,也不与第三方共享(第 3 节所列代我们处理数据的服务提供商除外)。

2.5 订阅信息

通过 RevenueCat 从 Apple 获取的订阅状态、产品和到期时间。付款由 Apple 处理,我们不会接触您的银行卡信息。

2.6 客服沟通

如果您通过邮件、Telegram 或 Facebook 联系我们,我们会收到您主动发送的信息。

2.7 仅保存在您设备上的信息

应用设置和收藏的服务器只保存在您的设备上,不会上传。

如果您开启拦截,拦截名单会下载到您的设备上,比对在设备上完成;被拦截的次数只保存在您的设备上,不会上传。

2.8 应用使用统计

在您同意数据收集之后,应用会上报少量应用内事件,用来了解应用和订阅页是否好用:首次打开、首次连接成功、出现免费额度提示或上锁线路提示、订阅页出现(以及从哪个页面进入)、选择套餐、购买的发起、完成、取消、被拦下或失败(只记大致的失败类别)、恢复购买、试用开始或结束、检查更新的结果、更新提示是否出现或被点击、通知提醒卡片是否出现或被点了开启、是否允许了通知、点开了哪类提醒,以及点击"给应用评分"入口,以及应用是否请求了系统评分弹窗(或为什么没有请求),以及是否开启了恶意网站拦截和广告与追踪器拦截(只记开或关,不含任何被拦截的网站或次数)。

我们不会逐条保存这些事件,只按事件、平台、应用版本和大致国家(您的设备首次注册时记录的国家)累加成每日总数。总数里不含您的设备标识、账户或 IP 地址。我们可能给不同设备显示略有不同的界面(例如首次打开时是否显示订阅页),这些每日总数会按界面版本分开统计。

为了衡量新设备在 1 天、7 天、30 天后的回访比例,我们还会为每台设备保存:2.1 节所述设备标识的单向加密哈希、首次看到该设备的日期,以及哪些天打开过应用(最多 64 天)。由于密钥由我们持有,这条记录可以对回您的设备记录,因此我们把它当作个人数据对待。它不含账户、位置、服务器或使用内容。

2.9 Apple Ads 归因

如果您是在 App Store 上点击或看到广告(Apple Ads)后安装的应用,Apple 可以告诉我们是哪个广告系列、广告组和关键词带来了这次下载。应用会向 Apple 的 AdServices 框架获取一个归因令牌。我们的订阅服务商 RevenueCat 用这个令牌向 Apple 查询上述信息,并保存在您的订阅记录中。应用只在您的设备上保存"是否来自广告",以及来自广告时的广告组编号。这一过程不使用广告标识符(IDFA),不请求跟踪权限,也不用于在其他公司的应用或网站上跟踪您。我们只用它衡量哪些 App Store 广告有效。

2.10 应用内一次性提问

在您于两个不同的日子连接成功之后,应用可能会询问一次您主要用 VPN 做什么。回答是自愿的,可以跳过。我们只保存按平台、App Store 国家或地区、大致时区分组(例如 UTC+7)和 Apple Ads 广告组(或"非广告")汇总的每日人数,不会把您的设备标识、账户或 IP 地址和回答一起保存。

2.11 网页付款订单

对于在我们网站上、而不是通过应用商店完成的付款(在提供网页付款的情况下,例如安卓应用),我们会保存订单记录:订单号、账户 ID 和账户邮箱(账户没有自己的邮箱时,例如通过 Telegram 登录、或通过 Apple 或 Google 登录但没有可用邮箱而建的账户,这是一个含有该登录账号 ID 或您账户 ID 的内部占位地址)、套餐和天数、金额和币种(及折合的美元金额)、付款方式、我们的收款地址或钱包账户、订单状态和相关时间(下单、付款期限、入账、退款),以及这笔订单给账户开通的会员到期时间。付款时,我们会保存付款凭据和到账金额:链上转账保存交易哈希、付款地址和到账时间;手机钱包付款保存交易号、您填写的备注(例如付款人姓名或手机尾号)和提交时间。退款时保存退款金额、退款时间和退款交易号。我们还会保存相关记录之间的关联(例如并入某个订单的付款),以及工作人员处理订单时写的简短备注(例如拒绝订单的原因)。

如果有一笔链上转账转入了我们的收款地址,却对不上任何订单,我们会保存它的交易哈希、付款地址、金额和时间,以便把它入账到正确的订单或账户,或原路退回。

这些记录用于给账户开通会员、处理退款和问题、记账、确保同一笔付款不会被重复计算,以及给您发送订单收据和 VIP 到期提醒。链上转账本身是公开的;我们通过区块链数据服务(TronGrid)查询转入我们收款地址的转账。钱包付款由钱包服务商处理,我们不会获得您的钱包密码或 PIN 码。需要人工核对的付款,我们可能会通过 Telegram 或邮件给自己发送提醒(见第 3 节)。通过 App Store 购买的订阅不会产生这些记录(见 2.5)。

2.12 新用户体验

我们可能会给新安装的设备提供几天免费的 VIP 体验。为了确保每台设备、每个账户只能领取一次,防止批量滥用,并了解体验是否有助于大家使用和订阅本服务,对于被分到体验组或不发体验的对照组的每台新设备,我们会在服务器上保存一条与设备标识(2.1)关联的记录,内容包括:分在哪一组以及测试名称;国家(为该设备检查体验资格时按网络判断)、平台和应用版本;体验的开始时间和原定结束时间;实际结束的时间和原因;对设备是否为运行我们应用的真实设备的检查结果和方式(2.1);以及体验开始后(对照组为检查后)7 天内该设备是否有付费会员、我们第一次看到的时间,以及该会员的购买方式(App Store,或在我们网站上用哪种付款方式)。为了比较两组,我们还会根据每台设备的每日流量统计(2.3)看它是否使用了 VPN,并根据连接凭证最近的使用时间(2.1)看应用在第一天之后是否再次使用。如果为该设备检查体验资格时您已登录,或在体验期间登录,这条记录可能会关联到该账户;退出登录或解绑设备不会去掉这个关联,注销账户会(见第 4 节)。体验资格检查、体验开始和结束的次数也会计入不含设备标识的每日总数(见 2.8)。

这条记录不保存您的 IP 地址。为了限制批量领取,我们按网络统计每天的领取次数:网段(IP 地址的前一部分,通常由许多用户共用,不是您的完整地址)只以加密钥的单向哈希保存,网络运营商的编号(ASN)原样保存。为了让每台设备在这些计数和每天的体验资格检查总数中只计一次,我们还会保存设备标识的加密钥单向哈希及这次检查的结果(例如设备不符合条件的原因)。这些计数和哈希最长 3 天后删除。

3. 服务提供商

提供商用途
AppleApp Store 分发、应用内购买、通过 Apple 登录、Apple Ads 归因
Google通过 Google 登录(确认您的 Google 账户)
Telegram通过 Telegram 登录(确认您的 Telegram 账户);开启时,向我们的工作人员发送需要核对的网页付款订单提醒(订单号、付款方式、金额、交易号或交易哈希的前几位;钱包付款还包括您填写的备注和账户邮箱)
RevenueCat订阅状态与收据验证;Apple Ads 归因(下载是否来自广告、来自哪个广告)
Cloudflare托管我们的接口、网站及内容分发
Resend代我们发送邮件,包括登录验证码和服务邮件(收据、VIP 到期提醒、安全通知);开启通知时,也把网页订单通知发到我们自己的邮箱。接收的信息:您的邮箱地址、邮件内容和邮件语言
TronGrid查询转入我们收款地址的链上转账(用于网页付款订单)
服务器托管商为我们的 VPN 服务器提供机房托管

这些提供商只为向我们提供服务而处理数据。我们不出售、出租或交易您的信息。

4. 保存期限

5. 您的选择和权利

6. 法律要求

在法律要求时,我们可能会披露第 2 节所述的有限信息。我们无法提供浏览记录、DNS 查询、流量内容或保存的 IP 地址,因为我们根本没有这些数据。

7. 安全

应用与我们服务器之间的流量是加密的;我们的接口通过 TLS 提供服务,系统访问权限仅限授权人员。

8. 儿童

本服务不面向 13 岁以下儿童,我们不会有意收集其个人信息。如果您认为有儿童向我们提供了数据,请联系我们,我们会删除。

9. 政策变更

如果本政策有变更,我们会在此页面发布新版本并更新上方日期;重大变更也会在应用内通知。

10. 联系我们

如有隐私相关的问题或请求(包括删除数据),请发邮件至 support@9fvpn.com。

9F Technologies LLC · 30 N Gould St, Sheridan, WY 82801, USA