Skip to main content
Every Impala deployment is single-tenant and logically isolated from other customers, so your data and operations remain separate and secure. That is true in both deployment shapes: an isolated deployment in Impala’s cloud, or Impala’s data plane inside your own AWS account and VPC, where your prompts, inputs and outputs never leave your account. Either way, prompts are not persisted and your data is never used for training — not for model training, not for fine-tuning, not for model improvement. What Impala keeps is the shape of the workload, not what’s in it: prompt lengths, concurrency, burstiness, cache reuse. That’s what Herd profiles to tune the execution plan. Impala is certified under SOC 2 Type II and security-tested on a regular cadence, including vulnerability assessments and penetration testing.

Impala Trust Center

SOC 2 Type II status, security controls, subprocessors and documents. Self-serve and current.
For anything specific to your environment, refer to the Trust Center or talk to your Impala contact.