What a desktop text expander can observe and store
A practical threat model for keyboard hooks, local snippet storage, clipboard use, backups, updates, and compliance scope.
Keyboard access is sensitive by definition
On Windows and X11, FlitKey monitors keyboard events to match enabled triggers and hotkeys. That capability is necessary for system-wide expansion and deserves the same scrutiny as other software with broad input access. On Wayland, FlitKey 0.5.0 does not implement global monitoring; it uses a user-opened picker and clipboard workflow.
Open source makes the implementation inspectable, but source availability is not proof that a downloaded binary matches the source or that every dependency is safe. Verify release provenance and follow endpoint policy.
Local storage changes who operates the server
FlitKey stores snippets and settings in a local JSON file under the user's configuration directory. It has no hosted account, central snippet database, or telemetry service. That reduces third-party data transfer and makes export and deletion understandable.
Local files remain exposed to the signed-in user, malware with equivalent access, administrators, disk images, search indexing, backup tools, and anyone who obtains an unencrypted device. Apply appropriate file permissions, full-disk encryption, account separation, and backup controls.
Clipboard workflows create a second copy
On Wayland, selecting a snippet places rendered text on the clipboard so the user can paste it. Clipboard managers may retain history. Remote desktop software and synchronized clipboards may copy the value elsewhere. Destination applications may log, sync, or submit the pasted text.
Disable clipboard history or synchronization where required, clear sensitive clipboard content, and do not use ordinary snippets as a password manager. Credentials, recovery codes, access tokens, private keys, and regulated records need purpose-built controls.
Offline is not a compliance certification
FlitKey has not been certified for HIPAA, GDPR, CCPA, SOC 2, ISO 27001, or comparable standards and does not offer a Business Associate Agreement. Compliance depends on the organization, purpose, legal role, policies, access controls, retention, incident response, endpoint configuration, and downstream systems.
A security review can use FlitKey's public source, local storage paths, privacy notice, and dependency list as inputs. The result belongs to the organization performing the assessment.
A practical minimum control set
- Install only from a verified project source.
- Keep the operating system and dependencies patched.
- Use least-privilege accounts and full-disk encryption.
- Exclude secrets and regulated records from ordinary snippets.
- Review clipboard history, backups, and sync services.
- Back up configuration securely and test deletion.
- Reassess after major product or platform changes.
Report suspected vulnerabilities privately through the documented security channel rather than placing exploit details or sensitive logs in a public issue.