Backfrom Groq’s own policies · verified 2026-09-02
Groq: data residency & retention
Headquarters
🇺🇸 United States (US)
Where inference runs
US, EU, Other
Groq discloses a global inference fleet — US, Helsinki Finland, Canada, and Dammam Saudi Arabia — but publishes no mapping of which site serves a given API request.
Region pinning
Enterprise plans only
Region-specific endpoints are enterprise-only; free/developer tiers use the global endpoint, and any retained data is stored in US-located GCP buckets regardless of compute location.
Prompt retention
Not retained
By default Groq does not retain customer data for inference requests, with a carve-out to temporarily log inputs/outputs for troubleshooting or abuse investigation, retained up to 30 days.
Trains on API data
No
The services agreement bars Groq from using inputs or outputs for training or fine-tuning any models unless explicitly permitted by the customer.
Zero data retention
Available
Self-serve ZDR toggle in Console Data Controls, which disables even the troubleshooting/abuse logging carve-out.
Compiled from Groq’s published privacy policy, terms, and documentation on 2026-09-02. “Not disclosed” means Groq publishes nothing on the point. Policies change without notice, so verify against the sources above before relying on this for compliance decisions.