This Data Processing Addendum ("DPA") is entered into between PlungeAI, Inc. ("PlungeAI", "we", "us") and the Customer, and sets out the terms on which PlungeAI processes Customer Personal Data on the Customer's behalf when it provides the Services. It forms part of, and is incorporated into, the PlungeAI Terms of Service at https://www.plungeai.com/terms (the "Terms"). The Customer accepts this DPA, including the SCCs and the UK Addendum where Annex 3 applies them, by accepting the Terms; no separate signature is required. This DPA applies for as long as PlungeAI processes Customer Personal Data under the Terms.
1. Definitions
1.1 Defined terms
In this DPA, the following terms have the meanings set out below:
- "Annex 1", "Annex 2" and "Annex 3" mean Sections 15, 16 and 17 of this DPA respectively.
- "Applicable Data Protection Law" means all laws and regulations relating to privacy and data protection that apply to the processing of Customer Personal Data under the Terms, including, to the extent applicable: (i) Regulation (EU) 2016/679 (the "GDPR") and the laws of the member states of the European Economic Area ("EEA") implementing or supplementing it; (ii) the GDPR as it forms part of the law of the United Kingdom under section 3 of the European Union (Withdrawal) Act 2018 (the "UK GDPR") and the Data Protection Act 2018; (iii) the Swiss Federal Act on Data Protection of 25 September 2020 (the "FADP") and its ordinances; (iv) the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020, Cal. Civ. Code § 1798.100 et seq., and its implementing regulations, Cal. Code Regs. tit. 11, § 7000 et seq. (together, the "CCPA"); and (v) the other United States state privacy laws listed in Section 12.6 (together with the CCPA, the "US Privacy Laws").
- "Business Purpose" means the purposes for which PlungeAI processes Customer Personal Data under Section 3 and Annex 1, namely to provide, maintain, support and secure the Services for the Customer in accordance with the Terms, each of which is a "business purpose" within the meaning of Cal. Civ. Code § 1798.140(e).
- "Controller" means the natural or legal person that alone or jointly with others determines the purposes and means of the processing of Personal Data, as defined in Art. 4(7) GDPR, and includes a "business" or "controller" as defined in the US Privacy Laws.
- "Customer" has the meaning given in the Terms: the individual who accepts the Terms or, where an individual accepts them on behalf of an organization, that organization.
- "Customer Personal Data" has the meaning given in the Terms: Personal Data contained in Customer Content or Output that PlungeAI processes on the Customer's behalf as a Processor. Customer Personal Data does not include PlungeAI Business Data (Section 2.3).
- "Data Subject" means the identified or identifiable natural person to whom Customer Personal Data relates, and includes a "consumer" as defined in the US Privacy Laws.
- "Personal Data" means any information relating to an identified or identifiable natural person, as defined in Art. 4(1) GDPR, and any information that constitutes "personal data", "personal information" or an equivalent term under Applicable Data Protection Law.
- "Personal Data Breach" means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data transmitted, stored or otherwise processed by PlungeAI or its Subprocessors, as described in Art. 4(12) GDPR, and includes a "breach of the security of the system" or equivalent term under the US Privacy Laws to the extent it affects Customer Personal Data. It does not include an unsuccessful attempt or activity that does not compromise the security of Customer Personal Data, such as pings, port scans, denial-of-service attacks that do not result in access to Customer Personal Data, or failed sign-in attempts.
- "Processor" means a natural or legal person that processes Personal Data on behalf of a Controller, as defined in Art. 4(8) GDPR, and includes a "service provider", "contractor" or "processor" as defined in the US Privacy Laws.
- "Restricted Transfer" means: (i) a transfer of Customer Personal Data that is subject to the GDPR to a country outside the EEA that is not the subject of an adequacy decision under Art. 45 GDPR; (ii) a transfer of Customer Personal Data that is subject to the UK GDPR to a third country where the transfer is not approved by regulations under Art. 45A UK GDPR; or (iii) a transfer of Customer Personal Data that is subject to the FADP to a country that the Swiss Federal Council has not recognized as providing an adequate level of protection under Art. 16(1) FADP; in each case, including an onward transfer, where the transfer would be prohibited by Applicable Data Protection Law in the absence of appropriate safeguards.
- "SCCs" means the standard contractual clauses for the transfer of personal data to third countries annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021, as incorporated and completed by Annex 3.
- "Sell" has the meaning given to "sell" in Cal. Civ. Code § 1798.140(ad), and "Selling" and "Sale" shall be construed accordingly.
- "Sensitive Data" has the meaning given in Annex 1.
- "Service Provider" has the meaning given to "service provider" in Cal. Civ. Code § 1798.140(ag), and includes a "contractor" under Cal. Civ. Code § 1798.140(j) and a "processor" under the other US Privacy Laws.
- "Share" has the meaning given to "share" in Cal. Civ. Code § 1798.140(ah), namely disclosing Personal Data to a third party for cross-context behavioral advertising, and "Sharing" shall be construed accordingly.
- "Subprocessor" has the meaning given in the Terms: a third party that PlungeAI engages to process Customer Personal Data on PlungeAI's behalf, as listed in the Subprocessors list. PlungeAI's own personnel are not Subprocessors.
- "Supervisory Authority" means an independent public authority established by an EEA member state under Art. 51 GDPR, the UK Information Commission, the Swiss Federal Data Protection and Information Commissioner ("FDPIC"), and any other governmental authority with jurisdiction to enforce Applicable Data Protection Law, including the California Privacy Protection Agency and the attorneys general of the States of the United States.
- "Third-Party Controller" means a Controller on whose behalf the Customer processes Customer Personal Data as a Processor, as described in Section 2.2(b).
- "UK Addendum" means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, version B1.0, issued by the UK Information Commissioner under section 119A(1) of the Data Protection Act 2018 and in force from 21 March 2022, as completed by Annex 3.
1.2 Terms defined elsewhere
(a) "Account", "Customer Content", "Order Form", "Output", "Product", "Product Terms" and "Services" have the meanings given in the Terms.
(b) "Processing" has the meaning given in Art. 4(2) GDPR, and "process" and "processed" shall be construed accordingly.
(c) Other capitalized terms used but not defined in this DPA have the meanings given in the Terms. The words "including" and "for example" are illustrative and do not limit the words that precede them.
2. Scope, Roles and Order of Precedence
2.1 Scope
(a) This DPA applies whenever PlungeAI processes Customer Personal Data in providing the Services, in every Product: One API, Agency, AI Consulting, Ocean Code and Ocean Vibe.
(b) Annex 1 describes the subject matter, nature, purpose and duration of the processing, the categories of Data Subjects and the categories of Personal Data, as required by Art. 28(3) GDPR.
(c) This DPA does not apply to processing that PlungeAI does not perform, including:
- processing that Ocean Code performs on the Customer's own machine, except for data that Ocean Code transmits to PlungeAI, such as model and tool calls made with a One API key;
- processing by the provider of an account that the Customer connects to the Services, such as a Google, Microsoft or Slack account, which that provider performs for the Customer under the Customer's own agreement with it; and
- processing by an AI model provider for calls made with the Customer's own account or API key with that provider, which that provider performs under the Customer's own agreement with it.
2.2 Roles of the parties
(a) Customer as Controller. Where the Customer is a Controller of Customer Personal Data, PlungeAI is its Processor.
(b) Customer as Processor. Where the Customer processes Customer Personal Data as a Processor on behalf of a Third-Party Controller, PlungeAI acts as the Customer's sub-processor (a Processor engaged by another Processor). In that case:
- the Customer warrants that its instructions to PlungeAI, its engagement of PlungeAI as a sub-processor and PlungeAI's engagement of Subprocessors under Section 6 have been authorized by the Third-Party Controller;
- the Customer is the single point of contact for the Third-Party Controller. PlungeAI shall act only on the Customer's instructions and shall have no obligation to deal with the Third-Party Controller directly, except where Applicable Data Protection Law or the SCCs require otherwise; and
- the Customer shall promptly pass on to the Third-Party Controller any notice, information or assistance PlungeAI provides under this DPA.
(c) US Privacy Laws. For Customer Personal Data subject to the US Privacy Laws, the Customer is a "business" or "controller" and PlungeAI is its Service Provider or processor, as further described in Section 12.
2.3 PlungeAI as an independent Controller
(a) PlungeAI is an independent Controller, and not a Processor, of Personal Data it processes for its own legitimate business purposes, including to create and administer Accounts; to bill, invoice and collect fees; to prevent fraud and abuse and enforce the Acceptable Use Policy; to secure and monitor its systems and networks; to communicate with the Customer about the Services; and to comply with its legal obligations ("PlungeAI Business Data").
(b) PlungeAI processes PlungeAI Business Data in accordance with its Privacy Policy at https://www.plungeai.com/privacy and Applicable Data Protection Law. This DPA does not apply to PlungeAI Business Data.
2.4 Order of precedence
(a) If there is a conflict among the following documents, the document listed first prevails to the extent of the conflict:
- an Order Form or other written agreement signed by both parties, including a data processing agreement for a Product signed by both parties;
- the SCCs, including as applied by the UK Addendum and the Swiss changes in Annex 3, for Restricted Transfers only;
- the applicable Product Terms, including any data processing terms published with them, for that Product;
- this DPA, for the processing of Personal Data;
- the Terms; and
- the Acceptable Use Policy and the other policies incorporated into the Terms.
(b) Agency and AI Consulting each have Product Terms on their own sites, at https://agency.plungeai.com/terms and https://consulting.plungeai.com/terms, together with their own data processing terms. Those data processing terms prevail over this DPA for that Product only, and only on the matters they address. On matters they do not address, this DPA applies.
(c) Notwithstanding Section 2.4(a), nothing in an Order Form or in any other document shall be read to contradict the SCCs, directly or indirectly, or to prejudice the fundamental rights or freedoms of Data Subjects. In accordance with Clause 5 of the SCCs, the SCCs prevail over any conflicting provision of a related agreement.
(d) On matters this DPA does not address, the Terms apply.
3. Processing on Documented Instructions
3.1 Documented instructions
(a) PlungeAI shall process Customer Personal Data only on the Customer's documented instructions, including with regard to transfers of Customer Personal Data to a third country or an international organization, as required by Art. 28(3)(a) GDPR.
(b) The Customer instructs PlungeAI to process Customer Personal Data:
- in accordance with the Terms, the applicable Product Terms, any Order Form and this DPA;
- as initiated by the Customer and its users through their use and configuration of the Services, including the models, tools, connectors, agents and workflows they select for each call or run, the accounts they connect and the content they submit; and
- in accordance with any other reasonable written instruction the Customer gives that PlungeAI agrees to in writing as consistent with the Terms.
(c) The Customer's selection of a model, tool or connector for a call or run is an instruction to transmit the relevant Customer Personal Data to the provider of that model, tool or connector, in the location shown on the Subprocessors list, for the purpose of that call or run.
(d) The instructions in Section 3.1(b) are the Customer's complete instructions at the time this DPA takes effect. An additional or changed instruction that falls outside the scope of the Services requires PlungeAI's prior written agreement and may be subject to additional fees agreed in writing.
3.2 Processing required by law
PlungeAI may process Customer Personal Data where Union or member state law to which PlungeAI is subject, or other law applicable to PlungeAI, requires it. In that case PlungeAI shall inform the Customer of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest (Art. 28(3)(a) GDPR).
3.3 Instructions that infringe the law
(a) PlungeAI shall immediately inform the Customer if, in PlungeAI's opinion, an instruction infringes Applicable Data Protection Law, as required by the second subparagraph of Art. 28(3) GDPR.
(b) PlungeAI may suspend the processing affected by that instruction until the Customer withdraws, modifies or confirms it in writing. PlungeAI is not obliged to perform a legal review of the Customer's instructions.
3.4 No training
PlungeAI shall not use Customer Personal Data, Customer Content or Output to train or fine-tune any AI model, and shall not license it to any third party for training.
3.5 Customer's responsibilities
The Customer shall:
(a) ensure that it has, and will maintain, a valid legal basis under Applicable Data Protection Law for the processing of Customer Personal Data under this DPA, and that its instructions comply with Applicable Data Protection Law;
(b) provide all notices to, and obtain all consents from, Data Subjects that Applicable Data Protection Law requires for that processing;
(c) be responsible for the accuracy and quality of Customer Personal Data and for the means by which it was obtained;
(d) not submit Sensitive Data to the Services except as permitted by Annex 1; and
(e) keep its Account credentials, API keys and the settings it controls secure, as described in Section 5.3.
4. Confidentiality of Personnel
(a) PlungeAI shall ensure that every person it authorizes to process Customer Personal Data has committed to confidentiality in writing or is under an appropriate statutory obligation of confidentiality, as required by Art. 28(3)(b) GDPR. That obligation shall continue after the person's engagement with PlungeAI ends.
(b) PlungeAI shall restrict access to Customer Personal Data to those personnel who need it to provide, support or secure the Services, and shall ensure that any person acting under its authority who has access to Customer Personal Data processes it only on the Customer's instructions, unless required to do so by law (Art. 29 and Art. 32(4) GDPR).
(c) PlungeAI personnel shall access Customer Content only: (i) where human review forms part of the Product the Customer ordered, such as the check of Agency work by a person before it is delivered to the Customer or the review of AI Consulting deliverables; (ii) where the Customer asks for support that requires it; (iii) where needed to investigate a security incident, abuse or a breach of the Acceptable Use Policy; or (iv) where the law requires it.
5. Security of Processing
5.1 Security measures
(a) Taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing, as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, PlungeAI shall implement and maintain appropriate technical and organizational measures to ensure a level of security appropriate to the risk, as required by Art. 28(3)(c) and Art. 32 GDPR.
(b) Those measures are designed to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure and unauthorized access. They are described in Annex 2 (the "Security Measures").
5.2 Changes to the Security Measures
The Security Measures are subject to technical progress and development. PlungeAI may update or modify them from time to time, provided that no update or modification results in a material decrease in the overall security of the Services or of Customer Personal Data.
5.3 Customer's security responsibilities
(a) The Customer is responsible for its use of the Services, including: securing its Account credentials, sign-in sessions and API keys; revoking a key it believes has been exposed; managing who has access to its Account; configuring the Services, including the spend caps, connected accounts, models and tools it selects; and securing Customer Personal Data while it is outside PlungeAI's systems, including on the Customer's own machine when it uses Ocean Code.
(b) The Customer has reviewed the Security Measures and agrees that, for the processing it instructs, they provide a level of security appropriate to the risk.
6. Subprocessors
6.1 General written authorization
(a) The Customer gives PlungeAI a general written authorization to engage Subprocessors to process Customer Personal Data, as permitted by Art. 28(2) GDPR and Clause 9(a) of the SCCs.
(b) The Customer authorizes each Subprocessor on the Subprocessors list (Section 6.2) at the date the Customer accepts this DPA.
6.2 Subprocessors list
(a) PlungeAI maintains a list of its Subprocessors at https://www.plungeai.com/subprocessors (the "Subprocessors list"). For each Subprocessor, the list states what it does, the Personal Data it processes, the location of processing and the Products for which it is engaged.
(b) Which Subprocessors process the Customer's Personal Data depends in part on the Customer's choices. In One API, Ocean Code and Ocean Vibe, an AI model provider or tool provider processes a request when the Customer or its agent selects that provider's model or tool. In Agency and AI Consulting, PlungeAI selects the models that perform the work.
(c) AI model providers process requests under their own API terms. PlungeAI selects API offerings and settings intended for business use and describes them on the Subprocessors list.
(d) A provider that processes Customer Personal Data under the Customer's own agreement with it, as described in Section 2.1(c), is not a Subprocessor.
6.3 Notice of new Subprocessors
PlungeAI shall give at least 30 days' notice before a new Subprocessor begins to process Customer Personal Data, so that the Customer can object as Art. 28(2) GDPR provides. PlungeAI gives notice by updating the Subprocessors list and by email to the Account owners. The Customer may ask for notices to be sent to an additional address by writing to legal@plungeai.com.
6.4 Right to object
(a) The Customer may object to a new Subprocessor on reasonable grounds relating to the protection of Customer Personal Data. To do so, the Customer shall notify legal@plungeai.com in writing within the 30-day notice period and explain its grounds.
(b) The parties shall discuss the objection in good faith. Alternatives may include a change in the Customer's configuration or a commercially reasonable change to the Services that avoids the use of that Subprocessor for the Customer's Personal Data.
(c) If the parties do not agree on an alternative within a reasonable time, the Customer may terminate the affected Service by written notice to legal@plungeai.com. PlungeAI shall refund, on a pro-rata basis, any fees the Customer prepaid for the affected Service for the period after termination. Termination under this Section 6.4(c) is the Customer's sole remedy for an objection.
(d) If the Customer does not object within the notice period, the new Subprocessor is deemed authorized.
6.5 Flow-down of obligations
(a) PlungeAI shall engage each Subprocessor only under a written contract that imposes on it data protection obligations at least as protective as those in this DPA, to the extent applicable to the nature of the services the Subprocessor provides, and in particular that provides sufficient guarantees to implement appropriate technical and organizational measures, as required by Art. 28(4) GDPR.
(b) Where a Subprocessor's processing of Customer Personal Data is a Restricted Transfer, PlungeAI shall ensure that the transfer is subject to a transfer mechanism recognized under Applicable Data Protection Law, in accordance with Clause 8.8 and Clause 9 of the SCCs.
(c) On the Customer's written request, PlungeAI shall provide a copy of the data protection terms it has concluded with a Subprocessor, as required by Clause 9(c) of the SCCs. PlungeAI may remove commercial information and other confidential terms beforehand, and may instead direct the Customer to those terms where the Subprocessor publishes them.
6.6 Liability for Subprocessors
PlungeAI remains fully liable to the Customer for the performance of each Subprocessor's data protection obligations, as required by Art. 28(4) GDPR, subject to Section 13.
7. Personal Data Breach
7.1 Notification
PlungeAI shall notify the Customer without undue delay, and in any event no later than 72 hours, after becoming aware of a Personal Data Breach, as required by Art. 33(2) GDPR. PlungeAI shall send the notice by email to the Account owners.
7.2 Content of the notice
The notice shall describe, to the extent the information is available to PlungeAI at the time, the matters listed in Art. 33(3) GDPR:
(a) the nature of the Personal Data Breach, including, where possible, the categories and approximate number of Data Subjects concerned and the categories and approximate number of Personal Data records concerned;
(b) the name and contact details of a contact point at PlungeAI from whom more information can be obtained;
(c) the likely consequences of the Personal Data Breach; and
(d) the measures PlungeAI has taken or proposes to take to address the Personal Data Breach, including, where appropriate, measures to mitigate its possible adverse effects, and any steps PlungeAI recommends the Customer take.
7.3 Information in phases
Where, and in so far as, it is not possible to provide all the information at the same time, PlungeAI shall provide it in phases without undue further delay, as permitted by Art. 33(4) GDPR.
7.4 PlungeAI's response
PlungeAI shall take reasonable steps to contain, investigate and remediate the Personal Data Breach, and shall keep a record of the facts, effects and remedial action taken, so that the Customer can meet its own documentation duty under Art. 33(5) GDPR.
7.5 Assistance and notices to others
(a) PlungeAI shall provide the Customer with reasonable assistance, taking into account the nature of the processing and the information available to PlungeAI, so that the Customer can notify the competent Supervisory Authority under Art. 33 GDPR and communicate the Personal Data Breach to Data Subjects under Art. 34 GDPR where required.
(b) The Customer is responsible for any notification to a Supervisory Authority or to Data Subjects that Applicable Data Protection Law requires of a Controller. PlungeAI shall not notify a Supervisory Authority or a Data Subject of a Personal Data Breach on the Customer's behalf without the Customer's prior written consent, unless the law requires it.
7.6 No admission of fault
PlungeAI's notification of or response to a Personal Data Breach under this Section 7 is not an acknowledgment by PlungeAI of any fault or liability with respect to the Personal Data Breach.
7.7 Reports by the Customer
The Customer shall report a suspected Personal Data Breach, and any suspected unauthorized use of its Account or API keys, to legal@plungeai.com without undue delay.
8. Assistance with Data Subject Requests, DPIAs and Prior Consultation
8.1 Data Subject requests
(a) Taking into account the nature of the processing, PlungeAI shall assist the Customer by appropriate technical and organizational measures, insofar as this is possible, to fulfill the Customer's obligation to respond to requests from Data Subjects exercising their rights under Chapter III GDPR (Arts. 12 to 22), as required by Art. 28(3)(e) GDPR, and their equivalent rights under other Applicable Data Protection Law.
(b) The Services include features that allow the Customer to access, correct, export and delete Customer Personal Data in many cases. Where the Customer cannot fulfill a request through those features, PlungeAI shall provide reasonable further assistance on the Customer's written request.
(c) If PlungeAI receives a request from a Data Subject that relates to Customer Personal Data and identifies the Customer, PlungeAI shall forward it to the Customer without undue delay. PlungeAI shall not respond to the request itself, except to direct the Data Subject to the Customer, unless the Customer authorizes it in writing or the law requires it.
8.2 Data protection impact assessments and prior consultation
Taking into account the nature of the processing and the information available to PlungeAI, PlungeAI shall provide the Customer with reasonable assistance in ensuring compliance with the obligations in Arts. 32 to 36 GDPR, as required by Art. 28(3)(f) GDPR, including with:
(a) any data protection impact assessment the Customer is required to carry out under Art. 35 GDPR in relation to the processing under this DPA; and
(b) any prior consultation with a Supervisory Authority the Customer is required to undertake under Art. 36 GDPR as a result of such an assessment.
PlungeAI may meet this obligation first by providing the information in this DPA, on the Subprocessors list and in the documentation of the Services.
8.3 Cooperation with Supervisory Authorities
PlungeAI shall cooperate, on request, with a competent Supervisory Authority in the performance of its tasks in relation to the processing under this DPA, as required by Art. 31 GDPR.
8.4 Costs
PlungeAI may charge a reasonable fee, agreed in advance in writing, for assistance under this Section 8 that goes beyond the features of the Services and the information PlungeAI makes generally available, except where the need for assistance arises from PlungeAI's breach of this DPA.
9. International Transfers
9.1 Locations of processing
(a) PlungeAI is established in the United States. PlungeAI hosts the Services on Cloudflare: its Workers are placed in the San Jose region, and its database primaries are in western North America. Requests reach Cloudflare's global network at the location nearest to the person making them.
(b) Subprocessors process Customer Personal Data in the locations stated on the Subprocessors list.
9.2 Transfers on instructions
PlungeAI shall transfer Customer Personal Data to a third country only on the Customer's documented instructions, which include the instructions in Section 3.1, or where required by law under Section 3.2.
9.3 Transfer mechanisms
(a) Where the transfer of Customer Personal Data from the Customer to PlungeAI is a Restricted Transfer, the SCCs, the UK Addendum and the Swiss changes apply to that transfer as set out in Annex 3, and are incorporated into this DPA by reference.
(b) Where PlungeAI makes an onward Restricted Transfer to a Subprocessor, PlungeAI shall ensure that the transfer is subject to a valid transfer mechanism under Applicable Data Protection Law, in accordance with Section 6.5(b).
9.4 Requests from public authorities
If PlungeAI receives a legally binding request from a public authority for disclosure of Customer Personal Data, PlungeAI shall, consistent with Clause 15 of the SCCs:
(a) notify the Customer promptly, unless the law prohibits notification, in which case PlungeAI shall use reasonable efforts to obtain a waiver of the prohibition;
(b) review the legality of the request and challenge it where, after careful assessment, it concludes that there are reasonable grounds to consider it unlawful;
(c) disclose only the minimum Customer Personal Data permissible when responding, based on a reasonable interpretation of the request; and
(d) document its assessment and make it available to the Customer to the extent the law permits.
9.5 Transfer impact assessments
PlungeAI shall provide the Customer with information reasonably necessary for the Customer to assess the laws and practices of the destination country under Clause 14 of the SCCs, to the extent that information is available to PlungeAI and is not confidential to a third party.
9.6 Changes in transfer mechanisms
(a) If PlungeAI adopts another transfer mechanism recognized under Applicable Data Protection Law that covers a Restricted Transfer, that mechanism shall apply to that transfer in place of the SCCs, to the extent it covers the transfer.
(b) If a transfer mechanism relied on under this DPA is invalidated, amended or replaced, the parties shall cooperate in good faith to put in place a valid alternative mechanism without undue delay.
10. Deletion or Return
10.1 Return
(a) During the term of the Services, the Customer may export Customer Content, including the Customer Personal Data it contains, using the export features of the Services.
(b) For 30 days after closure of the Account, the Customer may continue to export Customer Content, except where Section 17.7(a) of the Terms excludes export. If the Customer needs assistance with return, it shall write to legal@plungeai.com before that period ends.
10.2 Deletion
(a) At the end of the provision of the Services, PlungeAI shall, at the Customer's choice, return Customer Personal Data under Section 10.1 and delete it, as required by Art. 28(3)(g) GDPR.
(b) PlungeAI shall delete Customer Personal Data, including existing copies, within 30 days after the end of the Services. Archives of Customer Personal Data are kept while the Account is open and are deleted with it.
(c) During the term of the Services, the Customer may delete Customer Personal Data itself using the features of the Services. Records are otherwise kept for the periods stated in Annex 1.
10.3 Exceptions
(a) PlungeAI may retain Customer Personal Data where Union or member state law, or other law applicable to PlungeAI, requires storage. PlungeAI shall keep that data confidential, protect it in accordance with this DPA and process it only for the purpose the law requires.
(b) Copies of Customer Personal Data in backups are deleted as the backups expire on their normal cycle. Until then, this DPA continues to apply to them, and PlungeAI shall not restore or use them except to recover the Services from an incident.
10.4 Confirmation of deletion
On the Customer's written request, PlungeAI shall confirm the deletion of Customer Personal Data in writing. That confirmation is the certification of deletion described in Clause 8.5 of the SCCs.
11. Audits and Information
11.1 Information
(a) PlungeAI shall make available to the Customer all information necessary to demonstrate compliance with the obligations laid down in Art. 28 GDPR and in this DPA, as required by Art. 28(3)(h) GDPR.
(b) PlungeAI shall first meet any request for information with written information and available reports, which may include written responses to the Customer's reasonable security questionnaires, descriptions of the Security Measures, the Subprocessors list and the records of processing PlungeAI maintains under Art. 30(2) GDPR.
(c) PlungeAI does not currently hold a third-party security certification or attestation report. If PlungeAI obtains one, PlungeAI may provide it as part of the information under this Section 11.1.
11.2 Audits
If the information under Section 11.1 is not sufficient to demonstrate PlungeAI's compliance with this DPA, the Customer may conduct an audit, including an inspection, of PlungeAI's compliance with this DPA, on the following conditions:
(a) the Customer may conduct at most one audit in any 12-month period. Additional audits are allowed after a Personal Data Breach affecting Customer Personal Data or where a Supervisory Authority requires one;
(b) the Customer shall give at least 30 days' written notice to legal@plungeai.com, except where a Supervisory Authority requires a shorter period;
(c) the parties shall agree the scope, timing and duration of the audit in advance. The audit shall take place during normal business hours and shall be conducted so as to minimize disruption to PlungeAI's operations;
(d) the audit shall be conducted by the Customer or by an independent auditor that is not a competitor of PlungeAI, and every person conducting it shall be bound by confidentiality obligations no less protective than those in the Terms;
(e) the Customer shall bear its own costs of the audit, including those of its auditor; and
(f) the Customer shall provide PlungeAI with a copy of any audit report free of charge, and shall treat the report and all information obtained in the audit as PlungeAI's confidential information.
11.3 Limits
An audit does not entitle the Customer or its auditor to access the data of PlungeAI's other customers, PlungeAI's trade secrets, information subject to legal privilege, or systems operated by Subprocessors. An audit of a Subprocessor is governed by the terms between PlungeAI and that Subprocessor, and PlungeAI shall provide the Customer with the information about the Subprocessor that PlungeAI is entitled to share.
11.4 Relationship with the SCCs
The Customer agrees that its audit rights under Clause 8.9 of the SCCs shall be exercised in accordance with this Section 11. Nothing in this Section 11 limits any right of the Customer, a Data Subject or a Supervisory Authority under the SCCs.
12. United States Privacy Laws
12.1 Role and Business Purpose
(a) For Customer Personal Data subject to the CCPA, PlungeAI is the Customer's Service Provider. The Customer discloses Customer Personal Data to PlungeAI, and PlungeAI processes it, solely for the Business Purpose, as required by Cal. Civ. Code § 1798.100(d) and § 1798.140(ag) and Cal. Code Regs. tit. 11, § 7051 (11 CCR § 7051).
(b) The specific business purposes for which PlungeAI processes Customer Personal Data are those described in Annex 1.
12.2 Restrictions
PlungeAI shall not:
(a) Sell or Share Customer Personal Data;
(b) retain, use or disclose Customer Personal Data for any purpose, including any commercial purpose, other than the Business Purpose, or as otherwise permitted for a Service Provider by the CCPA and 11 CCR § 7050(a);
(c) retain, use or disclose Customer Personal Data outside the direct business relationship between PlungeAI and the Customer; or
(d) combine Customer Personal Data with Personal Data that PlungeAI receives from or on behalf of another person, or collects from its own interaction with the Data Subject, except as permitted by the CCPA and 11 CCR § 7050(a).
12.3 Compliance and assistance
PlungeAI shall:
(a) comply with the obligations that apply to it as a Service Provider under the CCPA, and provide the same level of privacy protection as the CCPA requires of the Customer;
(b) implement reasonable security procedures and practices appropriate to the nature of Customer Personal Data, as described in Section 5 and Annex 2;
(c) assist the Customer in responding to verifiable consumer requests, as described in Section 8.1, including by deleting, correcting or providing Customer Personal Data as the Customer instructs; and
(d) engage another Service Provider or contractor to process Customer Personal Data only under a written contract that meets the requirements of Cal. Civ. Code § 1798.140(ag)(2) and 11 CCR § 7051, and with notice to the Customer under Section 6.3.
12.4 Customer's rights
(a) The Customer may take reasonable and appropriate steps to ensure that PlungeAI uses Customer Personal Data in a manner consistent with the Customer's obligations under the CCPA, including through the information and audits described in Section 11.
(b) PlungeAI shall notify the Customer in writing if it determines that it can no longer meet its obligations under the CCPA.
(c) On notice, including notice under Section 12.4(b), the Customer may take reasonable and appropriate steps to stop and remediate unauthorized use of Customer Personal Data, including by instructing PlungeAI to suspend the affected processing or by suspending its use of the affected Service.
12.5 Certification
PlungeAI certifies that it understands the restrictions in this Section 12 and will comply with them.
12.6 Other US Privacy Laws
(a) For Customer Personal Data subject to the Virginia Consumer Data Protection Act (Va. Code Ann. § 59.1-575 et seq.), the Colorado Privacy Act (Colo. Rev. Stat. § 6-1-1301 et seq.), the Connecticut Data Privacy Act (Conn. Gen. Stat. § 42-515 et seq.), the Texas Data Privacy and Security Act (Tex. Bus. & Com. Code § 541.001 et seq.), or the comparable comprehensive consumer privacy laws of the other States of the United States as they take effect, PlungeAI is the Customer's processor, and the Customer is the controller.
(b) This DPA sets out the instructions for processing, the nature and purpose of the processing, the types of Personal Data, the duration of the processing and the rights and obligations of both parties, as those laws require, including Va. Code Ann. § 59.1-579, Colo. Rev. Stat. § 6-1-1305, Conn. Gen. Stat. § 42-521 and Tex. Bus. & Com. Code § 541.104. In particular, PlungeAI shall:
- process Customer Personal Data only on the Customer's instructions (Section 3);
- ensure that each person processing Customer Personal Data is subject to a duty of confidentiality (Section 4);
- engage a subcontractor only under a written contract that requires it to meet PlungeAI's obligations with respect to Customer Personal Data, after giving the Customer notice and an opportunity to object (Section 6);
- at the Customer's direction, delete or return Customer Personal Data at the end of the Services, unless the law requires retention (Section 10);
- make available all information in its possession necessary to demonstrate its compliance (Section 11.1); and
- allow and cooperate with reasonable assessments by the Customer or its designated assessor (Section 11.2). Where the applicable law permits, PlungeAI may instead arrange for a qualified and independent assessor to assess its policies and technical and organizational measures using an appropriate and accepted control standard or framework, and shall provide the report of that assessment to the Customer on request.
(c) PlungeAI shall not process Customer Personal Data for targeted advertising or profiling on its own behalf, and shall not sell it within the meaning of any US Privacy Law.
12.7 Customer's obligations
The Customer is responsible for providing the notices, honoring the opt-out and other rights, and conducting the assessments that the US Privacy Laws require of a business or controller with respect to Customer Personal Data.
13. Liability
(a) EACH PARTY'S LIABILITY, TAKEN TOGETHER IN THE AGGREGATE, ARISING OUT OF OR RELATING TO THIS DPA, THE SCCS AND THE UK ADDENDUM, WHETHER IN CONTRACT, TORT OR UNDER ANY OTHER THEORY OF LIABILITY, IS SUBJECT TO THE EXCLUSIONS AND LIMITATIONS OF LIABILITY IN THE TERMS.
(b) ANY REFERENCE IN THE TERMS TO THE LIABILITY OF A PARTY MEANS THE AGGREGATE LIABILITY OF THAT PARTY UNDER THE TERMS AND THIS DPA TOGETHER. ACCORDINGLY, THE CAP ON LIABILITY IN THE TERMS (THE GREATER OF THE FEES PAID BY THE CUSTOMER TO PLUNGEAI IN THE 12 MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM AND USD 100) APPLIES ONCE, IN AGGREGATE, ACROSS THE TERMS AND THIS DPA, AND NOT SEPARATELY TO EACH.
(c) NEITHER PARTY SHALL BE LIABLE UNDER THIS DPA FOR ANY INDIRECT, CONSEQUENTIAL, SPECIAL, INCIDENTAL, EXEMPLARY OR PUNITIVE DAMAGES, OR FOR ANY LOSS OF PROFITS, REVENUE, BUSINESS, GOODWILL OR DATA, TO THE EXTENT EXCLUDED BY THE TERMS.
(d) THE EXCLUSIONS AND LIMITATIONS IN THIS SECTION 13 DO NOT APPLY TO THE LIABILITIES EXCLUDED FROM THEM BY THE TERMS: THE CUSTOMER'S OBLIGATION TO PAY FEES; A PARTY'S INDEMNITY OBLIGATIONS; LIABILITY FOR FRAUD, GROSS NEGLIGENCE OR WILLFUL MISCONDUCT; AND ANY LIABILITY THAT CANNOT BE LIMITED OR EXCLUDED UNDER APPLICABLE LAW.
(e) NOTHING IN THIS DPA OR THE TERMS LIMITS OR EXCLUDES ANY RIGHT OF A DATA SUBJECT UNDER THE SCCS, INCLUDING UNDER CLAUSE 3 AND CLAUSE 12 OF THE SCCS, OR THE LIABILITY OF EITHER PARTY TO A DATA SUBJECT UNDER THE SCCS.
14. Term, Survival and Changes
14.1 Term
This DPA takes effect when the Customer accepts the Terms, or on the later date on which PlungeAI first processes Customer Personal Data, and continues until PlungeAI has deleted all Customer Personal Data in accordance with Section 10.
14.2 Survival
Any provision of this DPA that by its nature is intended to survive the end of the Terms shall survive, including Sections 4, 7, 10, 11, 13 and this Section 14, and the obligations in this DPA shall continue to apply to any Customer Personal Data that PlungeAI retains under Section 10.3.
14.3 Changes to this DPA
(a) PlungeAI may update this DPA to reflect changes in Applicable Data Protection Law, in the guidance of a Supervisory Authority, in the Services or in its Subprocessors. PlungeAI shall post every change at https://www.plungeai.com/dpa and update the Version and the Last Updated date.
(b) PlungeAI shall not make a change that materially reduces the overall protection of Customer Personal Data, unless the change is required by law or by a Supervisory Authority.
(c) A material change takes effect 30 days after PlungeAI gives notice of it by email to the Account and in the Dashboard at https://www.plungeai.com/dashboard. A Customer that objects may close its Account before the change takes effect, and shall receive a refund of its unused paid balance in accordance with the Terms.
(d) Changes to Subprocessors follow Section 6 and are not changes to this DPA.
(e) If the European Commission, the UK Information Commission or the FDPIC adopts or approves a revised version of the SCCs, the UK Addendum or the Swiss changes, PlungeAI may update Annex 3 to incorporate it, and the revised version shall apply to Restricted Transfers from the date stated in that update.
14.4 Governing law and venue
Except as provided in Annex 3 for the SCCs and the UK Addendum, this DPA is governed by the governing law of the Terms, the laws of the State of Idaho, excluding its conflict-of-laws rules, and disputes arising from it are subject to the exclusive jurisdiction of the state and federal courts located in the State of Idaho, as provided in the Terms. Nothing in this Section 14.4 limits a Data Subject's right to bring a claim before the courts specified in Clause 18 of the SCCs.
14.5 Third-party rights
Except for Data Subjects' rights as third-party beneficiaries under Clause 3 of the SCCs, no person other than the Customer and PlungeAI has any right under this DPA.
14.6 Notices
Notices to PlungeAI under this DPA shall be sent to legal@plungeai.com. Notices to the Customer shall be sent to the Account email or, where this DPA so provides, to the Account owners.
14.7 Severability
If any provision of this DPA is held invalid or unenforceable, the remaining provisions shall remain in full force, and the invalid or unenforceable provision shall be limited to the minimum extent necessary to make it valid while preserving the parties' intent.
15. Annex 1: Description of Processing
15.1 Description
This Annex 1 is the description of processing required by Art. 28(3) GDPR, and Annex I.A and I.B of the SCCs.
| Item | Description |
|---|---|
| Parties | Data exporter and Controller: the Customer, or, where Section 2.2(b) applies, the Customer as Processor acting for the Third-Party Controller. Contact: the Account email. Activities: use of the Services under the Terms. Data importer and Processor: PlungeAI, Inc., Ketchum, Idaho, United States. Contact: legal@plungeai.com. Activities: provision of the Services under the Terms. |
| Subject matter | PlungeAI's provision of the Services the Customer uses under the Terms, as described for each Product in Section 15.2. |
| Nature of processing | Collection, recording, organization, structuring, storage, retrieval, consultation, use, analysis, transmission to the AI model providers, tools and connected services the Customer selects, generation of Output, human review where it forms part of the Product, restriction, erasure and destruction. |
| Purpose of processing | To provide, maintain, support and secure the Services for the Customer under the Terms and in accordance with the Customer's documented instructions under Section 3, including to troubleshoot errors and to prevent abuse of the Services. Customer Personal Data is not used to train or fine-tune any AI model. |
| Duration | For the term of the Terms, and thereafter until deletion under Section 10. |
| Categories of Data Subjects | (i) The Customer's users: its personnel, contractors and other individuals the Customer authorizes to use the Services. (ii) Individuals whose Personal Data appears in Customer Content: the people named in or affected by the prompts, files, code, messages, briefs and other content the Customer or its users submit or connect, which may include the Customer's customers, prospects, contacts, email recipients and end users of the bots and apps built with the Services. |
| Categories of Personal Data | (i) Identity and contact data, such as names, email addresses and roles. (ii) Account data, such as user identifiers, team membership and role assignments. (iii) Content data, such as prompts, Output, files, code, messages, briefs, brand material, comments and workflow definitions. (iv) Connected-account data, such as access tokens and the data the Customer chooses to read from connected services, including performance data from advertising and analytics accounts. (v) Usage and log data, such as IP addresses, browser user agents, timestamps, the model, tool or agent called, the amount used, the cost, the result status and the actions taken. (vi) Records of approvals and sign-offs, where a Product records them. (vii) Billing contact data. Card and bank details are processed by Stripe and are not stored by PlungeAI. |
| Sensitive Data | The Services are not intended for Sensitive Data. "Sensitive Data" means: special categories of Personal Data under Art. 9(1) GDPR; Personal Data relating to criminal convictions and offenses under Art. 10 GDPR; "sensitive personal information" under Cal. Civ. Code § 1798.140(ae); "sensitive data" under the other US Privacy Laws; government identification numbers; financial account, debit or credit card numbers, alone or with any code or password permitting access; account sign-in credentials, other than those the Services are designed to hold; precise geolocation; health, genetic and biometric data; protected health information as defined in 45 C.F.R. § 160.103 under the Health Insurance Portability and Accountability Act of 1996 ("HIPAA"); and Personal Data of children under the age of 13, or of any older age at which the law gives children's data special protection. The Customer shall not submit Sensitive Data to the Services unless PlungeAI has agreed in an Order Form to process it. |
| Frequency | Continuous, for as long as the Customer uses the Services. |
| Retention | Customer Content is kept until the Customer deletes it or the Services end, and is then deleted under Section 10. Within the Services: execution traces are kept for 7 days in the live store and then archived; audit logs for 90 days live and then archived; run records for 180 days live and then archived; and the billing ledger for 400 days live and then archived. Archives are kept while the Account is open and are deleted with it. Backups expire on their normal cycle. Records PlungeAI keeps as PlungeAI Business Data, such as invoices and tax records, are retained as stated in the Privacy Policy. |
| Subprocessors | The Subprocessors, the subject matter and nature of their processing, and their locations are listed at https://www.plungeai.com/subprocessors. Their processing lasts for the duration stated above, subject to each provider's retention under its terms as described on that list. |
15.2 Processing by Product
| Product | Processing of Customer Personal Data |
|---|---|
| One API | Routing the Customer's calls to the models, tools, connectors and agents the Customer selects behind one API key or the MCP server, returning the results, and recording usage and run records |
| Agency | Making, checking, reviewing and delivering marketing work and, where the Customer connects accounts, publishing it and measuring its performance |
| AI Consulting | Scoping, proposing, building, testing, delivering and running the AI systems the Customer orders |
| Ocean Code | Processing the model and tool calls that Ocean Code makes through One API on the code, files and instructions the Customer gives it. Processing on the Customer's own machine is outside this DPA (Section 2.1(c)) |
| Ocean Vibe | Building and running the apps the Customer describes and creates |
16. Annex 2: Technical and Organisational Measures
This Annex 2 describes the Security Measures under Section 5 and Annex II of the SCCs. PlungeAI may update them under Section 5.2.
| Control area | Measure |
|---|---|
| Access control | Staff tools sit behind a sign-in. Each staff request is checked against the staff member's role before it runs, and access is limited to the personnel who need it for their role. The most sensitive system operations can require an additional authenticator-code verification. Customer resources are protected by server-side access checks that decide who may read, run or change each resource. |
| Encryption in transit | Traffic to the Services is encrypted with TLS, and plain HTTP requests are redirected to HTTPS. Calls between PlungeAI's own services run over Cloudflare Service Bindings or are authenticated with signed requests that carry replay protection. |
| Encryption at rest | PlungeAI's databases and stored data run on Cloudflare, which encrypts them at rest. |
| Credential protection | OAuth tokens and keys for the accounts the Customer connects are encrypted with AES-256-GCM. API keys are stored only as SHA-256 hashes: the full key is shown once, when it is created, and cannot be read back; afterwards only its first characters and last four characters are kept, so the Customer can recognize it. When PlungeAI's systems detect a secret, such as a password or key, in an execution trace, they replace it with a marker before the trace is stored. Review and share links in Agency and AI Consulting are stored only as hashes. Full card numbers are never stored by PlungeAI. |
| Key handling | Encryption keys for stored credentials are derived for each user from a master key that is held in a secrets store outside PlungeAI's databases. Key versions are recorded, so that keys can be rotated and stored data re-encrypted under the new version. Changes to platform keys and the secrets vault are restricted to the most privileged staff roles. |
| Tenant separation | Every record is tied to the Customer it belongs to, and Customer Personal Data is scoped to the Customer's Account. The Services are designed so that one customer cannot reach another customer's data. Agency and AI Consulting keep their data in their own databases and file storage, apart from the rest of the platform, and each client sees only its own data. |
| Logging and monitoring | Every change staff make in PlungeAI's operator tools is recorded in an admin audit log. Execution traces, audit logs and run records are kept for the periods in Annex 1. Forms are protected against automated traffic, and requests pass through Cloudflare's network, which applies its protections against network attacks. |
| Availability and backups | The Services run on Cloudflare's distributed infrastructure. Cloudflare D1 databases provide point-in-time recovery for a limited period, and older records are archived to object storage under the retention schedule in Annex 1. Backups expire on their normal cycle and are used only to recover the Services. |
| Vulnerability management | Changes to production code are kept under version control and are reviewed by PlungeAI before they are committed and deployed. PlungeAI applies security fixes to its code and dependencies according to the severity of the risk, and sets rate limits to protect the Services. |
| Incident response | PlungeAI maintains a process to detect, contain, investigate and remediate security incidents, and to notify Customers of a Personal Data Breach in accordance with Section 7. Suspected incidents can be reported to legal@plungeai.com. |
| Personnel | Personnel with access to Customer Personal Data are bound by confidentiality, receive access only where their role requires it, and access Customer Content only in the circumstances in Section 4(c). Access is removed when it is no longer needed. |
| Subprocessor management | Subprocessors are engaged only under written terms, as described in Section 6, and are listed with their function, data and location at https://www.plungeai.com/subprocessors. Card and bank details are processed by Stripe and never stored by PlungeAI. |
| Retention and deletion | Records are kept for the periods in Annex 1, and Customer Personal Data is deleted at the end of the Services in accordance with Section 10. |
17. Annex 3: International Transfer Mechanisms
17.1 EU Standard Contractual Clauses
Where the transfer of Customer Personal Data from the Customer to PlungeAI is a Restricted Transfer subject to the GDPR, the SCCs are incorporated into this DPA and completed as follows:
| Item | Selection |
|---|---|
| Module | Module 2 (controller to processor), where the Customer is a Controller. Module 3 (processor to processor), where the Customer is a Processor acting for a Third-Party Controller. |
| Data exporter | The Customer |
| Data importer | PlungeAI, Inc., Ketchum, Idaho, United States |
| Clause 7 (docking clause) | Does not apply |
| Clause 8.5 (duration of processing and erasure or return) | Certification of deletion is provided on the Customer's written request, in accordance with Section 10.4 |
| Clause 8.9 (documentation and compliance) | Audits are conducted in accordance with Section 11 |
| Clause 9(a) (use of sub-processors) | Option 2, general written authorization. The time period for prior notice of an intended change is 30 days, in accordance with Section 6 |
| Clause 11(a) (redress) | The optional language does not apply |
| Clause 13(a) (supervision) | The competent Supervisory Authority under Clause 13(a): where the Customer is established in an EU member state, the Supervisory Authority responsible for ensuring the Customer's compliance with the GDPR; where the Customer is not established in an EU member state but has appointed a representative under Art. 27(1) GDPR, the Supervisory Authority of the member state in which that representative is established; and where the Customer is not established in an EU member state and is not required to appoint a representative under Art. 27(2) GDPR, the Supervisory Authority of one of the member states in which the Data Subjects whose Personal Data is transferred are located, as identified under Clause 13(a) |
| Clause 17 (governing law) | Option 1. The law of Ireland |
| Clause 18(b) (choice of forum and jurisdiction) | The courts of Ireland |
| Annex I.A (list of parties) | The parties, contacts, activities and roles stated in Annex 1. Each party is deemed to have signed the SCCs, including Annex I, on the date the Customer accepts this DPA |
| Annex I.B (description of transfer) | Annex 1 (Section 15) |
| Annex I.C (competent supervisory authority) | As stated for Clause 13(a) |
| Annex II (technical and organizational measures) | Annex 2 (Section 16) |
| Annex III (list of sub-processors) | The Subprocessors list at https://www.plungeai.com/subprocessors |
Under Module 3, the Customer conveys the Third-Party Controller's instructions to PlungeAI, and PlungeAI's obligations to the Third-Party Controller run through the Customer as described in Section 2.2(b), except where the SCCs require otherwise.
The terms of this DPA describe how PlungeAI performs its obligations under the SCCs. They do not vary the SCCs or reduce any right under them.
17.2 UK International Data Transfer Addendum
Where the transfer of Customer Personal Data from the Customer to PlungeAI is a Restricted Transfer subject to the UK GDPR, the SCCs apply as amended by the UK Addendum, which is incorporated into this DPA and completed as follows:
| UK Addendum table | Completion |
|---|---|
| Table 1 (Parties) | The start date is the date the Customer accepts this DPA. The exporter is the Customer and the importer is PlungeAI, Inc., with the details and contacts stated in Annex 1 |
| Table 2 (Selected SCCs, Modules and Selected Clauses) | The version of the approved EU SCCs incorporated by Section 17.1, including the Appendix Information, with the modules and clauses selected there |
| Table 3 (Appendix Information) | Annex 1A (list of parties): Annex 1 (Section 15). Annex 1B (description of transfer): Annex 1 (Section 15). Annex II (technical and organizational measures): Annex 2 (Section 16). Annex III (list of sub-processors): the Subprocessors list at https://www.plungeai.com/subprocessors |
| Table 4 (Ending this Addendum when the Approved Addendum changes) | Either party may end the UK Addendum as set out in Section 19 of the UK Addendum |
Part 2 of the UK Addendum consists of the Mandatory Clauses of the Approved Addendum, being the template Addendum B1.0 issued by the UK Information Commissioner and laid before Parliament in accordance with section 119A of the Data Protection Act 2018 on 2 February 2022, as revised under Section 18 of those Mandatory Clauses.
17.3 Swiss transfers
Where the transfer of Customer Personal Data from the Customer to PlungeAI is a Restricted Transfer subject to the FADP, the SCCs apply as completed in Section 17.1, with the following changes:
| Item | Change |
|---|---|
| Competent supervisory authority (Clause 13 and Annex I.C) | The FDPIC, insofar as the transfer is governed by the FADP. Where the transfer is governed by both the FADP and the GDPR, the Supervisory Authority under Section 17.1 for the GDPR, in parallel with the FDPIC for the FADP |
| References to the GDPR | References to the GDPR are to be understood as references to the FADP, insofar as the transfer is governed by the FADP |
| Member state (Clause 18(c)) | The term "member state" shall not be interpreted to exclude Data Subjects in Switzerland from bringing a claim in their place of habitual residence in Switzerland |
| Governing law and forum (Clauses 17 and 18(b)) | As stated in Section 17.1 |
17.4 Other jurisdictions
Where Applicable Data Protection Law in another jurisdiction requires a transfer mechanism for a transfer of Customer Personal Data to PlungeAI, the parties agree to rely on the mechanism recognized by that law that is closest in substance to the SCCs, and shall cooperate in good faith to complete it.
18. Contact
Send questions about this DPA, objections to Subprocessors, audit and information requests, and reports of a suspected Personal Data Breach to:
PlungeAI, Inc. Ketchum, Idaho, United States Email: legal@plungeai.com Website: https://www.plungeai.com
19. Related Documents
- Terms of Service (
pol-legal-terms): https://www.plungeai.com/terms - Privacy Policy (
pol-legal-privacy): https://www.plungeai.com/privacy - Acceptable Use Policy (
pol-legal-aup): https://www.plungeai.com/acceptable-use - Subprocessors (
pol-legal-subprocessors): https://www.plungeai.com/subprocessors
20. Revision History
| Date | Version | Author | Changes |
|---|---|---|---|
| November 16, 2026 | 1.0 | PlungeAI Legal | Initial publication |