3 items
Log Simple Design QA issues and export them to CSV. Simple Design QA is a lightweight Chrome extension for manual UX/UAT logging on desktop web apps. What it does Opens from the toolbar popup and auto-fills: Page title Page URL Capture timestamp Lets users save issue details: Severity (Blocker, Major, Minor) Feedback type Issue text Optional reference link Optional selected container name (via on-page picker) Optional screenshot evidence (selected area or visible viewport capture) Stores logs locally in chrome.storage.local. Provides a Logs page to: Filter by severity and type Search by page title and feedback text Delete individual entries Preview saved screenshots Exports a ZIP file named like SDQA_YYYY-MM-DD_HH-mm-ss-SSS.zip containing: sdqa-logs.csv sdqa-logs.html screenshots/* (when screenshots exist) What it does not do Does not send logs or screenshots to any external server. Does not require account sign-in. Does not sync data across devices/accounts. Does not run continuously in the background to track browsing. Does not support restricted browser pages like chrome:// for area picker/screenshot capture. “Capture Full Page” captures the current visible viewport, not a stitched full-scroll page image. 3) Permissions justification storage Needed to save logs, selected container mappings, and popup draft state locally. activeTab Needed to read current tab context after user interaction and perform user-triggered capture/picker actions on that tab. tabs Needed to query the active tab and read its title/URL for auto-filled context fields. scripting Needed to inject temporary in-page scripts for: Container selection overlay Drag-to-select screenshot area overlay downloads Needed to generate and download the export ZIP file. 4) Privacy disclosure text Simple Design QA processes and stores QA data locally in your browser profile. Data collected (from user action) Page title and page URL from the active tab Capture timestamp User-entered severity, feedback type, and feedback text Optional reference link Optional selected container name Optional screenshot image data Temporary draft metadata (including active tab ID for same-tab draft restore) Data storage Stored in chrome.storage.local on the user’s device. Data remains until the user deletes entries, clears all logs, or uninstalls/clears extension storage. Exported files are saved locally via Chrome Downloads when user clicks Export. Data sharing No remote API calls for runtime logging/export features. No analytics, telemetry, or third-party data sharing in extension runtime. Data is not transmitted off-device unless the user manually shares exported files. 5) Simple FAQ for users Where are my logs saved? In your browser’s local extension storage (chrome.storage.local). Can I edit or delete logs? You can delete individual logs in the Logs page or clear all logs from the popup. Does this extension upload my screenshots anywhere? No. Screenshots are stored locally and only written to disk when you export. What does Export create? A ZIP with sdqa-logs.csv, sdqa-logs.html, and screenshot files (if any). Why can’t I capture on some pages? Chrome restricts extension actions on internal/restricted pages (for example chrome://). Does it keep unsaved text if I close the popup? Yes, draft content is restored on the same page URL; draft clears after save or URL change.
Feb 24, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.