DigiVibeTech

AuditBrief privacy policy

Last updated 15 November 2026. Publisher: DigiVibeTech. Contact: digivibetech.com

AuditBrief uses Chrome local storage only for optional normalized audit history. There is no licence check, trial timestamp, developer analytics endpoint, tracking SDK, account registration or cloud report storage.

Public audits

When you request a public URL audit, the extension sends the URL, device strategy and audit categories to Google's PageSpeed Insights API. An optional API key is sent to Google only with those requests and remains in memory in the workspace tab, not in extension storage. Public URLs must contain no personal data, credentials, query strings or fragments. Google processes the requests under its own policies. No key is required by AuditBrief, but public quota may be exhausted.

Imports and history

Local Lighthouse JSON files are parsed on this device and are not uploaded to PageSpeed or DigiVibeTech. They can contain sensitive URLs or resource details, so review them before importing or sharing an export. Raw reports remain in memory while the workspace tab is open. Optional history stores only normalized URLs, device settings, scores, failing-audit summaries, warnings and framework hints. It is capped at 20 runs within approximately 4 MB. Exported files and copied text are under your control; the extension does not send them to a coding assistant or GitHub.

Permissions and removal

The extension needs local storage and network access to PageSpeed Insights. It has no browsing-history permission, page-content script or general website access. It opens its own workspace tab only when you click its action. Delete audit history in the workspace. Uninstalling the extension removes its local records; exported files must be deleted separately. Closing the tab clears its session inputs.

Support: https://digivibetech.com/support/