TCAudit

Capture signed browser consent, cookie, storage and network evidence for authorized website audits.

TCAudit helps authorized website reviewers capture reproducible browser observations for technical consent, cookie, storage and network analysis. The extension works with a TCAudit account and an existing draft audit. Installing the extension or opening its side panel does not start page-evidence collection. The user must sign in, identify the exact project and audit, confirm authorization and the collection boundary, and deliberately connect the current tab. The tab's origin must match the audit target. During a connected audit, TCAudit can collect and upload complete page, frame, resource and request URLs; page titles and selected DOM or consent-interface context; consent-platform signals; cookie and browser-storage names, attributes and value lengths; IndexedDB, cache and service-worker metadata; navigation, request and response metadata; timestamps; coverage limitations; and audit/device identifiers. Complete URLs and the remaining metadata can still be sensitive. Main capabilities: • Save a baseline and the consent choices the target offers. • Use standard collection or deliberately enable enhanced Chrome debugger capture. • Capture same-origin pages with a bounded URL crawl. • Keep signed evidence queued locally during a temporary connection failure. • Review capture completeness before permanently finalizing the audit. • Copy or download a customer-controlled redacted diagnostic summary for support. The extension keeps settings, session/device credentials, recent audit identifiers, capture runtime, signed pending evidence and retry state in Chrome extension storage. It sends authenticated, device-signed evidence and minimized operational events to `https://api.tcaudit.ie` for the connected organization, project and audit. Page collectors remain dormant when no audit is attached, although the service worker can retry already queued uploads in the background. Protocol v4 deliberately excludes raw cookie values, raw Cookie headers, raw localStorage or sessionStorage values, request/response bodies, page passwords and payment-card data from audit evidence. The TCAudit password entered during sign-in is used only to authenticate with the TCAudit API and is not stored as audit evidence. Use TCAudit only on websites, accounts and browser profiles you own or are authorized to assess. Use a controlled test profile, minimize personal data and review exports before sharing. TCAudit records technical observations and coverage limitations; it does not provide legal advice, certification or a guarantee of compliance.