LOCALTR / SECURITY
Know where the connection goes.
See what stays on your Mac, what passes through the relay and which records to review before sharing.
Local use
Browser → proxy on Mac → local serviceThe local proxy runs on your Mac. Local HTTPS needs macOS trust for the CA created by LocalTR. Your project's external service calls follow their own paths. LocalTR's own external connections, such as licensing, updates and opt-in diagnostics, are also separate from this local proxy path.
Public sharing
Visitor → relay → Mac → local servicePublic HTTP requests and responses pass through the LocalTR relay. This is not presented as end-to-end encryption that the relay cannot read, or as zero server data transit. HTTPS does not remove that relay path.
Public sharing requirementsCaptures and selective redaction
Inspection captures are stored on the Mac, may contain headers and bodies, and may remain on disk after the app closes. Selected headers such as Authorization, Cookie, Set-Cookie, Proxy-Authorization, X-API-Key and X-Auth-Token, plus particular JSON/form fields, are covered by redaction. Not every query parameter, free-text secret or personal field is guaranteed to be detected.
The forwarded HTTP data and the stored inspection copy are different. Redaction is not a firewall that clears all data sent upstream. Review captures before export or replay.
Local trust material
Local CA and certificate material is kept in the app's Application Support area. Source code includes private-key file permission controls; these are not an absolute guarantee against a compromised Mac. Do not share the private key or a complete folder backup as support evidence.
Deleting files does not prove that macOS certificate trust has been removed. The guide provides removal prechecks, not a guarantee of complete helper/CA/data cleanup.
Open removal prechecksPublic access and responsibility
Password protection is optional; without it, clients that know the public address can send requests to your service.
Protection uses Basic Auth. Incorrect credentials produce 401 for a new request; pause produces 503 for a new request. Other layers can also produce these status codes. Pause does not guarantee instant cancellation of all transfers. These controls do not replace your application's authorization; protect administration pages, production credentials and real customer data separately.
Follow the password and pause stepsOperational data and reporting
Local records, public transit, app diagnostics and website measurement are different data classes. This inventory shows the distinction and the limits of the verified explanation.
· Review of current native source and website configuration. Actual diagnostic delivery by the distributed package and the production log inventory require separate verification.
| Data class | Purpose | Location / path | Choice and limit | Cleanup / help |
|---|---|---|---|---|
| Local captures | HTTP inspection copy; may contain headers and bodies. | Written to disk on the Mac; may remain after the app closes. | Selective redaction does not find every sensitive field. Review before sharing. | Capture cleanup and removal must be verified for your installed package. Capture and replay limits |
| Public HTTP transit | Carry requests and responses between the internet and the local service. | Visitor ↔ relay ↔ Mac ↔ service; headers and bodies pass along this path. | Applies when public sharing is enabled. Transit does not mean persistent logging. | Password and pause |
| Server operational records | Service operation, abuse investigation and troubleshooting. | Fields stored in production, storage location and retention were not verified in this review. | No zero-log or fixed deletion-time guarantee is made. | Privacy and data requests |
| Routine app diagnostics | Limited aggregate technical counters. | A separate Mac-to-diagnostics-service path in current source. Host/domain/path and free-text errors are excluded from this counter payload. | Opt-in preference, off by default. The distributed package's preference and actual delivery require separate verification. | Check the preference in the app; ask about your package through support. |
| Crash reports | Crash investigation; content is separate from routine counters. | From the Mac to the configured reporting service; the package payload was not verified here. | Requires separate opt-in and reporting configuration. Counter field limits are not a guarantee for all crash content. | Preference / package support |
| Website measurement | Optional visit counts. | Belongs to this website; separate from Mac app diagnostics. | Currently disabled. No third-party advertising tracking code is loaded. | Website privacy notice |
| CA and local trust material | Create local HTTPS certificates. | Application Support on the Mac; macOS system trust is a separate record. | Do not share the private key or a complete folder backup. | Removal prechecks |
Report a security issue
Prepare app/macOS versions and environment, approximate time, expected and observed results, and redacted reproduction steps.
Do not send passwords, session cookies, license keys or a CA private key. Response and resolution times are not guaranteed.
Personal data request
Read the privacy notice for the scope and verification process of data requests. The contact address is the same: info@localtr.dev. Do not include unnecessary identity documents or sensitive data in your first message.
LOCALTR / HELP
Have a question about the data flow?
Start with the support template for a security report. The download-opening notification is a separate, optional product notification; it does not send a security report or start a trial.