Does your solution have access to personal or institutional data?
Explanation
Guidance
This includes patient data, student data, employment data, human research data, financial data, etc.
Example Responses
Example Response 1
Yes, our learning management system has access to student data including names, email addresses, student ID numbers, course enrollment information, and academic performance data such as grades and assignment submissions This access is necessary to provide core functionality including user authentication, course delivery, grade tracking, and academic reporting All data is encrypted both in transit (using TLS 1.2+) and at rest (using AES-256) Access to this data is strictly controlled through role-based permissions, and all data access is logged and monitored We maintain compliance with FERPA requirements and have implemented data minimization practices to ensure we only collect and retain the minimum necessary data to provide our services.
Example Response 2
No, our network monitoring solution does not have access to personal or institutional data Our system only collects technical metadata about network traffic such as IP addresses, port numbers, protocol information, and network performance metrics We specifically designed our solution to avoid collecting payload data or content that might contain personal information The system does not integrate with identity management systems, HR databases, financial systems, or any other repositories of personal or institutional data All collected data is anonymized where possible, and our retention policies ensure that even the limited technical data we collect is not kept longer than necessary for operational purposes.
Example Response 3
Partially Our document management system has the capability to store any type of document, which could potentially include personal or institutional data if customers choose to upload such content However, our system itself does not specifically require or request personal data to function We do not have direct integration with systems containing personal data, but customers may upload documents containing such information We cannot guarantee that personal data will never be present in our system, as this depends on customer usage For this reason, we implement strong encryption (AES-256), role-based access controls, and audit logging to protect any sensitive data that may be uploaded We recommend that customers follow data minimization practices and avoid uploading sensitive personal information unless necessary.
Context
- Tab
- Privacy
- Category
- Required Questions

