logo
Try Grella Free
Privacy Policy

Last updated April 10, 2026

How Grella handles legal data, AI processing, and service providers.

A clear privacy notice for law firms and legal teams using Grella to process sensitive documents, questions, and AI-generated work product.

Customer content stays customer content

Grella does not sell customer content, use it for advertising, or use it to train Grella-owned foundation models.

AI processing is disclosed

AI providers process document text and queries to provide Grella's AI features under business API no-training commitments.

Security claims stay specific

The policy describes encryption, Cloud KMS, selected logging, and optional advanced isolation without overstating the default setup.

AI processing, not AI training.

Grella cannot answer questions about documents without processing the relevant text. The important distinction is that operational AI processing is disclosed, while customer content is not used to train Grella-owned foundation models or build models for other customers.

Current disclosure

AI providers process your document text and queries to provide Grella's AI features. We use business API providers that state they do not train models on customer API data.

What happens

Relevant document text, extracted content, prompts, queries, and outputs may be processed by AI and document-processing providers to deliver Grella features.

What does not happen

Grella does not sell customer content, use it for advertising, or claim that AI providers never technically receive the data needed to answer a query.

Security posture

Standard controls are separated from advanced options.

The page avoids making optional enclave, TEE, or HSM configurations sound like the default Grella deployment.

Standard deployment

  • TLS encryption in transit
  • Encryption at rest
  • Google Cloud KMS key management
  • Organization-level access controls
  • Selected product and system logs
  • Business API AI providers

Advanced firm options

  • Enclave or TEE processing for scoped workloads
  • Dedicated isolated infrastructure discussions
  • Cloud HSM-backed keys where available
  • Expanded contractual or retention terms
  • Broader audit logging as the platform matures
  • Independent penetration testing as practical