Fluent service providers and sub-processors
Sub-Processors
Version 2026-05-04.1 · Effective May 4, 2026
Fluent uses a small number of third-party service providers to run the meetfluent.app waitlist and the Fluent early-access service. This page lists the providers in scope, what they do for us, where they process data, and how to find their privacy commitments. We update this list when material changes occur.
Current Sub-Processors
| Provider | Role | Data categories | Processing locations | Reference |
|---|---|---|---|---|
| Cloudflare, Inc. | Hosting, edge compute (Workers), database (D1), object storage (R2), Pages, security (WAF, rate limiting) | All Fluent service data: account records, domain memories, artifacts, waitlist data, request logs | Global edge network with primary processing in the United States; data may transit through other regions Cloudflare operates | Privacy policy |
| Stripe, Inc. | Payment processing, subscription management, customer billing portal | Customer email and billing identifiers, subscription and checkout references, payment instrument data (handled directly by Stripe; never received or stored by Fluent) | United States; Stripe also operates regionally for non-US customers | Privacy policy |
What Is Not A Sub-Processor
Some services that interact with Fluent are not Fluent sub-processors because we do not direct their processing. They are third-party services you authorize and use under their own terms.
- AI assistants you connect (Claude, ChatGPT, Cursor, Codex, Claude Code, and similar): when you connect an assistant to Fluent through the Model Context Protocol with OAuth, the assistant acts as a client on your behalf. Content sent to the assistant provider is governed by that provider's terms and privacy policy. We recommend reviewing the assistant provider's data and training policy before connecting.
- Open-source software running in our environment (such as the Better Auth library and other libraries listed in the project's source code): these execute inside Fluent's own infrastructure and do not receive data outside it. The hosting provider for that infrastructure is listed above.
- Open-source self-run runtime: if you run the Fluent open-source runtime in your own environment, the providers you choose for that environment are your sub-processors, not ours. Fluent does not see data that stays in your self-run runtime.
Changes To This List
We will update this page when we add or change a sub-processor that materially affects how user data is handled. The version string at the top of this page identifies the current version. Where required by law or contract, we will provide advance notice through email or another reasonable channel.
Contact
Questions about a sub-processor or our data-protection arrangements with one can be sent to [email protected].