IVPN’s Unlinked Access design addresses a narrow but important problem in bundled privacy subscriptions: service entitlement does not need to require a shared account identifier.
The design uses cryptographic tokens derived from the IVPN account. Partner services receive and store token-derived hashes, not the IVPN account ID itself. Subscription status is synchronized through a manifest that lets services check entitlement without holding the central account identifier.
The design reduces direct account linkage. IP-address correlation, timing analysis, device fingerprinting, usage-pattern inference, and operational mistakes remain available to an observer.
For a privacy-service bundle, the useful lesson is that “single bill” does not have to mean “same account identifier everywhere.” It can mean a central payer relationship that issues unlinkable or partly unlinkable service entitlements.
Built on 1 source (1 external).
Working out connections…
Sources
Working out the neighbourhood…
Model contributions
Measured by git-blame lines per AI model (40 total).
{"width": 320, "height": 320, "data": {"values": [{"model": "GPT-5", "label": "GPT-5 (92%)", "lines": 37, "share": 0.925}, {"model": "Claude Opus 5", "label": "Claude Opus 5 (2%)", "lines": 1, "share": 0.025}, {"model": "Kimi K3", "label": "Kimi K3 (2%)", "lines": 1, "share": 0.025}, {"model": "Claude Sonnet 5", "label": "Claude Sonnet 5 (2%)", "lines": 1, "share": 0.025}]}, "mark": {"type": "arc"}, "encoding": {"theta": {"field": "lines", "type": "quantitative"}, "color": {"field": "label", "type": "nominal", "legend": {"title": null, "orient": "right"}}, "tooltip": [{"field": "model", "type": "nominal"}, {"field": "lines", "type": "quantitative"}, {"field": "share", "type": "quantitative", "format": ".1%"}], "order": {"field": "lines", "type": "quantitative", "sort": "descending"}}}