PlungeAI · Legal

Subprocessors

Version 1.0 · Effective November 16, 2026 · Last updated November 16, 2026

PlungeAI, Inc. — Company Legal Framework

Company
PlungeAI, Inc.
Registered Office
Ketchum, Idaho, United States
Legal Contact
legal@plungeai.com
Website
https://www.plungeai.com
Document ID
pol-legal-subprocessors
Version
1.0
Effective Date
November 16, 2026
Last Updated
November 16, 2026
Classification
Public
Review Schedule
Annual
Applies To
Third parties that process Personal Data on PlungeAI's behalf for any PlungeAI Product

This Subprocessors list (this "List") identifies the third parties that PlungeAI, Inc. ("PlungeAI", "we", "us") engages to process Personal Data on its behalf in providing the Services, together with the purpose of each engagement, the Personal Data concerned, the location of processing, the transfer safeguard relied on, and the Products affected. This List forms part of the Data Processing Addendum (pol-legal-dpa) between PlungeAI and each Customer. By entering into the DPA, the Customer gives PlungeAI general written authorization to engage the Subprocessors named in this List, subject to the notice and objection rights in Section 8.

1. Purpose and Scope

1.1 What a Subprocessor Is

(a) A "Subprocessor" is any third party that PlungeAI engages to process Customer Personal Data on PlungeAI's behalf in providing the Services. Where PlungeAI acts as a processor for the Customer, a Subprocessor is "another processor" within the meaning of Art. 28(2) and Art. 28(4) of Regulation (EU) 2016/679 (the "GDPR") and of the UK GDPR.

(b) Under Art. 28(2) GDPR, PlungeAI engages a Subprocessor only with the Customer's general written authorization, which the DPA gives for the Subprocessors named in this List, and informs the Customer of any intended addition or replacement so that the Customer can object (Section 8).

(c) Under Art. 28(4) GDPR, PlungeAI imposes on each Subprocessor, by written contract, data protection obligations at least as protective as those in the DPA (Section 2.2).

(d) For the purposes of the California Consumer Privacy Act, as amended (Cal. Civ. Code § 1798.100 et seq.), each Subprocessor receives personal information as PlungeAI's service provider within the meaning of Cal. Civ. Code § 1798.140(ag). PlungeAI does not sell or share personal information.

(e) A third party is not a Subprocessor when the Customer, or a user acting for the Customer, sends Personal Data to it under the Customer's own contract with that third party. Sections 4.5 and 7 describe these cases.

1.2 Relationship to Other Documents

(a) Capitalized terms used but not defined in this List have the meanings given in the Terms of Service (pol-legal-terms) or the DPA. "Services", "Account", "Customer Content", "Output", "Personal Data", "Product", "Product Terms", "Order Form" and "Subprocessor" have the same meaning in this List as in every other PlungeAI legal document.

(b) The DPA governs PlungeAI's processing of Customer Personal Data as a processor, including the obligations PlungeAI passes on to Subprocessors. This List names the Subprocessors that the DPA authorizes.

(c) The Privacy Policy (pol-legal-privacy) describes how PlungeAI processes Personal Data as a controller, including Account and billing data. The third parties named in this List also support that processing.

1.3 Agency and AI Consulting

(a) Agency and AI Consulting each have their own Product Terms, data processing terms and Subprocessor list, published on the Product's own site:

Product Subprocessor list Product Terms
Agency https://agency.plungeai.com/security#subprocessors https://agency.plungeai.com/terms
AI Consulting https://consulting.plungeai.com/security#subprocessors https://consulting.plungeai.com/terms

(b) For those Products, the Product's own data processing terms and Subprocessor list prevail over the DPA and this List, in accordance with the order of precedence in the Terms of Service. Section 6 reproduces the Subprocessors specific to those Products for completeness.

2. How We Engage Subprocessors

2.1 Due Diligence

