Data Security

1. Our Approach

Before we build anything, we settle three questions with the client: where the data will live, who can reach it, and what the AI is allowed to see. The answers are written down so a client's IT lead, insurer and regulators can review them.

2. Architecture

• Dedicated and isolated. Each client gets a single-tenant SEALED deployment on its own virtual private server on Amazon Web Services, located in the client's jurisdiction. There are no shared databases and no data flow between clients.
• Self-hosted AI. We build the full stack on open-weight models and open-source software. Inference runs inside the client's dedicated environment. Client data is not sent to third-party model APIs.
• Source-grounded retrieval. SEALED retrieves from the client's own indexed material and is designed to tie each output back to its source.
• Minimal data footprint. HoomanKind does not retain clients' raw source data. Content ingested into the deployment lives in the client's environment, in its vector store and supporting databases (PostgreSQL).

3. Technical Controls

• Encryption of data in transit and at rest
• Role-based access control
• Ethical walls and data partitions for restricted or conflicted material
• Multi-factor authentication for administrative access
• Audit logging of user and AI actions
• Backups with tested restoration
• Vulnerability patching and updates for systems we manage

4. Operational Controls

• Confidentiality agreements (NDAs) for all HoomanKind staff and contractors with access to client environments
• A documented incident response process
• Breach notification: if we confirm an incident affecting a client's data, we notify the affected client within 96 hours of confirmation, or sooner where the contract or the law requires

5. Data Ownership and Exit

• Clients own their data. That includes the content they upload and the vector store built from it.
• 30-day portability window. When an engagement ends, the client has 30 days to port the vector store out of the deployment.
• Destruction. After the engagement ends, the rented infrastructure is shut down, our proprietary pipelines and frameworks are removed, and all databases, including PostgreSQL, are destroyed.
• No raw data kept. HoomanKind does not hold raw client data before, during, or after an engagement.

6. Shared Responsibility

Security is a joint effort. HoomanKind secures the environment we build and manage. Clients are responsible for who they authorize as users, how they manage their own credentials and devices, and what they choose to upload. For regulated data such as protected health information, terms are set in a written agreement, including a BAA where applicable, before any such data is loaded.

7. Certification Status

Our SOC 2 attestation and HIPAA compliance program are in progress. They are not complete, and we do not claim otherwise. See our Governance & Compliance page for current status.