Your Data in GroqCloud

Understand how Groq uses customer data and the controls you have.

What Data Groq Retains

Groq handles two distinct types of information:

1. Usage Metadata (always retained)

   • We collect usage metadata for all users to measure service activity and system performance.
   • This metadata does not contain customer inputs or outputs.

2. Customer Data (retained only in limited circumstances)

   • By default, Groq does not retain customer data for inference requests.
   • Customer data (inputs, outputs, and related state) is only retained in two cases:
     1. If you use features that require data retention to function (e.g., batch jobs, fine-tuning and LoRAs).
     2. If needed to protect platform reliability (e.g., to troubleshoot system failures or investigate abuse).

You can control these settings yourself in the Data Controls settings.

When Customer Data May Be Retained

Review the Data Location section below to learn where data is retained.

1. Application State

Certain API features require data retention to function:

• Batch Processing (/openai/v1/batches): Input and output files retained for 30 days unless deleted earlier by the customer.
• Fine-tuning (/openai/v1/fine_tunings): Model weights and training datasets retained until deleted by the customer.

To prevent data retention for application state, you can disable these features for all users in your organization in Data Controls settings.

2. System Reliability and Abuse Monitoring

As noted above, inference requests are not retained by default. We may temporarily log inputs and outputs only when:

• Troubleshooting errors that degrade platform reliability, or
• Investigating suspected abuse (e.g. rate-limit circumvention).

These logs are retained for up to 30 days, unless legally required to retain longer. You may opt out of this storage in Data Controls settings, but you remain responsible for ensuring safe, compliant usage of the services in accordance with the terms and Acceptable Use & Responsible AI Policy.

Summary Table

Zero Data Retention

All customers may enable Zero Data Retention (ZDR) in Data Controls settings. When ZDR is enabled, Groq will not retain customer data for system reliability and abuse monitoring. As noted above, this also means that features that rely on data retention to function will be disabled. Organization admins can decide to enable ZDR globally or on a per-feature basis at any time on the Data Controls page in Data Controls settings.

Data Location

All customer data is retained in Google Cloud Platform (GCP) buckets located in the United States. Groq maintains strict access controls and security standards as detailed in the Groq Trust Center. Where applicable, Customers can rely on standard contractual clauses (SCCs) for transfers between third countries and the U.S.

Key Takeaways

• Usage metadata: always collected, never includes customer data.
• Customer data: not retained by default. Only retained if you opt into persistence features, or in cases for system reliability and abuse monitoring.
• Controls: You can manage data retention in Data Controls settings, including opting into Zero Data Retention.