SUBPROCESSORS

Infrastructure and provider transparency.

This page lists the third-party services Lingivo is designed to use for controlled beta and production workflows. Final customer contracts should confirm the active subprocessors for each deployment.

Render

Hosting and web service deployment for the Lingivo website, app, and backend API.

Supabase

Authentication and Postgres database services for users, organizations, memberships, projects, credits, audit logs, and workspace data.

OpenAI

AI processing for configured Lingivo Precision/OpenAI translation, LQA, glossary, analyzer, and style-guide workflows. Lingivo should use API/business terms that do not train on customer content by default unless the organization explicitly opts in.

Stripe

Payment processing, checkout, subscription/payment events, and credit fulfillment webhook events when billing is enabled.

Anthropic and Google Gemini

Provider connectors are scaffolded for future enterprise policy options. They should remain disabled until structured-output requests, privacy terms, and customer approvals are completed.

Customer-owned providers

Enterprise customers may choose customer-owned AI provider policy where available. In that mode, provider credentials should remain private backend environment variables, not browser settings or database fields.