← Back to App
Security & Threat Model

What Proxen protects — and what it doesn’t.

A complete, honest account of Proxen’s security architecture. No marketing language. No vague assurances. Just a clear-eyed assessment of how the system is built and where the real risks lie.

01 Security Architecture

Proxen’s architecture is designed around the principle of minimal attack surface. There are no Proxen servers. There is no Proxen database. Every prompt you type and every response you receive travels exclusively between your browser and Google’s AI API over an HTTPS-encrypted connection. Proxen itself is a static web application — a collection of HTML, CSS, and JavaScript files that runs entirely within your browser’s sandbox.

Your API key and conversation history are stored in your browser’s localStorage — on your device, in your browser, under your control. Proxen has no mechanism to transmit this data anywhere, because there is nowhere to transmit it to.

02 Data Flow Diagram

03 What Proxen Protects Against

Server breaches
There are no Proxen servers to breach. A compromised Proxen infrastructure cannot expose your data, because no such infrastructure exists.
Account database leaks
There are no user accounts. Proxen never asks for your name, email, or password. There is no Proxen account database that can be leaked.
Third-party tracking
No analytics, no tracking pixels, no telemetry scripts. Proxen loads only its own code and the Google Fonts stylesheet. Your usage is not observed.
Data mining by Proxen
Proxen cannot access or analyze your conversation data. It is a static client application with no backend, no connection pool, and no logging pipeline.
Cross-device profiling
Data never leaves your device via Proxen. Conversations and settings stored in localStorage remain local to that specific browser instance.

04 What Proxen Does Not Protect Against

Compromised browsers
If your browser is compromised at the process or OS level, any data in localStorage — including your API key — is at risk. Proxen cannot defend against this.
Malicious browser extensions
Browser extensions can read localStorage, inject scripts, and intercept network requests within the page. Only install extensions you trust from sources you trust.
Stolen or unlocked devices
Anyone with physical access to your unlocked device and browser can read your conversations and API key from localStorage. Lock your device and browser profile.
Network interception
While all API traffic is encrypted with HTTPS, sophisticated attackers on compromised networks (e.g. rogue captive portals with forged certificates) may pose risks depending on your device’s certificate trust store.
Google API vulnerabilities
Proxen relies entirely on Google’s API security. Any vulnerabilities in generativelanguage.googleapis.com are outside Proxen’s control. Review Google’s security practices independently.

05 Honest Assessment

Proxen’s serverless design eliminates an entire class of server-side vulnerabilities — breaches, leaks, and insider threats that affect traditional web applications simply do not apply here. That is a genuine, structural security advantage, not a marketing claim.

However, no application can protect against threats that originate on the device running it. The weakest links in the Proxen security chain are:

  • Your device’s physical and OS-level security
  • Your browser’s integrity and installed extension ecosystem
  • The security of Google’s Generative Language API
⚑ Proxen cannot protect against these threats. Maintaining a secure device, a clean browser profile, and awareness of Google’s API terms of service are your responsibility as the user.

06 Verification

You should not take these claims on faith. Everything described on this page is independently verifiable with tools built into your browser.

1
Inspect network traffic

Open DevTools → Network tab. Send a message in Proxen. Confirm that all API requests are directed exclusively to generativelanguage.googleapis.com. No requests to any Proxen domain should appear.

2
Read the source code

The complete, unminified source is available at github.com/xensenx/Proxen. Audit it yourself, or have someone you trust audit it. Every network call is visible in plain JavaScript.

3
Inspect local storage

Open DevTools → Application → Local Storage → your site origin. You can see exactly what Proxen has stored on your device — your API key, theme preference, and conversation history — and nothing else.

4
Verify no outbound connections at idle

Load Proxen without sending a message. The Network tab should show only the initial page load assets (HTML, CSS, JS, Google Fonts). Proxen makes no background pings, heartbeats, or telemetry calls.