Snapshot 28148
Normalized text
Scripts and page chrome removed; this is what change detection compares.
Nabla | Trust Center Nabla Trust Center Security and compliance are the backbone of healthcare. At Nabla, we place security and privacy at the top of our agenda because it is fundamentally tied to our customers' experience of our products. Within the Nabla Trust Center, you can request key documentation and explore detailed Security, Privacy & AI Governance adherence. Request Reports Compliance SOC 2 Type 2 ISO 27001 HIPAA CCPA Texas RAMP GDPR EU AI Act PIPEDA CIS Level 2 Resources SOC 2 Type II Report November 2024 to October 2025 ISO/IEC 27001 September 2025 TX-RAMP Certificate Level 2 January 2026 Pentest Executive Summary April 2026 AI Model Card CHAI version 2 AI Governance Whitepaper FAQs What security/compliance standards are used at Nabla? Nabla follows HIPAA, GDPR, SOC2, ISO27001 and NIST Cybersecurity standards for security and privacy. We have a dedicated Information Security and Privacy team who is responsible for both internal audits and working with external auditors to ensure compliance. Does Nabla have documented Security policies? Yes, Nabla has a collection of Information Security policies (25) that makes up our cybersecurity and compliance program. All policies are updated at minimum, annually. Does Nabla have an established Vendor Management Program? Yes, Nabla logs all vendors and uses standard risk ranking methodologies for criticality of each. Critical and high vendors are audited annually. Within the audit, we review their certification and audit reports, complete security questionnaires, and review physical security requirements (where applicable). Reviews are documented within our GRC tool. Where is my data stored? Nabla is a global organization and has clients across the world. U.S. based clients have data stored in U.S. regions within Google (GCP); all other clients are stored in EU Google (GCP) data centers. We also list our core vendors (subcontractors) on the bottom of this Trust Page. What data does Nabla retain? By default, we don't store audio. Clinicians can optionally share feedback that may include de-identified data. We retain clinical notes for a short period of time (14 days), which is configurable by client based on geographic region requirements. How is data encrypted? Data is encrypted via HTTPS (TLS 1.2+) in transit and via AES256 at rest. How does Nabla conform to AI regulations? Nabla tracks current AI regulations in relation to our product at a state and federal level. We have a dedicated AI Governance team and documented policy which includes a published model card. Does Nabla follow the EU AI Act? Yes. While Nabla is not considered high risk under the EU AI Act, we still follow requirements including published transparency standards on our model. Are new compliance reports published when available? Nabla will update all documents automatically in the Trust Portal once available. Further document requests can be sent to [email protected]. Monitoring Continuously monitored by Secureframe Subprocessors Nabla has worldwide operations. Separate data hosting environments are used for our U.S. clients. Google Cloud Infrastructure Hosting Central Region (USA) Belgium (All Non-USA) Azure Speech to Text Operations (U.S. Regions) Front Support Ticketing (No PHI) Monitoring Organizational Management Cybersecurity Insurance Cybersecurity insurance has been procured to help minimize the financial impact of cybersecurity loss events. Independent Advisor The board of directors or equivalent entity function includes senior management and external advisors, who are independent from the company's operations. An information security team has also been established to govern cybersecurity. Information Security Policy An Information Security Policy establishes the security requirements for maintaining the security, confidentiality, integrity, and availability of applications, systems, infrastructure, and data. Internal Control Monitoring A continuous monitoring solution monitors internal controls used in the achievement of service commitments and system requirements. Background Checks Background checks or their equivalent are performed before or promptly after a new hires start date, as permitted by local laws. Roles and Responsibilities Information security roles and responsibilities are outlined for personnel responsible for the security, availability, and confidentiality of the system. Information Security Program Review Management is responsible for the design, implementation, and management of the organization’s security policies and procedures. The policies and procedures are reviewed by management at least annually. Code of Conduct A Code of Conduct outlines ethical expectations, behavior standards, and ramifications of noncompliance. Advisor Meetings on Security Senior management and/or board of directors meets at least annually to review business goals, company initiatives, resource needs, risk management activities, and other internal/external matters. The information security team meets at least annually to discuss security risks, roles & responsibilities, controls, changes, audit results and/or other matters as necessary. Acceptable Use Policy An Acceptable Use Policy defines standards for appropriate and secure use of company hardware and electronic systems including storage media, communication tools and internet access. Performance Review Policy A Performance Review Policy provides personnel context and transparency into their performance and career development processes. Internal Control Policy An Internal Control Policy identifies how a system of controls should be maintained to safeguard assets, promote operational efficiency, and encourage adherence to prescribed managerial policies. Performance Reviews Internal personnel are evaluated via a formal performance review at least annually New Hire Screening Hiring managers screen new hires or internal transfers to assess their qualifications, experience, and competency to fulfill their responsibilities. New hires sign confidentiality agreements or equivalents upon hire. Disciplinary Action Personnel who violate information security policies are subject to disciplinary action and such disciplinary action is clearly documented in one or more policies. Organizational Chart Management maintains a formal organizational chart to clearly identify positions of authority and the lines of communication, and publishes the organizational chart to internal personnel. Communications Privacy Policy A Privacy Policy to both external users and internal personnel. This policy details the company's privacy commitments. Terms of Service Terms of Service or the equivalent are published or shared to external users. Communication of Critical Information Critical information is communicated to external parties, as applicable. Communication of Security Commitments Security commitments and expectations are communicated to both internal personnel and external users via the company's website. Access Security Access to Product is Restricted Non-console access to production infrastructure is restricted to users with a unique SSH key or access key Encryption-at-Rest Service data is encrypted-at-rest. Least Privilege in Use Users are provisioned access to systems based on principle of least privilege. Encryption-in-Transit Service data transmitted over the internet is encrypted-in-transit. Encryption and Key Management Policy An Encryption and Key Management Policy supports the secure encryption and decryption of app secrets, and governs the use of cryptographic controls. Access Control and Termination Policy An Access Control and Termination Policy governs authentication and access to applicable systems, data, and networks. Removal of Access Upon termination or when internal personnel no longer require access, system access is removed, as applicable. User Access Reviews System owners conduct scheduled user access reviews of production servers, databases, and applications to validate internal user access is commensurate with job responsibilities. Unique Access IDs Personnel are assigned unique IDs to access sensitive systems, networks, and information Administrative Access is Restricted Administrative access to production infrastructure is restricted based on the principle of least privilege. Asset Inventory A list of system assets, components, and respective owners are maintained and reviewed at least annually Availability Testing the Business Continuity and Disaster Recovery Plan The Business Continuity and Disaster Recovery Plan is periodically tested via tabletop exercises or equivalents. When necessary, Management makes changes to the Business Continuity and Disaster Recovery Plan based on the test results. Automated Backup Process Full backups are performed and retained in accordance with the Business Continuity and Disaster Recovery Policy. Uptime and Availability Monitoring System tools monitors for uptime and availability based on predetermined criteria. Business Continuity and Disaster Recovery Policy Business Continuity and Disaster Recovery Policy governs required processes for restoring the service or supporting infrastructure after suffering a disaster or disruption. High Availability Configuration The system is configured for high availability to support continuous availability, when applicable. Change Management Change Management Policy A Change Management Policy governs the documenting, tracking, testing, and approving of system, network, security, and infrastructure changes. Configuration and Asset Management Policy A Configuration and Asset Management Policy governs configurations for new sensitive systems Approval for System Changes System changes are approved by at least 1 independent person prior to deployment into production. Segregation of Environments Development, staging, and production environments are segregated. Baseline Configurations Baseline configurations and codebases for production infrastructure, systems, and applications are securely managed. Production Data Use is Restricted Production data is not used in the development and testing environments, unless required for debugging customer issues. Secure Development Policy A Secure Development Policy defines the requirements for secure software and system development and maintenance. Confidentiality Disposal of Customer Data Upon customer request, Company requires that data that is no longer needed from databases and other file stores is removed in accordance with agreed-upon customer requirements. Data Retention and Disposal Policy A Data Retention and Disposal Policy specifies how customer data is to be retained and disposed of based on compliance requirements and contractual obligations. Access to Customer Data is Restricted Access to, erasure of, or destruction of customer data is restricted to personnel that need access based on the principle of least privilege. Data Classification Policy A Data Classification Policy details the security and handling protocols for sensitive data. Incident Response Incident Response Plan An Incident Response Plan outlines the process of identifying, prioritizing, communicating, assigning and tracking confirmed incidents through to resolution. Incident Response Plan Testing The Incident Response Plan is periodically tested via tabletop exercises or equivalents. When necessary, Management makes changes to the Incident Response Plan based on the test results. Tracking a Security Incident Identified incidents are documented, tracked, and analyzed according to the Incident Response Plan. Lessons Learned After any identified security incident has been resolved, management provides a "Lessons Learned" document to the team in order to continually improve security and operations. Network Security Restricted Port Configurations Configurations ensure available networking ports, protocols, services, and environments are restricted as necessary, including firewalls. Endpoint Security Company endpoints are managed and configured with a strong password policy, anti-virus, and hard drive encryption Automated Alerting for Security Events Alerting software is used to notify impacted teams of potential security events. Network Security Policy A Network Security Policy identifies the requirements for protecting information and systems within and across networks. Network Traffic Monitoring Security tools are implemented to provide monitoring of network traffic to the production environment. Logging and Monitoring for Threats Logging and monitoring software is used to collect data from infrastructure to detect potential security threats, unusual system activity, and monitor system performance, as applicable. Risk Assessment Risk Assessment and Treatment Policy A Risk Assessment and Treatment Policy governs the process for conducting risk assessments to account for threats, vulnerabilities, likelihood, and impact with respect to assets, team members, customers, vendors, suppliers, and partners. Risk tolerance and strategies are also defined in the policy. Risk Assessment Formal risk assessments are performed, which includes the identification of relevant internal and external threats related to security, availability, confidentiality, and fraud, and an analysis of risks associated with those threats. Vendor Risk Management Policy A Vendor Risk Management Policy defines a framework for the onboarding and management of the vendor relationship lifecycle. Vendor Risk Assessment New vendors are assessed in accordance with the Vendor Risk Management Policy prior to engaging with the vendor. Reassessment occurs at least annually. Risk Register A risk register is maintained, which records the risk mitigation strategies for identified risks, and the development or modification of controls consistent with the risk mitigation strategy. Vendor Due Diligence Review Vendor SOC 2 reports (or equivalent) are collected and reviewed on at least an annual basis. Vulnerability Management Vulnerability and Patch Management Policy A Vulnerability Management and Patch Management Policy outlines the processes to efficiently respond to identified vulnerabilities. Third-Party Penetration Test A 3rd party is engaged to conduct a network and application penetration test of the production environment at least annually. Critical and high-risk findings are tracked through resolution.