Public support
Support and contact
Use these public routes for product support, documentation issues, and privacy-safe evidence sharing. Do not post private page data or client evidence in public issues.
Support routes
| Need | Route | What to include |
|---|---|---|
| Bug report or product feedback | GitHub Issues | Extension version, browser version, page type, workflow used, expected result, actual result, and redacted evidence. |
| Documentation issue | GitHub Issues | Page URL, unclear or outdated text, and the correction needed. |
| Privacy or export concern | Privacy and local data guidance, then GitHub Issues if the concern is public-safe. | Describe the data category and workflow. Do not attach raw exports from private pages. |
What to include
- Extension version and browser version.
- Whether the page was a normal web page, restricted page, iframe-heavy page, local file, or login-only workflow.
- Which workflow was used: scan results, dashboard, scanner module, Screen Reader Review, Browser Preference QA Controls, export, history, or local data clearing.
- Relevant diagnostics text or exported support JSON only after sensitive data has been reviewed and redacted.
- Expected result and actual result.
Privacy-safe support
Exports can contain page URLs, selectors, snippets, screenshots, reviewer notes, and diagnostics. Do not attach private client pages, credentials, personal data, internal QA evidence, or unredacted reports to public issues.
Chrome Web Store contact boundary
The Chrome Web Store developer account must still provide its official support email/contact during listing setup. This public site provides support documentation and public-safe issue reporting; it does not expose private implementation repositories or internal release evidence.