Privacy policy for Export Bookmarks and History to CSV or XLSX
Export Bookmarks and History to CSV or XLSX by Jonathon Wager
Privacy policy for Export Bookmarks and History to CSV or XLSX
Effective date: 2026-10-14
This extension reads your bookmarks (favorites in Microsoft Edge), browsing history and reading list inside your browser and turns them into files on your computer. That data never leaves your computer except inside the files you choose to save, and except that the optional link check requests each bookmarked address from its own website (described below). It is not sent to me or to anyone else. There are no analytics, no ads and no tracking, and nothing is sold.
What it reads
Your bookmarks (titles, URLs, folders and dates) when you open the popup, again whenever a bookmark changes while the popup is open, and when a backup runs.
Your browsing history (page titles, URLs, visit counts and visit times) only when you click "Load matching history" on the History tab, or when you build the all-data workbook.
Your reading list (titles, URLs, read state and dates) only when the Reading list tab is open, or when you build the all-data workbook. Microsoft Edge and Firefox have no reading list, so their versions do not ask for access to one and have no Reading list tab.
The extension uses this data to show the count and preview and to build the CSV, XLSX, HTML or JSON file you asked for. It never changes or deletes your bookmarks, history or reading list.
What it stores on your computer
- Your settings (formula protection, the save dialog option and the backup schedule), in the browser's synced extension storage. In Chrome with sync on, Google keeps a copy with your Google account and brings it to your other computers. In Microsoft Edge, whatever Edge sync carries goes through your Microsoft account, and in Firefox, Firefox Sync carries them through your Mozilla account. If you do not use sync, they stay on this computer.
- The popup filters and tab you last used, on this computer only.
- The time, file name and row count of the last backup.
- Your Pro status as ExtensionPay last reported it: whether and when you paid, the install date and the email address you paid with.
- ExtensionPay's own records, which its code keeps in the same synced storage: the install date, a random key for this install (created the first time you click Get Pro or Restore purchase) and a copy of your Pro status.
Exports are saved to your Downloads folder, or wherever you choose if you turned on the save dialog, and backups go to a folder inside Downloads. The extension keeps no copy of any file.
When it goes online
ExtensionPay (Pro purchases). Pro is sold through ExtensionPay (extensionpay.com), and Stripe processes the card. Until you click Get Pro or Restore purchase, the extension sends nothing to ExtensionPay. When you click one of them, it asks ExtensionPay to create the random key described above and opens ExtensionPay's page, in a tab for Get Pro or a small window for Restore purchase. What you type on those pages goes to ExtensionPay and Stripe, not through the extension.
Once a key exists, the extension asks ExtensionPay whether that key has paid: when you open the settings page, when you click Refresh status, when you open the popup or a backup runs and the last answer is more than 15 minutes old, and every second for up to two minutes after ExtensionPay's page reports a payment. Each request carries the key and nothing else from the extension, and never any bookmark, history or reading list data. ExtensionPay sees your IP address, as any website does.
If you buy Pro, ExtensionPay keeps your email address and a record of the payment, and I can see your email address and purchase date in my ExtensionPay account. I use them only to answer support and refund requests. Stripe's privacy policy covers the card payment: https://stripe.com/privacy
The extension also runs a small script on extensionpay.com pages, and only there. It waits for ExtensionPay's own page to say a payment went through, then tells the extension to check again. It reads nothing else on those pages.
Link check (optional, Pro). The first time you click "Check links", your browser asks whether the extension may access all websites. (Firefox draws that question behind the small popup, so there the extension first opens itself in a full tab and asks on your next click.) If you allow it, the extension sends a request to every http and https bookmark in your current selection, following redirects, to read the HTTP status code. It sends a HEAD request first and a GET request if the site refuses HEAD or returns an error. Each site therefore receives a request for its own bookmarked address from your IP address, much as it would see a visit from your browser, but without your cookies or saved logins. The page content is not read or kept. The status codes stay in the open popup (or full tab) and in the files you export. The check runs only when you click the button, and you can revoke the permission on the settings page or on the browser's extensions page.
Nothing else goes over the network. The Privacy policy and Support links on the settings page open this website in a tab when you click them.
How long it is kept
Settings, filters, the last backup result and the Pro status stay in the browser's extension storage until you remove the extension, and the browser deletes them then. Link check results are kept only until you close the popup or tab. The files you export are yours and stay wherever you saved them. ExtensionPay keeps the email address and payment record of a Pro purchase; ask me through the support page if you want them removed.
Who it is shared with
No one. Nothing is sold, and no data goes to me or to advertisers or analytics services. The only outside parties involved are ExtensionPay and Stripe, which handle a Pro purchase you make on their pages, Google, Microsoft or Mozilla, which sync your settings if you use your browser's sync, and the sites you bookmarked, which receive a request for their own address when you run the link check.
Permissions
bookmarks: Read bookmarks for exports and backups. Nothing is modified.
history: Read browsing history for the History export. Nothing is modified or deleted.
readingList: Read the reading list for its export. Nothing is modified. The Edge and Firefox versions do not ask for this.
storage: Keep settings, the last-used filters, the last backup result and the Pro status.
alarms: Start the daily or weekly backup at the hour you chose.
downloads: Save exports and backups as files.
offscreen: Build the backup file in the background, then close. Chrome and Edge only; in Firefox the extension's background page builds the file.
Script on extensionpay.com: Learn that a Pro payment has gone through.
Optional: all http and https sites: The link check, only after you allow it.
Limited use
The use of information received from the browser's bookmarks, history and reading list APIs follows the Microsoft Edge Add-ons developer policies, Mozilla's Add-on Policies and the Chrome Web Store User Data Policy, including the Limited Use requirements. It is used only to build the exports and backups you ask for, and it is not transferred to anyone apart from the link check requests described above.
Firefox
Firefox's install prompt says the extension collects no data. That matches this page: nothing it reads is sent to me or to anyone else, and the link check's requests go only to the sites you bookmarked, each for its own address. In Firefox you can also switch the link check's access off under Permissions on the extension's page in about:addons.
Changes and contact
If this policy changes, I will publish the new version at this address with a new effective date. You can reach me, Jonathon Wager, through the support page at https://wager-extensions.pages.dev/support/