Your input stays on your machine.
ShortcutCast handles keystrokes. That's why we're explicit about how we treat your input and what we send over the network.
TL;DR
- ✕ Does not read your normal typing — passwords, messages, or anything else.
- ✕ Does not capture the screen or collect files automatically.
- ✕ Does not send telemetry, usage analytics, or crash reports.
- ✕ Does not send your input, settings, or usage anywhere off your machine.
- ✕ Does not store settings in the cloud or on any server.
1. How we handle keystrokes
ShortcutCast receives keystrokes only in these two situations:
- Detecting the trigger: Only the trigger you recorded (a specific key or mouse button) is registered with the OS. Other keystrokes do not pass through ShortcutCast.
- Keys pressed while the grid is open: While the grid is visible, ShortcutCast captures the grid keys (QWERTY, digits, Space) and runs the matching action. Close the grid and keystrokes go back to the app underneath.
No other keystrokes, no screen contents, no window text — none of it is read.
2. Clipboard and files
The clipboard is touched only when you explicitly use a feature that does so.
- Clipboard snippet action: Writes your saved text to the clipboard and triggers a paste. Write-only — existing clipboard contents are not read.
- Pasting an icon: An image is read from the clipboard only when you explicitly select "paste" while setting an action icon.
Files you configure — contexts, actions, icon images — are saved in:
-
macOS:
~/Library/Application Support/ShortcutCast/ - Windows:
%APPDATA%\ShortcutCast\
These files never leave your machine. No cloud sync, no account.
3. Outbound traffic
ShortcutCast connects to the internet only for update checks and license verification. The traffic carries the values needed for those operations (version number, license info) — never your input, key history, settings, or usage data.
No telemetry. No usage analytics. No crash reporting.
4. Contact
Questions about this page or security disclosures? Email [email protected].