Privacy Policy & Security Architecture

About the bundled "PersonalSOC" (a separate app): the promise above is about RoamSwitch itself. PersonalSOC analyzes logs entirely on the device, and its LLM integration is off by default. If you enable LLM integration, the details of detections and the log lines behind them (secrets masked) may be sent to an external service through the LLM command you select, and how they are handled follows the terms of that LLM's provider. See the PersonalSOC page for details. The Mac version connects to lafine.net to fetch the latest version information only when you press "Check for updates" in Settings (nothing about the device or logs is sent).

About the bundled "PathScope" (a separate app): the promise above is about RoamSwitch itself. PathScope performs its analysis of privilege-escalation paths entirely on the device, and stores the history of results and its settings only on the device. Its LLM integration is off by default. If you enable it, a summary of the analysis results (paths, fix points and so on) and the contents of the configuration files you have it read with "LLM assist" (by default, values that look like passwords or keys are replaced and files such as private keys are not sent; if you choose "unrestricted" in Settings, things like password hashes are sent too, but private key files are still not sent and API key and password values are still replaced; replacement cannot be guaranteed to find every secret) may be sent to an external service through the LLM command you select, and how they are handled follows the terms of that LLM's provider. See the PathScope page for details. The app connects to lafine.net to fetch the latest version information only when you press "Check for updates" under "Updates" (nothing about the device or the analysis results is sent).

About the bundled "AccessScope" (a separate tool). The promise above is about RoamSwitch itself. AccessScope performs its diagnosis of access logs entirely on the device. It stores on the device its settings, the list of logs found by discovery (log paths and short notes only), state files used to compare with the previous run (finding fingerprints, counts and timestamps, plus converted values (hashes) and timestamps of the User-Agent families and paths seen, used to compare with the usual; no log contents; a hash is not anonymization, and values with few candidates, such as IPv4 addresses, can be recovered by brute force) and the exclusion rules the user writes (including reasons and IPs), and AccessScope itself does not send any of these anywhere. Its LLM integration is off by default. If you enable it, a summary of the diagnosis (including statistics such as counts, the names of the input log files and the reasons the user wrote in exclusion rules, and the stages, counts, account names and periods contained in detections of activity across logs, logins from unfamiliar sources and differences from the usual; IPs are defanged or pseudonymized) and the evidence log lines (secrets are masked; however, the masking cannot be guaranteed to find every secret) and, for the log-finding feature, information about this device's environment such as the names of running servers, log paths, and the names and sizes of files (not file contents) may be sent to an external service through the LLM command you select, and how they are handled follows the terms of that LLM's provider. See the AccessScope page for details. On Mac, the app connects to lafine.net to fetch the latest version information only when you press "Check for updates" under "Updates" in Settings (nothing about the device or its logs is sent).