Privacy Policy

Overview

Probe is a local HTTP/HTTPS debugging proxy. We are committed to protecting your privacy. This policy explains what data Probe handles and how it is treated.

Data That Stays on Your Device

Everything you capture stays on your machine. All captured network traffic, certificates, settings, and session data are stored locally and never leave your device. Specifically:

• Network traffic — HTTP/HTTPS requests and responses captured by the proxy are stored only in local memory or local session files on your computer.
• CA certificates — Generated locally and stored in your home directory (~/.probe/). Private keys never leave your machine.
• Settings and preferences — Stored locally via system preferences. Not synced or uploaded anywhere.
• Saved sessions and collections — Stored as local files on your computer.

Data We Do Not Collect

Probe does not:

• Send any captured traffic — no URLs, hosts, headers, or request/response bodies — to external servers
• Track your browsing or debugging activity, or anything about what you inspect
• Require an account or login
• Use advertising cookies or cross-site trackers
• Sell your data or share it with advertisers

Anonymous Usage Analytics

To learn which features are actually used so we can improve Probe, the app sends a small amount of anonymous, aggregate usage data through Aptabase, a privacy-focused, open-source analytics service. This is opt-out: it is on by default and you can turn it off at any time in Settings → General → Privacy.

What is sent:

• That the app was launched, and the coarse platform (macOS or Windows)
• Which UI mode you choose (Probe, Proxyman, or Charles)
• That a core feature was used — the feature name only (e.g. Composer, Map Local, Map Remote, saving a session)
• App version and operating system, captured automatically by Aptabase

What is never sent:

• Any captured traffic — no URLs, hosts, headers, bodies, or timing
• Anything that could identify you or reveal what you are debugging
• No account, cookies, or persistent device identifiers are used

Analytics requests bypass Probe's own proxy, so they are never captured or routed through it.

Network Connections

Probe makes the following outbound network connections:

• Update checks — On launch, Probe checks for new versions via a GitHub Gist. This request contains no personally identifiable information.
• Proxied traffic — When the proxy is running, Probe forwards HTTP/HTTPS requests from your configured devices to their intended destinations.
• CA certificate server — Probe runs a local HTTP server (default port 9098) to serve the CA certificate to devices on your local network.
• Usage analytics — When enabled, anonymous usage events are sent to Aptabase (*.aptabase.com). These contain no captured traffic and no personal data, and the request bypasses Probe's own proxy. See the Anonymous Usage Analytics section above.

Upstream Proxy

If you configure an upstream proxy, Probe routes traffic through that proxy server. Credentials you enter for upstream proxy authentication are stored locally and sent only to the configured proxy server.

Security Considerations

Probe performs HTTPS interception (MITM) to inspect encrypted traffic. This means:

• Probe generates a local Certificate Authority (CA) that you install on your devices.
• Probe can see the decrypted contents of HTTPS traffic routed through it.
• This data is only visible within the Probe app on your machine and is not transmitted elsewhere.
• You should only use Probe on networks and devices you own or have permission to debug.

Children's Privacy

Probe is a developer tool and is not directed at children under 13. We do not knowingly collect any personal information from anyone, including children.

Changes to This Policy

We may update this policy from time to time. Changes will be posted on this page with an updated date.

Contact

If you have questions about this privacy policy, please contact us at vinhtnk@guide.inc or open an issue on our GitHub repository.