The Trackingplan SDK only inspects the network requests that your site or app already sends to third‑party vendors (e.g., Google Analytics, HubSpot, Mixpanel, Google Ads), and forwards to our backend only the events required for anomaly detection, already anonymized on-device.
These requests are parsed locally in the browser or app, where anonymization and masking are applied as configured. Only the processed, non-identifiable event data is transmitted to Trackingplan’s servers. Once received, events are parsed, modeled, and continuously monitored to detect anomalies that may indicate implementation issues, whether in your own tracking or introduced by third-party tools. Through our web interface, teams can explore the detected schema, review alerts, and inspect sample events to debug tracking errors with full visibility and control.
Additionally, we do not introduce new identifiers, nor store IP addresses or fingerprinting data, as these are stripped before processing.
For a complete overview of our privacy and security measures, please visit our Privacy & Security documentation.