Security Built Into Every Layer
Version 1.0 — Last Updated: January 25, 2026
Security Commitments
Our Security Principles
| Principle | Description |
|---|---|
| Defense in Depth | Multiple layers of security controls protect against various threat vectors |
| Least Privilege | Access is granted only to the minimum extent necessary to perform job functions |
| Secure by Default | Security is built into our products and infrastructure from the ground up |
| Continuous Improvement | We continuously evaluate and enhance our security posture |
| Transparency | We communicate openly about our security practices and any incidents |
Data Privacy Commitments
- No Cross-Organization Data Sharing — Your data is logically isolated from other customers
- Organization-Scoped AI Learning — AI improvements are confined to your organization only
- No Sale of Data — We never sell customer data to third parties
- No External AI Training — We do not use your data to train general AI models
Organizational Security
Security Governance
Arbol AI maintains a comprehensive information security program overseen by executive leadership. Our security program includes:
- Security Leadership — Dedicated security personnel reporting to executive management
- Security Policies — Comprehensive policies covering all aspects of information security
- Risk Management — Ongoing risk assessment and management processes
- Security Committee — Regular review of security posture and emerging threats
Personnel Security
| Control | Description |
|---|---|
| Background Checks | All employees with access to customer data undergo background verification |
| Security Training | Mandatory security awareness training upon hire and annually thereafter |
| Confidentiality Agreements | All employees sign confidentiality and acceptable use agreements |
| Role-Based Access | Access to systems and data based on job responsibilities |
| Termination Procedures | Immediate access revocation upon employment termination |
Security Awareness Program
- New hire security orientation
- Annual security awareness training
- Phishing simulation exercises
- Security updates and communications
- Role-specific security training for developers and operations staff
Infrastructure Security
Cloud Infrastructure
Arbol AI's infrastructure is hosted entirely in the United States using enterprise-grade cloud providers:
| Provider | Purpose | Certifications |
|---|---|---|
| Amazon Web Services (AWS) | Primary cloud infrastructure | SOC 1/2/3, ISO 27001, FedRAMP, HIPAA |
| Google Cloud Platform (GCP) | Additional services | SOC 1/2/3, ISO 27001, FedRAMP, HIPAA |
Data Center Security
Our cloud providers maintain physical security controls including:
- 24/7/365 security personnel and monitoring
- Biometric access controls
- Video surveillance with retention
- Visitor management and escort requirements
- Environmental controls (fire suppression, climate control, flood protection)
- Redundant power and network connectivity
Infrastructure Hardening
- Operating Systems — Hardened base images with minimal installed software
- Patch Management — Regular security patching with critical patches applied within 24-72 hours
- Configuration Management — Infrastructure as Code (IaC) for consistent, auditable configurations
- Container Security — Hardened container images with vulnerability scanning
- Secrets Management — Secure storage and rotation of credentials and API keys
Data Protection
Data Classification
We classify data based on sensitivity to ensure appropriate protection:
| Classification | Description | Examples |
|---|---|---|
| Confidential | Highly sensitive customer data | Call recordings, transcripts, contact lists |
| Internal | Business-sensitive information | Customer account data, billing information |
| Public | Non-sensitive information | Marketing materials, public documentation |
Encryption Standards
Data at Rest
- AES-256 encryption for all stored data
- Encryption keys managed through AWS KMS / GCP KMS
- Automatic key rotation policies
- Hardware Security Modules (HSMs) for key protection
Data in Transit
- TLS 1.2 minimum (TLS 1.3 preferred) for all connections
- Perfect Forward Secrecy (PFS) enabled
- Strong cipher suites only (no weak or deprecated ciphers)
- HSTS enabled on all web endpoints
Data Isolation
- Logical Separation — Customer data is logically isolated using unique identifiers
- Tenant Isolation — Multi-tenant architecture with strict data boundaries
- Network Segmentation — Production, staging, and development environments are segregated
- Database Isolation — Per-customer encryption keys where applicable
Data Retention and Deletion
- Configurable retention periods for call recordings and transcripts
- Secure deletion processes that render data unrecoverable
- Automated purging of temporary data
- Customer-initiated deletion capabilities through dashboard
- 30-day removal from active systems, 90-day removal from backups
Application Security
Secure Development Lifecycle (SDLC)
| Phase | Security Activities |
|---|---|
| Design | Threat modeling, security requirements definition |
| Development | Secure coding standards, code review, static analysis |
| Testing | Dynamic application security testing, penetration testing |
| Deployment | Security configuration review, deployment verification |
| Operations | Runtime protection, continuous monitoring |
Code Security
- Code Review — All code changes require peer review before merging
- Static Analysis (SAST) — Automated scanning for security vulnerabilities in code
- Dynamic Analysis (DAST) — Regular testing of running applications
- Dependency Scanning — Continuous monitoring for vulnerable third-party libraries
- Secret Detection — Automated scanning to prevent credential exposure
Vulnerability Management
Risk-based prioritization with defined SLAs for vulnerability remediation:
| Severity | Remediation SLA |
|---|---|
| Critical | 24 hours |
| High | 7 days |
| Medium | 30 days |
| Low | 90 days |
Penetration Testing
- Annual third-party penetration testing by qualified security firms
- Remediation of identified findings
- Retest to verify remediation effectiveness
- Additional testing following significant changes
Access Control
Authentication
| Control | Implementation |
|---|---|
| Multi-Factor Authentication (MFA) | Required for all employee access to production systems |
| Single Sign-On (SSO) | Centralized authentication for enterprise applications |
| Password Policy | Minimum 12 characters, complexity requirements, no reuse |
| Session Management | Automatic timeout, secure session handling |
Customer Authentication
- Email/password authentication with strength requirements
- Optional multi-factor authentication (MFA) for customer accounts
- API key authentication for programmatic access
- OAuth 2.0 support for third-party integrations
- Session timeout and concurrent session controls
Authorization
- Role-Based Access Control (RBAC) for all systems
- Principle of least privilege enforced
- Regular access reviews (quarterly for privileged access)
- Just-in-time (JIT) access for production systems
- Audit logging of all access and authorization changes
Privileged Access Management
- Separate privileged accounts for administrative tasks
- Multi-person approval for sensitive operations
- Time-limited access grants
- Full audit trail of privileged actions
- Regular rotation of privileged credentials
Network Security
Network Architecture
- Virtual Private Cloud (VPC) isolation
- Private subnets for sensitive workloads
- Public subnets only for load balancers and bastion hosts
- Network Access Control Lists (NACLs) and Security Groups
- Micro-segmentation between services
Perimeter Security
| Control | Description |
|---|---|
| Web Application Firewall (WAF) | Protection against OWASP Top 10 and common attacks |
| DDoS Protection | AWS Shield / Cloudflare for DDoS mitigation |
| Rate Limiting | Protection against brute force and abuse |
| IP Allowlisting | Available for enterprise customers |
| API Gateway | Centralized API security controls |
Monitoring and Detection
- 24/7 security monitoring of infrastructure and applications
- Security Information and Event Management (SIEM)
- Intrusion Detection Systems (IDS)
- Anomaly detection and alerting
- Log aggregation and correlation
- Real-time alerting for security events
Network Logging
- VPC Flow Logs for network traffic analysis
- DNS query logging
- Load balancer access logs
- API Gateway access logs
- Retention per compliance requirements
Incident Response
Incident Response Program
Arbol AI maintains a documented incident response program that includes:
- Incident Response Plan — Documented procedures for security incidents
- Incident Response Team — Designated personnel with defined roles and responsibilities
- Communication Procedures — Internal and external communication protocols
- Post-Incident Review — Root cause analysis and lessons learned
Incident Classification
| Severity | Description | Response Time |
|---|---|---|
| Critical | Active breach, data exfiltration, service-wide outage | Immediate (< 1 hour) |
| High | Potential breach, significant vulnerability, major service degradation | < 4 hours |
| Medium | Suspicious activity, minor vulnerability | < 24 hours |
| Low | Minor security event, informational | < 72 hours |
Customer Notification
- Notification of security incidents affecting customer data
- Compliance with Delaware breach notification requirements (within 60 days)
- Clear communication of incident details, impact, and remediation
- Ongoing updates until incident resolution
Incident Response Phases
- Detection — Identification of potential security incident
- Containment — Limiting the scope and impact of the incident
- Eradication — Removing the threat from the environment
- Recovery — Restoring affected systems and services
- Post-Incident — Analysis, documentation, and improvement
Business Continuity
Disaster Recovery
| Metric | Target |
|---|---|
| Recovery Time Objective (RTO) | 4 hours for critical services |
| Recovery Point Objective (RPO) | 1 hour for critical data |
| Backup Frequency | Continuous for databases, daily for other data |
| Backup Retention | 30 days minimum |
| Geographic Redundancy | Multi-region deployment within the United States |
High Availability
- Multi-Availability Zone (AZ) deployment
- Auto-scaling for capacity management
- Load balancing across multiple instances
- Database replication and failover
- No single points of failure for critical services
Backup and Recovery
- Encrypted backups stored in geographically separate locations
- Regular backup integrity testing
- Documented and tested recovery procedures
- Annual disaster recovery exercises
Business Continuity Plan
- Documented business continuity procedures
- Identification of critical business functions
- Recovery priorities and timelines
- Regular testing and updates
- Communication plans for stakeholders
Vendor Management
Third-Party Risk Management
Arbol AI maintains a vendor risk management program that includes:
- Due Diligence — Security assessment before vendor engagement
- Contractual Requirements — Security and privacy obligations in contracts
- Ongoing Monitoring — Regular review of vendor security posture
- Incident Notification — Requirement for vendors to report security incidents
Sub-Processor List
All sub-processors are U.S.-based companies with data processing in the United States. We maintain a complete list of our sub-processors including their purpose, data processed, and security certifications.
View complete sub-processor listVendor Security Requirements
All vendors with access to customer data must:
- Maintain appropriate security certifications
- Implement encryption for data at rest and in transit
- Provide incident notification within 24 hours
- Allow security audits upon request
- Sign data processing agreements
Compliance and Certifications
Current Compliance
| Framework/Regulation | Status |
|---|---|
| SOC 2 Type II | In Progress (Target: Q2 2026) |
| Delaware Personal Data Privacy Act (DPDPA) | Compliant |
| California Consumer Privacy Act (CCPA/CPRA) | Compliant |
| Telephone Consumer Protection Act (TCPA) | Compliant (Customer Responsibility) |
| CAN-SPAM Act | Compliant |
| PCI DSS | Not Applicable (Payment processing via Stripe) |
Audit and Attestation
- Annual independent security assessments
- Penetration testing by qualified third parties
- Vulnerability assessments
- Compliance audits as required
Customer Compliance Support
We provide customers with:
- Data Processing Addendum (DPA) upon request
- Sub-processor list
- Security questionnaire responses
- Compliance documentation
- Audit reports (under NDA)
Customer Security Controls
Account Security Features
| Feature | Description |
|---|---|
| Multi-Factor Authentication | Optional MFA for customer accounts |
| API Key Management | Secure generation, rotation, and revocation of API keys |
| Role-Based Access | Granular permissions for team members |
| Audit Logs | Comprehensive logging of account activities |
| Session Controls | Configurable session timeout and management |
Data Controls
- Data Export — Export your data in standard formats (CSV, JSON)
- Data Deletion — Self-service deletion of recordings, transcripts, contacts
- Retention Settings — Configurable data retention periods
- Access Controls — Control who can access sensitive data within your organization
Integration Security
- OAuth 2.0 for third-party integrations
- Webhook signature verification
- IP allowlisting available for API access
- Secure credential storage for integrations
Security Best Practices for Customers
We recommend customers:
- Enable multi-factor authentication on all accounts
- Use strong, unique passwords
- Regularly review and rotate API keys
- Implement IP allowlisting where possible
- Regularly review user access and permissions
- Monitor audit logs for suspicious activity
- Keep integration credentials secure and rotate regularly
Responsible Disclosure
Security Vulnerability Reporting
Arbol AI welcomes responsible disclosure of security vulnerabilities. If you discover a security issue, please report it to us:
Email: tomas@getarbol.com
Subject Line: Security Vulnerability Report
What to Include
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Any proof-of-concept code (if applicable)
- Your contact information
Our Commitment
- We will acknowledge receipt within 24 hours
- We will investigate and provide updates on progress
- We will work to remediate valid vulnerabilities promptly
- We will not take legal action against researchers who act in good faith, avoid privacy violations, data destruction, or service disruption, and do not publicly disclose until we have addressed the issue
Scope
In Scope
- getarbol.com and subdomains
- Arbol AI APIs and services
- Arbol AI mobile applications
Out of Scope
- × Third-party services and integrations
- × Social engineering attacks
- × Physical security testing
- × Denial of service attacks
Contact Information
General Contact
Arbol Artificial Intelligence, Inc.
131 Continental Dr, Suite 305
Newark, DE 19713
United States
General Email: tomas@getarbol.com
Documentation Requests
For security questionnaires, audit reports, or compliance documentation, contact tomas@getarbol.com.
Frequently Asked Questions
Your data is protected through multiple layers: AES-256 encryption at rest, TLS 1.2+ encryption in transit, organization-level access controls, input validation, and multi-tenant isolation that keeps your data completely separate from other customers.
Yes, we support Single Sign-On through Clerk, which integrates with major identity providers including Google, Microsoft, and other OIDC-compatible providers.
Only authenticated members of your organization can access your data. Administrators have full access while members have limited permissions. All access is verified against your organization's membership and logged for audit purposes.
Deleted data is removed from active systems within 30 days and from backups within 90 days. We use secure deletion processes that render data unrecoverable.
Please contact us at tomas@getarbol.com to report any security concerns. We will acknowledge receipt within 24 hours and take all reports seriously.
We are currently pursuing SOC 2 Type II certification with a target completion of Q2 2026. We are compliant with CCPA/CPRA and Delaware privacy requirements.
All data is stored in the United States using enterprise-grade cloud providers (AWS and GCP) with appropriate security certifications including SOC 2 Type II and ISO 27001.
Have security questions?
Contact us to discuss your security requirements in detail.
This Security Overview is provided for informational purposes and describes Arbol AI's security practices as of the date indicated. Security practices may evolve over time as we continue to improve our security posture. This document does not create any contractual obligations. For questions about specific security requirements, please contact tomas@getarbol.com.
© 2026 Arbol Artificial Intelligence, Inc. All rights reserved.