{"trustCenterMetadata":{"slugId":"wcfc937w4gljs8gn89q1s","region":"us"},"company":{"name":"Factory","title":"Factory","description":"Welcome to our Trust Portal for Factory - your portal to understanding our unwavering commitment to data security, privacy, and compliance.","overviewSectionDescription":"You can access our compliance documentation, find answers to frequently asked questions related to security and privacy, and explore our robust security practices. We believe in maintaining transparency and building trust with our customers, and this portal is designed to provide you with the information and assurance you need to feel confident in our ability to protect your data.","contactEmail":"trust@factory.ai","privacyPolicy":"https://www.factory.ai/privacy-policy","awsMarketplaceListing":null,"awsMarketplaceSellerId":null,"publicReportEnabled":true,"website":null},"accessRequestFormDetails":{"fields":[{"name":"email","label":"Email","required":true,"type":"email"},{"name":"givenName","label":"First name","required":true,"type":"string","maxLength":200},{"name":"familyName","label":"Last name","required":true,"type":"string","maxLength":200},{"name":"companyName","label":"Company name","required":true,"type":"string","maxLength":200},{"name":"reason","label":"Reason","type":"enum","required":true,"options":["I'm an existing customer","I'm a prospective customer","Other"]},{"name":"accessLevel","label":"Access level","type":"enum","required":true,"options":["FULL_ACCESS","PARTIAL_ACCESS"]},{"name":"requestedResources","label":"Requested resources","type":"string[]","requiredWhen":{"accessLevel":"PARTIAL_ACCESS"}},{"name":"source","type":"string","required":true,"label":null}]},"frameworks":{"items":[{"id":"686ead77bc82cfdf42edcf12","name":"SOC 2","description":null,"logoUrl":"https://trust.factory.com/doc?s=11okt9lodn74dourfn3ll"},{"id":"6aad7524092654b556049071","name":"ISO 27001:2022","description":null,"logoUrl":"https://trust.factory.com/doc?s=lwonhoeu51zqv4439lh2xa"},{"id":"686ead77bc82cfdf42edcf13","name":"ISO 42001","description":null,"logoUrl":"https://trust.factory.com/doc?s=uwllm33ji835u2ir5di6we"},{"id":"686ead77bc82cfdf42edcf14","name":"Minimum Viable Secure Product","description":null,"logoUrl":"https://trust.factory.com/doc?s=qsozjfrhnkr16ce8qvgeib"},{"id":"686ead77bc82cfdf42edcf15","name":"CCPA","description":null,"logoUrl":"https://static.vanta.com/assets/framework-logo-ccpa.svg"}]},"dataCollected":{"items":[{"type":"Customer personally identifiable information","status":"COLLECTED"},{"type":"Employee personally identifiable information","status":"NOT_COLLECTED"},{"type":"Credit card information","status":"NOT_COLLECTED"},{"type":"Personal health information","status":"NOT_COLLECTED"},{"type":"Code Metadata","status":"COLLECTED"}]},"subprocessors":{"items":[{"id":"6552c413ae504f436c6a8112","name":"Microsoft Azure","purpose":"Cloud provider","location":"US","url":"azure.microsoft.com"},{"id":"64cda55a30f22aaf26cc423f","name":"Amazon Web Services","purpose":null,"location":"US","url":"aws.amazon.com"},{"id":"64cda77663d374d1e83da91c","name":"Google Cloud Platform","purpose":null,"location":"US","url":"cloud.google.com"},{"id":"64cdb24736d43b074ac05122","name":"GitHub","purpose":"","location":"US","url":"github.com"},{"id":"69a6131fa5c4db5e5c6317ef","name":"Anthropic","purpose":"Engineering","location":"US","url":"https://www.anthropic.com"},{"id":"690b9cabe75ddf8feb057501","name":"Axiom","purpose":"Analytics and log analysis","location":"US","url":"https://axiom.co"},{"id":"6a20b553d66bc8f3e4122102","name":"Baseten","purpose":"Engineering","location":"US","url":"https://www.baseten.co"},{"id":"69fbcd2c6a1b518fbea6ee7d","name":"E2B","purpose":"Cloud provider","location":"US","url":"e2b.dev"},{"id":"69a9f6884ace7ad3fd4978a0","name":"Fireworks","purpose":"Engineering","location":"US","url":"https://fireworks.ai"},{"id":"64cdb28636d43b074ac0513e","name":"Google Drive","purpose":"Document management","location":"US","url":"drive.google.com"},{"id":"6a67eb9d29fa8b8e6f3a9708","name":"Mistral","purpose":"Engineering","location":"US","url":"mistral.ai"},{"id":"6a2359d43e381e0895119b0d","name":"MongoDB","purpose":"Data storage and processing","location":"US","url":"mongodb.com"},{"id":"690b9c7545ee0764d785396b","name":"OpenAI","purpose":"Engineering","location":"US","url":"https://openai.com"},{"id":"690b9be8f4c780c72543e0d0","name":"Orb","purpose":"Billing","location":"US","url":"https://www.withorb.com"},{"id":"690b9c97f9a507458d7bd2dd","name":"Sentry","purpose":"Analytics and log analysis","location":"US","url":"https://sentry.io/"},{"id":"698ba8244c13f066647638fb","name":"Snowflake","purpose":"Engineering","location":"US","url":"https://www.snowflake.com/"},{"id":"64cda84136d43b074ac05104","name":"Slack","purpose":"Collaboration","location":"US","url":"slack.com"},{"id":"690b9c60bd2f95977b8d0d52","name":"Stripe","purpose":"Billing","location":"US","url":"http://stripe.com/"},{"id":"6a67eb3b1ff695c5636d651d","name":"Together","purpose":"Engineering","location":"US","url":"together.ai"},{"id":"64cdb38f9389ebaa49f44d36","name":"Vercel","purpose":"Engineering","location":"US","url":"vercel.com"},{"id":"690b9b3d50a7a7dda693598e","name":"WorkOS","purpose":"User authentication","location":"US","url":"https://workos.com"},{"id":"6ae3c834d196d99dab6b8a4f","name":"xAI","purpose":"Engineering","location":"US","url":"x.ai"}]},"faq":{"categories":[{"id":"677f11731748e2434fbe972f","name":"Infrastructure Security","items":[{"id":"677f11590938d69768241320","question":"How is my code and data protected in your infrastructure?","answer":"Our infrastructure is built with security-first principles:\n\n-   All infrastructure is defined as code using Terraform, ensuring consistent and secure deployments\n-   Resources are deployed in a Virtual Private Cloud (VPC) with private subnets\n-   Security groups strictly control access between components\n-   All data is encrypted at rest using AWS KMS and in transit using TLS\n-   DynamoDB tables use server-side encryption\n-   S3 buckets are configured with strict access controls and encryption\n-   ECS tasks run in private subnets with minimal required permissions"},{"id":"677f11590938d69768241321","question":"What security measures are in place for your deployments?","answer":"Our Kubernetes infrastructure includes:\n\n-   Separate control plane and data plane clusters for isolation\n-   Private subnets for worker nodes\n-   IAM roles with least privilege principles\n-   Prometheus monitoring for security metrics\n-   Regular security patches and updates\n-   Network policies controlling pod-to-pod communication"},{"id":"677f11590938d69768241322","question":"How do you handle logging and monitoring?","answer":"We employ comprehensive logging and monitoring:\n\n-   Prometheus and Grafana for metrics monitoring\n-   CloudWatch for AWS service monitoring\n-   Firehose for log aggregation\n-   Sentry for error tracking and performance monitoring\n-   Regular log analysis for security events"}]},{"id":"677f11731748e2434fbe9733","name":"Data Privacy","items":[{"id":"677f11590938d69768241324","question":"What data do you collect and store?","answer":"We manage:\n\n-   Repository metadata (file paths, function signatures, class definitions)\n-   User authentication information\n-   Organization configuration data\n-   Usage metrics and telemetry\n-   Session data for active users\n\nWe do NOT store:\n\n-   Complete source code from repositories\n-   Sensitive credentials or secrets\n-   Personal information beyond what's necessary for service operation"},{"id":"677f11590938d69768241325","question":"How is data isolated between organizations?","answer":"We ensure strict data isolation through:\n\n-   Separate DynamoDB tables per environment\n-   Organization-specific S3 buckets\n-   IAM roles and policies enforcing access boundaries\n-   Firestore security rules preventing cross-organization access\n-   Kubernetes namespace isolation for organization workloads"},{"id":"677f11590938d69768241326","question":"What happens to my data if I delete my account?","answer":"Upon account deletion:\n\n-   Organization data is removed from DynamoDB tables\n-   Associated S3 buckets are cleared\n-   Firestore records are deleted\n-   Authentication tokens are revoked\n-   All cached data is purged from our systems"}]},{"id":"677f11731748e2434fbe9737","name":"Access Control","items":[{"id":"677f11590938d69768241328","question":"How do you manage access to your systems?","answer":"We implement multiple layers of access control:\n\n-   WorkOS for organization authentication\n-   Firebase Authentication for user management\n-   IAM roles and policies for AWS resources\n-   RBAC for Kubernetes clusters\n-   VPC endpoints for private AWS service access\n-   Multi-factor authentication for administrative access"},{"id":"677f11590938d69768241329","question":"How do you protect against unauthorized access?","answer":"Protection measures include:\n\n-   Regular security audits\n-   Automated vulnerability scanning\n-   IP whitelisting for sensitive endpoints\n-   Rate limiting on API endpoints\n-   Session management with automatic timeouts\n-   Continuous monitoring for suspicious activities"}]},{"id":"677f11731748e2434fbe973a","name":"Compliance and Standards","items":[{"id":"677f11590938d6976824132b","question":"What security standards do you follow?","answer":"We align with industry best practices:\n\n-   SOC 2 Compliance\n-   ISO 42001 Compliance\n-   Following AWS Well-Architected Framework\n-   Implementing OWASP security guidelines\n-   Regular security assessments\n-   Continuous compliance monitoring through Vanta"},{"id":"677f11590938d6976824132c","question":"How do you handle security incidents?","answer":"Our incident response process includes:\n\n-   Automated alerts for suspicious activities\n-   Dedicated security response team\n-   Incident classification and prioritization\n-   Regular incident response drills\n-   Post-incident analysis and improvements\n-   Customer notification when required"},{"id":"677f11590938d6976824132d","question":"How often do you perform security updates?","answer":"We maintain a proactive security posture:\n\n-   Daily automated security scans\n-   Weekly dependency updates\n-   Monthly infrastructure security reviews\n-   Quarterly penetration testing\n-   Immediate critical patch deployment\n-   Regular security training for team members"}]},{"id":"677f11731748e2434fbe973e","name":"Reporting Security Issues","items":[{"id":"677f11590938d6976824132f","question":"How can I report a security vulnerability?","answer":"\nIf you discover a security vulnerability:\n\n1.  Email our CTO directly at [eno@factory.ai](mailto:eno@factory.ai)\n2.  Include detailed information about the vulnerability\n3.  Avoid sharing sensitive details publicly\n4.  Our security team will acknowledge within 24 hours\n5.  We'll provide regular updates on investigation progress\n6.  You'll receive confirmation when the issue is resolved"},{"id":"677f11731748e2434fbe9740","question":"Do you have a bug bounty program?","answer":"While we don't currently have a formal bug bounty program, we:\n\n-   Welcome responsible security disclosures\n-   Take all reports seriously\n-   Investigate issues thoroughly\n-   Credit researchers who report issues (with permission)\n-   Plan to establish a formal program in the future"}]},{"id":"6aeb06774f2dc25f7b761a6f","name":"FedRAMP","items":[{"id":"6aeb06f85b6b6d6f0f9dc6fc","question":"What is your quarterly review process? ","answer":"Quarterly Reviews: third Thursday of February, May, August and November. FedRAMP and agency customers get a calendar invitation. Information will be made available upon request to all qualifying parties. To register please contact fedramp@factory.com. "}]}]},"resources":{"categories":[{"id":"6aeb8137aa435ada45490c63","name":"Documentation","items":[{"id":"65ea66d46af50d8aa7bb976e","type":"document","title":"SOC 2 Type 1 Report","description":"The SOC 2 Report contains a certified audit of the Factory (system) that may be useful when assessing the risks arising from interactions with The San Francisco AI Factory Inc.’s system, particularly information about system controls that The San Francisco AI Factory Inc. has designed, implemented, and operated to provide reasonable assurance that its service commitments and system requirements were achieved based on the trust services criteria relevant to security (applicable trust services criteria) set forth in TSP section 100, 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (AICPA, Trust Services Criteria).","isPublic":false,"hasAccess":false,"isViewOnly":false,"url":null,"downloadUrl":null,"fileName":null,"slugId":"82k9voim3cc9ecotv3j8ew"},{"id":"694348bf3a72b762f590f9a8","type":"document","title":"SOC 2 Type 2 Report","description":"The SOC 2 Report contains a type 2 certified audit of the Factory (system) that may be useful when assessing the risks arising from interactions with The San Francisco AI Factory Inc.’s system, particularly information about system controls that The San Francisco AI Factory Inc. has designed, implemented, and operated to provide reasonable assurance that its service commitments and system requirements were achieved based on the trust services criteria relevant to security (applicable trust services criteria) set forth in TSP section 100, 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (AICPA, Trust Services Criteria).","isPublic":false,"hasAccess":false,"isViewOnly":false,"url":null,"downloadUrl":null,"fileName":null,"slugId":"qvyfftcbs38sm8q4qoct3"},{"id":"6afeae74542c9e05e1c5abcb","type":"document","title":"SOC 2 Bridge Letter","description":"Management bridge letter from Factory's Head of Security, dated November 19, 2026. It covers September 30, 2025 through November 19, 2026: the period after our latest SOC 2 Type II report and before the next report (audit period October 1, 2025 to September 30, 2026) is issued. Please submit a request to view this document.","isPublic":false,"hasAccess":false,"isViewOnly":false,"url":null,"downloadUrl":null,"fileName":null,"slugId":"bn33xnteetkkrdeufjpumj"},{"id":"6aff800d00df2fd2098b9789","type":"document","title":"ISO 27001 Certificate","description":"ISO/IEC 27001 is the world's best-known standard for information security management systems (ISMS). It defines requirements an ISMS must meet.","isPublic":false,"hasAccess":false,"isViewOnly":false,"url":null,"downloadUrl":null,"fileName":null,"slugId":"q3gm5abcffepkhcno18b5e"},{"id":"6aff80a273b4fe6d9b478ebc","type":"document","title":"ISO 27001 First Surveillance Audit Report","description":"ISO/IEC 27001 is the world's best-known standard for information security management systems (ISMS). It defines requirements an ISMS must meet.","isPublic":false,"hasAccess":false,"isViewOnly":false,"url":null,"downloadUrl":null,"fileName":null,"slugId":"k5f73i3ldel9x91o6wmna"},{"id":"6aff80d221b49bcd6561b5ff","type":"document","title":"ISO 42001 Certificate","description":"ISO 42001 is the first international standard for Artificial Intelligence (AI) management systems, providing a framework for organizations to establish, implement, maintain, and continuously improve their AI management system.","isPublic":false,"hasAccess":false,"isViewOnly":false,"url":null,"downloadUrl":null,"fileName":null,"slugId":"vyp6hfnhzm6p2ff7iip47"},{"id":"6aff8108d29f2b188d5410de","type":"document","title":"ISO 42001 Second Surveillance Audit Report","description":"ISO 42001 is the first international standard for Artificial Intelligence (AI) management systems, providing a framework for organizations to establish, implement, maintain, and continuously improve their AI management system.","isPublic":false,"hasAccess":false,"isViewOnly":false,"url":null,"downloadUrl":null,"fileName":null,"slugId":"s2pkfvgv17fkx2qnazu2tl"}]},{"id":"6aeb8137aa435ada45490c6b","name":"FedRAMP 20X","items":[{"id":"6ae39847ce6dee2182e3b66e","type":"document","title":"FedRAMP 20X Milestones","description":"Goals and milestones for Factory for Government's progress toward FedRAMP Certification through FedRAMP 20x, updated at least quarterly. Please submit a request to view this document. For questions, please contact fedramp@factory.com.","isPublic":false,"hasAccess":false,"isViewOnly":true,"url":null,"downloadUrl":null,"fileName":null,"slugId":"2cchiilqysl6jk5p4vfj"},{"id":"6ae431eb56cc6f9f0502d270","type":"document","title":"FedRAMP Ongoing Certification Report","description":"Next Report Publication Date: February 11, 2027","isPublic":false,"hasAccess":false,"isViewOnly":false,"url":null,"downloadUrl":null,"fileName":null,"slugId":"r7401odzngv6iqvwvlk7je"},{"id":"6aeb812a885c806cc2f324d0","type":"link","title":"Marketplace Listing","description":"","isPublic":true,"hasAccess":true,"isViewOnly":false,"url":"https://www.fedramp.gov/marketplace/products/FR2703160255/","downloadUrl":null,"fileName":null,"slugId":"i2n4hn5ynst2xkroedk3g"},{"id":"6af28c95de8ba71742c5b5f3","type":"document","title":"FedRAMP Certification Package Overview","description":"FedRAMP 20x Class A Certification Package Overview for Factory for Government (FR2703160255), version 1.1, 9 November 2026. Please submit a request to view this document. For questions, please contact fedramp@factory.com.","isPublic":false,"hasAccess":false,"isViewOnly":false,"url":null,"downloadUrl":null,"fileName":null,"slugId":"hv52y3oxpaiahyowhgo4i"},{"id":"6affbe4e6802fc1e5fdf910d","type":"document","title":"Secure Implementation Guidelines","description":"Secure Implementation Guidelines for Factory for Government (FedRAMP 20x), version 1.0, November 18, 2026. Explains how agencies securely configure the service, including top-level administrator accounts, recommended settings, and settings reserved for administrators. For questions, please contact fedramp@factory.com.","isPublic":true,"hasAccess":true,"isViewOnly":false,"url":null,"downloadUrl":"https://trust.factory.com/doc/trust?rid=6affbe4e6802fc1e5fdf910d&r=wcfc937w4gljs8gn89q1s&download=true","fileName":"Factory-for-Government-Secure-Implementation-Guidelines-v1.0-2026-11-18.pdf","slugId":"pkiiwnefscfz1w28jfs97"}]}]},"controls":{"lastUpdated":"2026-11-22T14:28:57.424Z","categories":[{"id":"654d675021d787390bf77d75","name":"Infrastructure security","controls":[{"id":"access-datastores-ssh","name":"Unique production database authentication enforced","description":"The company requires authentication to production datastores to use authorized secure authentication mechanisms, such as unique SSH key.","status":"PASSING"},{"id":"unique-account-authentication-enforced","name":"Unique account authentication enforced","description":"The company requires authentication to systems and applications to use unique username and password or authorized Secure Socket Shell (SSH) keys.","status":"PASSING"},{"id":"access-database-restricted-users","name":"Production database access restricted","description":"The company restricts privileged access to databases to authorized users with a business need.","status":"PASSING"},{"id":"access-revoked-termination","name":"Access revoked upon termination","description":"The company completes termination checklists to ensure that access is revoked for terminated employees within SLAs.","status":"PASSING"},{"id":"access-ssh-required","name":"Unique network system authentication enforced","description":"The company requires authentication to the \"production network\" to use unique usernames and passwords or authorized Secure Socket Shell (SSH) keys.","status":"PASSING"},{"id":"remote-access-mfa-enforced","name":"Remote access MFA enforced","description":"The company's production systems can only be remotely accessed by authorized employees possessing a valid multi-factor authentication (MFA) method.","status":"PASSING"},{"id":"remote-access-vpn-enforced","name":"Remote access encrypted enforced","description":"The company's production systems can only be remotely accessed by authorized employees via an approved encrypted connection.","status":"PASSING"},{"id":"intrusion-detection-system","name":"Intrusion detection system utilized","description":"The company uses an intrusion detection system to provide continuous monitoring of the company's network and early detection of potential security breaches.","status":"PASSING"},{"id":"log-management-utilized","name":"Log management utilized","description":"The company utilizes a log management tool to identify events that may have a potential impact on the company's ability to achieve its security objectives.","status":"PASSING"},{"id":"infra-network-segregation","name":"Network segmentation implemented","description":"The company's network is segmented to prevent unauthorized access to customer data.","status":"PASSING"},{"id":"network-firewalls-reviewed","name":"Network firewalls reviewed","description":"The company reviews its firewall rulesets at least annually. Required changes are tracked to completion.","status":"PASSING"},{"id":"network-firewalls-utilized","name":"Network firewalls utilized","description":"The company uses firewalls and configures them to prevent unauthorized access.","status":"PASSING"},{"id":"system-network-hardening","name":"Network and system hardening standards maintained","description":"The company's network and system hardening standards are documented, based on industry best practices, and reviewed at least annually.","status":"PASSING"},{"id":"support-infra-patched","name":"Service infrastructure maintained","description":"The company has infrastructure supporting the service patched as a part of routine maintenance and as a result of identified vulnerabilities to help ensure that servers supporting the service are hardened against security threats.","status":"PASSING"}]},{"id":"654d675021d787390bf77d8b","name":"Organizational security","controls":[{"id":"asset-disposal-procedures-utilized","name":"Asset disposal procedures utilized","description":"The company has electronic media containing confidential information purged or destroyed in accordance with best practices, and certificates of destruction are issued for each device destroyed.","status":"PASSING"},{"id":"production-inventory-maintained","name":"Production inventory maintained","description":"The company maintains a formal inventory of production system assets.","status":"PASSING"},{"id":"assets-portable-media-encrypted","name":"Portable media encrypted","description":"The company encrypts portable and removable media devices when used.","status":"PASSING"},{"id":"assets-anti-malware","name":"Anti-malware technology utilized","description":"The company deploys anti-malware technology to environments commonly susceptible to malicious attacks and configures this to be updated routinely, logged, and installed on all relevant systems.","status":"PASSING"},{"id":"background-checks-performed","name":"Employee background checks performed","description":"The company performs background checks on new employees.","status":"PASSING"},{"id":"code-of-conduct-acknowledged-contractors","name":"Code of Conduct acknowledged by contractors","description":"The company requires contractor agreements to include a code of conduct or reference to the company code of conduct.","status":"PASSING"},{"id":"code-of-conduct-acknowledged-employees","name":"Code of Conduct acknowledged by employees and enforced","description":"The company requires employees to acknowledge a code of conduct at the time of hire. Employees who violate the code of conduct are subject to disciplinary actions in accordance with a disciplinary policy.","status":"PASSING"},{"id":"confidentiality-agreement-acknowledged-contractors","name":"Confidentiality Agreement acknowledged by contractors","description":"The company requires contractors to sign a confidentiality agreement at the time of engagement.","status":"PASSING"},{"id":"confidentiality-agreement-acknowledged-employees","name":"Confidentiality Agreement acknowledged by employees","description":"The company requires employees to sign a confidentiality agreement during onboarding.","status":"PASSING"},{"id":"performance-evaluations-conducted","name":"Performance evaluations conducted","description":"The company managers are required to complete performance evaluations for direct reports at least annually.","status":"PASSING"},{"id":"policies-password-complexity","name":"Password policy enforced","description":"The company requires passwords for in-scope system components to be configured according to the company's policy.","status":"PASSING"},{"id":"MDM-system-utilized","name":"MDM system utilized","description":"The company has a mobile device management (MDM) system in place to centrally manage mobile devices supporting the service.","status":"PASSING"},{"id":"access-physical-visitors","name":"Visitor procedures enforced","description":"The company requires visitors to sign-in, wear a visitor badge, and be escorted by an authorized employee when accessing the data center or secure areas.","status":"PASSING"},{"id":"security-awareness-training-completed","name":"Security awareness training implemented","description":"The company requires employees to complete security awareness training within thirty days of hire and at least annually thereafter.","status":"PASSING"}]},{"id":"654d675021d787390bf77d9a","name":"Product security","controls":[{"id":"data-encrypted","name":"Data encryption utilized","description":"The company's datastores housing sensitive customer data are encrypted at rest.","status":"PASSING"},{"id":"control-self-assessments-conducted","name":"Control self-assessments conducted","description":"The company performs control self-assessments at least annually to gain assurance that controls are in place and operating effectively. Corrective actions are taken based on relevant findings. If the company has committed to an SLA for a finding, the corrective action is completed within that SLA.","status":"PASSING"},{"id":"penetration-testing","name":"Penetration testing performed","description":"The company's penetration testing is performed at least annually. A remediation plan is developed and changes are implemented to remediate vulnerabilities in accordance with SLAs.","status":"PASSING"},{"id":"data-encrypted-in-transit","name":"Data transmission encrypted","description":"The company uses secure data transmission protocols to encrypt confidential and sensitive data when transmitted over public networks.","status":"PASSING"},{"id":"policies-incident-monitoring","name":"Vulnerability and system monitoring procedures established","description":"The company's formal policies outline the requirements for the following functions related to IT / Engineering: \n\n- vulnerability management;\n\n- system monitoring.","status":"PASSING"}]},{"id":"654d675021d787390bf77da0","name":"Internal security procedures","controls":[{"id":"continuity-and-disaster-recovery-plans-established","name":"Continuity and Disaster Recovery plans established","description":"The company has Business Continuity and Disaster Recovery Plans in place that outline communication plans in order to maintain information security continuity in the event of the unavailability of key personnel.","status":"PASSING"},{"id":"continuity-disaster-recovery-plans-tested","name":"Continuity and Disaster Recovery plans tested","description":"The company has a documented Business Continuity/Disaster Recovery (BC/DR) plan and tests it at least annually.","status":"PASSING"},{"id":"cybersecurity-insurance-maintained","name":"Cybersecurity insurance maintained","description":"The company maintains cybersecurity insurance to mitigate the financial impact of business disruptions.","status":"N/A"},{"id":"configuration-management-system-established","name":"Configuration management system established","description":"The company has a configuration management procedure in place to ensure that system configurations are deployed consistently throughout the environment.","status":"PASSING"},{"id":"system-description","name":"SOC 2 - System Description","description":"Complete a description of your system for Section III of the audit report","status":"PASSING"},{"id":"whistleblower-policy-established","name":"Whistleblower policy established","description":"The company has established a formalized whistleblower policy, and an anonymous communication channel is in place for users to report potential issues or fraud concerns.","status":"PASSING"},{"id":"board-of-directors-briefing","name":"Board oversight briefings conducted","description":"The company's board of directors or a relevant subcommittee is briefed by senior management at least annually on the state of the company's cybersecurity and privacy risk. The board provides feedback and direction to management as needed.","status":"PASSING"},{"id":"board-of-directors-charter","name":"Board charter documented","description":"The company's board of directors has a documented charter that outlines its oversight responsibilities for internal control.","status":"PASSING"},{"id":"board-of-directors-expertise","name":"Board expertise developed","description":"The company's board members have sufficient expertise to oversee management's ability to design, implement and operate information security controls. The board engages third-party information security experts and consultants as needed.","status":"PASSING"},{"id":"board-of-directors-meeting","name":"Board meetings conducted","description":"The company's board of directors meets at least annually and maintains formal meeting minutes. The board includes directors that are independent of the company.","status":"PASSING"},{"id":"data-backup-procedures","name":"Backup processes established","description":"The company's data backup policy documents requirements for backup and recovery of customer data.","status":"PASSING"},{"id":"external-service-impact-notifications","name":"System changes externally communicated","description":"The company notifies customers of critical system changes that may affect their processing.","status":"PASSING"},{"id":"management-roles-responsibilities-defined","name":"Management roles and responsibilities defined","description":"The company management has established defined roles and responsibilities to oversee the design and implementation of information security controls.","status":"PASSING"},{"id":"organization-structure-documented","name":"Organization structure documented","description":"The company maintains an organizational chart that describes the organizational structure and reporting lines.","status":"PASSING"},{"id":"role-responsibilities-specified","name":"Roles and responsibilities specified","description":"Roles and responsibilities for the design, development, implementation, operation, maintenance, and monitoring of information security controls are formally assigned in job descriptions and/or the Roles and Responsibilities policy.","status":"PASSING"},{"id":"support-system-available","name":"Support system available","description":"The company has an external-facing support system in place that allows users to report system information on failures, incidents, concerns, and other complaints to appropriate personnel.","status":"PASSING"},{"id":"system-changes-communicated","name":"System changes communicated","description":"The company communicates system changes to authorized internal users.","status":"PASSING"},{"id":"access-reviews","name":"Access reviews conducted","description":"The company conducts access reviews at least quarterly for the in-scope system components to help ensure that access is restricted appropriately. Required changes are tracked to completion.","status":"PASSING"},{"id":"incident-response-plan-tested","name":"Incident response plan tested","description":"The company tests their incident response plan at least annually.","status":"PASSING"},{"id":"incident-response-policies-established","name":"Incident response policies established","description":"The company has security and privacy incident response policies and procedures that are documented and communicated to authorized users.","status":"PASSING"},{"id":"policies-incident-management","name":"Incident management procedures followed","description":"The company's security and privacy incidents are logged, tracked, resolved, and communicated to affected or relevant parties by management according to the company's security incident response policy and procedures.","status":"PASSING"},{"id":"access-physical-datacenter","name":"Physical access processes established","description":"The company has processes in place for granting, changing, and terminating physical access to company data centers based on an authorization from control owners.","status":"PASSING"},{"id":"access-physical-review","name":"Data center access reviewed","description":"The company reviews access to the data centers at least annually.","status":"PASSING"},{"id":"commitments-externally-communicated","name":"Company commitments externally communicated","description":"The company's security commitments are communicated to customers in Master Service Agreements (MSA) or Terms of Service (TOS).","status":"PASSING"},{"id":"external-support-resources","name":"External support resources available","description":"The company provides guidelines and technical support resources relating to system operations to customers.","status":"PASSING"},{"id":"service-description-communicated","name":"Service description communicated","description":"The company provides a description of its products and services to internal and external users.","status":"PASSING"},{"id":"risk-assessment-objectives","name":"Risk assessment objectives specified","description":"The company specifies its objectives to enable the identification and assessment of risk related to the objectives.","status":"PASSING"},{"id":"risk-assessment-performed","name":"Risks assessments performed","description":"The company's risk assessments are performed at least annually. As part of this process, threats and changes (environmental, regulatory, and technological) to service commitments are identified and the risks are formally assessed. The risk assessment includes a consideration of the potential for fraud and how fraud may impact the achievement of objectives.","status":"PASSING"},{"id":"risk-assessment-program","name":"Risk management program established","description":"The company has a documented risk management program in place that includes guidance on the identification of potential threats, rating the significance of the risks associated with the identified threats, and mitigation strategies for those risks.","status":"PASSING"},{"id":"third-party-agreements","name":"Third-party agreements established","description":"The company has written agreements in place with vendors and related third-parties. These agreements include confidentiality and privacy commitments applicable to that entity.","status":"PASSING"},{"id":"vulnerability-scans-conducted","name":"Vulnerabilities scanned and remediated","description":"Host-based vulnerability scans are performed at least quarterly on all external-facing systems. Critical and high vulnerabilities are tracked to remediation.","status":"PASSING"}]},{"id":"654d675021d787390bf77dc6","name":"Data and privacy","controls":[{"id":"data-retention-procedures-established","name":"Data retention procedures established","description":"The company has formal retention and disposal procedures in place to guide the secure retention and disposal of company and customer data.","status":"PASSING"},{"id":"customer-data-deleted-upon-leave","name":"Customer data deleted upon leaving","description":"The company purges or removes customer data containing confidential information from the application environment, in accordance with best practices, when customers leave the service.","status":"PASSING"},{"id":"data-classification-policy","name":"Data classification policy established","description":"The company has a data classification policy in place to help ensure that confidential data is properly secured and restricted to authorized personnel.","status":"PASSING"}]}]},"updates":{"items":[{"id":"6ada654a329c9bfb45cab833","title":"New subprocessor: Sakana AI","description":"We are contracting with Sakana AI to provide AI model processing functions to our customers, starting on or after November 21, 2026.","category":"GENERAL","publishedAt":"2026-10-22T19:34:34.382Z"},{"id":"6acff64ce45b28170e7d1134","title":"New subprocessor: Meta","description":"We are contracting with Meta to provide AI model processing functions to our customers, starting on or after November 13, 2026.","category":"GENERAL","publishedAt":"2026-10-14T21:38:20.408Z"},{"id":"6ab1a6d18b3fdfc08bdb48d8","title":"New subprocessor: Databricks","description":"We have contracted with Databricks to provide AI model processing functions to our customers, and to store sensitive internal data, starting on or after October 21, 2026.","category":"GENERAL","publishedAt":"2026-09-21T21:51:13.619Z"},{"id":"6a68ede33eb5286e718f219a","title":"New subprocessor: Snowflake","description":"We have contracted with Snowflake to provide AI model processing functions to our customers, starting on or after August 27, 2026.","category":"GENERAL","publishedAt":"2026-07-28T17:58:59.001Z"},{"id":"6a67ed01e47969185ad55a5f","title":"New subprocessor: Mistral","description":"We have contracted with Mistral to provide AI model processing functions to our customers, starting on or after August 26, 2026.","category":"GENERAL","publishedAt":"2026-07-27T23:42:57.433Z"},{"id":"6a67ecf0b6cc9c8dc1f1f6e2","title":"New subprocessor: Together","description":"We have contracted with Together to provide AI model processing functions to our customers, starting on or after August 26, 2026.","category":"GENERAL","publishedAt":"2026-07-27T23:42:40.491Z"},{"id":"6a67ecdab6cc9c8dc1f1f5d4","title":"New subprocessor: Baseten","description":"We have contracted with Baseten to provide AI model processing functions to our customers, starting on or after August 26, 2026.","category":"GENERAL","publishedAt":"2026-07-27T23:42:18.012Z"},{"id":"6a67ecaf112efb734d45a89b","title":"New subprocessor: E2B","description":"We have contracted with E2B to provide cloud compute instances to our customers, starting on or after August 26, 2026.","category":"GENERAL","publishedAt":"2026-07-27T23:41:35.686Z"},{"id":"6a235e18259cb175ff666727","title":"New subprocessor: MongoDB","description":"We are contracting with MongoDB to store usage data.","category":"GENERAL","publishedAt":"2026-06-05T23:39:04.174Z"},{"id":"6a20b70bbe7f31b2391c3acc","title":"New subprocessor: Baseten","description":"We are contracting with Baseten to provide AI model processing functions to our customers.\n","category":"GENERAL","publishedAt":"2026-06-03T23:21:47.951Z"},{"id":"6a20b684f49bf29ece3ef2c2","title":"New subprocessor: Second Front","description":"We are contracting with Second Front to provide FedRamp hosting for government customers.","category":"GENERAL","publishedAt":"2026-06-03T23:19:32.992Z"},{"id":"69a9fbadc8febb7ec34e4aff","title":"New subprocessor: Fireworks","description":"We have contracted with Fireworks to provide AI model processing functions to our customers.","category":"GENERAL","publishedAt":"2026-03-05T21:54:53.449Z"},{"id":"69a774291cded24a7295c98b","title":"New subprocessor: Anthropic","description":"We have contracted with Anthropic to provide AI model processing functions to our customers.","category":"GENERAL","publishedAt":"2026-03-03T23:52:09.902Z"}]},"media":{"items":[]}}