Fieri relies on a small set of infrastructure and platform providers. The provider involved depends on the feature, platform, and current deployment.
Service-provider access is not a sale. These systems process information to deliver, secure, bill, or observe Fieri. Fieri does not authorize them to use conversation or voice content for targeted advertising.
| Provider or system | Purpose | Information involved |
|---|---|---|
| netcup (Germany; Fieri-operated deployment) | Application API, PostgreSQL databases, Redis security and event functions, background jobs, speech and text-to-speech services, waitlist storage, self-hosted Postal email delivery, and operational tooling. | Account identifiers, product content, transcripts, audio, voice references, waitlist email and attribution data, email delivery and suppression metadata, security events, and technical metadata as required by the feature. |
| Cloudflare | Public website and waitlist-endpoint network delivery and protection, plus R2 object storage for account-linked audio, generated speech, and images. | IP address and request metadata; waitlist email and referral or campaign metadata in transit when submitted; object identifiers, voice samples, generated audio, sealed-note audio, and profile images. |
| Groq | OpenAI-compatible large-language-model inference used to generate or analyze text. | Prompts, conversation context, user text, generated output, and request metadata. |
| LiveKit | Real-time room and audio transport for live voice conversations. | Room and participant identifiers, connection metadata, and live audio. |
| Ory Kratos | Account authentication and identity workflows. Fieri may operate this software on its own infrastructure. | Email address, identity identifier, verification status, sessions, and authentication metadata. |
| Langfuse | AI reliability, cost, quality, and debugging observability. Fieri may operate this software on its own infrastructure. | Conversation identifiers, model metadata, latency, token use, scores, and, where enabled for a relevant flow, prompt or response content. |
| Sentry-compatible error monitoring | Application error detection, diagnostics, and incident response. Current deployments may use a self-hosted compatible service such as GlitchTip. | Error details, request and device metadata, release version, and diagnostic context. |
| RevenueCat | Subscription entitlement, purchase restoration, webhook processing, and customer subscription tools when paid features are enabled. | Fieri user identifier, app/store identifiers, product, entitlement, transaction, renewal, and subscription status. |
| Novu | Notification subscriber and delivery orchestration when notifications are enabled. | User identifier, delivery address or device token, notification preferences, and message metadata. |
| Apple and Google | App distribution, platform authentication, in-app purchases, subscription management, refunds, and platform services. | Platform account or authentication token, app and device metadata, product and transaction information. Apple and Google also act under their own terms and privacy policies. |
Speech providers
Speech-to-text and text-to-speech can be provided by Fieri-operated models or by a configured OpenAI-compatible endpoint. Audio and transcripts are sent only to the systems needed for the requested voice feature. Because deployment can change during provider failover, the app's feature disclosure and this page describe the processing category as well as the named current systems.
Provider changes
Fieri may replace a provider or add one to improve reliability, security, or functionality. We will update this page before or promptly after a material production change. If a change creates a materially different use of personal information, Fieri will provide additional notice or request consent where required.
Questions
For the provider used by a specific feature, data-location questions, or a copy of information available about contractual safeguards, email support@thefieriapp.com.