WinDEETS reads the Windows event logs on the PC it runs on, through the Windows Event Log API. It reads when you open the Data View, press Refresh or press Load older events. It does not poll in the background.
It reads the Drivers, Services, Startup apps, Scheduled tasks and Installed software tables from Windows when you open a tab or press Refresh.
A watcher for alert events runs in memory. It saves nothing and sends nothing.
WinDEETS stores no history of your machine. It writes three small files under %LOCALAPPDATA%\com.windeets\data: machine.json (this install's identity), settings.json, and evidence.jsonl, which holds only the events you flag to keep.
A log file, windeets.log, sits in %LOCALAPPDATA%\com.windeets\logs. It is rotated at 10 MB, never synced and sent nowhere.
Export for review writes the flagged events to your Downloads folder, and only when you press it.
It sends no usage statistics or telemetry, and it has no analytics library. We hold nothing about you or your machine.
Once per launch it fetches a list of search addresses for Winny from windeets.com. The request carries only a User-Agent. A build outside the Microsoft Store also makes an anonymous update check. The Store build does not, because the Store delivers updates.
Winny sends nothing until you pick a search engine. Then your question opens as a link in your own browser, with personal data redacted first.
Signing in is optional. Only two things need it: sending a bug report, and switching on display settings from your Microsoft 365 workspace. Signing in copies none of your data anywhere. The app keeps only a refresh token, encrypted for your Windows user.
A bug report is sent only when you are signed in and press Send. The panel lists what it will send, and asks you not to include names, email addresses, tenant details or secrets. It lands as an issue in an internal Turbo Client Systems repository.
WinDEETS runs with your own Windows rights. Reading, flagging and exporting events needs no account.
Some logs, such as Security, need administrator rights. WinDEETS says how many it could not read. Read as administrator relaunches it through the Windows UAC prompt, and signed-in features are off in that copy.
Sign-in asks Microsoft for these permissions: openid, profile, offline_access and User.Read. It asks for no file or site permission. If you switch on display settings, it asks once more for Sites.Selected, which reaches only sites a tenant admin granted this app.
WinDEETS reads and explains. It repairs nothing and changes no Windows setting.
It cannot show an event Windows has already overwritten when a log filled up. Flag an event first to keep it.
It cannot read a protected log without administrator rights.
It does not run in the background to collect logs for later.
Written from the WinDEETS source on October 22, 2026. If this page and the app ever disagree, the app is right: tell us at support@windeets.com.