Last updated 10 October 2026.
This page lists the Providers currently engaged by Generative Chaos LLC to process Service Data on our behalf, by the categories set out in section 4.1 of our Privacy Policy.
This list is maintained here rather than in the Policy so that a change of Provider within a category does not require the Policy itself to be amended. The categories, the data disclosed and the purposes in section 4.1 continue to govern in every case, and section 4.3 applies to every Provider below: none may use your User Content to train, fine-tune or otherwise develop its own models.
Every Provider below is bound by a data processing agreement with Generative Chaos LLC, in force today. The last column links to the text of that agreement as the Provider publishes it.
| Category | Provider | Established in | Data processing agreement |
|---|---|---|---|
| Speech-to-text | ElevenLabs, Inc. | United States | In force |
| Speech-to-text | Soniox Inc. | United States | In force (signed 8 October 2026) |
| Language models | OpenAI OpCo, LLC | United States | In force |
| Language models | Anthropic PBC | United States | In force |
| Cloud infrastructure | Cloudflare, Inc. | European Union and United States | In force |
| Product analytics | PostHog, Inc. | European Union and United States | In force |
| Payment processing | Stripe, Inc. | United States | In force |
Files attached to a meeting may reach two categories. Every file held with a meeting — one you attached yourself, one taken with the Service's own camera, or one you confirmed from your device's photo library — is held by the cloud infrastructure Provider. Where we are able to read a file, it is also disclosed to a language-model Provider, in order to write the summary of that meeting — a photograph is looked at, a document is read as its text — and where a photograph was taken during the recording and the recording's own clock can place it, the point in the recording at which it was taken is disclosed with it. Not every file can be read and not every file is; one that is not reaches the cloud infrastructure Provider and nobody else. No file is ever sent to a speech-to-text Provider. Paragraph 3.1a of the Privacy Policy says the same thing from the other side.
Payment processing applies only to a plan paid for at chui.io. The payment processor receives what you give it directly — your name, your email address and your payment details — together with the identifiers of your account or company and of your agreement to the terms of purchase, and the name of your company where it is the company that pays; it receives no User Content. For preventing fraud and meeting the financial rules that bind it, it is also a controller in its own right, as section 4.1 of the Privacy Policy says. A subscription bought inside an application from the Apple App Store or Google Play is paid to Apple or Google, who sell it in their own right and are not listed here in that capacity.
We may change or add a Provider within a category — for example, engaging a different speech-to-text engine. Where we do, this page is updated. Where a change materially affects how User Content is processed, we will also give notice within the application, as section 17 of the Privacy Policy requires.
Where our Data Processing Addendum applies — that is, where the account belongs to an organisation acting as a controller — clause 4.4 of it requires reasonable advance notice of any addition or replacement, given before the new Provider begins, and gives that organisation a right to object.
Questions about this list: privacy@chui.io