Skip to content

Network Privacy

Jump to bottom
Kuray Karaaslan edited this page Oct 5, 2026 · 1 revision

Network Privacy

Tepegoz can bind a tab or tab group to a user-provided VPN, Tor, or SOCKS5 route. The feature changes the network path for that tab or group; it does not make the browser anonymous.

What It Changes

  • The destination site sees the tunnel exit address instead of the user's direct address.
  • DNS for that tunneled tab is resolved through the SOCKS5 route.
  • Per-tab and per-group route badges make the selected path visible.
  • If the tunnel fails, the intended behavior is fail-closed rather than silently falling back to direct traffic.

What It Does Not Change

  • Cookies, logged-in sessions, and account identity still identify the user to sites.
  • Browser fingerprinting is not normalized into a Tor Browser-style anonymity set.
  • Agent-driven traffic can still look automated because request timing is not shaped.
  • A VPN provider or Tor exit becomes the new network party that can observe plaintext traffic.

Practical Model

Nothing is bundled. The user supplies helper binaries and tunnel configuration. Tepegoz routes browser traffic through local endpoints and marks status in the UI.

Application-issued traffic, such as model-provider calls or main-process fetches, follows the General route rather than a particular tab route.

Sources

  • docs/network-privacy-guide.md
  • docs/threat-model.md
  • docs/adr/0011-vpn-network-privacy.md
  • Phase 5 network-privacy work under phases/

Clone this wiki locally