Local feedback data
Content used for your research
- Comments and replies
- Displayed authors and engagement
- Full source URLs
- Excel, CSV, and JSON files
- Local extraction history
Default destination: the local Runner and files on your computer.
Data & Telemetry
Two data flows, kept deliberately separate.
The feedback you collect belongs to the local extraction workflow. Optional diagnostics use a strict technical allowlist and separate infrastructure.
Optional technical diagnostics
Mechanics used to improve reliability
- Random installation ID after consent
- Platform and extension/adapter version
- Requested and actual record counts
- Result, duration, and controlled stop reason
- Selected feature-demand category
Default state: off until explicit consent and valid public configuration exist.
Never in product analytics
Content and credentials stay out.
- Cookies, sessions, authorization, tokens, passwords
- Google accounts, Chrome profiles, or platform logins
- Comment or reply text
- Authors, usernames, user IDs, or avatars
- Full URLs, URL hashes, titles, or search terms
- HTML, DOM, screenshots, or response bodies
- Export files or raw errors
- IP addresses in product analytics tables
- Advertising IDs, fingerprints, or cross-device IDs
Retention
Short-lived raw events, de-identified aggregates.
| Data | Maximum retention |
|---|---|
| Raw technical events containing a random installation ID | 90 days |
| Daily aggregates without installation ID | 12 months |
| Full-IP security logs, only if operationally required and kept separate | 7 days |
Control
Consent can be refused or withdrawn.
Refusing diagnostics does not affect extraction, local saving, Excel/CSV/JSON downloads, or history. Turning diagnostics off stops new events and clears any unsent diagnostic queue.
Future cloud workspaces or feedback synchronization would require a different disclosure and consent. They cannot reuse diagnostics consent.