Privacy policy

Muscle Memory collects nothing, sends nothing, and has no server to send it to.

What it stores

Two things, both on your own machine, both through the browser's extension storage:

• Your settings, in chrome.storage.sync, so they follow your Chrome profile between machines the way your bookmarks do.
• Three values, in chrome.storage.local: how many times the extension pressed a shortcut on your behalf, how many of those Figma acted on, and the name of the last one. That name comes from a fixed list of four written in the source, so it can never contain anything you typed. This is what the diagnostics panel reports.

What it does not do

• No analytics, no telemetry, no error reporting, no unique identifier.
• No network requests of any kind. The extension declares no host permissions and cannot reach a remote server.
• No reading of your Figma files, designs, comments or account. To find the banners it can hide, it does read the text of page elements in memory and test three fixed patterns against them, on editor pages only. Nothing read that way is stored, kept, or sent anywhere.
• Nothing is shared with anyone, because nothing leaves your machine.

Permissions

One permission, storage, for the settings above. Site access is limited to www.figma.com and nothing else: no <all_urls>, no other domain. Chrome describes that access as "read and change your data on figma.com", which is what any extension that touches a page has to ask for. What it does with it is read keyboard and mouse events, and the wording of banners.

Removing your data

"Reset everything" in the options page clears the settings. Uninstalling the extension removes both stores entirely. There is no copy anywhere else.

Verifying all of this

The extension has no build step: the source on GitHub is byte for byte what runs in your browser. Searching it for fetch, XMLHttpRequest or WebSocket returns nothing.

Muscle Memory is not affiliated with Figma, Inc.
Questions: open an issue.