Privacy & trust
Export Public Comments Without Sharing Login Cookies
A local current-page workflow can collect public feedback without asking for browser cookies or account credentials.
Published 2026-08-10 · 5 minute read
Your browser session stays with you
FeedbackMosaic starts from a page you have already opened. You start the extraction, and the extension reads the page content needed for that task. It does not ask you to paste a Cookie header, export a session, or provide account credentials.
A login session can expose far more than the public discussion you want to collect. Exporting comments should not require handing that session to another service.
What stays local by default
The local Runner saves the working data and lets you download it again from local history.
- comment and reply text;
- displayed authors;
- source URLs;
- Excel, CSV, and JSON exports;
- local task history.
Diagnostics are optional
Anonymous technical diagnostics stay off until a public endpoint and privacy policy are available and you opt in. If enabled, diagnostics can include technical fields such as platform, version, result, counts, duration, and a controlled stop reason. They do not include comment text, authors, full URLs, page titles, search terms, DOM, screenshots, or raw errors.
Turning diagnostics off does not disable extraction, local history, or downloads.
Platforms still control access
Keeping cookies local does not remove a platform's access rules. A login wall, challenge, rate limit, or unavailable page can still stop a task. Records already collected are kept as a partial result with the stop reason shown.
Note: Platforms can change how pages load and display comments. The examples in this article describe the pages we tested.