Sattva

How Sattva works with your data

Sattva builds custom knowledge systems for nonprofits. This page explains who owns the system we build, where it runs, and what that means for your security and data governance reviews.

The short version

  1. You own your system. The system we build is yours: your data, your configuration, and any code written specifically for you. It stays yours should you choose to stop working with Sattva. The shared components underneath it are Sattva’s, licensed to you permanently (see point 4).
  2. By default, we host it for you. Each organization gets its own dedicated deployment with its own database. Your data is never stored alongside another organization’s. We run the infrastructure, including the service that connects and syncs your tools, so your team doesn’t have to. The third-party services involved are listed on our Trust page.
  3. Or it runs in your accounts. If your policies call for it, we deploy the system to accounts you control (your cloud, your data warehouse, your LLM provider) instead. In that model our engineers work inside your environment, on your systems, with credentials you issue and under your access policies, and you can revoke that access at any time.
  4. We keep the shared components. Sattva maintains a common library (integrations, schemas, workflows) used across every system we build. Those components are code, not data, and nothing in them is derived from your data. You receive a perpetual, royalty-free license to every component in your system. Our agreement with you names which categories count as shared components; everything outside them is yours.
  5. You can leave at any time. If we have been hosting your system, we move it to accounts you control or return your data, as you prefer. If you keep working with Sattva, we maintain your system under a maintenance agreement, which at minimum keeps the shared components current and can extend to building new custom capabilities.

What this means for your review

How to classify Sattva depends on which of the two you choose.

When we host your system, Sattva is a service provider that processes your data on your behalf: a software vendor in the usual sense. Our Trust page describes isolation, encryption, subprocessors and how the AI handles your data, and labels each commitment as active, planned, or available on request. We will sign a data protection addendum and complete your security questionnaire.

When it runs in your accounts, your data stays in your environment, and the relevant security certifications (SOC 2, encryption, access logging) are those of the platforms you already run on. In a vendor review we expect to be classified as professional services with system access, not as a hosted software vendor. We are happy to sign your standard contractor confidentiality and acceptable-use terms, and to complete a security questionnaire scoped to that role.

What we don’t do

Why we host by default

Most of the organizations we work with don’t have a team to run cloud infrastructure, and don’t want one. Hosting the system for them is the simpler start. The choice isn’t permanent: a system we host can move to your accounts later.

Questions

Ask us anything about this. Our goal is to align on security and data governance, and we are open to modifying our approach in order to meet your internal governance policies.