Save Page retains on-page SEO metadata locally, including title tags, descriptions, keywords, headings and other page declarations. SEO reports are downloaded only when you request an export. This metadata is deleted with its saved result or when you clear all results. Google Search is Coming soon in the production extension. Existing Google Search datasets and source captures remain stored locally until you delete them.
The Chrome extension
Automations, preferences, license keys, webhook destinations, captured Values, and lightweight execution checkpoints stay in chrome.storage.local. The Dashboard retains run history, activity, source URLs, Google result datasets, full readable source text, and optional capped HTML in local IndexedDB. Screenshots and fetched files stay in the extension’s private local file storage.
Results remain until you explicitly delete them, including after rerunning or deleting an automation. Editor Test captures are retained too. The dashboard shows storage usage and provides confirmed bulk deletion. Deleting an individual file leaves a deleted reference in its run history. Active runs and content used by an export are protected from deletion.
Automation data is used only to run those automations. It is not sent to this website. There is no Tab Automation account and no device sync. The Dashboard guide explains how to export and delete retained results. Removing the extension, or clearing its storage in Chrome, deletes this data from the computer. A pasted license key is the exception below.
Webhook destinations you save (name, URL, optional default message) stay in chrome.storage.local on this computer. The URL is shown redacted in the panel and in Activity. Removing a destination unlinks it from automations. Nothing posts until you select a destination and turn Webhook on for a Send Alert or Repeat moment.
Only then does Chrome POST directly from this computer to the URL you chose — Slack, Discord, ntfy, or any HTTPS endpoint, or HTTP on localhost. The payload can include the resolved message, the current page URL and host, the automation name and id, the event type, and any Values named in the message template. Those endpoints may be third parties. Chrome must be running. Nothing relays through Tab Automation servers. The extension does not forward cookies or extra headers, and it does not retry a failed POST.
A license key you paste in Settings is stored in chrome.storage.localon this computer. The extension sends that key tohttps://api.tabautomation.app to activate or validate it. That API talks to Lemon Squeezy, which issued the key at checkout. We do not send tab URLs, page content, or automation graphs with that request. You do not create a Tab Automation account. Lost-key recovery is the Lemon Squeezy receipt or My Orders page. The extension also creates a random installation token in Chrome local storage and sends it with license activation and validation requests. Our licensing API obtains your checkout email and customer, order, product and license identifiers from Lemon Squeezy through checks and signed webhooks.
Our PostgreSQL database retains that email, those identifiers, license status and expiry, the license-key hash and last four characters, the installation-token hash, and the corresponding activation identifier. These records provide license access and recovery, enforce one initial Explorer claim per email and one active Chrome installation/profile, and handle refunds and disabled licenses. License records include order and refund status, but no card or bank-account details; the current Explorer checkout is free. We do not store full license keys, raw installation tokens or complete webhook bodies on the server.
The token is excluded from sync, exports, analytics and logs. Clearing a key retains the installation token so re-entry can reuse the activation; it does not release the provider activation or delete server licensing records. Use My Orders to release an activation, or our Contact form for licensing-data requests. The one-claim record remains after expiry or disabling; it is not automatically reset by clearing the extension.
If you claim an Explorer License before the Chrome Web Store launch, we use your checkout email address to send you a one-time email when the extension is ready to install.
Share usage statistics in Settings is on until you turn it off. While it is on, the extension sends feature usage counts to Google Analytics: the extension version, the interface language, whether a saved automation is a custom graph or a library workflow, which step types it contains, whether it repeats or loops, how a run ended, a coarse step count and duration, whether the stored license status is valid, whether you started a custom automation, whether you paused a run, whether you removed an automation, which pre-built workflow you started, whether you opened the results dashboard, the export format, whether a license check was valid, invalid, expired, or empty, and the first time a license check succeeds. Google may receive the request’s IP address. The extension does not send page addresses, page content, selectors, typed text, search terms, or the license key with those counts. Counts include a random client id, a session id and a fixed engagement value. The client id is stored inchrome.storage.local on this computer so repeat counts can be grouped without an account. Turning the switch off stops later counts.
The extension asks Chrome for sidePanel, tabs, alarms, storage, unlimitedStorage, scripting, notifications, offscreen, downloads, debugger, and host access on all URLs. Host access is there so the picker, watches, and steps can run on the http(s) page you assign. unlimitedStorage allows retained results to exceed ordinary browser quotas; storage can still fail when the disk is full.downloads saves files or JSON, CSV, Markdown, and ZIP exports only after you request them. Captures never trigger automatic downloads. Files up to 1,000,000,000 bytes are fetched directly using HTTP(S) GET, following redirects and Chrome’s normal credential rules, including applicable cookies. Files and captures are not uploaded to Tab Automation. When you pick an element or links, the panel also asks Chrome for that page’s origin. Chrome UI pages, extension pages, and the Chrome Web Store cannot be automated. The extension does not access Chrome’s browsing-history database. It retains assigned page URLs, captured source URLs, and run history locally. Requested exports can contain these URLs, and enabled webhooks can send the current page URL to your selected destination.
The required debugger permission supports both viewport and Full page screenshots, as well as configured clicks, double-clicks, hover, supported text entry, and key presses on the assigned tab. Type Text values, including passwords if you supply them, are stored locally in automation configuration and entered on that page. They are not sent to Tab Automation servers. During capture, the extension temporarily attaches to the assigned tab to capture its current viewport or full document without switching tabs or focusing windows. Chrome displays a debugging notice while attached for screenshots or input. Access is released after the operation or cancellation; recovery cleanup handles interrupted operations. Full-page images are processed locally in an offscreen document. All screenshots are saved to this computer; they are not uploaded. Temporary recovery metadata is kept in chrome.storage.session so interrupted captures can be cleaned up when the extension restarts.
The side panel may load the assigned tab’s favicon from its image URL. When tab status indicators are enabled, the extension also fetches favicon images from the page’s icon URLs and generates running or paused badges locally in an offscreen document. These image requests go to the icon host and may include existing cookies, subject to Chrome’s cookie rules. Generated icons are held in a temporary local rendering cache; they are not uploaded to our servers. Saved automation and Library metadata keep the underlying website icon URL. You can turn indicators off in Settings using Show automation status on tab icons. Reloads and Go To steps load the URLs you chose in the assigned tab.
Limited use: Tab Automation uses this data only to provide this single purpose — automations on Chrome tabs you leave open. It does not sell the data or use it for advertising. Transfers are limited to the feature requests described above, such as enabled webhooks, page and file requests, license verification, and usage statistics when that Settings switch is on, or disclosures required by law.
This website
Local development loads no analytics. On the production site we load Google Analytics after the page is idle so we can see which pages are used and which Chrome Web Store links are clicked. Store-link events include the page path and the link’s placement, such as the header or a guide. A click does not tell us whether you installed the extension. Ads signals are turned off in our configuration. If your browser sends Global Privacy Control, we do not load that script.
Google may set cookies or similar storage and receive page URLs and basic device data. Google is based in the United States, so page URLs and basic device data may leave your country. How long Google keeps it is set in the Analytics property, not in this repository. We do not set a retention window here.
This site also stores a theme choice in this browser. It does not set first-party cookies of its own. There are no Tab Automation accounts. Checkout for an Explorer License, when the share link is set, happens on Lemon Squeezy — not on this site.
If you submit the form on /contact or /uninstall, we store the topic, your message, an optional email if you leave one, and the browser user agent. If Chrome opened /uninstall with the extension version in the address, we store that version too. That data lives in a Cloudflare D1 database for this site. We use it to read what you sent. The Chrome extension does not send tab or page content with that form. Chrome may open /uninstall when you remove the extension; you choose whether to submit.
Privacy questions
For questions about this policy or requests concerning personal data held by Tab Automation, use our contact form. Include an email address if you would like a reply. For licensing-related requests, use your checkout email so we can identify the relevant records. Do not send your license key.
Your rights
For the extension, automation configuration and retained results are on your computer; licensing records are held separately on our server as described above. Browse and delete retained outputs in the Results dashboard. Removing an automation deletes its configuration and stops active work, while historical outputs remain. Uninstalling the extension or clearing its storage removes local results. Exports already saved to your Downloads folder remain until you remove them. Temporary ZIP files are removed after export completion or cancellation; the download operation history remains.
For this website, you can send Global Privacy Control and we will not load Google’s script. If you submitted a form, you can ask us to access or erase that row through /contact. If the law where you live gives you rights to access, erase, or object to personal data we hold, use that form. You may also complain to your local supervisory authority.
Children
This site and the extension are not directed at children under 13. We do not knowingly collect personal data from children.
Changes
This policy can change. The updated text will appear on this page with a new date.