What AutoMate stores
To let you record and replay a workflow, AutoMate saves that workflow on your device. A recording can include:
- The steps you performed (clicks, typing, navigation, scrolls, file selections) described in plain language.
- Information needed to find each element again on the page (element roles, labels, visible text, and page URLs for the pages in your flow).
- Values you typed into fields, so a step can be replayed. Fields detected as passwords or that you mark as secret are flagged and masked in the interface.
Some things are deliberately never stored:
- 2FA / one-time codes are never captured. When a step waits for a 2FA code, you type it directly into the website; AutoMate records only that it should pause there.
- File uploads store only the file name — never the contents of the file.
Where your data is stored
All storage is local to your browser profile, on your device:
- IndexedDB (database
war-db) — holds your saved recordings. - Session storage (
chrome.storage.session) — temporarily holds the state of an in-progress run so it can resume; cleared when the browser session ends. - Local storage (
chrome.storage.local) — a single flag remembering whether you've seen the first-run tutorial.
None of this is synced to any account or cloud. AutoMate does not use chrome.storage.sync.
What AutoMate does not do
- No accounts, sign-in, or user profiles.
- No network requests to any server or API. AutoMate has no backend.
- No analytics, telemetry, crash reporting, advertising, or tracking of any kind.
- No third-party services and no remotely-loaded code — the extension runs entirely from the code shipped in the package.
- No selling, sharing, or transferring of your data. There is nothing collected to sell.
When data leaves your device
The only way a recording leaves your device is if you choose to export it. AutoMate lets you save a workflow as a .json file (or download CSV data) to your computer. Secret values (passwords, codes) are excluded from exports by default; they are included only if you explicitly tick the "include secret values" option. Where an exported file then goes is up to you.
About the "debugger" permission
AutoMate requests Chrome's debugger permission (you'll see a warning about it at install). It is used for one purpose: to reliably replay your recorded input — clicks and keystrokes — on the page using Chrome's local DevTools protocol. It is not used to inspect network traffic and it sends no data off your device. Chrome shows a banner while an automated run is active so it's always clear when replay is happening.
Website permissions
AutoMate does not request access to any website at install time. When you record or replay on a site, it asks for permission for that site on demand. Because real workflows often span more than one domain (for example, an app and its separate login provider), it may request broad access at that moment — but only to record and replay the actions you initiate.
Children's privacy
AutoMate is a general-purpose tool and is not directed at children. It collects no personal information from anyone.
Changes to this policy
If this policy changes, the "Last updated" date above will change, and the updated version will be posted at this URL.
Contact
Questions about privacy? Email shaunpeh@gmail.com.