Local feedback data
The feedback you collect
- Comments and replies
- Displayed authors and engagement
- Full source URLs
- Excel, CSV, and JSON files
- Local extraction history
Stored by default: in the local Runner and files on your computer.
Data & Telemetry
Your feedback and diagnostics are separate.
The comments and reviews you collect stay in the local workflow. Optional diagnostics use a small set of technical fields and separate infrastructure.
Optional technical diagnostics
Data that helps us fix problems
- Random installation ID after consent
- Platform and extension or adapter version
- Requested and actual record counts
- Result, duration, and stop reason
- Selected feature category
Default state: off until you opt in and a valid public endpoint is configured.
Privacy boundary
Diagnostics never include your content or account details.
- 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
How long diagnostics are kept.
| Data | Maximum retention |
|---|---|
| Raw technical events containing a random installation ID | 90 days |
| Daily totals without an installation ID | 12 months |
| Full-IP security logs, only when needed and stored separately | 7 days |
Your choice
Diagnostics are optional.
You can decline or turn off diagnostics without affecting extraction, local saving, downloads, or history. Turning diagnostics off stops new events and clears the unsent diagnostic queue.
A future cloud workspace or feedback sync would need its own disclosure and consent.