The short version. HTTrail captures on your device or a Mac/proxy you select. Remote capture can send traffic, captured flows, diagnostics, and pairing information to that destination. Pairing with a Mac also transfers CA material as explained below. The developer does not automatically receive your captures; you can send information to us if you choose to contact support or share an export.
Contents
1. Scope & who we are
This Privacy Policy explains how the HTTrail application and these HTTrail product, support, and legal pages handle information. HTTrail is provided by Anusoft ("we", "us", "our"). It covers the macOS and iOS versions; available features depend on the platform and build.
HTTrail is an HTTPS debugging proxy and API client for traffic you are authorized to inspect. You choose the capture target, destination servers, and any export or sharing recipients.
2. What the developer receives
The app does not require an account and does not include developer analytics, advertising, activity tracking, or automatic third-party crash-reporting SDKs. We do not operate an account-based backend that automatically receives your captured traffic, API collections, or credentials. We do not sell your capture data.
This does not mean data can never leave a device. The proxy forwards traffic, remote mode transfers information to your selected Mac or proxy, and you can export files, copy data, or send a support message. These are described separately below.
3. Capture data and storage
When you route traffic through HTTrail or send requests from its API client, the app may process URLs, methods, headers, cookies, authentication tokens, API keys, session credentials, request and response bodies, realtime messages, timing, status codes, and connection metadata. Captures can therefore contain highly sensitive personal or confidential information.
Captured sessions, request history, collections, environments, rules, and settings are stored on the device running that capture or client. On macOS this uses the user's Application Support storage; on iOS it uses the app container and shared App Group storage used by the app and Packet Tunnel extension.
In paired remote mode, captured flows and diagnostics can be sent to and saved on your selected Mac. Pairing includes a device name and identifier and capture-session information. A manually selected proxy or relay also processes traffic routed through it. Copies may therefore exist on more than one device.
4. Your certificate authority and pairing
Builds that support HTTPS interception generate a local root Certificate Authority (CA) and use it to issue certificates for the hosts you choose to inspect. Trusting that CA allows the corresponding proxy to decrypt those connections. The sandboxed Mac App Store build does not provide CA-based HTTPS interception.
Pairing transfers the CA certificate and private key from the phone to the Mac you select, so the Mac can run a dedicated proxy for that device. The current pairing mechanism uses HTTP on your local network, so use it only with a trusted Mac and trusted network. The Mac holds the received CA in memory for the paired proxy rather than writing that received key to its keychain or capture files. This is distinct from the Mac's own locally generated CA and from saved traffic sessions.
A configuration profile or exported root certificate contains the public certificate needed for trust; it is not the same as the private key sent during pairing. Protect private keys and any device that holds them. We do not automatically receive your CA material.
Trust only authorized systems. Install or trust the HTTrail CA only on devices you own or are authorized to administer. Stop capture, restore proxy/VPN settings, and remove the installed profile or trusted CA when you no longer need it. Unpairing stops the paired proxy; it does not delete previously saved capture sessions. See support guidance and the Terms of Use.
5. Network connections and sharing
- Proxying and API requests: traffic is forwarded to the origin server, proxy, or relay you configure. Composing, replaying, and realtime connections contact the endpoint you select. Those recipients receive the request information sent to them.
- Paired capture: your chosen Mac receives pairing data and can receive captured flows and connection diagnostics from the phone. This is a user-selected remote capture path, not an automatic developer upload.
- Discovery and setup: local-network discovery, pairing, and profile installation communicate with your chosen devices or a local profile-serving endpoint.
- Exports and clipboard: you can save HAR files, body bytes, header dumps, certificates/profiles, and generated request code, or copy content to the system clipboard. Files and copied commands can retain credentials. Sharing or pasting sends them to the destination you choose.
The receiving Mac, proxy, origin server, app, or file-sharing recipient has its own storage and privacy practices. HTTrail does not add the developer as a recipient automatically.
6. Retention and your controls
Saved captures and request history remain in their respective device stores until you delete them. Use the in-app controls to delete selected flows or sessions, delete saved sessions, clear request history, and clear diagnostics where offered. Stop active capture first if you do not want new records to be created.
Deleting on the phone does not delete copies already saved on a paired Mac, and deleting a session does not necessarily clear separate history, diagnostics, exports, collections, or settings. Clear the relevant category on each device. Unpairing or changing the capture target stops that route but does not retract previous data.
Remove files saved or shared elsewhere and manage backups separately. Removing the app does not necessarily remove macOS Application Support files, trusted certificates, configuration profiles, proxy settings, shared copies, or backups. Follow the support cleanup steps rather than assuming uninstalling performs every cleanup action.
7. This website
These static pages are hosted through Cloudflare. Serving and protecting the site involves request metadata such as IP address, requested URL, request time, browser/system information, and traffic or security data. Cloudflare may retain service or security logs according to the service configuration and its policies. See Cloudflare's privacy policy.
The pages do not embed advertising, analytics, external fonts, third-party media, or forms. They do not upload your HTTrail captures. Following an App Store, download, or GitHub link opens a separate service with its own policy.
8. Third-party services and support
HTTrail uses open-source libraries for networking and cryptography. These are part of the app, not analytics services. Network requests you make still reach the chosen destination and may pass through a configured proxy or relay.
If you email contact@anusoft.com, we receive your address, message, and attachments you choose to send. We use them to respond and investigate, and retain them as needed for support and applicable legal obligations. Send only necessary, redacted details. Do not send private CA keys, passwords, or unredacted session tokens.
9. Security
Protect every capture device, selected Mac, export, and private key. Use a trusted local network for pairing, strong device passwords, operating-system account protection, and disk encryption where available. Avoid exposing capture or pairing ports to untrusted networks. HTTPS inspection deliberately changes the trust path and exposes decrypted content to the proxy; it does not make third-party traffic safe.
HAR files, headers, body exports, and generated cURL commands are not automatically anonymous. Even a HAR exported without response bodies can retain URLs, cookies, authorization headers, and request bodies. Review and redact before sharing. No storage or network method guarantees absolute security.
10. Authorized use and your choices
Use HTTrail only on devices, systems, and traffic you own or are explicitly authorized to inspect. You are responsible for lawful capture and sharing. See the Terms of Use. You can choose the capture route, stop capture, remove CA trust, and delete local records.
Depending on your location, you may have rights to access, correct, delete, or receive a copy of personal information we hold, or to object to certain processing. Contact us about website or support information. We cannot remotely access or erase captures held only on your devices or by recipients you selected.
11. Children's privacy
HTTrail is a developer tool and is not directed at children. It does not automatically send children's captured traffic to us. If a child has sent personal information to support, a parent or guardian may contact us to request its removal.
12. International users
You choose the origin servers, capture destinations, and export recipients, which may be in other countries. Website hosting and support providers may also process information internationally. Applicable privacy law and provider safeguards govern those activities; local capture does not imply that every transfer remains within one country.
13. Changes to this policy
We may update this policy to reflect changes in the app or website. We will revise the date above and provide further notice where required. A material change in automatic developer collection would be described before that change takes effect.
14. Contact
Anusoft
Email: contact@anusoft.com