Privacy Policy

Last updated: October 26, 2026 · Contact: developerext7@gmail.com

This Privacy Policy describes how the Chrome extension “Quick Chrome History Export” (“the Extension”, “we”), published by Kobaltstack LLC, handles data. The Extension is available on the Chrome Web Store. Its main job, turning your history into a file, runs entirely on your device; lifetime-access billing is handled by our billing provider as described in section 2.5.

1. Our principles

• Privacy policies should be human-readable. No legal cosplay, no boilerplate describing things we don’t do.
• The simplest data practice is no data practice. The less we collect, store, or transmit, the less can leak.
• Match the reasonable expectation of the user. You installed an extension to export your history. It does that, and asks for payment only where the Extension is paid.

2. What data we process

2.1 Processed and stored locally on your device

• Your browsing history, only when you ask for an export. When you click “Download as CSV”, “Download as JSON” or “Download as XLSX”, the Extension reads your Chrome history for the period you selected through Chrome’s built-in history API: page title, URL, date and time of each visit, visit count, typed count and transition type (for example, link or typed address). It builds the file in your browser’s memory and hands it to Chrome’s download manager. The Extension does not keep its own copy of your history.
• The exported file. It is saved to your computer (usually the Downloads folder) and stays under your control. Anyone who can open that folder, or wherever you copy the file, can read it, so treat it like any other personal document.
• A small counter for the rating prompt. In chrome.storage.local the Extension keeps the number of successful exports, whether you rated or dismissed the “Enjoying the app?” prompt, and when you dismissed it. It contains no history, URLs or personal information.
• Lifetime-access status. In chrome.storage.local the Extension keeps whether you have bought lifetime access, when that was last confirmed, the email of the account you signed in with (if any) and the result of the last access check. The toolbar popup also remembers which view it last showed, so it opens without flicker.
• Billing component data. The billing component (section 2.5) keeps its sign-in session, a randomly generated visitor identifier, the count of free exports you have used and a cached copy of the current prices in the Extension’s own storage on your device — never in cookies.

2.2 Data sent to servers

Your browsing history, the pages you visit and your exported files are never sent anywhere. We do not run a server that receives data from the Extension. The only data that leaves your device is the billing data described in section 2.5, which goes to our billing provider and, if you buy, to the payment processor.

2.3 How we use the data

Your browsing history is used solely to create the export file you asked for, on your device. The rating counter is used solely to decide when to show the rating prompt. Billing data is used solely to decide whether a download is free or needs lifetime access, to sell and restore lifetime access, to answer your support requests, and to understand and improve the purchase flow. None of this data is used to build a profile of you, it is not used for advertising, and it is not shared beyond the providers named in section 6. These are the only purposes for which any data is processed.

2.4 Web pages the Extension opens

The Extension opens a few ordinary web pages in a new tab. It does not attach your history or any other data to these links.

• After installation, a welcome page with instructions opens once on this website (export-chrome-history.app/welcome/, see section 11).
• If you uninstall the Extension, Chrome opens a short, optional feedback form hosted on Google Forms. Anything you choose to type there is sent to Google Forms and handled under Google’s Privacy Policy.
• If you click a star in the rating prompt, 4 or 5 stars open the Extension’s review page on the Chrome Web Store, and 1 to 3 stars open the same Google Forms feedback form. Nothing opens unless you click.
• If a download needs lifetime access, the Extension opens its own unlock page (part of the Extension, not a website). Signing in with Google or Apple and paying open those providers’ pages, as described in section 2.5.

2.5 Lifetime access: sign-in, payments and access checks

Exporting never requires an account in countries where the Extension is free; there it never asks for a payment. Where the Extension is paid, the first few exports are free; after that, a download opens the unlock page, where you can buy lifetime access with a one-time payment, or restore a purchase you made earlier. To know which case applies, each time you click a download button the Extension asks the billing service whether this download is allowed — unless your purchase was confirmed in the last 7 days, in which case no request is made.

Billing is provided by Monetize.software. It runs on the subdomain platform.export-chrome-history.app, which is delegated to and operated by them — it is not hosted on our web server. The payment itself is completed on the checkout page of a PCI-compliant payment processor that opens in a new tab. The Extension contains no remote code: the billing component ships bundled inside the extension package and talks to the billing service directly from your browser.

What is sent to the billing service:

• A randomly generated visitor identifier and the identifier of our paywall, so prices, your free exports and your purchase status can be looked up
• The fact that you clicked a download button, counted against your free exports — never what you exported, the period or format you chose, or any history entry
• Your email address, only if you sign in (to buy, or to restore a purchase on another computer): either typed by you together with a password you choose, or shared by Google or Apple if you use their sign-in. Sign-in tokens are stored locally in the Extension’s own storage on your device, never in cookies
• If you use Contact support on the unlock page: the email address and message you type and any files you choose to attach, so we can reply
• Your purchase status (whether you have bought lifetime access), so the Extension knows whether to unlock exports
• Anonymous purchase-flow events (purchase screen viewed or closed, price selected, checkout started, purchase completed or failed, free exports used up, not offered in your region, errors) used to understand and improve the purchase flow
• Your IP address is seen by the billing service like by any web server; it uses it to derive your country, which selects the currency and regional price and whether the Extension is paid in your country at all. We see only aggregated country statistics in the billing dashboard, never your IP address

