Privacy & permissions
Last updated: September 10, 2026
Windsify Mac operates locally. No telemetry, no account, no analytics — typed text is never collected or sent. This page explains keyboard processing, optional support reports, permissions, and what this website collects.
The Accessibility permission
Windsify Mac uses Accessibility permission 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. There is no background keyboard recording, telemetry, or account system. The optional Shortcut Help test described below keeps one shortcut in memory for your review.
Optional Shortcut Help reports
In Settings → Shortcut Help, clicking Test shortcut starts a diagnostic session for one shortcut. It stops after that shortcut, ten seconds, cancellation, or leaving Windsify. Windsify previews the mapping without executing the command; macOS may still handle reserved system keys before they reach the test.
The report is filled in automatically: app and macOS versions, edition, keyboard-service and permission states, known conflict identifiers, input-source identifier, the function-key preference when available, and a limited list of connected keyboard product names, vendor/product IDs and transports. When accessible, it also includes numeric F1–F12 pairs from the keyboard driver’s advertised function-row mapping. This metadata lookup does not monitor raw HID input events. One test event can include its original key code, modifiers, event type, keyboard type and matching rule. The connected keyboard list does not identify which device sent the event.
Reports stay in memory. You can review the complete report, copy it, or open an email draft to [email protected]. Nothing is sent until you send that email. Starting another test replaces the previous result; quitting Windsify discards it. Reports contain no typed text, clipboard contents, window titles, document names, license keys, Accessibility text or device serial numbers.
Network
Core keyboard and window functionality requires no network connection.
License activation, validation, and deactivation contact Polar's public customer license API. Those requests contain the license key, Windsify's Polar organization identifier, and — after activation — the device activation identifier. They do not contain typed text, clipboard contents, window titles, document names, or Accessibility values.
The 14-day trial stores its authoritative first-launch and most recently observed dates in the macOS Keychain, with Application Support and UserDefaults migration mirrors. The license key, device activation identifier, most recent successful validation time, and an authoritative inactive status when Polar rejects the license are stored together in the macOS Keychain for license recovery and offline access.
Windsify uses Sparkle to check the signed update feed at windsify.com/appcast.xml. You can start a check from the app menu, and Sparkle asks for permission before enabling scheduled checks. You can also explicitly choose to download and install future updates automatically.
Update requests expose ordinary HTTPS connection metadata and the update client user agent; system profiling is disabled. They do not include the license key, typed text, clipboard contents, window titles, document names, or Accessibility values. Signed and notarized update archives are downloaded from the public Windsify release repository.
Buy, Manage License, and Source open their corresponding pages in the system browser.
Screen Recording
Not requested, not required. Windsify Mac moves windows through the Accessibility API and does not capture screen pixels.
Purchase, review and feedback links
When you choose to buy from the app, fixed labels identify the purchase entry: menu, Free mode banner or License settings. These labels contain no user or installation identifier. Review links open Product Hunt in your browser; you choose whether to sign in and submit a review. Feedback links open an email draft for you to review and send. Email feedback stays private unless you give permission to publish it.
This website
windsify.com serves static files and sets no cookies. Visits and anonymous product actions, such as download and checkout clicks, are counted in aggregate. No cookie or visitor ID follows you. A recognized search-engine referrer may be classified as an organic landing; only the provider name is retained, never its URL or your search terms. This classification applies to the current landing page, without tracking you between pages. When you arrive through an allow-listed campaign link or a recognized search engine, its anonymous campaign label may be carried into Polar checkout so aggregate visits, checkout clicks and orders can be compared.
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
See Source & License for the Free and Pro edition terms. For anything else, email [email protected].