Built for confidential work
Private credit work involves material non-public information. We are designing Arthen to keep your data private and under your control.
Arthen is early stage. This page describes how we are designing security and what we are building; items marked as planned are not yet available.
SOC 2 Type II and ISO/IEC 42001 certification are in progress. We do not hold either today.
- Zero retention
- Our design goal is that model providers process your requests without keeping them, and that your documents, financial statements and models are not used to train models. We will confirm the terms of each provider we use before we handle customer data.
- Dedicated VPC
- Planned: deployment inside your firm's own Virtual Private Cloud on AWS, Azure or GCP, so that files and indexes stay within your environment. We are scoping this with design partners.
- Encryption
- We are building Arthen to encrypt data at rest with AES-256 and in transit with TLS 1.2 or higher. On our roadmap: customer-managed encryption keys through AWS KMS or Azure Key Vault for enterprise deployments.
- Tenant isolation
- Our design goal is to keep each firm’s data separate, with independent encryption keys per fund and no co-mingling of data across tenants. Planned for the first customer deployments.
- Access controls
- We are building role-based permissions and information barriers (Chinese walls) so that only designated team members can reach specific files. On our roadmap, in step with our design partners.
- Audit logs
- We commit to building a log of AI answers, citations and calculations, with time, user and source document, so that your team can review how a result was produced. Planned.
Talk to us about security
Tell us what your security team needs to see. We are happy to talk it through, and to agree an NDA before you share anything confidential.