What is never sent: your browsing history, the pages you visit, your exported files, or the period and format you choose. The billing service cannot see what you export.

Card details are entered on the payment processor’s checkout page and are handled by the processor under its own privacy policy. We never see, store or transmit card numbers.

Lifetime access is a one-time payment: there is no subscription and nothing to cancel. You can request a refund within 14 days of purchase — write to us at the address below. See the Refund Policy.

3. What we do NOT collect

• Names, phone numbers, postal addresses. An email address is processed only if you sign in or contact support (section 2.5)
• Passwords — if you sign in with email and password, the password goes only to the billing provider’s sign-in service; we never see it
• Card numbers or bank details — payments are completed on the payment processor’s page, never in the Extension
• The content of the pages you visit
• Keystrokes, mouse movements, or screen recordings
• Data from children under 13 (knowingly)

4. Permissions we request and why

The Extension requests only the permissions it needs to do its job, as declared on its Chrome Web Store listing. Each permission is used locally on your device to provide the feature it belongs to — none of them is used to transmit your history or files to us or to any third party.

• history — to read your visits for the period you choose, only when you click a download button, so they can be written into the export file
• downloads — to save the generated CSV, JSON or XLSX file to your computer
• storage — to keep the rating-prompt counter, your lifetime-access status and the billing component’s data described in §2.1 on your device
• offscreen — to open a hidden extension page that hosts the billing component and keeps your sign-in and purchase status in one place. It is created when you point at or click a download button, or open the unlock page, and it never reads your history
• Access to websites (http://*/*, https://*/*) — the Extension loads the SheetJS spreadsheet library it uses for XLSX files into web pages. The library only provides spreadsheet functions; the Extension does not use it to read, change, collect or transmit the content or address of any page

5. Data retention

• History read for an export — held in memory only while the file is being built, then released
• Exported files — stay on your computer until you delete them
• Rating-prompt counter, lifetime-access status and billing component data on your device — stay until you uninstall the Extension or clear Chrome’s extension storage; sign-in tokens are also removed when you sign out
• Billing records (email, purchase history, support requests) — kept by our billing provider and the payment processor for as long as your purchase is active and afterwards as required for accounting and tax purposes
• Your Chrome history itself — is managed by Chrome. The Extension never changes or deletes it

6. Data sharing, selling, and Limited Use

We do not sell, rent, or trade any data, and we do not share user data with advertisers or anyone else. The only third parties that process data on our behalf are our billing provider, Monetize.software, and, if you buy, the payment processor (section 2.5) — each receives only what it needs for its job. Our use of any user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Specifically:

• We do not sell or transfer user data to third parties, outside of the approved use cases.
• We do not use or transfer user data for purposes that are unrelated to the Extension’s single purpose.
• We do not use or transfer user data to determine creditworthiness or for lending purposes.
• We do not use user data to serve personalized, re-targeted, or interest-based advertising.
• We do not allow humans to read your data, except where you give explicit consent, where required for security, or to comply with applicable law.

7. Your rights

Apart from the billing data described in section 2.5, we do not collect personal data, so there is nothing tied to “you” that we could look up on our side. You can:

• Delete your local data by uninstalling the Extension or clearing extension storage in Chrome’s settings, and by deleting any files you exported
• Sign out on the Extension’s account screen, which removes the sign-in tokens from your device
• Ask us to delete your account and billing data — email us; we will forward the request to the billing provider and the payment processor, subject to their legal retention duties
• Contact us at developerext7@gmail.com with any questions or concerns

If you are located in the EEA, UK, or California, you have rights under GDPR / UK GDPR / CCPA including access, rectification, erasure, and objection. Contact us at the email above to exercise these rights.

8. International data transfers

The Extension does not transfer your history or files internationally because it does not transmit them at all — they stay on your device. The web server hosting this website is a VPS in the European Union (Germany); the billing subdomain in section 2.5 is operated by our billing provider, not by us. If you sign in or buy, the billing provider and the payment processor may process your email and payment data in other countries under their own safeguards (standard contractual clauses or equivalent).

9. Security

Your history and exported files are processed and stored locally by Chrome on your own device, so there is no server of ours that could be breached to expose them. All requests to the billing service and the payment processor go over HTTPS (TLS); sign-in tokens are kept in the Extension’s own storage, not in cookies; card details are entered only on the payment processor’s PCI-compliant checkout page. Web traffic to this website is protected by HTTPS as well.

10. Children

The Extension is not directed at children under 13. We do not knowingly collect data from children. If you believe a child has used the Extension, contact us and we will take appropriate action.

11. This website

export-chrome-history.app is a static website, including the welcome page the Extension opens after installation. It sets no cookies and runs no analytics or tracking. Like any web server, ours keeps standard access logs (IP address, requested page, time, browser) for about 10 days, for security and troubleshooting. Fonts are loaded from Google Fonts, so your browser connects to Google’s servers when you open a page, which shares your IP address with Google under Google’s Privacy Policy. The contact form sends nothing by itself: it opens your own email app with the message pre-filled, and the email you send is used only to reply to you.

12. Changes to this policy

If we change this policy, we will update the “Last updated” date at the top. Material changes will be communicated via the Chrome Web Store listing and/or our website.

13. Contact

Questions, requests, or privacy concerns:
developerext7@gmail.com
Postal address: Kobaltstack LLC, 447 Broadway, 2nd Floor, 3436, New York, NY 10013, New York, US