Subprocessors
Last updated: July 2, 2026
To provide Salf AI, we rely on the third parties listed below to process customer data on our behalf. This list supplements our Privacy Policy and applies to all Salf plans.
Core subprocessors
| Vendor | Purpose | Data processed | Location |
|---|---|---|---|
| Lovable | Application platform, hosting, edge runtime, database, authentication, and product/authentication email delivery. Lovable's platform runs on Supabase and Cloudflare infrastructure. | Account, application, and operational data; authentication events; server logs. | United States (Cloudflare edge, Supabase primary region). |
| Lovable AI Gateway | Routes large-language-model requests to underlying model providers (currently Google Gemini) for classification, extraction, and drafting. Requests under our agreement are not used to train the underlying models. | Prompts and context passed with them (e.g., inbound reply text after PII redaction, company descriptions, meeting-extraction inputs); model responses. | United States. |
| Salf AI SDR Backend (Render, Inc.) | Salf-operated inference microservice hosted on Render, Inc. It orchestrates Anthropic Claude requests used by the reply-classification, reply-drafting, meeting-extraction, campaign-generation, and contact-enrichment features. Only inputs required for the invoked feature are sent; PII (card numbers, SSNs, IBANs, phone numbers) is redacted before transmission. | Sanitized, PII-redacted inbound email text, reply subject/sender, campaign context, and generated model output. Transported over TLS with a shared bearer secret. Render has confirmed that HTTP request bodies are not stored in Render's platform logs (only request metadata is logged, retained per plan: Hobby 7 days / Pro 14 days / Scale or Enterprise 30 days) and that Render does not train models on any nonpublic customer data, including private service logs or metrics. A GDPR DPA is available to all Render workspaces via the Render dashboard; SOC 2 and ISO 27001 reports are available on Pro-or-higher plans under NDA. | United States (Render, Inc.) and the underlying Anthropic API region. |
| Google LLC | Gmail API (send/read on your behalf) and Google Calendar API (create/update events), only after you connect your Google account. | Message metadata and bodies you authorize Salf to read or send; calendar events created by Salf. | United States and global Google infrastructure. |
| Apollo.io | B2B contact and company enrichment, and on-demand phone-number reveal. | Company domains, prospect names/titles/emails, and enrichment responses. Phone reveal is only invoked when you explicitly click Reveal. | United States. |
| Stripe, Inc. | Payment processing, subscription management, and hosted billing portal. | Billing name, address, email, tax IDs (where applicable), and payment card details, all collected by Stripe directly. Salf stores only Stripe IDs, plan/status, and invoice metadata. | United States. |
Notice of new subprocessors
We may add or replace subprocessors as the Service evolves. When we do, we will update this page. Customers on annual or enterprise plans who want advance notice of new subprocessors can email us at privacy@salf.ai to be added to the notification list.
Where Salf operates from
Salf is operated from Ontario, Canada. Our subprocessors are primarily located in the United States. See Section 12 of our Privacy Policy for international-transfer details.