”CiteExport ProBack to home ↗

CiteExport Pro Privacy Policy

Last updated: 2026-10-03

CiteExport Pro for NotebookLM helps you preview and export loaded notebook content with source references on the legacy https://notebooklm.google.com/ and current https://notebook.google.com/ sites. This policy distinguishes the current publicly available billing-disabled Beta from the separate billing-enabled release candidate and a future paid production release. The candidate is not yet a public paid offer, but it already initializes the payment SDK and performs account/paid-status requests.

Notebook content and exports — both versions

When you open or refresh the exporter, or select text to export, the extension reads the relevant loaded NotebookLM responses, notes, study guides, flashcards, mind-map text, formatting, citation controls, source titles, source links and source passages. You may also paste notes and edit content or citation fields in the export dialog. Your chosen content may contain personal or sensitive information.

When you invoke the exporter or its popup, the extension reads the current tab URL to identify a supported notebook site and route the interface. It also reads the loaded notebook/page title as the default export title, which you can edit. These values are handled locally in memory. The extension does not enumerate or retain a list of visited pages, store a browsing-history log, or transmit the current notebook URL/title to payment services. Your chosen export title is included in files you request, as part of the local export content.

When you request source inspection, the extension sequentially inspects citation controls and visible tooltips or source panels. It may hover over or click a citation control to reveal a source passage. It uses information exposed by the page, does not call NotebookLM's private APIs, and does not infer missing quotations from source titles.

Notebook content, pasted text, citation edits, document titles and export generation are processed in memory on your device. They are not sent to a publisher-operated server, a payment provider or a language-model service. The extension does not persist notebook content or citation edits in Chrome extension storage. Closing the dialog discards its editing state. Generated download blobs may remain temporarily in memory until their download URLs are released, normally within 60 seconds.

Generated Word, PowerPoint, Anki, CSV, Markdown and ZIP files use your browser's download handling. Saved files remain under your control and may contain the content and source passages you selected. Source links in files make ordinary website requests if you open them. The extension does not download remote source images or other remote media.

Allowance, storage and the public Beta

The Beta provides unlimited Markdown exports and three free combined exports across the other available formats. Free export records use chrome.storage.sync: committed export request identifiers and temporary reservations containing creation time, export format and paid/free status. These records contain no notebook text or source quotations. Reservations stop counting against the allowance after 15 minutes; expired records are removed when the ledger is subsequently rewritten. Committed free-export records remain until the extension's stored data is removed.

Chrome may synchronize storage.sync data through your signed-in browser account when synchronization is enabled. When synchronization is disabled, Chrome keeps that data locally. Local extension storage is cleared when the extension is removed. Chrome controls synchronization and its associated data handling. See Chrome's storage documentation.

The current publicly available Beta is built with billing disabled. It does not initialize or start the ExtPay account service, make account or payment-status requests, or open purchasing flows. It does not create ExtPay account identifiers or ExtPay installation/account records. If you previously used a billing-enabled build with the same extension identity, disabling billing does not itself erase previously stored records.

Billing-enabled release candidate and future paid release

The separate release candidate is built with billing enabled. It initializes and starts the bundled ExtPay SDK in the background and registers/retrieves account information and paid-access status. Account and paid-status requests can occur before a user makes a purchase. It must not be treated as a billing-disabled build.

The publisher has registered the ExtensionPay application notebooklm-citeexport-pro and verified its USD $9.90 one-time and $3.99/month plans. Stripe is connected, and ExtensionPay marks Stripe and its live customer portal as configured. The store's public contact email is verified, and the publisher has completed its trader declaration. Checkout, paid unlock, restoration and subscription-management end-to-end acceptance remain pending. The candidate is now represented by a Chrome Web Store draft and has not been reviewed or published. Provider configuration does not establish a successful purchase. The current public Beta remains billing-disabled; the candidate will become a public paid release only after payment acceptance and store release are complete.

The billing-enabled candidate and any subsequent paid release use the bundled ExtPay SDK for optional Pro purchases, purchase restoration, subscription management and paid-status verification through ExtensionPay. The candidate includes hosted purchase/restoration entry points. When those flows are operational, checkout and restoration occur on the provider's pages. ExtensionPay identifies Stripe as its payment processor. The extension does not receive or store full payment-card numbers.

ExtPay uses Chrome sync storage, with a local-storage fallback when sync storage is unavailable. It records an installation timestamp when initialized. Depending on purchases or restoration, the SDK can store an account/API identifier and a cached account response containing an email address, paid status and payment date, installation/trial dates, plan details, subscription status and cancellation dates. These records may synchronize through Chrome independently of the application's own local cache.

The SDK uses the account identifier to retrieve paid-access status and open checkout or restoration pages. Those requests use HTTPS and do not include notebook text, source quotations or branding. In the billing-enabled candidate, custom branding and a small paid-access cache containing a paid flag and last-check time are stored locally. Recently verified paid access may be used for up to 24 hours if payment verification is unavailable; that does not imply automatic deletion of the cache after 24 hours.

Ordinary HTTPS requests from the billing-enabled SDK to ExtensionPay expose the connection's IP address and other network/request metadata to the receiving service. If you open provider-hosted pages, those pages also receive ordinary connection metadata; Stripe receives it when its hosted checkout or account pages are visited. An IP address may indicate an approximate location. The extension does not use GPS, request geolocation permission, or perform location tracking. Provider privacy policies govern their processing of this metadata.

ExtensionPay and Stripe handle buyer/account information and billing records under their own practices. ExtensionPay's published FAQ states that its website uses Google Analytics while its extension SDK does not add analytics to extensions. Removing the extension does not delete a purchase, cancel a subscription or delete payment-provider records.

Permissions

The extension handles the currently invoked tab URL and notebook/page title as disclosed above, but does not request the browser-history API permission or enumerate a visited-page history. It also does not request cookies, broad all-site access, clipboard or geolocation permissions. It does not read your Google password or NotebookLM authentication cookies. Runtime libraries are packaged with the extension.

Data use and Limited Use

CiteExport Pro uses information obtained through Chrome APIs and NotebookLM's visible page only for its disclosed content-export purpose. In the billing-enabled candidate and any paid release, account information is used only for the related paid-access administration. This use complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

The extension does not sell user data, use it for personalized advertising, transfer it for unrelated purposes, or use it to determine creditworthiness or for lending. It contains no advertising, analytics SDK or publisher-operated telemetry. Notebook content is not made available to the publisher through the extension. The public Beta uses Chrome synchronization of allowance records. The billing-enabled candidate also performs the account/status processing described above, including before purchase. Notebook content is not sent through those requests.

Your choices, retention and contact

You choose which content to export and which source passages to inspect. Closing the exporter discards its editing state. You can delete downloaded files and remove the extension to clear its local extension storage. Chrome controls synchronized data and account settings. For the billing-enabled candidate and any paid release, payment providers control their account and billing records separately from extension removal, even when the public Beta remains available alongside them.

Persistent records use Chrome's storage facilities; this extension does not add its own encryption layer to those stored values. Protecting your device, browser account and downloaded files remains under your control.

For privacy questions, data requests or product support, contact haowenapps@gmail.com.