GroqCloud

Inputs and outputs are not retained by default or used for training without permission; limited abuse and feature-specific retention exceptions remain.

Plan Scope

GroqCloud inference and related API features; offline negotiated terms may supersede the online agreement.

Prompt Retention

Inference inputs and outputs are not retained by default. Reliability or abuse logs may retain them up to 30 days; batch files are retained up to 30 days and fine-tuning data until deleted.

Response Retention

Same policy as prompts and feature state.

Ordinary Logging

Usage metadata is always retained and excludes customer inputs and outputs.

Model Training

Groq is not permitted to train or fine-tune models on inputs or outputs without explicit customer permission or instruction.

Product Improvement

Customer data use is limited to providing the service, customer instructions, law, reliable operation, and acceptable-use enforcement under the current agreement.

Human Or Operator Access

Access may occur as needed for reliable operation, abuse investigation, legal compliance, or customer-instructed features; zero-data-retention controls restrict reliability and abuse access.

Subprocessors And Routing

Groq affiliates, subprocessors, and contractors receive limited rights needed to deliver the service; third-party model terms may also apply.

Deletion Controls

All customers may enable zero data retention. The agreement calls for deletion of customer data within 30 days after termination, subject to documented or legal exceptions.

Caveat

Zero data retention disables features that require stored application state; regional and offline agreements may differ.