Subprocessors & Third-Party Services

Last updated August 2026

ℹ️ This is a complete list, not a sample — the LLM Connect codebase touches exactly the services below. No analytics vendor, ad network, payment processor, cloud storage provider, or AI vendor is integrated anywhere in this application.
ServiceWhat it's used forWhat it receives
Your own hosting provider Runs the application (PHP), database (MySQL/MariaDB), and stores uploaded files on local disk Everything — this is your infrastructure. [Fill in: your actual hosting provider's name for a real deployment.]
Google Fonts (fonts.googleapis.com) Loads the Fraunces, Inter, and IBM Plex Mono typefaces used in the interface Standard web request metadata (including IP address) when a visitor's browser fetches the font files directly from Google — see Cookie Policy
Public STUN servers (stun.l.google.com, by default) Helps two browsers discover how to connect directly for a video/audio call (a standard, required part of how WebRTC works) Only the technical information needed to establish a connection (public IP/port) — never your call's audio, video, or chat content, which travels directly between participants
Your outgoing mail transport (PHP mail() by default) Sends account emails: verification, password reset, parental consent requests, deletion confirmations Whatever your hosting provider's mail configuration routes through — typically your own domain's mail server

If you add a new one

Adding any new third-party service — analytics, payments, customer support chat, an AI vendor, cloud storage — should come with an update to this page and, likely, to the Privacy Policy's itemized notice, since DPDP requires disclosing new processing purposes before or when they start, not after the fact.