Privacy policy
SpeedLink keeps your keymap in your browser. It collects nothing, sends nothing to us or anyone else, and has no analytics.
What SpeedLink stores
Your keymap: for each key you assign, the link, its name, and how it opens (the open mode, how an open
tab is matched, and whether the current tab closes). It is kept in chrome.storage.sync. If Chrome Sync is
on, Chrome copies it between your own devices through your Google account. That is Chrome's feature, under Google's
privacy policy: SpeedLink has no server and never sees it.
A short-lived record that lets you undo the last assign is kept in chrome.storage.session. It stays on
your device and is gone when the browser closes or after a minute.
What SpeedLink reads and does not keep
- The address and title of your open tabs, to switch to a tab that is already open, to mark keys whose site is open, and to fill in the page you are assigning. They are used in memory and never stored or sent.
- Key presses on a page, only to notice the trigger (⌥ Option on a Mac, Alt elsewhere) and a key pressed with it. Nothing you type is recorded, stored or sent.
- SpeedLink does not read page content.
What SpeedLink does not do
- It makes no network requests of its own.
- It has no analytics, telemetry, advertising or crash reporting.
- It shares nothing with third parties, and sells nothing.
- It loads no code from outside the extension.
Your control
Edit or clear any key in the extension's Options page, or remove the extension to delete its local data. Your synced copy can be cleared from Chrome's sync settings.
Changes
If this policy changes, the new version is published here with a new effective date.
Contact
Questions or concerns: open an issue at github.com/itigancov/speedlink/issues. No email address is published.