1. Overview
WebAudit is designed to perform webpage audits primarily inside the user's browser. It does not require an account, does not operate a backend or cloud database, and does not include an analytics service.
This Privacy Policy explains what information WebAudit accesses, how it is processed, where audit information is stored, and what happens when the optional AI explanation feature is used.
2. Information WebAudit accesses
When the user explicitly invokes WebAudit on a supported HTTP or HTTPS page, the extension accesses webpage content needed to perform the requested audit. This can include the page's DOM structure, elements, attributes, text-related properties, images, styles, headings, links, controls, and other information exposed by the page that is relevant to the audit rules.
WebAudit does not request or intentionally collect passwords, authentication credentials, financial information, health information, precise location information, or personal communications as a separate category of data.
3. How webpage content is used
Webpage content is accessed solely to provide the extension's audit functionality, including:
- Accessibility analysis
- UX and interaction analysis
- Visual design checks
- SEO checks
- Performance-related checks
- Identification of affected elements and audit findings
- Generation of an annotated page capture for the audit results
Local-first processing: Normal audits are performed locally in Chrome. The complete webpage is not uploaded to a WebAudit server because WebAudit does not operate a WebAudit backend or cloud database.
4. Audit history and local storage
Completed audits can be stored locally in the user's Chrome profile using browser storage. This may include audit results, findings, metadata, and annotated page captures associated with an audit.
WebAudit does not maintain a cloud copy of this audit history. Users can export, import, reopen, or permanently delete their locally saved audits through the extension where those features are provided.
5. Optional AI explanation
AI is optional and is not used during a normal audit. If the user explicitly configures an OpenAI API key and selects Explain with AI for a finding, WebAudit sends the selected structured finding directly to OpenAI so that an explanation can be generated.
The information sent for this optional request is limited to the selected finding and its structured audit context, which may include information such as:
- Finding title and description
- Audit category and severity
- Structured evidence associated with the finding
- Information about the selected affected element needed to explain the finding
The complete webpage is not sent to OpenAI by WebAudit for an AI explanation. No AI request is made unless the user explicitly invokes the AI explanation feature.
OpenAI receives information directly from the extension for that user-initiated request. WebAudit does not operate a proxy server for the AI request.
6. API keys
If the user chooses to use the optional AI explanation feature, the user may provide their own OpenAI API key. The key is used to make the user-requested AI request to OpenAI. Users should treat API keys as sensitive credentials and should not share them with other people.
WebAudit does not require an OpenAI API key to perform normal webpage audits.
7. Data sharing
WebAudit does not sell user data and does not use audit information for advertising, creditworthiness, lending, or unrelated profiling purposes.
The only external data transfer described by this policy is the user-initiated request to OpenAI when the optional Explain with AI feature is explicitly used. Normal audits are processed locally in the browser.
8. Data retention and deletion
WebAudit does not maintain a central WebAudit account or cloud audit database. Audit history stored by the extension remains in the user's browser storage until the user deletes it, removes the extension/browser profile data, or otherwise clears the relevant browser storage.
Users can permanently delete saved audits through WebAudit's audit-history controls where available.
9. Permissions
| Permission | Purpose |
|---|---|
activeTab |
Allows WebAudit to operate on the tab where the user explicitly invokes the extension. |
scripting |
Allows the extension to run its audit logic against the current webpage. |
storage |
Stores extension settings and locally saved audit information in the browser. |
sidePanel |
Provides WebAudit's Chrome side-panel interface for displaying audit results. |
https://api.openai.com/* (optional host permission) |
Used only when the user explicitly enables and invokes the optional AI explanation feature. |
10. Supported and restricted pages
Chrome prevents extensions from auditing certain protected browser pages, the Chrome Web Store, and some restricted documents. WebAudit does not attempt to bypass those browser restrictions.
11. Security
WebAudit is designed to minimize data transmission by performing normal audits locally. No security measure can guarantee absolute protection, so users should keep Chrome and the extension up to date and should protect any API credentials they choose to configure.
12. Children's privacy
WebAudit is a developer and website-auditing tool and is not directed specifically at children. WebAudit does not knowingly request children's personal information.
13. Changes to this policy
This Privacy Policy may be updated when WebAudit's functionality, data practices, or applicable requirements change. The version and effective date shown at the top of this page will be updated when material changes are made.
14. Contact
For privacy questions, requests, or concerns about WebAudit, contact the developer at:
Developer contact: YOUR-EMAIL@example.com
Replace the placeholder email address above with your real support/privacy email address before publishing this page.