Macro Recorder ("the extension", "we") is a Chrome extension that lets you record keyboard and mouse interactions on a web page and play them back later. This policy explains what data the extension touches, where it's stored, and what we don't do with it.
Everything the extension records stays in your own browser
(chrome.storage.local). We do not send data to any
server, we don't use analytics or advertising, and password or
card fields are automatically excluded from recording.
While you record a macro, the extension captures and stores locally:
This data forms the "macro" that you choose to save, export, or delete from the extension's own popup.
<input type="password">
fields and fields with cc-*/password
autocomplete attributes, and does not store their content while
recording. When playing back a macro that passed through one of those
fields, you'll be prompted for the value at that moment via an
on-page overlay; that value is never stored.
All recorded macros are stored exclusively in
chrome.storage.local, the browser's own local storage,
tied to your Chrome profile. The extension has no server of its own and
makes no network calls: there is no fetch, no
XMLHttpRequest, and no connection to external services.
Your data never leaves your device unless you export it yourself.
You can export any macro to a .json file that downloads to
your device, and import it again later. That export is a manual action
you initiate; the resulting file stays under your exclusive control and
we have no access to it.
| Permission | What it's used for |
|---|---|
storage |
Save your macros and settings locally in your browser. |
activeTab / tabs |
Know which tab to record or play back on, and open/activate the tab needed for playback. |
scripting |
Inject the script that detects your interactions (recording) and the one that draws the ghost cursor during playback. |
debugger |
Play back the macro via the Chrome DevTools Protocol, generating
"trusted" keyboard/mouse events (isTrusted: true) that
behave just like actions you'd perform yourself, including on
React/Angular/Vue sites. Chrome will show a warning ("this extension
is debugging this browser") while a macro plays back; this is
standard behavior for this permission and disappears once playback
ends.
|
alarms |
Allow scheduling automatic playback of a macro at a specific time. |
host_permissions: <all_urls> |
Required because the extension needs to be able to record and play back on any page you choose to visit, not just one specific site. |
We do not share, sell, or transfer your data to third parties. As explained in section 3, the extension has no server infrastructure to send anything to in the first place.
Your macros are protected by the same storage and permission system Chrome uses to isolate each extension's data. By excluding passwords and payment data from recording, we reduce the risk of sensitive information being stored by accident.
chrome://extensions or clearing its storage from Chrome's settings.chrome.storage.local.Macro Recorder is not directed at children under 13, and we do not knowingly collect data from children.
If we update this policy (for example, when adding new features), we will publish the new version on this same page with a revised update date.
If you have questions about this privacy policy, you can reach us at:
mvrcrx@gmail.com