General Statement

CardioLog is an innovative, cross platform solution for enterprise portal analytics and business process analytics (BPA). Providing much more than common click-stream analysis, CardioLog offers valuable, in-depth usage reports thanks to its integration with the portal's unique object model, hierarchical structure, metadata, user groups, user profiles and action types. Hence, CardioLog allows for monitoring and control over portal activity, business processes, and knowledge management. With CardioLog, customers can maximize their ROI from portal investment and assure a successful deployment of the portal and its connected applications. CardioLog enables a more streamlined and efficient use by staff, reduces headcount, and can improve employee, customer, and trading partner productivity and satisfaction.


Privacy Policy

Intlock puts a great amount of emphasis on privacy, making sure that CardioLog can provide organizations with the information they need while still protecting personal information. CardioLog does not use personal identifiable information (PII) if it goes against company policy.  Furthermore, according to strict laws in many different countries in regards to privacy policy, Intlock has created different components which allow organizations to accomplish exactly what they need, where they need it.

CardioLog's Anonymous User Flag and PII Concealment features allow organizations to improve their portal with an analytics solution without compromising their employees' full privacy. These components allow organizations to disable the collection and/or presentation of employee PII (such as name, email, IP address).


Ownership of Data

CardioLog is an on premise solution. Therefore all the usage data for any specific portal is collected on that customer's servers and does not leave the organization.  No usage data collected is viewed by Intlock or any third party. Furthermore, Intlock has no access to the data collected by CardioLog.


CardioLog Cookies

CardioLog uses first-party cookies to track visitor interactions. These cookies are used to store information, such as what time the current visit occurred, whether the visitor has been to the site before, and what site referred the visitor to the web page. Browsers do not share first-party cookies across domains.


Use of IP Address and Personal Information

Every computer and device is assigned an Internet Protocol (IP) address when connected to the internet. These numbers are usually used to identify the geographical location of the user (known as geolocation). In order to analyze this information CardioLog collects the IP address of website visitors.

When used with intranet portals, CardioLog collects user PII (Personally identifiable information) from various organizational sources, including Active Directory, SharePoint User Profiles, and connected social networks. 

CardioLog administrators can either disable the collection of IP addresses and PII data, or simply hide this data completely from the reporting interface.  


Visitor Exclusion

The CardioLog Black List module provides administrators with an easy way to define rules for completely excluding usage data collection for specific users or IP addresses.

  • No labels