Privacy & permissions
Last updated: August 7, 2026
Windsify Mac operates locally. No telemetry, no account, no analytics — your keystrokes never leave the Mac. This page explains the one permission the app asks for, what its event engine keeps in memory, and what this website does and doesn't collect.
The Accessibility permission
Windsify Mac asks for one macOS permission: Accessibility. It is required to:
- actively translate keyboard events;
- identify the frontmost application and focused control;
- obtain the focused window;
- move, resize, minimize, and restore windows.
Windsify Mac does not use Accessibility to read or store the text you type. Its logs never include characters, clipboard contents, window titles, document names, or accessibility values from text controls.
Input and event data
The event engine evaluates virtual key codes, modifier flags, event phase, and the frontmost application's bundle identifier — in memory. Each event is discarded as soon as the matching action is selected. No events are recorded and nothing is transmitted: the app has no telemetry and no account system.
Network
Core keyboard and window functionality requires no network connection. If a signed update service is added in the future, it will be documented separately and remain optional.
Screen Recording
Not requested, not required. Windsify Mac moves windows through the Accessibility API and does not capture screen pixels.
This website
windsify.com serves static files. It sets no cookies, runs no analytics, and makes no requests to third-party servers.
Purchases are handled by Polar as the merchant of record. When you buy a license, checkout happens on Polar's pages and your payment details go to Polar — not to windsify.com. Polar's privacy policy governs checkout.
Questions
The source is MIT-licensed, so you can read exactly what the app does. For anything else, open a GitHub issue.