Data Privacy and Protection
1. GDPR and Privacy Laws at Pistachio
We take data protection and information security seriously. Customers can trust us to operate at a high standard when it comes to security and data protection.
Pistachio is ISO/IEC 27001 certified, meaning we meet internationally recognized standards for protecting data. As an ISO 27001 certified company, our entire business is managed and operated along the following three principles:
- Protecting the confidentiality, integrity, and availability of information
- Identifying and assessing risks to information, and implementing appropriate controls
- Enabling continual monitoring and improvement
We apply the same high standard to our day-to-day management and operations as we do the development of our products. We take appropriate and commercially reasonable technical and organizational measures to protect against unauthorized or unlawful processing of any personal data provided by a customer, or any accidental loss, destruction or damage of data.
As required under ISO 27001, our compliance is subject to external review on an annual basis, meaning we have full-day sit-downs with an external, independent auditor who goes through our work requirement-by-requirement to confirm we are fully compliant.
Data Management Policy
To ensure information is classified and given an appropriate protection level, retained and securely disposed of, we have a Data Management Policy in place classifying data and information systems in accordance with legal requirements, sensitivity, and business criticality.
We have established three classes of data; confidential, restricted and public. Pistachio’s customer data is classified as confidential, meaning we treat it as highly sensitive with the highest levels of protection. Among other measures, access is restricted to specific employees or departments, and these records can only be passed to others with approval from the data owner or a company executive.
Responsible Representatives
Pistachio’s compliance with information security and data protection is dealt with by:
- Our COO, Marianne Sagerup, former corporate lawyer with a master's degree in law and two finance degrees from NHH (CEFA & MBA in finance).
If you have questions about our privacy practices or need to exercise your privacy rights, please contact us at privacy@pistachioapp.com.
2. Our Role as a Processor of Data
When a customer uses Pistachio’s products Practice or Presence, Pistachio processes personal data on behalf of the customer. We only process personal data as a processor acting on behalf of the customer (as controller).
In general, we collect and process personal data solely for the purpose of delivering our products including the Pistachio Platform (the latter including information on billing, statistics, security and legal obligations towards customers).
As required under GDPR, Pistachio has a Privacy Notice on our website, and data subjects can contact Pistachio via a contact form on our website in case of inquiries relating to our compliance with GDPR.
As data processor, we are subject to GDPR as well as local privacy laws in countries of operation. As required by our ISO 27001 certification, we have a policy in place setting out Relevant Laws, Regulations, and Contractual Requirements applicable to us. This policy represents a workbook for Pistachio, listing all relevant laws and regulations applicable to Pistachio’s operations.
For further detail on rights and how Pistachio processes personal data as a controller, please refer to Pistachio’s Privacy Policy.
3. Data Collection and Usage
This section describes the data Pistachio collects and how that data is used.
Basis of Data Collection
From a customer’s perspective, Pistachio’s processing of data is based on the principle of legitimate interest; balancing the customer's (employer’s) interest in mitigating cyber threat against how invasive the processing is for the data subject (generally not very invasive as its work-related data and behavior contrary to e.g. sensitive personal information and health data). This is in line with other cyber security products on the market, typically built on monitoring personal data only with different goals across product (data loss prevention, threat detection, antivirus, etc).
Collection of certain personal data is necessary for the Pistachio Platform to operate effectively. We collect several types of data about each licensed user (i.e. the employee) by reading the user’s profile data taken from Microsoft Entra ID. This collected data includes the user’s ID, display name, status (enabled/disabled), department, given name, surname, job title, mobile phone number, email address, location, language, and photo, as well as the name of each Entra group the user is a member of. This data is used to show admins in Pistachio relevant information, and to improve targeting of simulated attacks for Practice.
Across products, data collection is focused on specific purposes such as customizing and personalizing user experience, improving the Pistachio Platform and the services we provide, enhancing our data security measures, and complying with any applicable laws and regulations.
Customer Information
In addition to personal data of licensed users (i.e. employees), we collect the customer’s name and billing information, the latter being passed directly to our payment processor (we do not receive or store this data on our servers). We store a record of the transaction for the purpose of providing the customer with account history, invoicing, and billing support. Also, we collect and store data on actions taken on the Pistachio Platform by the customer’s admin users such as whether the Platform is turned on or off.
For any person visiting our website, to view our marketing and support materials or to navigate the product, we collect information about pages visited. This data is associated with a pseudonymous cookie identifier. If you are logged in, this data is associated with your logged in account (and therefore the identity of the visitor). We only collect this data for Pistachio, and we do not share it with others. You can refer to our Privacy Policy for a detailed description of our use of cookies.
Information on Licensed Users - Practice
As for Practice, we collect data about how each user interacts with the Pistachio Platform, such as attacks and training each user received, whether the user failed a given attack or confirmed the training, and other interaction data of that type, to allow us to determine which attacks and training programs to send. In this context, data on how users interact includes future features that we release introducing new ways for users to interact with training and attacks.
Information on Licensed Users - Presence
Presence uses audit logs to detect insider threat. Upon receipt of audit logs via a customer’s Microsoft tenant, the following data is made available to us:
- File activity data, including the name and path of the file and the action the user took (access, modify, delete, download, and upload).
- Email activity data, such as emails sent, including the subject line, size of the email, and the name of any attachments.
- Login events, including whether the login was successful and the device used.
- Other events, such as Copilot interaction data.
Audit log processing is required for the product to function, as processing of personal data forms basis for detecting insider threats. Logs monitored are the same audit logs typically monitored manually by a customer’s IT admin. Thus, the processing and monitoring Prescence does, is often covered by the existing data policies of the customer.
From a data privacy perspective, Presence is less invasive than manual review of audit logs by IT admins, since the IT team does not see audit logs of individuals unless Presence reports suspicious behavior after assessment by the products reasoning model, see below.
A full list of the types of data Microsoft makes available can be found here. Currently, we create the following subscriptions to access the necessary audit logs:
- Audit.AzureActiveDirectory
- Audit.Exchange
- Audit.SharePoint
- Audit.General (includes all other workloads not included in the previous content types)
No one has access to the models except Pistachio, and they are only used for the purpose of insider threat detection. Collected data is never used by Google for training their models.
In line with the principle of legitimate interest, Presence does not target individual users from the get-go. Rather, the models have been trained to generally monitor each licensed user daily, to identify behavior deemed suspicious based on the models’ understanding of context and intent (contrary to flagging users based on simple rules). The product fine-tunes models based on detected threats to improve performance over time. By illustration, the model might identify users who are frequently accessing files that do not align with their role, logging in at unusual hours or performing multiple actions at the same time, downloads sensitive files (especially right before exiting the company), searching through other people’s open documents and shared sites or sending sensitive documents via email with no obvious reason for doing so.
Before notifying a customer of a potential threat, Presence runs additional AI models to validate the findings. These models are given more data and are tasked to investigate a potential threat in a more holistic manner. The product only sends an alert if the validation models confirm a user is a potential insider threat. This limits the invasiveness of the product and reduces workload on the customer’s side.
Presence does not make automated decisions with legal consequences, as there is a human involved on the customer side confirming and deciding how to proceed if the product reports a potential threat.
Regardless of the customer’s interest in using the product, we urge customers to inform its employees about Presence being used, to ensure transparency in line with applicable data privacy legislation and to benefit from the preventive effect. Are you wondering how to best communicate the implementation of Presence within your organization? Pistachio’s legal team is available to help you with format and content upon request, at no additional cost to Pistachio customers.
Integrations - Presence
In addition to collecting data from Microsoft, Pistachio also supports a number of optional integrations that customers can connect in order to provide additional audit logs for analysis. Currently, Pistachio offers the following integrations:
HubSpot. Pistachio utilizes the HubSpot audit log API to gather information about how licensed Presence users behave. The data collected includes login activity and export actions.
Gong. Similar to HubSpot, Pistachio accesses Gong data via their audit log API. The data collected includes login activity, download actions, and pages viewed.
GitHub. The audit log for GitHub is unfortunately not made available externally via API, but the data is rather streamed into a Google Cloud Storage bucket that Pistachio provides. Currently, Pistachio is only listening for git.Clone actions.
In each case, the possible data collected via these integrations is likely to expand to fit new use cases, and when that happens this document will be updated accordingly.
4. Retention and Sharing of Data
This section describes Pistachio's policies for storing, deleting, and sharing data.
Data Retention
Pistachio retains data as long as the company has a need for its use, or to meet regulatory or contractual requirements. Once data is no longer needed, it is securely disposed of or archived.
For Practice, this means we retain data for as long as the customer uses our product and for an additional period of 12 months thereafter. After this time, we securely erase personal data from our product. The additional 12-month period is simply to allow for the customer to download security training insights at the end of the fiscal year prior to the data being disposed of (e.g. for audit and compliance reporting purposes).
Personally identifiable information (PII) is deleted or de-identified as soon as it no longer has a business use.
For Presence, we only store data for as long as we need it to detect the threats, which is 60 days. However, in the event that an alert is generated about an employee, the data is then stored and made available to the customer as a CSV file for as long as the customer is using our service. This allows the customer to go back and review past cases. This is in line with other cybersecurity products on the market.
Pistachio documents our retention period in the Data Retention Matrix included in our Data Management Policy, which has been reviewed as a part of our ISO 27001 certification process.
Sharing and Transfer
Pistachio stores all personal data in Google Cloud servers located in Europe. We uphold strict data privacy and security protocols to ensure the data is kept confidential and secure. We do not transfer personal data to countries outside the European Economic Area (EEA) or share data with any third parties unless such action is necessary to provide our services or comply with the law. As for Presence in particular, the AI models used run inside of Google Cloud’s Vertex AI, and the data never leaves the Google data centers in Europe.
All personal data stored in Google Cloud is encrypted at rest, and access to our internal systems is strictly limited to a small group of authorized individuals. We regularly update and test our security technology to ensure the ongoing integrity and confidentiality of your data.
5. Summary of Contractual Framework
For the sake of ease, we have summarized the key elements of our contractual framework below, which confirms our procedures and processes as described in this document.
Privacy policy: here
Data processing agreement: here
Pistachio’s obligations with respect to the processing of personal data is governed by a Data Processing Agreement (DPA) entered into with the customer as controller. Our template DPA is used unless the customer insists on using its own DPA template.
Terms of service
1. GDPR and Privacy Laws at Pistachio
We take data protection and information security seriously. Customers can trust us to operate at a high standard when it comes to security and data protection.
Pistachio is ISO/IEC 27001 certified, meaning we meet internationally recognized standards for protecting data. As an ISO 27001 certified company, our entire business is managed and operated along the following three principles:
- Protecting the confidentiality, integrity, and availability of information
- Identifying and assessing risks to information, and implementing appropriate controls
- Enabling continual monitoring and improvement
We apply the same high standard to our day-to-day management and operations as we do the development of our products. We take appropriate and commercially reasonable technical and organizational measures to protect against unauthorized or unlawful processing of any personal data provided by a customer, or any accidental loss, destruction or damage of data.
As required under ISO 27001, our compliance is subject to external review on an annual basis, meaning we have full-day sit-downs with an external, independent auditor who goes through our work requirement-by-requirement to confirm we are fully compliant.
Data Management Policy
To ensure information is classified and given an appropriate protection level, retained and securely disposed of, we have a Data Management Policy in place classifying data and information systems in accordance with legal requirements, sensitivity, and business criticality.
We have established three classes of data; confidential, restricted and public. Pistachio’s customer data is classified as confidential, meaning we treat it as highly sensitive with the highest levels of protection. Among other measures, access is restricted to specific employees or departments, and these records can only be passed to others with approval from the data owner or a company executive.
Responsible Representatives
Pistachio’s compliance with information security and data protection is dealt with by:
- Our COO, Marianne Sagerup, former corporate lawyer with a master's degree in law and two finance degrees from NHH (CEFA & MBA in finance).
If you have questions about our privacy practices or need to exercise your privacy rights, please contact us at privacy@pistachioapp.com.
2. Our Role as a Processor of Data
When a customer uses Pistachio’s products Practice or Presence, Pistachio processes personal data on behalf of the customer. We only process personal data as a processor acting on behalf of the customer (as controller).
In general, we collect and process personal data solely for the purpose of delivering our products including the Pistachio Platform (the latter including information on billing, statistics, security and legal obligations towards customers).
As required under GDPR, Pistachio has a Privacy Notice on our website, and data subjects can contact Pistachio via a contact form on our website in case of inquiries relating to our compliance with GDPR.
As data processor, we are subject to GDPR as well as local privacy laws in countries of operation. As required by our ISO 27001 certification, we have a policy in place setting out Relevant Laws, Regulations, and Contractual Requirements applicable to us. This policy represents a workbook for Pistachio, listing all relevant laws and regulations applicable to Pistachio’s operations.
For further detail on rights and how Pistachio processes personal data as a controller, please refer to Pistachio’s Privacy Policy.
3. Data Collection and Usage
This section describes the data Pistachio collects and how that data is used.
Basis of Data Collection
From a customer’s perspective, Pistachio’s processing of data is based on the principle of legitimate interest; balancing the customer's (employer’s) interest in mitigating cyber threat against how invasive the processing is for the data subject (generally not very invasive as its work-related data and behavior contrary to e.g. sensitive personal information and health data). This is in line with other cyber security products on the market, typically built on monitoring personal data only with different goals across product (data loss prevention, threat detection, antivirus, etc).
Collection of certain personal data is necessary for the Pistachio Platform to operate effectively. We collect several types of data about each licensed user (i.e. the employee) by reading the user’s profile data taken from Microsoft Entra ID. This collected data includes the user’s ID, display name, status (enabled/disabled), department, given name, surname, job title, mobile phone number, email address, location, language, and photo, as well as the name of each Entra group the user is a member of. This data is used to show admins in Pistachio relevant information, and to improve targeting of simulated attacks for Practice.
Across products, data collection is focused on specific purposes such as customizing and personalizing user experience, improving the Pistachio Platform and the services we provide, enhancing our data security measures, and complying with any applicable laws and regulations.
Customer Information
In addition to personal data of licensed users (i.e. employees), we collect the customer’s name and billing information, the latter being passed directly to our payment processor (we do not receive or store this data on our servers). We store a record of the transaction for the purpose of providing the customer with account history, invoicing, and billing support. Also, we collect and store data on actions taken on the Pistachio Platform by the customer’s admin users such as whether the Platform is turned on or off.
For any person visiting our website, to view our marketing and support materials or to navigate the product, we collect information about pages visited. This data is associated with a pseudonymous cookie identifier. If you are logged in, this data is associated with your logged in account (and therefore the identity of the visitor). We only collect this data for Pistachio, and we do not share it with others. You can refer to our Privacy Policy for a detailed description of our use of cookies.
Information on Licensed Users - Practice
As for Practice, we collect data about how each user interacts with the Pistachio Platform, such as attacks and training each user received, whether the user failed a given attack or confirmed the training, and other interaction data of that type, to allow us to determine which attacks and training programs to send. In this context, data on how users interact includes future features that we release introducing new ways for users to interact with training and attacks.
Information on Licensed Users - Presence
Presence uses audit logs to detect insider threat. Upon receipt of audit logs via a customer’s Microsoft tenant, the following data is made available to us:
- File activity data, including the name and path of the file and the action the user took (access, modify, delete, download, and upload).
- Email activity data, such as emails sent, including the subject line, size of the email, and the name of any attachments.
- Login events, including whether the login was successful and the device used.
- Other events, such as Copilot interaction data.
Audit log processing is required for the product to function, as processing of personal data forms basis for detecting insider threats. Logs monitored are the same audit logs typically monitored manually by a customer’s IT admin. Thus, the processing and monitoring Prescence does, is often covered by the existing data policies of the customer.
From a data privacy perspective, Presence is less invasive than manual review of audit logs by IT admins, since the IT team does not see audit logs of individuals unless Presence reports suspicious behavior after assessment by the products reasoning model, see below.
A full list of the types of data Microsoft makes available can be found here. Currently, we create the following subscriptions to access the necessary audit logs:
- Audit.AzureActiveDirectory
- Audit.Exchange
- Audit.SharePoint
- Audit.General (includes all other workloads not included in the previous content types)
No one has access to the models except Pistachio, and they are only used for the purpose of insider threat detection. Collected data is never used by Google for training their models.
In line with the principle of legitimate interest, Presence does not target individual users from the get-go. Rather, the models have been trained to generally monitor each licensed user daily, to identify behavior deemed suspicious based on the models’ understanding of context and intent (contrary to flagging users based on simple rules). The product fine-tunes models based on detected threats to improve performance over time. By illustration, the model might identify users who are frequently accessing files that do not align with their role, logging in at unusual hours or performing multiple actions at the same time, downloads sensitive files (especially right before exiting the company), searching through other people’s open documents and shared sites or sending sensitive documents via email with no obvious reason for doing so.
Before notifying a customer of a potential threat, Presence runs additional AI models to validate the findings. These models are given more data and are tasked to investigate a potential threat in a more holistic manner. The product only sends an alert if the validation models confirm a user is a potential insider threat. This limits the invasiveness of the product and reduces workload on the customer’s side.
Presence does not make automated decisions with legal consequences, as there is a human involved on the customer side confirming and deciding how to proceed if the product reports a potential threat.
Regardless of the customer’s interest in using the product, we urge customers to inform its employees about Presence being used, to ensure transparency in line with applicable data privacy legislation and to benefit from the preventive effect. Are you wondering how to best communicate the implementation of Presence within your organization? Pistachio’s legal team is available to help you with format and content upon request, at no additional cost to Pistachio customers.
Integrations - Presence
In addition to collecting data from Microsoft, Pistachio also supports a number of optional integrations that customers can connect in order to provide additional audit logs for analysis. Currently, Pistachio offers the following integrations:
HubSpot. Pistachio utilizes the HubSpot audit log API to gather information about how licensed Presence users behave. The data collected includes login activity and export actions.
Gong. Similar to HubSpot, Pistachio accesses Gong data via their audit log API. The data collected includes login activity, download actions, and pages viewed.
GitHub. The audit log for GitHub is unfortunately not made available externally via API, but the data is rather streamed into a Google Cloud Storage bucket that Pistachio provides. Currently, Pistachio is only listening for git.Clone actions.
In each case, the possible data collected via these integrations is likely to expand to fit new use cases, and when that happens this document will be updated accordingly.
4. Retention and Sharing of Data
This section describes Pistachio's policies for storing, deleting, and sharing data.
Data Retention
Pistachio retains data as long as the company has a need for its use, or to meet regulatory or contractual requirements. Once data is no longer needed, it is securely disposed of or archived.
For Practice, this means we retain data for as long as the customer uses our product and for an additional period of 12 months thereafter. After this time, we securely erase personal data from our product. The additional 12-month period is simply to allow for the customer to download security training insights at the end of the fiscal year prior to the data being disposed of (e.g. for audit and compliance reporting purposes).
Personally identifiable information (PII) is deleted or de-identified as soon as it no longer has a business use.
For Presence, we only store data for as long as we need it to detect the threats, which is 60 days. However, in the event that an alert is generated about an employee, the data is then stored and made available to the customer as a CSV file for as long as the customer is using our service. This allows the customer to go back and review past cases. This is in line with other cybersecurity products on the market.
Pistachio documents our retention period in the Data Retention Matrix included in our Data Management Policy, which has been reviewed as a part of our ISO 27001 certification process.
Sharing and Transfer
Pistachio stores all personal data in Google Cloud servers located in Europe. We uphold strict data privacy and security protocols to ensure the data is kept confidential and secure. We do not transfer personal data to countries outside the European Economic Area (EEA) or share data with any third parties unless such action is necessary to provide our services or comply with the law. As for Presence in particular, the AI models used run inside of Google Cloud’s Vertex AI, and the data never leaves the Google data centers in Europe.
All personal data stored in Google Cloud is encrypted at rest, and access to our internal systems is strictly limited to a small group of authorized individuals. We regularly update and test our security technology to ensure the ongoing integrity and confidentiality of your data.
5. Summary of Contractual Framework
For the sake of ease, we have summarized the key elements of our contractual framework below, which confirms our procedures and processes as described in this document.
Privacy policy: here
Data processing agreement: here
Pistachio’s obligations with respect to the processing of personal data is governed by a Data Processing Agreement (DPA) entered into with the customer as controller. Our template DPA is used unless the customer insists on using its own DPA template.
Terms of service
1. GDPR and Privacy Laws at Pistachio
We take data protection and information security seriously. Customers can trust us to operate at a high standard when it comes to security and data protection.
Pistachio is ISO/IEC 27001 certified, meaning we meet internationally recognized standards for protecting data. As an ISO 27001 certified company, our entire business is managed and operated along the following three principles:
- Protecting the confidentiality, integrity, and availability of information
- Identifying and assessing risks to information, and implementing appropriate controls
- Enabling continual monitoring and improvement
We apply the same high standard to our day-to-day management and operations as we do the development of our products. We take appropriate and commercially reasonable technical and organizational measures to protect against unauthorized or unlawful processing of any personal data provided by a customer, or any accidental loss, destruction or damage of data.
As required under ISO 27001, our compliance is subject to external review on an annual basis, meaning we have full-day sit-downs with an external, independent auditor who goes through our work requirement-by-requirement to confirm we are fully compliant.
Data Management Policy
To ensure information is classified and given an appropriate protection level, retained and securely disposed of, we have a Data Management Policy in place classifying data and information systems in accordance with legal requirements, sensitivity, and business criticality.
We have established three classes of data; confidential, restricted and public. Pistachio’s customer data is classified as confidential, meaning we treat it as highly sensitive with the highest levels of protection. Among other measures, access is restricted to specific employees or departments, and these records can only be passed to others with approval from the data owner or a company executive.
Responsible Representatives
Pistachio’s compliance with information security and data protection is dealt with by:
- Our COO, Marianne Sagerup, former corporate lawyer with a master's degree in law and two finance degrees from NHH (CEFA & MBA in finance).
If you have questions about our privacy practices or need to exercise your privacy rights, please contact us at privacy@pistachioapp.com.
2. Our Role as a Processor of Data
When a customer uses Pistachio’s products Practice or Presence, Pistachio process personal data on behalf the customer. We only processes personal data as a processor acting on behalf of the customer (as controller).
In general, we collect and process personal data solely for the purpose of delivering our products including the Pistachio Platform (the latter including information on billing, statistics, security and legal obligations towards customers).
As required under GDPR, Pistachio has a Privacy Notice on our website, and data subjects can contact Pistachio via a contact form on our website in case of inquiries relating to our compliance with GDPR.
As data processor, we are subject to GDPR as well as local privacy laws in countries of operation. As required by our ISO 27001 certification, we have a policy in place setting out Relevant Laws, Regulations, and Contractual Requirements applicable to us. This policy represents a workbook for Pistachio, listing all relevant laws and regulations applicable to Pistachio’s operations.
For further detail on rights and how Pistachio processes personal data as a controller, please refer to Pistachio’s Privacy Policy.
3. Data Collection and Usage
This section describes the data Pistachio collects and how that data is used.
Basis of Data Collection
From a customer’s perspective, Pistachio’s processing of data is based on the principle of legitimate interest; balancing the customer's (employer’s) interest in mitigating cyber threat against how invasive the processing is for the data subject (generally not very invasive as its work-related data and behavior contrary to e.g. sensitive personal information and health data). This is in line with other cyber security products on the market, typically built on monitoring personal data only with different goals across product (data loss prevention, threat detection, antivirus, etc).
From Pistachio’s perspective, collection of certain personal data is necessary for the Pistachio Platform to operate effectively. We collect several types of data about each licensed user (i.e. the employee) by reading the user’s profile data taken from Microsoft Entra ID. This collected data includes the user’s ID, display name, status (enabled/disabled), department, given name, surname, job title, mobile phone number, email address, location, language, and photo, as well as the name of each Entra group the user is a member of. This data is used to show admins in Pistachio relevant information, and to improve targeting of simulated attacks for Practice.
Across products, data collection is focused on specific purposes such as customizing and personalizing user experience, improving the Pistachio Platform and the services we provide, enhancing our data security measures, and complying with any applicable laws and regulations.
Customer Information
In addition to personal data of licensed users (i.e. employees), we collect the customer’s name and billing information, the latter being passed directly to our payment processor (we do not receive or store this data on our servers). We store a record of the transaction for the purpose of providing the customer with account history, invoicing, and billing support. Also, we collect and store data on actions taken on the Pistachio Platform by the customer’s admin users such as whether the Platform is turned on or off.
For any person visiting our website, to view our marketing and support materials or to navigate the product, we collect information about pages visited. This data is associated with a pseudonymous cookie identifier. If you are logged in, this data is associated with your logged in account (and therefore the identity of the visitor). We only collect this data for Pistachio, and we do not share it with others. You can refer to our Privacy Policy for a detailed description of our use of cookies.
Information on Licensed Users - Practice
As for Practice, we collect data about how each user interacts with the Pistachio Platform, such as attacks and training each user received, whether the user failed a given attack or confirmed the training, and other interaction data of that type, to allow us to determine which attacks and training programs to send. In this context, data on how users interact includes future features that we release introducing new ways for users to interact with training and attacks.
Information on Licensed Users - Presence
Presence uses audit logs to detect insider threat. Upon receipt of audit logs via a customer’s Microsoft tenant, the following data is made available to us:
- File activity data, including the name and path of the file and the action the user took (access, modify, delete, download, and upload).
- Email activity data, such as emails sent, including the subject line, size of the email, and the name of any attachments.
- Login events, including whether the login was successful and the device used.
- Other events, such as Copilot interaction data.
Audit log processing is required for the product to function, as processing of personal data forms basis for detecting insider threats. Logs monitored are the same audit logs typically monitored manually by a customer’s IT admin. Thus, the processing and monitoring Prescence does is normally covered by the existing data policies of the customer.
A full list of the types of data Microsoft makes available can be found here. Currently, we create the following subscriptions to access the necessary audit logs:
- Audit.AzureActiveDirectory
- Audit.Exchange
- Audit.SharePoint
- Audit.General (includes all other workloads not included in the previous content types)
No one has access to the models except Pistachio, and they are only used for the purpose of insider threat detection. Collected data is never used by Google for training their models.
In line with the principle of legitimate interest, Presence does not target individual users from the get-go. Rather, the models have been trained to generally surveil each license user daily, to identify behavior deemed suspicious based on the models’ understanding of context and intent (contrary to flagging users based on simple rules). The product fine-tunes models based on detected threats to improve performance over time. By illustration, the model might identify users who are frequently accessing files that do not align with their role, logging in at unusual hours or performing multiple actions at the same time, downloads sensitive files (especially right before exiting the company), searching through other people’s open documents and shared sites or sending sensitive documents via email with no obvious reason for doing so.
Before notifying a customer of a potential threat, Presence runs additional AI models to validate the findings. These models are given more data and are tasked to investigate a potential threat in a more holistic manner. The product only sends an alert if the validation models confirm a user is a potential insider threat. This limits the invasiveness of the product and reduces workload on the customer’s side.
Presence does not make automated decisions with legal consequences, as there is a human involved on the customer side confirming and deciding how to proceed if the product reports a potential threat.
Regardless of the customer’s interest in using the product, we urge customers to inform its employees about Presence being used and its implications for employees engaged in insider‑threat behavior.
Integrations - Presence
In addition to collecting data from Microsoft, Pistachio also supports a number of optional integrations that customers can connect in order to provide additional audit logs for analysis. Currently, Pistachio offers the following integrations:
HubSpot. Pistachio utilizes the HubSpot audit log API to gather information about how licensed Presence users behave. The data collected includes login activity and export actions.
Gong. Similar to HubSpot, Pistachio access Gong data via their audit log API. The data collected includes login activity, download actions, and pages viewed.
GitHub. The audit log for GitHub is unfortunately not made available externally via API, but the data is rather streamed into a Google Cloud Storage bucket that Pistachio provides. Currently, Pistachio is only listening for git.Clone actions.
In each case, the possible data collected via these integrations is likely to expand to fit new use cases, and when that happens this document will be updated accordingly.
4. Retention and Sharing of Data
This section describes Pistachio's policies for storing, deleting, and sharing data.
Data Retention
Pistachio retains data as long as the company has a need for its use, or to meet regulatory or contractual requirements. Once data is no longer needed, it is securely disposed of or achieved.
For Practice, this means we retain data for as long as the customer uses our product and for an additional period of 12 months thereafter. After this time, we securely erase personal data from our product.
Personally identifiable information (PII) is deleted or de-identified as soon as it no longer has a business use.
For Presence, we only store data for as long as we need it to detect the threats, which is 60 days. However, in the event that an alert is generated about an employee, the data is then stored and made available to the customer as a CSV file for as long as the customer is using our service. This allows the customer to go back and review past cases. This is in line with other cybersecurity products on the market.
Pistachio documents our retention period in the Data Retention Matrix included in our Data Management Policy, which has been reviewed as a part of our ISO 27001 certification process.
Sharing and Transfer
Pistachio stores all personal data in Google Cloud servers located in Europe. We uphold strict data privacy and security protocols to ensure the data is kept confidential and secure. We do not transfer personal data to countries outside the European Economic Area (EEA) or share data with any third parties unless such action is necessary to provide our services or comply with the law. As for Presence in particular, the AI models used run inside of Google Cloud’s Vertex AI, and the data never leaves the Google data centers in Europe.
All personal data stored in Google Cloud is encrypted at rest, and access to our internal systems is strictly limited to a small group of authorized individuals. We regularly update and test our security technology to ensure the ongoing integrity and confidentiality of your data.
5. Summary of Contractual Framework
For the sake of ease, we have summarized the key elements of our contractual framework below, which confirms our procedures and processes as described in this document.
Privacy policy: here
Data processing agreement: here
Pistachio’s obligations with respect to the processing of personal data is governed by a Data Processing Agreement (DPA) entered into with the customer as controller. Our template DPA is used unless the customer insists on using its own DPA template.
Terms of service
Current version: