Effective 24 October 2026

Subprocessors

Who else handles data so the Service can work, and exactly what they receive.

1. Current subprocessors

These providers process personal data on our behalf to run Flare Reply. Each is bound by a written agreement to protect the data and use it only to provide its service to us.

ProviderPurposeDataLocation
SupabaseDatabase and authentication, including sign-in and invitation emailsAccount data, workspace data and lead dataRegion chosen for the project
VercelApplication hosting and request logsAll data passing through the app; IP addresses in logsMumbai, India (bom1) and edge network
InngestBackground job processing (lead processing, retries, sync)Job inputs and results: record IDs, outcomes and the lead details alerts need (such as name and campaign); never access tokensUnited States
Meta PlatformsLead Ads, Pages, Marketing API, Conversions API and WhatsApp Cloud APILead IDs, hashed email and phone, CRM stage names, WhatsApp messagesGlobal
AnthropicAI lead scoring (Claude API)Lead form answers and the business descriptionUnited States
GoogleSign in with Google, and Google Sheets sync when a business turns it onFor sign-in, Google sends us the person’s name, email address and profile photo; for sync, the lead rows the business chooses to syncGlobal
ResendAlert and notification emails (new leads, failed events, verification codes)Email addresses and alert contentsUnited States
TelegramAlerts, when a business turns them onAlert contents (lead name, phone, campaign)Global
RazorpaySubscription billingBilling contact and payment details (card or UPI data is handled by Razorpay, not stored by us)India

Meta, Google, Telegram and Razorpay are used only when a customer turns on the related feature.

2. Changes

We update this page before a new subprocessor starts handling personal data. Customers who want advance notice by email, or want to object to a change, can write to the email address shown in your account; see section 7 of the Data Processing Addendum.