Before a Subprocessor processes Customer Personal Data, PlungeAI shall assess its security, confidentiality and data protection practices, in proportion to the Personal Data it will process and the risk to data subjects. PlungeAI shall engage only Subprocessors that provide sufficient guarantees to implement appropriate technical and organizational measures, as Art. 28(1) and Art. 32 GDPR require.

2.2 Written Terms

(a) Each Subprocessor shall be bound by written terms that are at least as protective of Customer Personal Data as the DPA, including the obligations listed in Art. 28(3)(a)–(h) GDPR.

(b) Each Subprocessor shall process Customer Personal Data only for the purpose stated for it in this List.

(c) PlungeAI remains responsible to the Customer for each Subprocessor's performance of its data protection obligations, as Art. 28(4) GDPR provides, subject to the limitations of liability in the Terms of Service and the DPA.

2.3 Transfer Safeguards

(a) Where a Subprocessor processes Customer Personal Data outside the European Economic Area, the United Kingdom or Switzerland in a transfer that Chapter V GDPR, or its UK or Swiss equivalent, restricts, PlungeAI shall make the transfer under the safeguard stated for that Subprocessor in this List.

(b) In the tables below, "SCCs" means the Standard Contractual Clauses approved by Commission Implementing Decision (EU) 2021/914, Module 3 (processor to processor), together with the UK International Data Transfer Addendum (version B1.0) for transfers from the United Kingdom and the adaptations required by the Swiss Federal Act on Data Protection for transfers from Switzerland.

(c) The DPA sets out the transfer terms between PlungeAI and the Customer.

2.4 Review

(a) PlungeAI shall review this List, and each Subprocessor's terms and practices, at least annually, in line with this List's Review Schedule.

(b) PlungeAI shall also review a Subprocessor when it learns of a material change in that Subprocessor's terms, security practices or locations of processing, or of a security incident affecting Customer Personal Data.

(c) PlungeAI may stop using a Subprocessor at any time. When it does, PlungeAI shall update this List.

3. Infrastructure and Operations

These Subprocessors support the Services as a whole.

Subprocessor Purpose Personal Data Location Transfer Safeguard Products
Cloudflare, Inc. Hosting of PlungeAI's websites, applications and services; data storage in D1 databases, KV and R2; bot protection on forms (Turnstile); cookieless visit counts (Web Analytics) All Personal Data the Services hold, including Account details, Customer Content, Output, run records, files and logs, and Turnstile challenge data United States: Workers placed in the San Jose region and database primaries in western North America. Requests reach Cloudflare's global network at the location nearest the user SCCs All Products
Stripe, Inc. Card and US bank (ACH) payments, One API top-ups, subscriptions, invoices and refunds Billing contact details, card or bank details (held by Stripe only; PlungeAI never stores full card numbers), and invoice lines United States SCCs One API, Agency, AI Consulting (all paid Products)
Resend, Inc. Delivery of the email PlungeAI sends, including sign-in codes, notices and invoices The recipient's email address, the message text and its links United States SCCs All Products

4. Artificial Intelligence Model Providers

These Subprocessors operate the artificial intelligence models that the Services make available. A provider processes a request only when a model it serves handles that request.

Subprocessor Purpose Personal Data Location Transfer Safeguard Products
Anthropic Claude models The prompts, files and other content in the request, and the model's response United States SCCs One API, Ocean Code, Ocean Vibe
OpenAI GPT and other OpenAI models The prompts, files and other content in the request, and the model's response United States SCCs One API, Ocean Code, Ocean Vibe
Google Gemini, Imagen and Veo models The prompts, files and other content in the request, and the model's response United States SCCs One API, Ocean Code, Ocean Vibe
Mistral AI Mistral models The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
Cohere Command and embedding models The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
DeepSeek DeepSeek models The prompts, files and other content in the request, and the model's response China SCCs One API, Ocean Code, Ocean Vibe
xAI Grok models The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
Perplexity Sonar models The prompts, files and other content in the request, and the model's response United States SCCs One API, Ocean Code, Ocean Vibe
Moonshot AI Kimi models The prompts, files and other content in the request, and the model's response China SCCs One API, Ocean Code, Ocean Vibe
Meta Meta models The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
NVIDIA Models hosted on NVIDIA's API The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
Groq Hosting of open models The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
Cerebras Hosting of open models The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
Together AI Hosting of open models The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
Fireworks AI Hosting of open models The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
DeepInfra Hosting of open models The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
TypeSafe Jev decision models, reached through Cloudflare Workers AI or through OpenRouter The state and questions in the request, and the model's answers United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe
OpenRouter Aggregation and routing of requests to models served by other providers (Section 4.4) The prompts, files and other content in the request, and the model's response United States and other countries where the provider operates SCCs One API, Ocean Code, Ocean Vibe

