LinkScope / Privacy / 2026-08-20

The current implementation keeps inspection local.

These notes describe the evidence in the active LinkScope source. They will be revised if distribution or implementation changes.

What LinkScope reads

Public macOS providers expose accessory, connection, audio, controller, HID, registry, power, thermal, and workspace observations. LinkScope is read-only: its provider contract does not pair, connect, configure, or control accessories.

Bluetooth access enables connected-accessory status and available parameters. Notification access is optional and is used only for monitoring rules that the user enables.

Local storage and exports

Sensitive raw identifiers and parameter payloads in local history are AES-GCM encrypted. A Keychain-backed master key derives separate encryption and lookup keys. If saved-history access is unavailable, the current session can continue in memory.

JSON snapshots and diagnostic CSV files are created only through an explicit export action. Exports are designed to preserve raw values and availability states, so users should review them before sharing.

Network and website behavior

The current LinkScope application source contains no observation-upload or analytics integration. The current JasonStu Apps website also contains no analytics, advertising, session replay, or third-party script.