Copy Tables to Excel + Cleanup
Privacy policy

Version 1.1.0 · September 29, 2026

Table capture and processing

When you click the extension, it reads visible tables in the current webpage and the page title and source URL path. Table contents may include personal or financial information, such as customer names, identifiers, order details, and amounts, depending on the page you choose. We use this information only to provide table preview, cleanup, copying, export, and saved recipes. Table contents and captured page information are processed locally; the extension does not upload them to the publisher, ExtensionPay, or Stripe. It does not monitor your general browsing history.

Local storage and your choices

Captured tables and source information are held in Chrome extension session storage during the browser session. A saved cleanup recipe contains settings, column names, choices and types, and the first row as a layout signature; this may contain table data. Recipes are saved in local extension storage when you choose Save recipe. A new recipe replaces the previous one. Uninstalling removes extension storage, but downloaded files and clipboard contents remain under your control outside the extension.

Purchases and license verification

We use ExtensionPay and Stripe for checkout and purchase restoration. ExtensionPay manages the purchase status used to unlock Pro features. Its bundled library stores an installation timestamp, a license identifier, and returned purchase/account information, which can include an email address, payment status, payment timestamp, trial or plan information. The library uses Chrome synchronized extension storage, with local storage as a fallback. Chrome may synchronize this license/account information according to your browser settings. Table captures and cleanup recipes are not placed in synchronized storage by this extension.

Purchase checks and checkout communicate with ExtensionPay over HTTPS. These requests expose normal connection information, such as an IP address, to the service. Payment details are entered on the provider's checkout pages, not into the table editor. The extension does not read or store card numbers. The publisher may access purchase/customer records through ExtensionPay and Stripe to provide billing support. Payment providers retain information according to their own policies and applicable requirements. See ExtensionPay and Stripe's privacy policy.

Permissions and remote code

activeTab and scripting allow capture after you click the extension. Storage transfers captures to the editor, remembers recipes, and supports license/account information. Access to https://extensionpay.com/* allows the bundled library to communicate with the payment service for plans, checkout, restoration, and license verification. All executable code, including the payment library, is packaged with the extension. Network requests retrieve payment information, not remote executable code.

Limited use and sharing

We do not sell user data or use it for advertising, unrelated profiling, creditworthiness, or lending decisions. Information is used only to provide the extension's table-processing functionality, paid access, and related support. The extension's use and transfer of information comply with the Chrome Web Store User Data Policy, including its Limited Use requirements. This build contains no analytics or advertising code.

Contact and deletion requests

For support or requests relating to purchase records, contact [email protected]. Closing the browser session clears session captures. Uninstalling removes extension-managed storage; copies synchronized through Chrome and payment-provider records may be governed by their respective retention controls. Required transaction records may need to be retained by the payment providers or publisher.