TabScribe Privacy Policy
The short version: TabScribe is 100% local. We do not collect, store, transmit, sell, or share any of your data — period. There are no analytics services, no tracking pixels, no remote servers, and no background network requests. Every byte of information TabScribe handles stays on your machine.
1. Who We Are
TabScribe is a free, open-source Chrome extension that helps you copy all open browser tabs as Markdown, JSON, plain text, or HTML — and save/restore tab groups locally. TabScribe is developed and maintained by AuraFlame · 灵烨工作室. This privacy policy applies to the TabScribe Chrome extension, the marketing website at tabscribe.auraflame.tech, and the GitHub repository at github.com/auraflame/tabscribe.
2. What Data We Process
TabScribe processes only the data needed to perform the core feature (copying and organizing your open tabs). Concretely, when you click the extension icon, the keyboard shortcut, or a context-menu item, TabScribe reads from your browser:
- The list of currently open browser tabs (title, URL, favicon URL).
- Tab groups you have created, including their names and the tabs in each group.
- Your saved tab group history (only the groups you explicitly chose to save).
- Your local preferences: language, theme (light/dark/auto), output format defaults, delimiter, and the last-used format.
- Optional: which tabs you have selected when you invoke a "copy selected" action.
This data is processed in-memory, in your browser, only at the moment you invoke a TabScribe action. It is used to render the popup UI, build the output string, write it to your clipboard, or save it to local storage.
3. What Data We Do Not Collect
TabScribe does not collect, store, transmit, sell, or share any of the following:
- Your name, email address, phone number, account credentials, or any personal identifier.
- The full content of any web page you visit (HTML, body text, images, or scripts).
- Your browser history, bookmarks, cookies, autofill, or saved passwords.
- Keystrokes, form input, or anything you type into other pages.
- Location, IP address, device fingerprint, advertising ID, or hardware identifiers.
- Aggregate usage statistics, crash reports, telemetry, or "anonymous" analytics.
TabScribe contains no third-party analytics SDKs, no tracking pixels, and no error-reporting services (no Sentry, no Google Analytics, no Mixpanel, no Plausible, nothing). The extension's source code is public on GitHub and can be audited by anyone.
4. How Your Data Is Stored
All persistent TabScribe data is stored locally on your device using Chrome's
chrome.storage.local API. This storage is sandboxed per extension and
per browser profile — no other extension, website, or user can read it.
Specifically, we store locally:
- Tab groups you explicitly saved (a name, the list of URLs, and the save date).
- User preferences (language, theme, output format, delimiter, last-used format).
You can clear all TabScribe data at any time:
- Open the TabScribe popup.
- Go to Settings → Data → Clear all saved tab groups.
- Or, from Chrome's extension page, click "Remove extension" — this deletes all TabScribe storage permanently.
TabScribe never uploads any of this data to a remote server. The extension's network activity, if any, is limited to fetching the favicon of each open tab via the standard browser pipeline when rendering the popup — equivalent to favicons loading in any new tab page.
5. Network Requests
TabScribe does not initiate any network requests of its own. The only "network activity" related to TabScribe is:
- Favicon loading: when rendering the tab list, the browser may request favicons for each open tab through its normal pipeline. This is the same behavior as Chrome's new tab page — TabScribe does not make these requests itself.
- "Export as file" downloads: when you choose to save a tab list
as a Markdown/JSON/HTML/Text file, the file is generated locally and offered as a
download through Chrome's standard
chrome.downloadsAPI. The file is saved to your local disk. No copy is sent anywhere.
TabScribe does not call any third-party API, telemetry endpoint, or remote service. The extension has no "phone home" behavior.
6. Chrome Permissions Explained
Chrome requires extensions to declare the minimum set of permissions they need. Here is what TabScribe requests and why:
tabs— to read the list of open tabs (title and URL) so you can copy or save them.tabGroups— to read, create, and update Chrome's native tab groups (so you can group and restore them).storage— to save your tab groups and preferences locally viachrome.storage.local.downloads— to trigger "Export as file" so the downloaded Markdown/JSON/HTML/Text file lands in your Downloads folder.activeTab— to access the currently active tab only when you click the extension icon or a context-menu item (Chrome's least-privilege access pattern).contextMenus— to add the "Copy tab as…" right-click menu items on regular pages and on links.- Host permission:
<all_urls>— required so the context-menu "Copy link as Markdown" can run on any link you right-click. TabScribe does not inject content scripts into pages.
All permissions are used solely for the features described above. TabScribe does not declare any permission it does not actively use.
7. Third-Party Services
TabScribe itself integrates with zero third-party services. The marketing website at tabscribe.auraflame.tech loads two external resources:
- Google Fonts (Inter, JetBrains Mono) — for typography. Google's privacy policy applies to those requests.
- jsDelivr CDN — to host the Cal Sans webfont file. jsDelivr's privacy policy applies.
Neither of these is loaded by the extension itself. Both are standard, public content-delivery services and receive only the same request metadata any browser would send when fetching a public asset.
8. Children's Privacy
TabScribe does not target children under the age of 13 (or the equivalent minimum age in your jurisdiction). Because the extension collects no data at all, it is inherently safe for users of any age. If you are a parent or guardian and have questions, please contact us at the address below.
9. Changes to This Policy
Because TabScribe collects no data, future updates to this policy are expected to be clarifying or cosmetic. We will update the "Effective" date at the top of this page whenever the policy changes. Material changes will also be announced in the extension's changelog and on the GitHub releases page. We will not silently broaden the scope of data we collect.
10. Open Source & Audit
TabScribe's full source code is publicly available at github.com/auraflame/tabscribe under a permissive open-source license. You (or any security researcher) can audit the code to verify every claim made in this policy. If you find a discrepancy between the code and this policy, the code is the source of truth — and please report it to us so we can fix either the code or the policy.
11. Contact
Questions, concerns, or privacy requests? Email liuxinye660@gmail.com. We respond to privacy-related emails within 7 business days. Because we collect no data, most "data deletion" requests are automatically satisfied — removing the extension deletes all of its local storage.