Legal

Sub-processors

To run Lindy we rely on a small set of trusted third parties that process customer data on our behalf. This page lists them and what each is used for. We keep it current as our providers change.

Last updated 8 October 2026 6 sub-processors
Before AI processing

Before meeting content is sent to the AI service for processing, the names and email addresses of participants are removed and replaced with anonymous labels, and restored only inside Lindy after a result is returned. Your content is not used to train models; Google may retain Gemini API prompts for a limited period solely for abuse monitoring under its terms, and Lindy deletes batch-processing jobs once results are retrieved. See our Privacy Policy for full detail on how your data is handled.

Sub-processorPurposeMore information
GoogleGoogle LLC / Google Ireland Calendar, Drive and Gmail APIs for reading the meetings and notes you connect (Gmail: meeting-notes messages only); Google Gemini for AI task extraction when Fireworks AI is unavailable. Google sub-processors
Fireworks AIFireworks AI, Inc. AI task extraction: reads masked meeting and message content (names and emails replaced with labels) to find tasks, promises and decisions. Not used to train models. Fireworks AI privacy policy
ClerkClerk, Inc. User authentication and session management. Clerk sub-processors
ChargebeeChargebee, Inc. Subscription management and billing. Chargebee sub-processors
ZiinaZiina Payment LLC Payment processing. Ziina privacy policy
LoopsLoops, Inc. Transactional and product email delivery. Loops privacy policy
PostHogPostHog, Inc. Product analytics, error tracking and session replay (all on-screen text and inputs masked) to keep the service secure and improve it. PostHog privacy policy

Questions about our sub-processors? Email info@lindyhq.com.