TrayPilot Privacy Policy
TrayPilot is a local Windows utility. It does not require an account and
does not send personal data, telemetry, audio, microphone recordings,
screen captures, packet contents, or user documents to a server. The app
reads local display, audio, network-adapter, and Windows settings needed
to provide its controls. Settings and diagnostic logs are stored locally
under %LOCALAPPDATA%\TrayPilot. Users can remove this data
by deleting that folder.
What TrayPilot accesses on your device
- Connected monitor information (name, brightness, refresh rate, HDR capability/state) — read and adjusted locally via DDC/CI or Windows display APIs.
- Audio endpoints (playback devices, microphone) — used to switch devices and toggle mute, via local Windows audio APIs.
- Local network adapter statistics (aggregate download/upload throughput) — read locally to display activity; TrayPilot does not inspect packet contents.
- Windows settings such as theme, Night Light, power mode, desktop icon visibility, and lock/session actions — read and changed locally via Windows APIs.
- A configurable keyboard shortcut you set, stored locally to open the app's flyout.
What TrayPilot does not do
- No account or sign-in of any kind.
- No cloud service, backend server, or remote sync.
- No telemetry or analytics collection.
- No microphone recording or audio capture.
- No screen capture.
- No inspection of network packet contents.
- No advertising or third-party tracking SDKs.
Data storage and retention
TrayPilot stores your configured settings (such as your keyboard shortcut)
and local diagnostic logs entirely on your own device, under
%LOCALAPPDATA%\TrayPilot. This data never leaves your device
and is not accessible to the developer. Diagnostic logs may include
application error details but do not contain passwords, credentials, or
the contents of your files.
How to delete your data
Uninstalling TrayPilot removes the application. To remove all locally
stored settings and logs, delete the folder
%LOCALAPPDATA%\TrayPilot after uninstalling.
Why TrayPilot requests broad system permissions
TrayPilot declares the Windows runFullTrust capability
because it needs low-level access to display hardware (DDC/CI monitor
controls), Windows Management Instrumentation (for laptop panel
brightness), audio endpoint COM interfaces, and network adapter
statistics — none of which are exposed through sandboxed app APIs. This
capability does not cause TrayPilot to transmit any data off your
device; it only affects which local Windows APIs the app is permitted
to call.
Children's privacy
TrayPilot is a general-purpose system utility with no user accounts, social features, or user-generated content, and it is not directed at children. It does not knowingly collect personal information from anyone, including children.
Changes to this policy
If TrayPilot's data practices change in a future release, this page will be updated and the "Last updated" date above will change accordingly.
Contact
For setup and usage help, see the TrayPilot Quick Guide. For general app support, open an issue in the public TrayPilot website repository. Please do not include personal or sensitive information in public issues. For privacy requests, use the publisher contact details on the TrayPilot Microsoft Store listing.