WebToSparkOrdinary extraction and export
WebToSpark processes the rendered DOM of pages you already opened. Derived records can include titles, text, source links, media URLs, comments, reviews and platform metadata. Extraction, cache and ordinary file export happen on your device without uploading page content, usage data, telemetry or diagnostics.
The extension does not read cookies, authentication tokens, passwords, payment data, private messages or form inputs. Sensitive routes and DOM areas are excluded. It does not download media or fetch exported links to validate them.
Local storage and deletion
IndexedDB holds parsed documents, cache indexes, saved-history metadata and the local allowance ledger. Chrome local storage holds settings, small tab states and signed license tokens. Files are written to your chosen destination.
Cache is subject to freshness and local eviction. Clear cache in Options when needed; history and usage remain. Removing history removes metadata only. Deleting exported files is your responsibility. Clearing all extension data or uninstalling can remove local extension records; keep files you need separately.
Website requests and experimental AI
Opening a confirmed collection workspace navigates to public entry pages and creates normal website requests. Separately started experimental Research Agent scrolling can also cause website loading. These actions carry platform and account risks.
The experimental Agent is off by default, requires Pro and the macOS Native Host, and remains deferred as a finished product. Its optional AI transport, if explicitly enabled and fully configured with a real provider, can send selected extracted titles, text, metrics and links to the configured endpoint. A completed production AI service is not promised. Review the provider’s policies before sharing content. Local research packets do not make AI calls.
This website and voluntary contact
This website uses Google Analytics to measure aggregate, anonymized traffic; it sets analytics cookies and shares usage data with Google under Google's policies. The extension itself stays local and sends no page content, usage or diagnostics to this site. Ordinary hosting and third-party sites you choose to visit can process connection information under their own practices.
If you contact the developer yourself, share only the information needed to resolve your request. The contact page explains how to prepare a report without secrets.
Changes and questions
This statement describes version 1.2.0 and this website. Check release notes and this page when updating, especially before enabling experimental integrations.