Container analysis
The GTM JSON file selected in the auditor is parsed in the browser with a Web Worker. Custom HTML is never executed. The file is not posted to an application server by the local audit flow.
Privacy
How this build handles audit data.
A practical description of the data paths in Tag Audit Studio today.
Current release status
This is product information, not a final legal privacy notice. A public launch still needs a data controller, contact details, retention policy, and jurisdiction-specific review.
Local workspace history
After an analysis, the browser stores the structured audit summary, score, findings, and graph relationships in local browser storage for the active local workspace. The original JSON source is not automatically retained as workspace history.
Cookies and analytics
Optional analytics is disabled in this deployment. Consent preferences are stored in the browser so the application can remember the visitor's choice. Local analysis does not require analytics.
Production integrations
Clerk, Cloudflare D1, and Stripe are included as configurable foundation modules. They are not active until their credentials, bindings, access rules, and operating policies are configured for a production environment.