1. Local-first traffic inspection
ProxyLens is designed to inspect traffic on your Mac. Captured requests, responses, and saved sessions are not uploaded to XeonTech unless you deliberately export or share them with support.
ProxyLens security
Information & Data Security
ProxyLens handles network traffic, saved sessions, exported logs, and optional agent context. This page explains the security posture users should expect.
2. Sensitive traffic
Captures may include tokens, cookies, credentials, API keys, personal data, customer data, or proprietary payloads. Treat saved sessions and exports as sensitive development artifacts.
3. HTTPS certificate handling
HTTPS decryption requires a locally trusted certificate. Only enable inspection for development and debugging contexts where you have permission. Remove or distrust certificates you no longer use.
4. Log sharing
ProxyLens helps you share focused logs with your team, but you are responsible for reviewing exports before sending them. Redact authorization headers, session cookies, account identifiers, payment data, and confidential payloads.
5. MCP server and agents
The ProxyLens MCP server can make structured debugging context available to compatible tools or agents. Before connecting an agent, confirm which tool is receiving context and whether that tool sends data to a third-party service.
6. Support data
When contacting XeonTech support, send the smallest useful repro and redact secrets first. We may request version details, crash logs, configuration notes, or redacted sample traffic to investigate an issue.
7. Customer responsibilities
You are responsible for access control on your Mac, secure handling of exports, compliance with your organization policies, and lawful use of traffic inspection tools.
8. Reporting security concerns
Report suspected ProxyLens security issues through XeonTech support. Include impact, reproduction steps, affected version, and whether sensitive data may be involved.