The DPA covers Groq processing Personal Data on the Customer's behalf; roles depend on applicable law
Depending on the applicable Data Protection Laws, the Customer is a Controller or a Processor and Groq is a Processor or sub-Processor for Groq's Processing of Personal Data to provide the Cloud Services. The DPA applies to Groq's Processing of Personal Data on the Customer's or a Customer Affiliate's behalf (as applicable) for providing the Cloud Services specified in the Services Agreement. The scope, nature, purposes and duration of the processing, the types of Personal Data and the Data Subjects are as described in the DPA, including its Schedule A (Details of Processing).
Supporting quotations
Depending on the applicable Data Protection Laws, Customer is a Controller or Processor and Groq is a Processor or sub-Processor with respect to Groq's Processing of Personal Data to provide the Cloud Services under the Agreement.
This DPA applies to Groq's Processing of Personal Data on Customer's or Customer Affiliate's behalf (as applicable) for the provision of the Cloud Services as specified in the Services Agreement.
The scope, nature, purposes, and duration of the processing, the types of Personal Data Processed, and the Data Subjects concerned are as described in this DPA, including its Schedule A (Details of Processing).
included within any Customer Data that is Processed by Groq in connection with providing the Cloud Services under the Services Agreement
Qualifications & exceptions
Which role each party has depends on the applicable Data Protection Laws.
The DPA applies to Processing done on the Customer's or Customer Affiliate's behalf for providing the Cloud Services, not to every Groq data use.
Not stated here
The document does not say which Customers are Controllers and which are Processors; it states only that this depends on applicable law.
Groq processes Personal Data only to provide the services, on documented instructions, or as the law requires
Groq commits to Process Personal Data only (a) to provide, maintain and support the Cloud Services and fulfill its obligations to the Customer under the Agreement, (b) on the Customer's behalf in compliance with the Customer's documented instructions, and (c) as required by Data Protection Laws. For a legally required use under (c), Groq will tell the Customer about the legal requirement before processing, unless the applicable law prohibits that notice.
Supporting quotations
Groq will Process Personal Data only: (a) to provide, maintain, and support the Cloud Services and fulfill its obligations to Customer under the Agreement; (b) on Customer's behalf in compliance with Customer's documented instructions; and (c) as required by Data Protection Laws (however, Groq will inform Customer of the legal requirement before processing for that purpose unless the applicable law prohibits such notice).
that apply to Groq’s Processing of Personal Data
Qualifications & exceptions
The notice before legally required processing is not given where applicable law prohibits it.
The list of permitted purposes is introduced by "only".
Not stated here
The document does not say how the Customer gives documented instructions or what form they take.
Groq will not sell or share Personal Data, use it for other purposes, or re-identify de-identified data
Groq will not "sell" or "share" Personal Data (as those terms are defined in Data Protection Laws), or otherwise Process Personal Data for any purpose other than the specific purposes described in the DPA or outside the direct business relationship with the Customer. Groq also will not attempt to re-identify de-identified data, except as permitted by Data Protection Laws.
Supporting quotations
Groq will not "sell" or "share" (as such terms are defined in Data Protection Laws) Personal Data, or otherwise Process Personal Data for any purpose: (x) other than for the specific purposes described in this DPA, or (y) outside of the direct business relationship with Customer.
Groq will not attempt to re-identify de-identified data except as permitted by Data Protection Laws.
Qualifications & exceptions
"Sell" and "share" take their meaning from Data Protection Laws.
The re-identification promise has an exception for what Data Protection Laws permit.
Not stated here
The document does not say whether Groq uses Personal Data to train or improve its own models; it states only the limits above and the purposes in Section 2.3.
Legal Rights & Agreement Rules · Restriction or exception
The Customer must give required notices, comply with its laws and hold the right to provide the data to Groq
The Customer will ensure that (a) all required notices have been given and authorizations obtained under Data Protection Laws for Groq (and its Affiliates and Subprocessors) to Process Personal Data as the Agreement contemplates, (b) it has complied and will keep complying with the Data Protection Laws that apply to it, and (c) it has and will keep the right to transfer or provide access to Personal Data to Groq for Processing under the Agreement.
Supporting quotations
Customer will ensure that: (a) all such notices have been given, and all such authorizations have been obtained, as required under Data Protection Laws, for Groq (and its Affiliates and Subprocessors) to Process Personal Data as contemplated by the Agreement
it has complied, and will continue to comply, with all Data Protection Laws applicable to it
it has, and will continue to have, the right to transfer, or provide access to, Personal Data to Groq for Processing in accordance with the terms of the Agreement
Qualifications & exceptions
The duties are the Customer's, not Groq's.
The notices and authorizations are those "required under Data Protection Laws".
Not stated here
The text says "all such notices" without an earlier phrase it refers back to; the document does not say which notices are meant beyond those required under Data Protection Laws.
Legal Rights & Agreement Rules · Company commitment
For Customers in Saudi Arabia, Groq will use commercially reasonable efforts so other laws do not block PDPL compliance
For Customers domiciled in the Kingdom of Saudi Arabia, to the extent Groq is also subject to Data Protection Laws in other jurisdictions, Groq will use commercially reasonable efforts to ensure that its compliance with those other laws does not prevent it from meeting its obligations under the PDPL in relation to its Processing of Customer Personal Data under the Agreement.
Supporting quotations
For Customers domiciled in the Kingdom of Saudi Arabia, to the extent Groq is also subject to Data Protection Laws in other jurisdictions, it will use commercially reasonable efforts to ensure that its compliance with such other Data Protection Laws do not prevent it from meeting its obligations under the PDPL
Qualifications & exceptions
Applies only to Customers domiciled in the Kingdom of Saudi Arabia.
The commitment is to commercially reasonable efforts, not a guaranteed result.
Applies to the extent Groq is also subject to Data Protection Laws in other jurisdictions.
Security & Safeguards · Company commitment
Groq will bind the people it authorizes to process Personal Data to confidentiality
Groq will ensure that its employees, contractors and any other persons it authorizes to Process Personal Data are subject to confidentiality obligations about that activity or are under an appropriate statutory obligation of confidentiality.
Supporting quotations
Ensure that the employees, contractors, and any other persons it authorizes to Process Personal Data are subject to confidentiality obligations regarding such activity or are under an appropriate statutory obligation of confidentiality.
Qualifications & exceptions
Covers employees, contractors and other persons Groq authorizes to Process Personal Data.
Legal Rights & Agreement Rules · Company commitment
Groq will promptly tell the Customer of complaints and government requests, and will challenge data demands where it can
Groq will promptly notify the Customer of any third-party or Data Subject complaints about the Processing of Personal Data and any government request for access to, or information about, Groq's Processing of Personal Data on the Customer's behalf, unless applicable laws prohibit this, and will give commercially reasonable cooperation and assistance on such a request. If Groq is prohibited by applicable laws from disclosing the details of a government request, it does not need the prior consent of the Customer or any Data Subject for mandatory disclosures of Personal Data under applicable laws, but it will use reasonably available legal mechanisms to challenge data access demands, and any attached non-disclosure provisions, through the applicable government process.
Supporting quotations
Promptly notify Customer of: (i) any third-party or Data Subject complaints regarding the Processing of Personal Data; or (ii) any government request for access to or information about Groq's Processing of Personal Data on Customer's behalf, unless prohibited by applicable laws.
Groq does not require the prior consent of the Customer or any Data Subject for mandatory disclosures of Personal Data under applicable laws, but Groq will use reasonably available legal mechanisms to challenge any demands for data access through the applicable government process that it receives, as well as any attached non-disclosure provisions.
Qualifications & exceptions
Notice is not given where applicable laws prohibit it.
Where disclosure is mandatory under applicable laws, Groq does not need the consent of the Customer or any Data Subject.
The commitment to challenge is limited to "reasonably available legal mechanisms".
Assistance is "commercially reasonable".
Not stated here
The document does not say what counts as a reasonably available legal mechanism or how often Groq challenges demands.
Legal Rights & Agreement Rules · Company commitment
Groq will give commercially reasonable help with impact assessments and regulator consultations
Groq will provide commercially reasonable assistance and cooperation to the Customer for the Customer's data protection impact assessment of actual or proposed Processing of Personal Data when Data Protection Laws require it, and for the Customer's consultation with regulatory authorities where Data Protection Laws require it. Groq will also comply with any obligation that applies to Groq under Data Protection Laws to consult a regulatory authority about its own Processing.
Supporting quotations
Provide commercially reasonable assistance to and cooperation with Customer for Customer's performance of a data protection impact assessment of Processing or proposed Processing of Personal Data, when required by Data Protection Laws.
Provide commercially reasonable assistance and cooperation to Customer for Customer's consultation with regulatory authorities in relation to the Processing or proposed Processing of Personal Data where required by Data Protection Laws
Qualifications & exceptions
Assistance is "commercially reasonable".
Applies only when required by Data Protection Laws.
Legal Rights & Agreement Rules · Company commitment
Groq commits to CCPA processor restrictions on combining data and to the same level of privacy protection
Groq will comply with the CCPA's restrictions on Processors about combining Personal Data with personal data received from, or on behalf of, another person or persons. It will also comply with the CCPA in its role as Processor, including by providing the same level of privacy protection the CCPA requires. Groq will promptly notify the Customer if it determines that it can no longer meet its obligations under the DPA or Data Protection Laws.
Supporting quotations
Comply with the CCPA's restrictions applicable to Processors regarding combining Personal Data with personal data received from, or on behalf of, another person or persons.
Comply with the CCPA in connection with its role as Processor, including by providing the same level of privacy protection as required by the CCPA.
Promptly notify Customer if it determines that it can no longer meet its obligations under this DPA or Data Protection Laws.
Qualifications & exceptions
The restrictions that apply are those the CCPA places on Processors.
The CCPA commitments apply to Groq in its role as Processor.
Not stated here
The document does not say what the Customer may do after Groq notifies it that it can no longer meet its obligations.
Use & Processing · Procedure
Groq sends data subject requests to the Customer and helps through a set process: the Customer tries self-service first
If Groq receives a direct request from a Data Subject about rights under Data Protection Laws, it will direct the Data Subject to the Customer to process the request. Groq will give commercially reasonable help to the Customer in meeting the Customer's duties to answer Data Subject requests, by following the process in Section 4.2. Under that process, when the Customer receives a request or inquiry about Personal Data that Groq Processes, the Customer will first use its Cloud Services containing Personal Data to address it itself and, only to the extent it cannot do so that way, contact Groq customer support for additional help.
Supporting quotations
If Groq receives a direct request from a Data Subject regarding rights under Data Protection Laws, Groq will direct the Data Subject to Customer for further processing of the request.
Groq will provide commercially reasonable assistance to Customer in fulfilling its obligations under Data Protection Laws to respond to Data Subject requests by following the process outlined in Section 4.2.
(a) first access its Cloud Services containing Personal Data to address the request or inquiry itself; and (b) to the extent Customer is not able to fulfill the request itself through such access, contact Groq customer support for additional assistance
means an identified or identifiable natural person about whom Personal Data relates
Qualifications & exceptions
The Customer must first try to address the request itself through its Cloud Services; Groq support is for what the Customer cannot do through that access.
Groq's help is "commercially reasonable".
Not stated here
The document does not say how quickly Groq responds to a support request or whether Groq itself ever answers a Data Subject.
Groq keeps appropriate security measures (Annex II) and may update them without lowering overall security
Groq will implement appropriate administrative, technical, physical and organizational measures designed to protect Personal Data, based on the type and sensitivity of the Personal Data Processed. The specific measures for the Cloud Services are described in Annex II of Schedule A. The Customer acknowledges that these measures are subject to technical progress and that Groq may update or modify them from time to time, provided the changes do not degrade the overall security of the Cloud Services the Customer purchased.
Supporting quotations
Groq will implement appropriate administrative, technical, physical, and organizational measures designed to protect Personal Data based on the type and sensitivity of the Personal Data Processed.
Details regarding the specific security measures that apply to the Cloud Services are as described in Annex II of Schedule A (Details of Processing) below.
Groq may update or modify these measures from time to time, provided that such updates and modifications do not result in the degradation of the overall security of the Cloud Services purchased by Customer.
Qualifications & exceptions
The measures are described as "designed to" protect Personal Data, which is not a guarantee of any outcome.
Groq may update the measures; the limit is that updates must not degrade the overall security of the Cloud Services purchased by the Customer.
The level of protection is based on the type and sensitivity of the Personal Data Processed.
Not stated here
The document does not say how the Customer is told when security measures are updated.
The Customer is responsible for its own access controls, feature configuration, and deletion and backup
The Customer is responsible for properly implementing access and use controls and for configuring the Cloud Services features it chooses to use, in line with the Agreement and in a way the Customer deems adequate. This expressly includes maintaining appropriate security, protection, deletion and backup of its own Personal Data.
Supporting quotations
Customer will be responsible for properly implementing access and use controls and configuring certain features and functionalities of the Cloud Services that Customer may elect to use
including, without limitation, maintaining appropriate security, protection, deletion, and backup of its own Personal Data
Qualifications & exceptions
The duty covers features the Customer elects to use.
Adequacy is measured by what "Customer deems adequate", while staying in accordance with the Agreement.
Not stated here
The document does not say what happens if the Customer's configuration is inadequate.
Security & Safeguards · Company commitment
Groq will notify the Customer of a Data Breach without undue delay and within 72 hours after becoming aware
Groq will notify the Customer without undue delay, and in any event within 72 hours after becoming aware of a Data Breach, and will assist the Customer with its breach notification obligations under Data Protection Laws. That assistance includes taking commercially reasonable steps to mitigate the effects and reduce the risk to affected Data Subjects, and giving the Customer, to the extent known, the nature of the Data Breach (including how it occurred, the categories and approximate number of Data Subjects and records concerned), its likely consequences, and the measures Groq has taken or proposes to take.
Supporting quotations
Groq will notify Customer without undue delay, but in any event within 72 hours after becoming aware of any Data Breach and will assist Customer in Customer's compliance with its Data Breach notification-related obligations under Data Protection Laws
Taking commercially reasonable steps to mitigate the effects of the Data Breach and reduce the risk to Data Subjects whose Personal Data was involved
Providing Customer with the following information, to the extent known:
The nature of the Data Breach, including, where possible, how the Data Breach occurred, the potential categories and approximate number of Data Subjects concerned, and the categories and approximate number of Personal Data records concerned;
The likely consequences of the Data Breach; and
Measures taken or proposed to be taken by Groq to address the Data Breach
a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data
Qualifications & exceptions
The 72 hours run from when Groq becomes aware of the Data Breach, not from when it occurred.
The information listed is given only "to the extent known".
The mitigation duty is limited to commercially reasonable steps.
A Data Breach means a breach of security affecting Personal Data as defined in the DPA.
Not stated here
The document does not say how Groq delivers the notice or to whom at the Customer.
Legal Rights & Agreement Rules · Restriction or exception
Reporting a breach is not an admission of fault, and the Customer alone decides whom to notify
Groq's obligation to report a Data Breach is not, and will not be construed as, an acknowledgement of fault or liability by Groq. The Customer is solely responsible for deciding whether to notify affected Data Subjects and for giving that notice, and for deciding whether supervisory authorities must be notified, as its own business and compliance needs require.
Supporting quotations
Groq's obligation to report a Data Breach under this DPA is not and will not be construed as an acknowledgement by Groq of any fault or liability of Groq with respect to such Data Breach.
Customer is solely responsible for determining whether to notify impacted Data Subjects and for providing such notice, and for determining whether relevant supervisory authorities need to be notified of a Data Breach
Qualifications & exceptions
Applies to breach reports made under this DPA.
Not stated here
The document does not say whether Groq will itself notify any Data Subject or authority.
Use & Processing · Permission or license
The Customer gives general authorization for Groq to use Subprocessors, and Groq stays liable for them
The Customer provides general authorization for Groq to use Subprocessors to Process Personal Data in line with the DPA and Data Protection Laws. Where Groq subcontracts any of its rights or obligations concerning Personal Data, Groq remains liable for performing all its obligations under the DPA, whether they are performed by Groq, its Affiliates or its Subprocessors.
Supporting quotations
Customer provides general authorization for Groq to use Subprocessors to Process Personal Data in accordance with the provisions within this DPA and Data Protection Laws.
Groq will remain liable for the performance of all its obligations under this DPA, whether or not performed by Groq, its Affiliates or Subprocessors.
means any third party that Groq engages to Process Personal Data in connection with providing the Cloud Services
Qualifications & exceptions
Use of Subprocessors must be in accordance with the provisions in the DPA and Data Protection Laws.
The liability statement is limited to Groq's obligations under this DPA.
Groq publishes a Subprocessor List, gives 15 days' notice of changes to subscribers, and handles objections
Groq's Subprocessor List is at the stated web address and Groq will keep it up to date. If the Customer subscribes to email notifications on that website, Groq will notify the Customer of intended changes to the list at least 15 days before they take effect, by email, a posting on the website, notification in Console or other reasonable means. The Customer may object in writing to a new Subprocessor within 15 days of the notice, on reasonable grounds relating to data protection. Groq will then use commercially reasonable efforts to offer a change in the Cloud Services, or recommend a commercially reasonable change to the Customer's use, that avoids Processing by the objected-to Subprocessor without a material change to the Customer's use of the affected Cloud Services. If Groq cannot provide such a change, the Customer may, in its sole discretion, suspend or terminate the affected Cloud Services.
Supporting quotations
Groq will maintain an up-to-date Subprocessor List.
If Customer subscribes to email notifications as provided on the Subprocessor List website, then Groq will notify Customer of any changes Groq intends to make to the Subprocessor List at least 15 days before the changes take effect, which may be via email, a posting on the Subprocessor List website, or notification in Console or other reasonable means.
Customer may object in writing to the appointment of a new Subprocessor within 15 days of such notice, provided that such objection is based on reasonable grounds relating to data protection.
Customer may, in its sole discretion, suspend or terminate the affected Cloud Services in the event that Groq is not able to provide a commercially reasonable change to cure Customer's Subprocessor objection.
Qualifications & exceptions
The 15 days' advance notice is promised only if the Customer subscribes to email notifications.
Notice may be given by email, a posting on the Subprocessor List website, Console notification or other reasonable means.
An objection must be in writing, made within 15 days of the notice, and based on reasonable grounds relating to data protection.
Groq's duty is commercially reasonable efforts to offer a workaround; the Customer's remedy if none exists is to suspend or terminate the affected Cloud Services.
Not stated here
The document does not say whether the Customer receives a refund or other consequences when it suspends or terminates after an objection; that depends on the Services Agreement, which is not part of this document.
The Subprocessor List itself is not part of this document.
Groq may transfer and process Personal Data in the US and other countries, with a lawful mechanism for onward transfers
Groq may transfer and Process Personal Data to and in the United States and other countries where Groq or its Subprocessors maintain Processing operations. When Groq makes an onward transfer of Personal Data, it will ensure that a lawful data transfer mechanism is in place before transferring the data from one country to another.
Supporting quotations
Groq may transfer and Process Personal Data to and in the United States and other countries where Groq or its Subprocessors maintain Processing operations.
Where Groq engages in an onward transfer of Personal Data, Groq will ensure that a lawful data transfer mechanism is in place prior to transferring Personal Data from one country to another.
Qualifications & exceptions
Transfers may go to countries where Groq or its Subprocessors maintain Processing operations.
The lawful transfer mechanism commitment applies to onward transfers from one country to another.
Not stated here
The document does not list the countries where Groq or its Subprocessors process data; the Subprocessor List it points to is not part of this document.
Legal Rights & Agreement Rules · Context
The EU SCCs are deemed signed when the Customer enters the Agreement, using Module 2 or Module 3
To the extent legally required, by entering into the Agreement the Customer and Groq are deemed to have signed the EU SCCs, which form part of the DPA and are completed as Sections 8.2.a to 8.2.j state. Module 2 applies to transfers from the Customer as a Controller to Groq as a Processor, and Module 3 applies to transfers from the Customer as a Processor to Groq as a sub-Processor.
Supporting quotations
To the extent legally required, by entering into the Agreement, Customer and Groq are deemed to have signed the EU SCCs, which form part of this DPA and will be deemed completed as follows:
Module 2 of the EU SCCs applies to transfers of Personal Data from Customer (as a Controller) to Groq (as a Processor) and Module 3 applies to transfers of Personal Data from Customer (as a Processor) to Groq (as a sub-Processor)
completed as specified in Section 8 (International Data Transfers) below
Qualifications & exceptions
The deemed signature applies only "to the extent legally required".
Which module applies depends on whether the Customer is a Controller (Module 2) or a Processor (Module 3).
Not stated here
The text of the EU SCCs is not reproduced in this document.
EU SCC choices: no docking clause, general authorization for Subprocessors, Irish law and Irish courts
The DPA fixes these EU SCC options: the optional docking clause (Clause 7) does not apply; for Subprocessors (Clause 9) the parties select Option 2, general written authorization; the optional redress language in Clause 11 is not included; for governing law (Clause 17) the parties choose Option 1, the law of an EU Member State that allows third-party beneficiary rights, and select the laws of Ireland; and for forum (Clause 18) the parties select the courts of Ireland.
Supporting quotations
Clause 7 (the optional docking clause) does not apply
Under Clause 9 (Use of Subprocessors), the Parties select Option 2 (General written authorization)
Under Clause 11 (Redress), the optional language will not be deemed to be included
Under Clause 17 (Governing law), the Parties choose Option 1 (the law of an EU Member State that allows for third-Party beneficiary rights). The Parties select the laws of Ireland
Under Clause 18 (Choice of forum and jurisdiction), the Parties select the courts of Ireland
Customer provides general authorization for Groq to use Subprocessors
Qualifications & exceptions
These selections apply to the EU SCCs, which are deemed signed only to the extent legally required.
Not stated here
This document does not say how Irish law or Irish courts interact with the governing law and forum terms of the Services Agreement, which is not part of this document.
The EU SCC annexes are completed through Schedule A, the Irish supervisory authority and the Subprocessor website
Annex I(A) and I(B) of the EU SCCs (List of Parties) are completed as described in Schedule A. For Annex I(C), the parties follow the rules for identifying the competent supervisory authority under Clause 13 and, to the extent legally permissible, select the Irish Data Protection Commission. Annex II (technical and organizational measures) is completed as provided in Annex II of Schedule A, and Annex III (List of Subprocessors) is completed by the information on Groq's Subprocessor website.
Supporting quotations
Annex I(A) and I(B) (List of Parties) is completed as described in Schedule A
the Parties will follow the rules for identifying such authority under Clause 13 and, to the extent legally permissible, select the Irish Data Protection Commission
Annex II (Technical and organizational measures) is completed as provided in Annex II of Schedule A
Annex III (List of Subprocessors) is completed by the information available at
Qualifications & exceptions
The Irish Data Protection Commission is selected only "to the extent legally permissible"; otherwise the Clause 13 rules identify the authority.
Not stated here
Annex I(C) in Schedule A names the "Irish Data Protection Commissioner" and says it applies "where possible"; this document does not explain whether that differs from the Irish Data Protection Commission named here.
The Subprocessor website content is not part of this document.
For UK GDPR transfers, the UK Transfer Addendum forms part of the DPA and takes precedence as its terms say
For transfers of Personal Data subject to the UK GDPR, the UK International Data Transfer Addendum to the EU SCCs (the "UK SCCs") forms part of the DPA and takes precedence over the rest of the DPA as set out in the UK SCCs. It is completed as follows: the parties' details are the parties and their affiliates to the extent involved in the transfer; the Key Contacts are the contacts specified in the Services Agreement; the Approved EU SCCs in Table 2 are the EU SCCs as executed by the parties; either party may end the DPA as set out in Section 19 of the UK SCCs; and by entering into the Agreement the parties are deemed to be signing the UK SCCs.
Supporting quotations
For transfers of Personal Data subject to the UK GDPR, the International Data Transfer Addendum to the EU SCCs
forms part of this DPA and takes precedence over the rest of this DPA as set forth in the UK SCCs
(d) either Party may end this DPA as set out in Section 19 of the UK SCCs; and (e) by entering into the Agreement, the Parties are deemed to be signing the UK SCCs.
Qualifications & exceptions
Applies only to transfers subject to the UK GDPR.
The UK SCCs take precedence over the rest of the DPA as set forth in the UK SCCs.
The version referred to is the one available as of the Effective Date.
Not stated here
The text of the UK SCCs and of Section 19 is not reproduced in this document, so the grounds on which a party may end the DPA are not described here.
Legal Rights & Agreement Rules · Context
For Swiss FADP transfers, the EU SCCs apply with Swiss adjustments and a Swiss supervisory authority
For transfers subject to the Swiss FADP, the EU SCCs form part of the DPA as Section 8.2 states, with these differences to the extent the FADP requires: references to the GDPR are read as references to the FADP where the transfers are subject exclusively to the FADP and not the GDPR; the term "Member State" is not read so as to stop Data Subjects in Switzerland from suing for their rights in their place of habitual residence under Clause 18(c); and the relevant supervisory authority is the Swiss Federal Data Protection and Information Commissioner (for transfers subject to the FADP and not the GDPR), or both that Commissioner and the supervisory authority identified in the EU SCCs where the FADP and the GDPR each apply.
Supporting quotations
For transfers of Personal Data that are subject to the FADP, the EU SCCs form part of this DPA as stated in Section 8.2 of this DPA, but with the following differences, to the extent required by the FADP
the term "Member State" in EU SCCs will not be interpreted in such a way as to exclude Data Subjects in Switzerland from the possibility of suing for their rights in their place of habitual residence (Switzerland) in accordance with Clause 18(c) of the EU SCCs
the relevant supervisory authority is the Swiss Federal Data Protection and Information Commissioner (for transfers subject to the FADP and not the GDPR), or both such Commissioner and the supervisory authority identified in the EU SCCs (where the FADP and GDPR apply, respectively)
Qualifications & exceptions
The differences apply only "to the extent required by the FADP".
The FADP-only references apply only where transfers are subject exclusively to the FADP and not to the GDPR.
Legal Rights & Agreement Rules · Company commitment
For Saudi PDPL transfers, Groq follows the KSA C2P Clauses importer duties and the Customer must meet exporter duties
For transfers subject to the PDPL, Groq will comply with the data importer's obligations in the KSA C2P Clauses, which are incorporated into and form part of the DPA. The party details for Appendix 1 are in the Order Form, with the data exporter a controller and the data importer a processor; the processing details for Appendix 2 are in Annex I of the DPA; and the security measures for Appendix 3 are in Annex II. The Customer will take all actions necessary to comply with its PDPL obligations as a data exporter, including where applicable satisfying a permitted purpose and the conditions prescribed under law, conducting a transfer risk assessment, and putting in place appropriate measures to mitigate the risks it identifies.
Supporting quotations
Groq will comply with the data importer's obligations set out in the KSA C2P Clauses, which are incorporated into and form part of this DPA
the details of the parties are set out in the Order Form; the data exporter is a controller and the data importer is a processor
Customer will take all actions necessary to comply with its obligations under PDPL as a data exporter, including, where applicable, satisfying a permitted purpose and conditions prescribed under law, conducting a transfer risk assessment, and putting in place appropriate measures to mitigate the risks identified during the course of any such assessment.
specifically including the Second Template (Controller to Processor), as amended, updated or replaced from time to time
Qualifications & exceptions
Applies only to transfers subject to the PDPL.
The Customer's listed steps apply "where applicable".
Not stated here
The Order Form is not part of this document, so the party details for Appendix 1 are not described here.
The text says Annex I (Details of Processing) of this DPA; in this document those details appear in Annex I of Schedule A, and this document does not explain the difference in wording.
Legal Rights & Agreement Rules · User right or choice
Groq gives compliance information such as SOC 2 reports; the Customer may request an audit only in set circumstances
To the extent Data Protection Laws require it, Groq will make available information reasonably necessary to confirm its compliance with the DPA, for example SOC 2 or similar audit reports by a qualified third-party auditor (an "Audit Report"). Except as the Services Agreement provides otherwise about audits, if the Customer has a reasonable basis to conclude an Audit Report is not sufficient to confirm compliance, the Customer may request an audit of the Groq systems and records relevant to Groq's Processing of Personal Data on the Customer's behalf. The audit is at the Customer's sole expense, on 30 days' prior written notice, on a mutually agreed date and time, and during normal business hours. The Customer limits audits to no more than once in any 12 calendar months, except that after a Data Breach it may exercise its audit right even if an audit was done in the prior 12 months.
Supporting quotations
To the extent required by Data Protection Laws, Groq will make available such information reasonably necessary to confirm Groq’s compliance with this DPA (e.g., SOC 2 or similar audit reports issued by a qualified third-party auditor, “Audit Report”).
Except as provided otherwise in the Services Agreement regarding audits, if Customer has a reasonable basis to conclude that an Audit Report provided by Groq is not sufficient to confirm such compliance, Customer may, at Customer’s sole expense, upon 30 days’ prior written notice and subject to a mutually agreed upon date and time, request an audit during normal business hours of those Groq systems and records relevant to Groq’s Processing of Personal Data on Customer’s behalf.
Customer will limit its exercise of audit rights to not more than once in any 12 calendar month period, except in the event of a Data Breach, following which Customer may exercise its audit right even if one has already been performed in the prior 12-month period.
Qualifications & exceptions
Groq's duty to provide compliance information applies "to the extent required by Data Protection Laws".
An audit may be requested only if the Customer has a reasonable basis to conclude the Audit Report is not sufficient.
The Customer pays for the audit, gives 30 days' written notice, and the date and time must be mutually agreed.
Limited to once per 12 calendar months, except following a Data Breach.
The provision yields to anything the Services Agreement provides otherwise about audits.
Not stated here
The document does not say what the Services Agreement provides about audits, because that agreement is not part of this document.
The document does not say whether Groq may refuse or reschedule a requested audit beyond the requirement of a mutually agreed date.
Legal Rights & Agreement Rules · Restriction or exception
Audit reports and audit results are Groq's Confidential Information
Any Audit Report or other results of audits undertaken in connection with the DPA are deemed the Confidential Information of Groq.
Supporting quotations
Any Audit Report or other results of audits undertaken in connection with this DPA will be deemed the Confidential Information of Groq.
Qualifications & exceptions
Applies to Audit Reports and other results of audits undertaken in connection with the DPA.
Not stated here
The Confidential Information terms of the Services Agreement are not part of this document, so what use or disclosure of the results is permitted is not described here.
On request, Groq deletes Personal Data within a maximum of 180 days, except legal retention and backups
Before or at termination of the Services Agreement, the Customer may ask Groq to delete all Personal Data in its possession or control, as soon as reasonably practicable and within a maximum period of 180 days. The requirement does not apply to the extent Groq is required by applicable law to retain some or all of the Personal Data, or to Personal Data archived on back-up systems; Groq will securely isolate and protect that data from any further processing, except as applicable law requires.
Supporting quotations
Prior to termination or at termination of the Services Agreement, Customer may request Groq to promptly delete all Personal Data in its possession or control as soon as reasonably practicable and within a maximum period of 180 days
except that this requirement will not apply to the extent that Groq is required by applicable law to retain some or all of the Personal Data, or to Personal Data it has archived on back-up systems, which Personal Data Groq will securely isolate and protect from any further processing, except to the extent required by applicable law
10. Destruction Or Retrieval Of Personal Data
Qualifications & exceptions
Deletion happens only if the Customer requests it, before or at termination of the Services Agreement.
Not required for Personal Data Groq must keep by law or Personal Data archived on back-up systems.
Isolated back-up data is protected from further processing except as applicable law requires.
Not stated here
The text does not say whether the 180-day maximum runs from the request or from termination.
The heading mentions retrieval, but the text describes only deletion; this document does not describe a process for the Customer to retrieve its Personal Data.
No deadline is stated for removing Personal Data held on back-up systems.
Legal Rights & Agreement Rules · Permission or license
Groq may modify the DPA as needed to comply with data protection law, if that does not degrade services or safeguards
Despite anything to the contrary in the Services Agreement, Groq reserves the right to make any modification to the DPA that is required to comply with Data Protection Law, so long as the modification does not degrade any service functionalities or safeguards associated with providing the Cloud Services.
Supporting quotations
Notwithstanding anything else to the contrary in the Services Agreement, Groq reserves the right to make any modification to this DPA as may be required to comply with Data Protection Law so long as any such modification will not degrade any service functionalities or safeguards associated with providing the Cloud Services.
Qualifications & exceptions
Limited to modifications required to comply with Data Protection Law.
A modification may not degrade service functionalities or safeguards for providing the Cloud Services.
Not stated here
The document does not say how or when the Customer is told of a modification, or whether the Customer may object.
The text uses "Data Protection Law" (singular), while the defined term is "Data Protection Laws"; the document does not comment on the difference.
Legal Rights & Agreement Rules · Restriction or exception
DPA claims follow the Services Agreement's limits; the DPA lasts as long as the Services Agreement or the processing
Any claims brought under the DPA are subject to the terms and conditions of the Services Agreement, including its exclusions and limitations. The DPA remains in force through the term of the Services Agreement, or for as long as Groq is Processing Personal Data subject to the DPA, whichever is longer.
Supporting quotations
Any claims brought under this DPA will be subject to the terms and conditions, including, but not limited to, the exclusions and limitations specified in the Services Agreement.
This DPA will remain in force and effect through the term of the Services Agreement, or for as long as Groq is Processing Personal Data subject to this DPA, whichever is longer.
Qualifications & exceptions
Claims are subject to the Services Agreement's exclusions and limitations.
The term runs for the longer of the Services Agreement term and the period of Groq's Processing of Personal Data subject to the DPA.
Not stated here
The exclusions and limitations in the Services Agreement are not part of this document, so any liability cap or exclusion that applies to DPA claims is not described here.
Legal Rights & Agreement Rules · Context
Annex I: Customer is exporter (Controller), Groq is importer (Processor); electronic acceptance is the signature
Schedule A, Annex I(A) lists the data exporter as the Customer, described as the Controller, whose contact details are as provided in the Services Agreement. The data importer is the Groq Contracting Party specified in the Services Agreement, described as the Processor. The Customer's electronic acceptance of the Services Agreement constitutes the Customer's signature to the DPA.
Supporting quotations
Schedule A – Details of Processing
The exporter (Controller) is Customer and Customer’s contact details are as provided in the Services Agreement. Customer’s electronic acceptance of the Services Agreement constitutes Customer’s signature to the DPA.
The importer (Processor) is the Groq Contracting Party specified in the Services Agreement.
Qualifications & exceptions
The exporter is described as a Controller in Annex I, while Section 2.1 says the Customer is a Controller or Processor depending on applicable law and Section 8.2.a covers a Customer acting as a Processor.
Not stated here
The document does not explain how Annex I's description of the Customer as the Controller relates to Section 2.1 and Section 8.2.a, which also contemplate a Customer acting as a Processor.
The Groq Contracting Party is not named in this document.
Annex I: covered data is any Personal Data in Customer Data, including inputs, outputs and sensitive data
Annex I(B) lists the data subjects as any data subjects whose Personal Data is contained in the data exporter's data being processed by the Cloud Services, including the Customer's Authorized Users. The categories of Personal Data are any Personal Data incorporated within Customer Data (as determined by the Customer), including data the Customer inputs when it uses the Cloud Services and any Personal Data in the generated output (Input and Output as defined in the Services Agreement). Any Personal Data may include sensitive or special categories of personal data as incorporated within Customer Data (as determined by the Customer), and the restrictions and safeguards specified in Annex II apply to those categories (if any).
Supporting quotations
Any data subjects whose Personal Data is contained in Data Exporter’s data being processed by the Cloud Services, as set out in the Services Agreement which describes the provision of Cloud Services to Customer, including Customer’s Authorized Users.
Any Personal Data incorporated within Customer Data (as determined by Customer), including such data inputted by Customer when it uses the Cloud Services, and any Personal Data in the generated output (Input and Output as defined in the Services Agreement).
Any Personal Data may include sensitive personal data or special categories of personal data (as defined under applicable Data Protection Laws) as incorporated within Customer Data (as determined by Customer). The restrictions and safeguards specified in Annex II apply to these categories of Personal Data (if any).
means an identified or identifiable natural person about whom Personal Data relates
included within any Customer Data that is Processed by Groq in connection with providing the Cloud Services under the Services Agreement
Qualifications & exceptions
The categories are "as determined by Customer", so Annex I does not itself limit what kinds of Personal Data the Customer may include.
Sensitive data is covered only if the Customer's data includes it; the Annex II safeguards apply "if any".
Not stated here
Input and Output are defined in the Services Agreement, which is not part of this document.
Annex II as supplied lists general security measures and does not separately name additional safeguards for sensitive categories of data.
Annex I: transfers are continuous, to provide the Cloud Services; the nature of processing is in the Services Agreement
Annex I(B) says the data is transferred on a continuous basis as needed to provide the Cloud Services for the term of the Services Agreement. The nature of the Processing is set out in the Services Agreement. The purpose of the data transfer is for Groq to provide the Cloud Services to the Customer under and in accordance with the Agreement.
Supporting quotations
On a continuous basis as needed to provide the Cloud Services to Customer for the term of the Services Agreement.
The nature of the Processing is set out in the Services Agreement.
The purposes of the data transfer are for Groq to provide the Cloud Services to Customer under and in accordance with the Agreement.
Groq will Process Personal Data only: (a) to provide, maintain, and support the Cloud Services and fulfill its obligations to Customer under the Agreement
Qualifications & exceptions
The purpose statement is tied to providing the Cloud Services under the Agreement; Section 2.3 separately limits the purposes for which Groq may Process Personal Data.
Not stated here
The nature of the Processing is not described in this document; it points to the Services Agreement, which is not supplied.
Annex I: data is retained as long as needed for the processing purposes, unless the law requires otherwise
Annex I(B) states that the data will be retained for the time period needed to accomplish the purposes of Processing, unless otherwise required by applicable law. Section 10 separately lets the Customer ask Groq to delete the Personal Data, within a maximum of 180 days, subject to legal retention and back-up exceptions.
Supporting quotations
The data will be retained for the time period needed to accomplish the purposes of Processing, unless otherwise required by applicable law.
Prior to termination or at termination of the Services Agreement, Customer may request Groq to promptly delete all Personal Data
Qualifications & exceptions
Retention is for the time needed to accomplish the purposes of Processing, unless applicable law requires otherwise.
Not stated here
The document does not give a number of days or years for the retention period beyond "the time period needed to accomplish the purposes of Processing".
This document does not say how long data is kept if the Customer makes no deletion request.
Annex I: transfers to Subprocessors last for the duration of the Agreement; the Subprocessor website lists them
For transfers to sub-processors, Annex I refers to the Subprocessor website for a list of Groq's Subprocessors and the nature of the services they provide, and states that all transfers will last for the duration of the Agreement between the parties.
Supporting quotations
for a list of Groq’s Subprocessors and the nature of the services they provide. All transfers will last for the duration of the Agreement between the Parties.
Groq's Subprocessor list is available at
Qualifications & exceptions
The duration is stated as the duration of the Agreement between the parties.
Not stated here
The Subprocessors and the services they provide are not listed in this document.
Annex I: the competent supervisory authority follows Data Protection Law and, where possible, is the Irish regulator
Annex I(C) says the data exporter's competent supervisory authority will be determined in accordance with Data Protection Law and, where possible, will be the Irish Data Protection Commissioner.
Supporting quotations
The Data Exporter’s competent supervisory authority will be determined in accordance with Data Protection Law and, where possible, will be the Irish Data Protection Commissioner.
Qualifications & exceptions
The Irish authority applies only "where possible"; otherwise the authority is determined under Data Protection Law.
Not stated here
Annex I(C) says "Irish Data Protection Commissioner" while Section 8.2.h says "Irish Data Protection Commission"; the document does not say whether these are meant to be the same body.
Annex II describes Groq's information security program, a subset of what its Trust Center publishes
Groq says it maintains an information security program designed to safeguard its systems, data and Customer Data, and Annex II describes the program and security standards it maintains for the Cloud Services and Customer Data. Annex II is the place Section 5.1 and Section 8.2.i point to for the specific security measures. The Security Measures listed are a subset of the information on Groq's Trust Center, which applies to the DPA.
Supporting quotations
Groq maintains an information security program designed to safeguard its systems, data, and Customer Data.
The Security Measures below include a subset of the information available on the Groq Trust Center, which applies to this DPA.
Details regarding the specific security measures that apply to the Cloud Services are as described in Annex II of Schedule A (Details of Processing) below.
Qualifications & exceptions
The program is described as "designed to" safeguard systems and data, not as a guarantee.
The listed Security Measures are a subset of the information on the Trust Center.
Not stated here
The Trust Center content is not part of this document, so the remaining measures and standards it holds are not described here.
Annex II: Groq uses SSO, mandatory multi-factor authentication, access reviews and credential revocation for staff
For authenticating and authorizing internal employee and service access, Groq says it maintains measures designed to cover: single sign-on for third-party services used to deliver the Cloud Services and role based access controls when provisioning internal access; mandatory multi-factor authentication for Groq's identity provider; unique login identifiers for each user; review and approval processes for access requests to services storing Customer Data; quarterly access audits for sensitive roles; procedures to promptly revoke access when employees leave; procedures for reporting and revoking compromised credentials such as passwords and API keys; and password reset procedures that verify identity first.
Supporting quotations
Groq maintains the following measures designed for authenticating and authorizing internal employee and service access:
Role Based Access Controls (RBAC) are used when provisioning internal access to the Cloud Services
Mandatory multi-factor authentication is used for authenticating to Groq’s identity provider
Unique login identifiers are assigned to each user
Established review and approval processes for any access requests to services storing Customer Data
Quarterly access audits designed to ensure access levels are appropriate for the sensitive roles
Established procedures for promptly revoking access rights upon employee separation
Established procedures for reporting and revoking compromised credentials such as passwords and API keys
Established password reset procedures, including procedures designed to verify the identity of a user prior to a new, replacement, or temporary password
Qualifications & exceptions
The measures are introduced as "designed for" authenticating and authorizing internal employee and service access.
Quarterly access audits are described as designed to ensure access levels are appropriate for the sensitive roles.
Security & Safeguards · Company practice
Annex II: a third-party identity service means Groq stores no user passwords; Customer Data is separated by organization
For authenticating and authorizing customers to the Cloud Services, Groq says it maintains measures designed to include: using a third-party identity access management service to manage Customer identity, meaning Groq does not store user-provided passwords on users' behalf; and logically separating Customer Data by organization account using unique identifiers. Within an organization account, unique user accounts are supported.
Supporting quotations
Groq maintains the following measures designed for authenticating and authorizing customers to the Cloud Services:
Use of a third-party identity access management service to manage Customer identity, meaning Groq does not store user-provided passwords on the users’ behalf
Logically separating Customer Data by organization account using unique identifiers.
Within an organization account, unique user accounts are supported.
Qualifications & exceptions
Separation is by organization account, using unique identifiers; the text describes it as logical separation.
Not stated here
The document does not name the third-party identity service.
For securing and operating its cloud infrastructure, Groq says it maintains measures designed to include: deploying primary backend resources behind Zero Trust Network Access (ZTNA) solutions; routinely auditing the Cloud Services for security vulnerabilities; managing application secrets and service accounts with a secrets management service; configuring network security policies and firewalls for least-privilege access against a pre-established set of permissible traffic flows and blocking non-permitted flows; and monitoring Cloud Services logs for security and availability.
Supporting quotations
Groq maintains the following measures designed for securing and operating its cloud infrastructure:
Primary backend resources are deployed behind Zero Trust Network Access (ZTNA) solutions
The Cloud Services are routinely audited for security vulnerabilities
Application secrets and service accounts are managed by a secrets management service
Network security policies and firewalls are configured for least-privilege access against a pre-established set of permissible traffic flows. Non-permitted traffic flows are blocked
Cloud Services logs are monitored for security and availability
Qualifications & exceptions
Zero Trust Network Access covers "primary backend resources", as the text states.
Not stated here
The document does not say how often "routinely" audits occur.
Security & Safeguards · Company practice
Annex II: Groq manages corporate devices with endpoint management, mandatory patching and anti-malware
For securing its corporate systems, including laptops and on-premises infrastructure, Groq says it maintains measures designed to include endpoint management of corporate workstations and devices, automatic application of security configurations to workstations, mandatory patch management, malware and anti-virus detection and alerting, and maintaining appropriate security logs.
Supporting quotations
Groq maintains the following measures designed for securing its corporate systems, including laptops and on-premises infrastructure:
Endpoint management of corporate workstations and devices
Automatic application of security configurations to workstations
Mandatory patch management
Malware and anti-virus detection and alerting
Maintaining appropriate security logs
Qualifications & exceptions
Applies to Groq's corporate systems, including laptops and on-premises infrastructure.
Security & Safeguards · Company practice
Annex II: employee access to the Cloud Services is least-privilege; Customer Data is used only as the Agreement allows
For preventing Authorized Users from accessing data beyond their rights and preventing unauthorized input, reading, copying, removal, modification or disclosure, Groq says it maintains measures designed to include: employee access to the Cloud Services following the principle of least privilege, with only employees whose job function involves supporting delivery of the Cloud Services credentialed to the Cloud Services environment; and Customer Data submitted to the Cloud Services being used only in accordance with the terms of the Agreement and any other applicable contractual agreements with the Customer.
Supporting quotations
Groq maintains the security measures designed for preventing Authorized Users from accessing data beyond their authorized access rights and for preventing the unauthorized input, reading, copying, removal, modification, or disclosure of data.
Employee access to the Cloud Services follows the principle of least privilege. Only employees whose job function involves supporting the delivery of Cloud Services are credentialed to the Cloud Services environment
Customer Data submitted to the Cloud Services is only used in accordance with the terms of the Agreement, and any other applicable contractual agreements in place with Customer.
Qualifications & exceptions
Only employees whose job function involves supporting delivery of the Cloud Services are credentialed to the Cloud Services environment.
Not stated here
The document does not say which other contractual agreements with the Customer may govern use of Customer Data.
Security & Safeguards · Company practice
Annex II: production data is encrypted at rest and in transit, with access audit trails and workstation disk encryption
For preventing unauthorized access, alteration or removal of data during transfer and for securing and logging transfers, Groq says it maintains measures designed to include: encryption of data at rest in production datastores using strong encryption algorithms, encryption of data in transit, an audit trail for all data access requests for production datastores, full-disk encryption required on all corporate workstations, and device management controls required on all corporate workstations.
Supporting quotations
Groq maintains the following measures designed for preventing the unauthorized access, alteration, or removal of data during transfer, and for securing and logging all transfers:
Encryption of data at rest in production datastores using strong encryption algorithms
Encryption of data in transit
Audit trail for all data access requests for production datastores
Full-disk encryption required on all corporate workstations
Device management controls required on all corporate workstations
Qualifications & exceptions
Encryption at rest is stated for production datastores.
The audit trail is stated for data access requests for production datastores.
Not stated here
The document does not name the encryption algorithms or key management arrangements, and does not say what "strong" means.
Security & Safeguards · Company practice
Annex II: Groq designs for restoring systems after interruption, fault reporting and intrusion detection and prevention
For maintaining Cloud Services functionality through accidental or malicious intent, Groq says it maintains measures designed to include ensuring systems may be restored in the event of an interruption, ensuring systems are functioning and faults are reported, and anti-malware and intrusion detection or prevention solutions implemented comprehensively across its environment.
Supporting quotations
Groq maintains the following measures designed for maintaining Cloud Services functionality through accidental or malicious intent:
Ensuring that systems may be restored in the event of an interruption
Ensuring that systems are functioning and faults are reported
Anti-malware and intrusion detection/prevention solutions implemented comprehensively across our environment
Qualifications & exceptions
The text reads "through accidental or malicious intent"; this document does not explain that wording further.
Not stated here
The document does not state recovery time or recovery point targets.
Security & Safeguards · Company practice
Annex II: Groq separates data processed for different purposes and restricts access by role
For separate processing of data collected for different purposes, Groq says it maintains measures designed to include logical segregation of Customer Data, restriction of access to data stored for different purposes according to staff roles and responsibilities, and segregation of business information system functions.
Supporting quotations
Groq maintains the following measures designed for separate processing of data collected for different purposes:
Logical segregation of Customer Data
Restriction of access to data stored for different purposes according to staff roles and responsibilities
Segregation of business information system functions
Qualifications & exceptions
The separation is described as logical segregation of Customer Data.
Security & Safeguards · Company practice
Annex II: Groq does threat modeling, annual penetration tests, annual external audits and vulnerability management
For detecting and managing cybersecurity risks, Groq says it maintains measures designed to include: threat modeling to document and triage sources of security risk; penetration testing of the Cloud Services at least annually, with remediation items resolved as soon as possible on a timetable commensurate with the risk; annual engagements of a qualified, independent external auditor to review Groq's security practices against recognized audit standards, including SOC 2 Type II certification audits, with summary details provided upon reasonable request; and a vulnerability management program designed to ensure prompt remediation of vulnerabilities affecting the Cloud Services.
Supporting quotations
Threat modeling to document and triage sources of security risk for prioritization and remediation
Penetration testing is conducted on the Cloud Services at least annually, and any remediation items identified are resolved as soon as possible on a timetable commensurate with the associated risk
Annual engagements of a qualified, independent external auditor to conduct periodic reviews of Groq’s security practices against recognized audit standards, including SOC 2 Type II certification audits. Upon reasonable request, Groq will provide summary details
A vulnerability management program designed to ensure the prompt remediation of vulnerabilities affecting the Cloud Services
Groq maintains the following measures designed for detecting and managing cybersecurity risks:
To the extent required by Data Protection Laws, Groq will make available such information reasonably necessary to confirm Groq’s compliance with this DPA
Qualifications & exceptions
Penetration testing is stated as at least annually; remediation is on a timetable commensurate with the associated risk.
Summary details of the external audits are given only "upon reasonable request".
Section 9 separately says Groq provides compliance information such as SOC 2 reports to the extent required by Data Protection Laws.
Not stated here
The document does not say who may make a reasonable request for summary details or what form the summary takes.
The document does not say how the "summary details" relate to the audit reports described in Section 9.
Annex II: Groq gives employees annual security training and screens them, including criminal background checks
For vetting, training and managing personnel on security matters, Groq says it maintains measures designed to include annual security training for employees, with supplemental training as appropriate, and appropriate employee background screening, including criminal background checks.
Supporting quotations
Groq maintains the following measures designed for vetting, training, and managing personnel with respect to security matters:
Annual security training for employees, and supplemental security training as appropriate.
Appropriate employee background screening, including criminal background checks.
Qualifications & exceptions
Supplemental training is "as appropriate".
Background screening is "appropriate" screening, including criminal background checks.
Not stated here
The document does not say whether the screening and training also apply to contractors, which the DPA lists elsewhere as persons authorized to Process Personal Data; Annex II says "employees".
Security & Safeguards · Company practice
Annex II: Groq's facilities use locked doors and gates, 24-hour video surveillance and entry and exit logs
For preventing unauthorized physical access to Groq facilities, Groq says it maintains measures designed to include physical barrier controls such as locked doors and gates, 24-hour video surveillance and alarm systems (including video of facility entrances and exits), and logging of facility exits and entries.
Supporting quotations
Groq maintains the following measures designed for preventing unauthorized physical access to Groq facilities:
Physical barrier controls including locked doors and gates
24-hour video surveillance and alarm systems, including video surveillance of facility entrance and exit points
Logging of facility exits and entries
Qualifications & exceptions
Applies to Groq facilities.
Not stated here
The document does not say whether these measures also apply to the facilities of Groq's Subprocessors.
Security & Safeguards · Company practice
Annex II: Groq uses written safeguard contracts with agents and formal security assessments of subprocessors
For managing third-party security risks, including for any Subprocessor or subcontractor to whom Groq provides Customer Data, Groq says it maintains measures designed to include written contracts designed to ensure that any agent agrees to maintain reasonable and appropriate safeguards to protect Customer Data, and a formal security assessment by Groq's Security team of all third-party subprocessors.
Supporting quotations
Groq maintains the following measures designed for managing third party security risks, including with respect to any Subprocessor or subcontractor to whom Groq provides Customer Data:
Written contracts designed to ensure that any agent agrees to maintain reasonable and appropriate safeguards to protect Customer Data
Vendor Security Assessments: all third party subprocessors undergo a formal security assessment process by Groq’s Security team.
means any third party that Groq engages to Process Personal Data in connection with providing the Cloud Services
Qualifications & exceptions
The contract measure is stated as written contracts "designed to ensure" agents maintain "reasonable and appropriate" safeguards.
The security assessment is stated for "all third party subprocessors"; the text does not mention other subcontractors in that item.
Not stated here
The document does not say how often Subprocessors are reassessed or what happens if one fails an assessment.
Annex II: Groq keeps an incident response plan and notifies the Customer of a Data Breach under the DPA
Groq says it maintains a security incident response plan designed for responding to and resolving events that compromise the confidentiality, availability or integrity of the Cloud Services or Customer Data. It includes aggregating system logs for security and general observability from a range of systems to facilitate detection and response, and, if Groq becomes aware that a Data Breach has occurred, notifying the Customer in accordance with the DPA.
Supporting quotations
Groq maintains a security incident response plan designed for responding to and resolving events that compromise the confidentiality, availability, or integrity of the Cloud Services or Customer Data
Groq aggregates system logs for security and general observability from a range of systems to facilitate detection and response
If Groq becomes aware that a Data Breach has occurred, Groq will notify Customer in accordance with the DPA.
a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data
Qualifications & exceptions
The notification item refers to the DPA's notice terms rather than stating its own deadline.
Annex II: Groq performs regular security and vulnerability testing against legal and contractual security requirements
Groq says it performs regular security and vulnerability testing to assess whether key controls are implemented properly and are effective, measured against requirements under Data Protection Law and its policies and procedures, and designed to ensure continued compliance with obligations imposed by law, regulation or contract with respect to the security of Customer Data and the maintenance and structure of Groq's information systems.
Supporting quotations
Groq performs regular security and vulnerability testing to assess whether key controls are implemented properly and are effective as measured against requirements under Data Protection Law and its policies and procedures
Qualifications & exceptions
Testing is described as "regular".
Not stated here
The document does not say how often "regular" testing occurs or whether results are shared with the Customer.
Legal Rights & Agreement Rules · Context
The DPA is part of the Groq Services Agreement and has a stated order of precedence
This addendum is incorporated into and made part of the Groq Services Agreement between the Groq Contracting Party and the Customer, for use of Groq's Cloud Services, and is stated as effective October 15, 2025. Capitalized terms not defined here take their meaning from the Services Agreement, and "Agreement" in the DPA means the Services Agreement and the DPA together. If the documents conflict on the subject matter of the DPA, the order of precedence (highest first) is the Standard Contractual Clauses as provided in the DPA, the body of the DPA, documents attached to the DPA, and then the Services Agreement.
Supporting quotations
Effective: October 15, 2025
is incorporated into and made part of the Groq Services Agreement between the Groq Contracting Party and Customer
In the event of any conflict between these documents as to the subject matter of this DPA, the following order of precedence applies (in descending order): (a) the Standard Contractual Clauses as provided in this DPA; (b) the body of the DPA; (c) any documents attached to the DPA; and (d) the Services Agreement.
Qualifications & exceptions
The order of precedence applies only to conflicts as to the subject matter of this DPA, not to every term of the Services Agreement.
Not stated here
The Groq Services Agreement itself is not part of this document, so terms defined only there (for example Customer Data, Cloud Services, Order Form) are not described here.
This document does not identify which entity is the Groq Contracting Party.
Legal Rights & Agreement Rules · Context
Controller and Processor take their meanings from the applicable data protection laws
The DPA does not define Controller, Business, Processor or Service Provider itself. Each has the meaning it has under the applicable Data Protection Laws; the terms "Business" and "Service Provider" are included, where applicable, in "Controller" and "Processor" respectively.
Supporting quotations
have the meanings set forth under Data Protection Laws
Qualifications & exceptions
Which meaning applies depends on which Data Protection Law governs the particular processing.
Not stated here
The document does not say which law's definitions apply in a given case.
Legal Rights & Agreement Rules · Context
Data Protection Laws means all applicable privacy and data protection laws in any jurisdiction, including named laws
"Data Protection Laws" covers all applicable laws, regulations and other legally binding requirements in any jurisdiction on privacy, data protection, data security and breach notification that apply to Groq's Processing of Personal Data. The definition says it includes, without limitation and to the extent applicable, California's CCPA (as amended by the CPRA), the EU GDPR, the Swiss FADP, the UK GDPR and Saudi Arabia's PDPL.
Supporting quotations
means all applicable laws, regulations, and other legally binding requirements in any jurisdiction relating to privacy, data protection, data security, breach notification, that apply to Groq’s Processing of Personal Data, including, without limitation, to the extent applicable
Qualifications & exceptions
The named laws are included only "to the extent applicable"; the list is not exhaustive.
Only laws that apply to Groq's Processing of Personal Data are covered.
Not stated here
This document does not say which of the listed laws apply to any particular Customer.
Personal Data is limited to personal data inside Customer Data that Groq processes to provide the Cloud Services
"Personal Data" means personal data, personal information or personally identifiable information (or equivalent terms under Data Protection Laws) that is included within Customer Data and is Processed by Groq in connection with providing the Cloud Services under the Services Agreement. "Data Subject" is an identified or identifiable natural person the Personal Data relates to. "Process" or "Processing" has its meaning under Data Protection Laws or, if not defined there, means any operation on Personal Data, such as collection, storage, use, disclosure, combination, restriction, erasure or destruction.
Supporting quotations
included within any Customer Data that is Processed by Groq in connection with providing the Cloud Services under the Services Agreement
means an identified or identifiable natural person about whom Personal Data relates
means any operation or set of operations performed on Personal Data or on sets of Personal Data, whether or not by automated means
Qualifications & exceptions
Personal Data is only what is included within Customer Data and processed by Groq in connection with providing the Cloud Services; other personal data Groq holds is not defined as Personal Data here.
The Processing definition is open-ended ("such as").
Not stated here
Customer Data is defined in the Services Agreement, which is not part of this document.
Data Breach means a security breach affecting Personal Data
"Data Breach" is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data. The defined term drives the breach notification duties later in the DPA.
Supporting quotations
a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Personal Data
Qualifications & exceptions
It covers both accidental and unlawful causes and both loss of data and unauthorized access.
The EU SCCs and KSA C2P Clauses are the named transfer clauses, applied as Section 8 states
"EU SCCs" means the standard contractual clauses issued under Commission Implementing Decision (EU) 2021/914, completed as specified in Section 8 of the DPA. "KSA C2P Clauses" means the Saudi Data & AI Authority standard clauses for personal data transfer under the PDPL, specifically the Second Template (Controller to Processor), as amended, updated or replaced over time. Section 8 says the EU SCCs apply to the extent legally required and that Groq will comply with the data importer's obligations in the KSA C2P Clauses.
Supporting quotations
completed as specified in Section 8 (International Data Transfers) below
specifically including the Second Template (Controller to Processor), as amended, updated or replaced from time to time
To the extent legally required, by entering into the Agreement, Customer and Groq are deemed to have signed the EU SCCs
Groq will comply with the data importer's obligations set out in the KSA C2P Clauses, which are incorporated into and form part of this DPA
Qualifications & exceptions
The EU SCCs are deemed signed only "to the extent legally required".
The KSA C2P Clauses are defined as amended, updated or replaced from time to time, so the operative text can change.
Not stated here
The text of the EU SCCs and the KSA C2P Clauses is not reproduced here.