Legal

Sub-processors

RingLeadAI uses the third parties below to run the service. Each one processes customer data only to the extent needed for the purpose stated, under a contract that requires it to protect that data. We do not sell customer data, and no sub-processor is permitted to use it for its own purposes.

Last updated: September 8, 2026

Sub-processors we use

These are used by every account. All processing takes place in the United States.

  • Amazon Web Services (AWS) — Application hosting and compute. United States (us-east-1).
  • Supabase — Managed PostgreSQL database and object storage. United States (us-east-1).
  • Stripe — Payments, subscriptions and invoicing. United States.
  • Resend — Transactional email (account, billing and system notices). United States.
  • Twilio — Telephony — outbound and inbound call carriage. United States.
  • Telnyx — Telephony — phone numbers and SIP carriage. United States.
  • LiveKit — Real-time audio transport for AI voice calls. United States.
  • Deepgram — Speech-to-text for AI voice calls. United States.
  • Cartesia — Text-to-speech for AI voice agents. United States.
  • ElevenLabs — Text-to-speech for AI voice agents (optional). United States.
  • Anthropic — Language models for drafting and reply handling. United States.
  • OpenAI — Language models for classification, scoring and transcription. United States.
  • Sentry — Application error monitoring. United States.

Integrations the customer connects

These are used only if the customer chooses to connect them, with the customer's own account or API key. Data flows to them because the customer asked it to, and disconnecting stops it.

  • Slack — Delivers notifications to a channel the customer chooses.
  • HubSpot — Two-way sync of leads and activity.
  • Pipedrive — Two-way sync of people and activity.
  • Cal.com — Calendar availability and meeting booking during AI calls.
  • Apollo — Lead enrichment, using the customer's own API key.

Language models and customer data

Anthropic and OpenAI are called through their business APIs, under terms that do not permit customer data to be used to train their models. We do not host or fine-tune any model, and no model is trained on customer data. Each request carries only the data of the single organization it belongs to.

Data received from a connected integration is never sent to a language model. In particular, the Slack integration is delivery-only: RingLeadAI reads no Slack messages, channels or user profiles, so no Slack content reaches a model.

Where data is stored

Customer data is held in the United States, in the AWS US East (N. Virginia) region. It is encrypted in transit and at rest, and access tokens and API keys are additionally encrypted by the application before they are stored.

Changes to this list

We update this page when a sub-processor is added or removed. Customers with an active subscription can ask to be notified of changes in advance by writing to legal@ringleadai.com, which is also the address for any question about this list or for a copy of our data processing terms.