[{"data":1,"prerenderedAt":160},["ShallowReactive",2],{"blog:what-data-does-a-vpn-see":3},{"zh-CN":4,"en":87},{"blocks":5,"faq":71},[6,9,11,13,17,19,21,23,26,34,37,44,46,49,51,53,55,58,60,62,64,67,69],{"type":7,"html":8},"p","回答「VPN 是什么」这个问题之前，很多人心里其实先问的是另一件事：用了 VPN 之后，服务商本身能看到我的哪些数据？这个问题比「VPN 是什么」更具体，答案也更值得说清楚——用了 VPN 不等于对谁都变成一片空白，只是原来看得到的东西换了个位置，落到了不同的人手里。",{"type":7,"html":10},"这篇按「谁在什么时候能看到什么」来讲：连接的时候，本地网络、VPN 服务商、目标网站分别站在什么位置；服务商在连接瞬间技术上一定会经手的是哪几项；哪些东西无论用不用 VPN、政策写得多严格，都轮不到它看到。",{"type":7,"html":12},"先说清楚这篇的范围：讲的是 VPN 服务商这一端能看到什么，不是目标网站那一端。你登录的账号、买了什么、发了什么消息，目标网站自己心里有数，这不是 VPN 管得到的事，后面会单独说清楚这条界线画在哪。",{"type":14,"id":15,"html":16},"h2","bp-vantage","连接的时候，到底是谁在经手你的流量",{"type":7,"html":18},"把一次连接拆开看，涉及三个不同的位置：你本地的网络（家里的 Wi-Fi、公司网络，或者手机信号）、中间的 VPN 服务商，还有最终的目标网站。没有 VPN 的时候，本地网络能看到你连的是哪个网站；用了 VPN 之后，本地网络只能看到你连了 VPN 这个中间点，看不到你实际访问的是哪个网站——这一段的具体机制，\u003Ca href=\"\u002Fblog\u002Fvpn-encryption-basics\u002F\">VPN 加密入门\u003C\u002Fa>那篇讲得更细。",{"type":7,"html":20},"换个角度想会更直观：没有 VPN 的时候，你的网络运营商站在你和整个互联网之间，能看到你连的每一个网站；用了 VPN，相当于在你和运营商之间多加了一层，运营商现在只看得到「你连了 VPN 这个中间点」，看不清后面具体去了哪——但 VPN 这一层本身，站的位置正好是原来运营商站的位置，看到的东西自然也接近。",{"type":7,"html":22},"所以「本地网络看不到」和「没有人看到」不是一回事，看到的位置换成了 VPN 服务商这一端。这篇要讲清楚的，正是换到这个新位置之后，具体能看到什么、看不到什么，两边各占了多大一块。",{"type":14,"id":24,"html":25},"bp-sees","VPN 服务商在连接瞬间技术上会经手什么",{"type":27,"items":28},"list",[29,30,31,32,33],"你的真实出口 IP——设备连接节点时用的地址，这是建立连接的必要条件，任何一家服务商，不管政策写得多严格，这一步都绕不过去。这个 IP 只在连接节点的那一刻和它有关，跟你设备在其他网络下用的地址是两回事，换一个网络、换一个节点，这个 IP 本身也会跟着变。","连接建立和结束的时间点——你连了多久、什么时候断开，这类时间戳信息在连接过程里天然存在，不是服务商额外收集来的，但单独存在时，跟「你当时具体在做什么」之间没有直接对应关系。","这段连接传输的总流量大小——多少数据量经过了这条线路，通常也是运营和限速要用到的数字，跟内容本身是两件事；流量是个总量数字，不会告诉服务商这些数据具体花在了哪个网站或者哪个 App 上。","你要连接的目标地址在路由层面要经过它——道理和快递中转站一样，中转站要知道包裹送到哪个网点，才能把包裹转发出去，域名信息可能会在这个环节短暂经手，哪怕内容本身是加密的、读不出来。","这次连接大致是在持续传输大量数据，还是间歇性的小额往来——这类粗粒度的模式在流量层面本身就看得出来，不需要读懂内容也能看出个大概，这也是为什么单纯说「内容加密了」并不等于「什么都藏住了」。",{"type":14,"id":35,"html":36},"bp-not-see","这段时间之内，服务商具体看不到什么",{"type":27,"items":38},[39,40,41,42,43],"网页或者 App 里具体的内容——你打的字、发的消息、看的哪一页，被目标网站自己的加密（地址栏那把锁）处理过之后，这一层是读不出来的。","你在目标网站登录的账号、填的表单——那是目标网站自己记录的东西，从来不在 VPN 这一层的「看得懂」范围内，换哪家服务商都一样。","断开连接之后你在设备上做的事——那已经完全在 VPN 能触及的范围之外，跟这段连接没有关系，不会因为之前连过就留下尾巴。","你在设备本身装了哪些其他 App、存了什么文件——这些完全是设备本地的信息，跟有没有连接 VPN 没有任何关系，VPN 从一开始就触及不到这一层。","你在同一台设备上，没走这条 VPN 连接的其他流量——如果只有部分应用被设置成走这条隧道，剩下的流量本来就在这层保护范围之外，这不是 VPN「漏看了」，是它本来就没被安排经手这一段，两者的区别值得分清楚，免得高估了保护的范围。",{"type":45},"downloads",{"type":14,"id":47,"html":48},"bp-logs","无日志政策改变的是「看到之后」那一步",{"type":7,"html":50},"上面列的几项，是连接那一瞬间技术上会经手的东西，不是「服务商记录了什么」。这两件事经常被混着说，但完全不是一回事：会经手，不代表会被写成记录、长期留存下来。",{"type":7,"html":52},"举个例子，一家服务商完全可以做到「连接建立的那一刻确实经手了你的 IP」，同时也做到「这条信息几十秒后就从内存里清掉，从没写进任何数据库」——这两件事同时成立，并不矛盾，说的是同一件事的两个不同阶段。",{"type":7,"html":54},"有没有留存、留存多久、留存之后怎么处理，是无日志政策要回答的问题，跟连接瞬间技术上会经手什么是两个不同层面，一个说的是「存不存在」，一个说的是「会不会被记下来」。\u003Ca href=\"\u002Fblog\u002Fwhat-is-a-no-logs-policy\u002F\">无日志政策到底意味着什么\u003C\u002Fa>那篇专门拆解了后面这一步该怎么读懂。",{"type":14,"id":56,"html":57},"bp-practical","知道了这些，具体能改变什么",{"type":7,"html":59},"担心的如果是「本地网络或者公共 Wi-Fi 能不能看到我访问的内容」，VPN 加密这一层直接解决，管的正是这一段，公共场所连的免密码热点是这一层保护最能派上用场的场景。担心的如果是「这段连接会不会被长期记录、留下痕迹」，那要看的是无日志政策写得认不认真，不是加密这一层——两个担心对应两个完全不同的答案，混着问容易得到似是而非的结论。",{"type":7,"html":61},"换节点能改变的是「目标网站看到的出口地址」，改变不了「服务商自己知不知道这是你的账号」——登录用的还是同一个账号，付款信息也没变，这两层不要混在一起判断，无日志和「匿名」不是同一个承诺。",{"type":7,"html":63},"至于免费产品会不会拿这些数据做别的用途，\u003Ca href=\"\u002Fblog\u002Ffree-vpn-risks-explained\u002F\">免费 VPN 的真实代价\u003C\u002Fa>那篇讲过，不靠订阅赚钱的产品，数据本身更容易变成收入来源，判断一个产品值不值得信任，这也是该看的一项，比只看宣传语可靠得多。同样一份连接信息，落在靠订阅盈利的产品手里和落在靠数据变现的产品手里，处理方式很可能完全不一样，这才是选服务商时真正该关心的差别。",{"type":14,"id":65,"html":66},"bp-final","总结",{"type":7,"html":68},"VPN 不是让你对谁都变成一片空白，而是把「谁能看到你在访问什么」这件事，从本地网络换到了 VPN 服务商这一端。服务商在连接瞬间技术上会经手出口 IP、连接时间、流量大小和目标地址这几项，但看不到内容本身、看不到你登录了哪个账号，断开之后的事更是完全触及不到。",{"type":7,"html":70},"这几项列出来，是为了让「VPN 能不能保护隐私」这个问题有一个具体、可以核对的答案，而不是停留在「应该可以吧」这种模糊的猜测上。想先弄清楚 VPN 整体解决的是什么问题，\u003Ca href=\"\u002Fblog\u002Fwhat-is-a-vpn\u002F\">VPN 是什么\u003C\u002Fa>从更基础的地方讲起。\u003Ca href=\"\u002Fsecurity\u002F\">快橙\u003C\u002Fa>执行无日志政策，不把上面这些连接信息写成能追溯到账号的长期记录，\u003Ca href=\"\u002Forder\u002F\">注册\u003C\u002Fa>后每天有免费试用时长，想验证这一层说得认不认真，先用起来看看比什么都管用。",[72,75,78,81,84],{"q":73,"a":74},"服务商看不到我发的消息内容，那它凭什么知道我用了多少流量？","流量大小是「传输了多少数据」这个数字，不需要读懂内容也能统计，就像快递称重不用打开包裹一样。内容和流量大小是两件不相关的事，一个看得到，一个看不到。",{"q":76,"a":77},"VPN 能不能让网站不知道是我登录的？","不能，这不是 VPN 要解决的问题。你登录了哪个账号，是目标网站自己的记录，跟连接走的是哪条线路没有关系，VPN 不参与、也改变不了这一层。",{"q":79,"a":80},"目标网站能看到我的真实位置吗？","网站看到的出口地址会是你连接的节点，不是你自己网络本身的出口，网站据此判断的地区会跟着变成节点所在的地区，但这只是地址层面的变化，不是承诺网站完全没有任何办法判断。",{"q":82,"a":83},"无日志政策和这篇讲的是不是一回事？","不是一回事，是相邻的两件事。这篇讲的是连接瞬间技术上会经手什么，无日志政策讲的是这些信息之后会不会被写成记录、留存多久，\u003Ca href=\"\u002Fblog\u002Fwhat-is-a-no-logs-policy\u002F\">无日志政策到底意味着什么\u003C\u002Fa>专门讲后面这一步。",{"q":85,"a":86},"换个节点，服务商是不是就看不到我是谁了？","看不到你访问了哪个网站是一回事，但账号和付款信息本身还是跟你的注册身份绑定的，换节点不会让这一层消失，这是无日志政策和「匿名」两个概念常被混淆的地方。",{"blocks":88,"faq":144},[89,91,93,95,97,99,101,103,105,112,114,121,122,124,126,128,130,132,134,136,138,140,142],{"type":7,"html":90},"Before answering "what is a VPN," a lot of people are really asking something more specific: once I'm connected, what can the provider itself see about me. That question deserves a real answer — using a VPN doesn't make you invisible to everyone, it just moves what's visible to a different place, into different hands.",{"type":7,"html":92},"This covers who sees what, and when: where your local network, the VPN provider, and the destination site each stand at the moment of a connection; exactly what a provider technically handles the instant a connection is made; and what stays out of its reach no matter how the policy is written.",{"type":7,"html":94},"One boundary worth setting first: this covers what the VPN provider's side sees, not the destination site's side. Which account you're logged into, what you bought, what you typed — the destination site keeps its own record of that, and it's not something a VPN reaches into. That line gets drawn more precisely further down.",{"type":14,"id":15,"html":96},"Who actually handles your traffic at the moment of connection",{"type":7,"html":98},"Break a single connection into three positions: your local network (home Wi-Fi, an office network, or a phone signal), the VPN provider in the middle, and the destination site at the far end. Without a VPN, the local network can see exactly which site you're connecting to; with one, the local network only sees that you connected to the VPN — it loses sight of the actual destination. \u003Ca href=\"\u002Fen\u002Fblog\u002Fvpn-encryption-basics\u002F\">The basics of VPN encryption\u003C\u002Fa> covers the mechanics of that part in more depth.",{"type":7,"html":100},"It helps to flip the view around: without a VPN, your ISP sits between you and the entire internet, seeing every site you connect to. With one, there's now an extra layer between you and the ISP — the ISP sees only "connected to a VPN" and loses the destination. But the VPN occupies roughly the position the ISP used to occupy, so what it sees is, unsurprisingly, similar in kind.",{"type":7,"html":102},"So "the local network can't see it" and "no one can see it" are not the same claim — what's visible moved to the VPN provider's side instead. The rest of this covers exactly what that new vantage point can and can't see, and how much of the picture each half actually covers.",{"type":14,"id":24,"html":104},"What a provider technically handles the moment you connect",{"type":27,"items":106},[107,108,109,110,111],"Your real outbound IP — the address your device uses to reach the node. This is a precondition for the connection existing at all, and no provider, however strict its policy, skips this step. That IP only applies to that one moment with that one node — it's a different thing from whatever address your device uses on other networks, and it changes the moment you switch networks or nodes.","When the connection started and ended — timestamps that exist naturally as part of any connection, not something collected on top of it. On their own, though, a timestamp doesn't map to what you were actually doing at the time.","How much data moved over that connection in total — a number providers typically use for operations and rate-limiting, and a different thing entirely from content. It's a total; it doesn't tell the provider which site or app that data belonged to.","The address you're connecting to has to pass through it at the routing level — the same logic as a courier hub: the hub needs to know which branch a package is headed to before it can forward it. Domain information can pass through briefly at this stage even when the content itself is encrypted and unreadable.","Roughly whether a connection is one long transfer or a string of small intermittent exchanges — that coarse pattern is visible at the traffic level on its own, without reading any content, which is exactly why "the content is encrypted" doesn't mean "nothing about it is visible."",{"type":14,"id":35,"html":113},"What stays completely out of reach during that same window",{"type":27,"items":115},[116,117,118,119,120],"The actual content inside a page or an app — what you typed, what you sent, which specific page you viewed — once the destination site's own encryption (the padlock in the address bar) has processed it, this layer can't read it.","Which account you're logged into on the destination site, or what you filled into a form there — that's the destination site's own record, never something a VPN layer can read, and that stays true no matter which provider is in the middle.","Whatever you do on the device after disconnecting — that's entirely outside anything a VPN touches, unrelated to the connection that just ended, and it doesn't leave a trail just because a connection happened earlier.","Whatever other apps are installed on the device, or what files are stored on it — purely local information that has nothing to do with whether a VPN is connected; a VPN never had access to that layer in the first place.","Any other traffic on the same device that isn't routed through this particular connection — if only some apps are set to use the tunnel, the rest was never inside this layer's coverage to begin with. That's not the VPN "missing" something; it was simply never asked to handle that traffic, and the difference is worth keeping straight so the scope of protection doesn't get overestimated.",{"type":45},{"type":14,"id":47,"html":123},"What a no-logs policy changes is the step after seeing it",{"type":7,"html":125},"Everything listed above is what technically passes through at the moment of connection — it is not the same claim as "the provider recorded it." Those two ideas get blended together constantly, but they're not the same thing at all: passing through doesn't mean it gets written down and kept.",{"type":7,"html":127},"For example, a provider can genuinely do both at once: handle your IP the instant a connection is made, and also clear that piece of information from memory thirty seconds later, never writing it to any database. Those two things aren't in tension — they're two different stages of the same event.",{"type":7,"html":129},"Whether something gets retained, for how long, and what happens to it afterward is exactly what a no-logs policy answers, and that's a different layer from what technically passes through at the moment of connection — one is about whether something exists at all, the other is about whether it gets written down. \u003Ca href=\"\u002Fen\u002Fblog\u002Fwhat-is-a-no-logs-policy\u002F\">What a no-logs policy actually means\u003C\u002Fa> covers how to read that second part properly.",{"type":14,"id":56,"html":131},"What this actually changes in practice",{"type":7,"html":133},"If the worry is "can my local network or public Wi-Fi see what I'm browsing," VPN encryption is the layer that answers it directly — that's exactly the part it covers. If the worry is instead "will this connection get recorded and leave a trail," the answer depends on how seriously the no-logs policy is written, not on encryption — two different worries, two different answers, and mixing them up tends to produce a conclusion that sounds right without actually being right.",{"type":7,"html":135},"Switching nodes changes the address the destination site sees; it doesn't change whether the provider itself knows this is your account. The same login, the same payment details — that layer doesn't disappear just because the node did. This is exactly where no-logs and "anonymous" get confused for each other.",{"type":7,"html":137},"As for whether a free product puts this data to some other use, \u003Ca href=\"\u002Fen\u002Fblog\u002Ffree-vpn-risks-explained\u002F\">the real cost of free VPNs\u003C\u002Fa> covers that — a product not funded by subscriptions makes the data itself a more likely revenue source, and that's worth weighing when judging whether a product deserves trust, more so than the marketing copy. The same connection information behaves very differently depending on whether it lands with a subscription-funded product or a data-funded one, and that difference is the one actually worth caring about when choosing a provider.",{"type":14,"id":65,"html":139},"In summary",{"type":7,"html":141},"A VPN doesn't make you invisible to everyone — it moves who can see what you're connecting to from the local network over to the VPN provider. The provider technically handles the outbound IP, connection timing, data volume, and destination address at the moment of connection, but it can't see the content itself, can't see which account you're logged into, and has no reach at all into anything after you disconnect. Listing these out is what turns "can a VPN protect privacy" into a specific, checkable answer instead of a vague "probably."",{"type":7,"html":143},"To start from what a VPN solves in the first place, \u003Ca href=\"\u002Fen\u002Fblog\u002Fwhat-is-a-vpn\u002F\">what a VPN is\u003C\u002Fa> covers that from the ground up. \u003Ca href=\"\u002Fen\u002Fsecurity\u002F\">FastOrange\u003C\u002Fa> runs a no-logs policy and doesn't turn this connection information into a long-term record tied back to an account — \u003Ca href=\"\u002Fen\u002Forder\u002F\">signing up\u003C\u002Fa> gets free trial time every day, and testing it yourself says more about whether that promise holds up than any of this does.",[145,148,151,154,157],{"q":146,"a":147},"The provider can't see the content of my messages — so how does it know how much data I used?","Data volume is just a number — how much passed through — and reading that number doesn't require reading the content, the same way a courier can weigh a package without opening it. Content and volume are unrelated things; one is visible, the other isn't.",{"q":149,"a":150},"Can a VPN keep a website from knowing it's me logging in?","No, and that's not a problem a VPN is built to solve. Which account you log into is the destination site's own record, unrelated to which route the connection took. A VPN doesn't touch that layer and can't change it.",{"q":152,"a":153},"Can the destination site see my real location?","The site sees the address of the node you connected through, not your own network's address, and whatever region it infers will follow the node instead. That's a change at the address level — it isn't a promise that a site has no way at all to make a judgment.",{"q":155,"a":156},"Is this the same thing as a no-logs policy?","No, they're adjacent but different. This page covers what technically passes through a connection at the moment it happens; a no-logs policy covers whether that gets written down afterward and for how long — \u003Ca href=\"\u002Fen\u002Fblog\u002Fwhat-is-a-no-logs-policy\u002F\">what a no-logs policy actually means\u003C\u002Fa> covers that second part.",{"q":158,"a":159},"If I switch nodes, does the provider stop knowing who I am?","Not seeing which site you visited is one thing, but your account and payment details are still tied to the identity you signed up with — switching nodes doesn't erase that layer. This is exactly where no-logs and "anonymous" get confused for each other.",1793918312075]