CloudLast verified May 11, 2026

Groq Cloud data retention policy

Groq Cloud's Data Processing Addendum commits not to train on customer information and processes API data only to provide the service. Verified policy summary plus how to route Groq through Meetily as a BYOK summary provider.

Quick policy snapshot

Default retention: See vendor policy
Zero data retention available: Yes
Trains on API customer data by default: No

Groq's training default

Groq Cloud's Data Processing Addendum is explicit: training on customer information is prohibited. Groq is an inference provider, not a foundation-model developer, so the company does not have a research-data pipeline that would consume your prompts. Processing is limited to providing the cloud service and complying with legal requirements.

When Meetily users select a Groq-hosted model as their summary provider via BYOK, the request hits api.groq.com under your API key. The defaults on this page apply.

Retention

Groq's DPA commits to retaining data only for the period needed to provide the service, with a maximum 180-day deletion window after contract termination. The DPA defers active-service retention specifics to the Services Agreement; the current binding text lives at console.groq.com/docs/legal.

For abuse monitoring and operational telemetry, short-term retention is the practical default for any cloud inference provider. Review the current agreement before deployment in regulated environments.

Zero data retention

Contractual zero-retention or limited-retention terms are negotiable through Groq's enterprise sales process. The public DPA does not document a self-serve ZDR toggle.

How Meetily uses Groq

Meetily routes Groq traffic through your own API key. Your account's contract terms apply. The transcript text is sent over TLS to api.groq.com for summarization, and the response is returned to Meetily and stored locally on your device. Audio is never transmitted to Groq at any point.

Groq is a reasonable cloud-summary target for Meetily users who want a low-latency BYOK provider that does not train on their data. For zero retention by construction, switch to local Ollama and keep the entire pipeline on-device.

Last verified: May 11, 2026 . Policy source: Groq Cloud policy

Frequently asked questions

Does Groq train models on my API prompts?

No. Groq Cloud's Data Processing Addendum prohibits training on customer information. Processing is limited to providing cloud services and complying with legal requirements. Groq does not develop or train foundation models on customer prompts.

What is the default retention period for Groq API traffic?

Groq retains API data for the time period needed to provide the service, with a maximum 180-day deletion window after contract termination. The DPA defers the active-service retention window to the Services Agreement; review the current agreement at console.groq.com/docs/legal for the binding text.

Is zero data retention available for Groq?

Groq supports contractual zero-retention or limited-retention terms for enterprise customers. The public DPA does not detail self-serve ZDR; contact Groq directly to negotiate retention terms that match your data-handling requirements.

Where is Groq API data stored geographically?

Groq's DPA states data may be transferred and processed in the United States and other countries where Groq operates. Groq's primary infrastructure is US-based. Confirm current region options in the Trust Center at trust.groq.com.

How do I request deletion of data Groq has retained?

Submit a deletion request per the procedures in Groq's DPA. Upon termination of service, Groq's DPA commits to data deletion within 180 days unless legal obligations require longer retention.

Does Groq have SOC 2 or other compliance certifications?

Groq publishes its compliance posture on their Trust Center at trust.groq.com. SOC 2 Type 2 is the most relevant baseline for cloud LLM inference providers; check the current certifications list before regulated deployments.

How does Meetily handle Groq when I pick it as my summary provider?

Meetily transcription is always 100% local. When you select a Groq-hosted model as your summary provider via BYOK, Meetily routes transcript text (not audio) to api.groq.com using your own API key. The retention and training defaults on this page apply to your traffic.

Why is Groq popular for low-latency summarization?

Groq's LPU inference hardware delivers very low time-to-first-token on supported open-weight models (Llama, Mixtral, Gemma). For Meetily users who want a fast cloud summary path but still need an API that does not train on their data, Groq is a reasonable BYOK target. For zero retention by construction, switch to local Ollama instead.

Use Groq Cloud with Meetily, on your terms

Meetily transcription stays 100% local. For summaries, bring your own Groq Cloud key (BYOK) so the data path matches the policy you just read - or pick a local model if you want zero retention by construction.

Set up BYOK Download Meetily