Anthropic, Google and OpenAI also process Personal Data for Agency and AI Consulting, as described in Section 6.

4.1 The Customer Chooses the Model

(a) In One API, the Customer chooses the model for each request. Ocean Code runs on the Customer's own machine and calls models through One API, so the Customer chooses the model for each of its requests in the same way.

(b) A request, and the Personal Data in it, goes only to the provider that serves the model chosen for that request. Which of the providers in this Section process the Customer's Personal Data therefore depends on the models the Customer chooses.

4.2 Models Served by More Than One Provider

Where the Customer chooses a model that more than one provider in this Section serves, PlungeAI may route the request to any of those providers. A provider for which the Customer has supplied its own key is tried first (Section 4.5). The x-ocean-route header of each response names the model and provider of each attempt.

4.3 Where the Provider of Each Model Is Shown

The model list at https://www.plungeai.com/docs shows the provider of each model, including whether a model is reached through OpenRouter.

4.4 OpenRouter

OpenRouter acts as an aggregator. When the Customer chooses a model that is reached through OpenRouter, OpenRouter receives the request and routes it to an underlying provider that serves the model. That underlying provider also processes the request, as OpenRouter's subprocessor, under OpenRouter's terms with it.

4.5 The Customer's Own Provider Key or Account

When the Customer supplies its own key or account for a model provider, requests made with that key or account are processed by the provider under the Customer's own contract with it. For those requests, the provider is not PlungeAI's Subprocessor, and PlungeAI acts only to transmit the request and return the response.

4.6 Provider Terms

(a) Each provider in this Section processes the data it receives under its own API or business terms, including its terms on data retention and on the use of data to improve its models.

(b) PlungeAI selects API offerings and settings intended for business use. PlungeAI does not use Customer Content or Output to train or fine-tune any artificial intelligence model and does not license it to anyone for training.

(c) The Customer should review the relevant provider's terms before sending Personal Data to its models.

5. Search and Tool Providers

One API offers tools that call outside services. When the Customer, or an agent acting for the Customer, uses such a tool, the request goes to that tool's provider. The platform's web search tool sends each query to the following search engines.

Subprocessor Purpose Personal Data Location Transfer Safeguard Products
Brave Web search (Brave Search) The search queries an agent writes United States SCCs One API, Ocean Code, Ocean Vibe, AI Consulting
Tavily Web search The search queries an agent writes United States SCCs One API, Ocean Code, Ocean Vibe, AI Consulting
Exa Web search The search queries an agent writes United States SCCs One API, Ocean Code, Ocean Vibe, AI Consulting
Perplexity Web search with answers (Sonar) The search queries an agent writes United States SCCs One API, Ocean Code, Ocean Vibe, AI Consulting

AI Consulting uses these search engines when its agents research a prospect or a research question for the Customer.

6. Product-Specific Subprocessors

In Agency and AI Consulting, PlungeAI chooses the models that perform the work. The following Subprocessors therefore process Personal Data for those Products whether or not the Customer uses One API itself. Each Product's own Subprocessor list (Section 1.3) governs for that Product.

