← Back to App
Privacy & Data

Your data. Your device.
Always.

Proxen is designed with a privacy-first philosophy. This page explains precisely what is stored, where it lives, and what we will never touch.

Last updated: 2026-08-06

What Data Is Stored

Proxen stores the minimum amount of data needed to function. Everything persisted is written to your browser's localStorage and never leaves your device via Proxen.

  • API Key — Your Google Gemini API key, stored locally so you don't need to re-enter it on every visit.
  • Username — The display name you set in the app, used to personalise the interface.
  • Task List — Any tasks or to-do items you create within the app, saved so they persist across sessions.
  • Recent Conversation Context — The last 6 messages from your current conversation are kept in memory to provide coherent, context-aware AI responses during a session.
  • UI Preferences — Settings such as your chosen theme (dark / light), stored under the key proxen_theme.

Where It Is Stored

All data listed above lives exclusively in your browser's localStorage for the Proxen origin. It is scoped to your browser profile on your device.

No cloud sync by Proxen. Proxen does not operate any servers, databases, or cloud infrastructure. There is no Proxen backend that your data is sent to, synced with, or backed up on. Data stays exactly where localStorage puts it — on your machine.

What Data Is Never Collected

Proxen does not collect, transmit, or process any of the following — not now, not ever:

  • Email addresses or any form of account credentials
  • IP addresses or geolocation data
  • Analytics, telemetry, or usage metrics
  • Device fingerprints or hardware identifiers
  • Browsing history or cross-site tracking
  • Personally identifiable information (PII) of any kind
  • Crash reports or error logs sent to a remote server
There are no tracking pixels, no third-party analytics scripts, and no advertising SDKs embedded in Proxen. The app is entirely client-side.

Third-Party Data Sharing

When you send a message in Proxen, your message (along with the recent conversation context) is transmitted directly from your browser to Google's Gemini API using the API key you provided.

  • The API request travels from your browser → Google's servers directly.
  • Proxen never acts as a proxy or relay — your messages do not pass through any Proxen-operated server.
  • Proxen never receives, logs, or stores a copy of your conversation.
  • Google's own data handling practices apply to anything sent to the Gemini API. Refer to the Google Privacy Policy ↗ and the Gemini API Terms of Service ↗ for details on how Google handles API data.
Your API key is sent as a request header directly to Google. It is never transmitted to, or accessible by, any Proxen-operated endpoint.

How to Remove All Data

You have full control over your locally stored data. There are three ways to erase everything:

Option 1 — In-app Reset

  1. 1 Open Proxen and navigate to Settings (gear icon).
  2. 2 Click the Reset System button.
  3. 3 Confirm the prompt. All stored keys, tasks, username, and preferences will be wiped immediately.

Option 2 — Browser DevTools

  1. 1 Open DevTools with F12 (or Ctrl+Shift+I / Cmd+Option+I).
  2. 2 Go to the Application tab → Storage → Local Storage.
  3. 3 Select the Proxen origin and delete individual keys, or click Clear All.

Option 3 — Clear Site Data

  1. 1 In your browser settings, navigate to Privacy & Security → Site Settings (or "Manage Website Data").
  2. 2 Search for the Proxen domain and select Clear data or Delete.
  3. 3 This removes all site storage including localStorage, cookies, and cached files for the domain.

Contact & Feedback

Proxen is an open-source project maintained by xensenx. If you have questions about this privacy policy, discover a data-handling issue, or want to suggest improvements, please reach out via GitHub:

  • Open an issue or discussion on the Proxen GitHub repository ↗
  • All source code is publicly auditable — you can verify every data-handling claim made on this page by reading the code directly.