Personal Identifiable Information (PII) is any set of data that can be used to identify a specific individual. PII can be as simple as a username, or a date of birth, or as sensitive as a full name, an address, a social security number, or any type of financial data (billing address, credit card information, CVV, etc.). They are considered sensitive data and are the information used in identity theft as, in a data breach, PII is a target for attackers due to its high value when sold on darknet markets or the dark web.
However, as data grows more complex, and considering that organizations nowadays rely on several external services to do analytics, product development, marketing automation, or sales (Google Analytics, Amplitude, Hubspot, Adjust, Intercom, Salesforce, Pipedrive, Braze, etc.), checking that you are not sending any PII-sensitive data to all these third-party integrations can be overwhelming.
To help you with that, Trackingplan automatically connects and documents everything that flows between your sites and apps to third-party integrations (e.g.: Google Analytics, Segment, Mixpanel, etc.). This provides a roadmap with powerful cross-service insights to effectively ensure only PII-compliant data is accurately collected, responsibly managed, and integrated efficiently across teams and platforms.
Moreover, apart from automatically discovering your data integrations to easily see what data you are actually collecting and the schemas beneath this process, Trackingplan’s Privacy Report allows you to see at a glance which private data your site is collecting from your users and forwarding to third parties.
That way, personal data – like user emails, IP addresses, SSNs, credit cards, and so on – will be automatically spotted and labeled here in order to detect any possible privacy issue or security-sensitive data that should not have been collected or forwarded to your analytics services.
To learn more, check our documentation on Trackingplan’s Privacy Report.