Subprocessor Purpose Personal Data Location Transfer Safeguard Products
Anthropic Claude models that write, check and judge the work, and run the chat in the AI Consulting portal and dashboard Briefs, brand profiles, approved claims, intake answers, findings, engagement records, chat messages, and the images being checked United States SCCs Agency, AI Consulting
Google Gemini, Imagen and Veo models that write and render images and video Briefs, brand profiles, image and video prompts written from the Customer's brief, and the images and clips made from them United States SCCs Agency, AI Consulting
OpenAI GPT models on which a bot that PlungeAI builds for the Customer may run, when PlungeAI chooses one for it The bot's test cases and answers, and, after delivery, the messages the Customer's own customers send to the bot United States SCCs AI Consulting
Slack Delivery of review and digest notices to a Slack channel the Customer connects The notice text, without links to the work United States SCCs Agency, only when the Customer connects a channel

7. Connected Accounts You Direct

7.1 Sign-In and Connections

Several Products let the Customer sign in with, or connect, its own accounts with Google (including Gmail, Drive, Calendar, Google Ads and Google Analytics), Microsoft, GitHub or Slack. When the Customer does so, the Customer decides which data flows between that account and PlungeAI, and the provider processes that data under the Customer's own contract with it. For that data, the provider is not PlungeAI's Subprocessor and is not listed in Sections 3 to 6.

7.2 Ocean Code

Ocean Code runs on the Customer's own machine. An account the Customer connects to Ocean Code, such as Slack, exchanges data directly with the Customer's machine.

7.3 Product Lists

Where a Product's own Subprocessor list names a provider for an activity described in this Section, such as the Agency Slack notices in Section 6, that list governs for that Product.

7.4 Disconnection

The Customer may disconnect a connected account at any time. The Privacy Policy describes how PlungeAI handles data from connected accounts.

8. Notice of Changes and Right to Object

8.1 Notice of a New Subprocessor

(a) PlungeAI shall give at least 30 days' notice before a new Subprocessor begins to process Customer Personal Data. The same notice applies when a Subprocessor replaces another.

(b) PlungeAI gives notice by updating this List, with the new Subprocessor's purpose, Personal Data, location, transfer safeguard and Products, and by emailing the owners of each Account at the Account email.

8.2 Subscribing to Notices

Any person may ask to receive notices under this Section at an additional email address by writing to legal@plungeai.com.

8.3 Objection

(a) The Customer may object to a new Subprocessor on reasonable grounds relating to the protection of Personal Data. To object, the Customer shall send a written notice to legal@plungeai.com within the 30-day notice period that names the Subprocessor and states the grounds for the objection.

(b) PlungeAI shall consider the objection in good faith and discuss it with the Customer. Together the parties shall seek a reasonable alternative, such as a change in the Customer's configuration or use of the affected Service that avoids processing of Customer Personal Data by that Subprocessor.

(c) If no alternative is agreed, the Customer may terminate the affected Service by written notice to legal@plungeai.com. PlungeAI shall then refund, on a pro-rata basis, any fees the Customer has prepaid for the terminated Service. For One API, PlungeAI shall refund the unused paid balance in accordance with the Terms of Service.

(d) If the Customer does not object within the 30-day notice period, the Customer is deemed to authorize the new Subprocessor under the DPA's general written authorization.

8.4 No Emergency Replacement

PlungeAI does not use an emergency replacement procedure. Every new or replacement Subprocessor is subject to the full 30-day notice in Section 8.1, including where an existing Subprocessor must be replaced urgently. Removing a Subprocessor requires no advance notice; PlungeAI updates this List when it does so.

8.5 Agency and AI Consulting

For Agency and AI Consulting, notice of a new Subprocessor and the right to object follow that Product's data processing terms (Section 1.3).

9. Contact

Questions about this List or about PlungeAI's Subprocessors, objections under Section 8.3 and requests under Section 8.2 should be sent to:

PlungeAI, Inc. Ketchum, Idaho, United States Email: legal@plungeai.com Website: https://www.plungeai.com

11. Revision History

Date Version Author Changes
November 16, 2026 1.0 PlungeAI Legal Initial publication