Legal
Lovelio Sub-Processors
Last updated: 28 August 2026 - Lovelio Pty Ltd ACN 701 461 298
Third parties that process Lovelio customer data on our behalf.
Lovelio uses the following sub-processors to deliver its Recruitment Automation Platform. A sub-processor is any third party that processes customer data on Lovelio's behalf. This list is current as of 28 August 2026. We will update it before onboarding any new sub-processor, and existing customers receive 30 days' notice of any material change.
Current sub-processors
| Name | Purpose | Data handled | Location |
|---|---|---|---|
| Supabase, Inc. | Primary database, authentication, and object storage. | All customer and candidate records at rest, including resumes and interview notes. | The customer-selected Sydney, London, or United States project region, plus the separate platform directory project for limited account-routing records. |
| Amazon Web Services, Inc. | Regional migration infrastructure, including encrypted source-backup storage, migration compute, secrets, and operational logs. | Customer-supplied migration backups, migration artifacts, provider transfer credentials, and migration task logs while a managed data migration is in progress or retained under the migration policy. | Sydney, London, or the western United States, matching the customer migration region. |
| Anthropic, PBC | Large language model processing for resume parsing, application assessment, candidate summaries, and drafting of emails, offers, and job specifications. | Resume text, job descriptions, candidate notes, and prompts passed to the model. Anthropic does not use data sent via the API to train its models. | United States. |
| OpenAI | Optional large language model processing where the relevant Lovelio data-flow gate and contractual controls allow it. | The prompts and content approved for the selected model route. Real candidate documents are blocked unless Lovelio enables the required contractual and retention controls. | United States and other contracted service regions where configured. |
| Voyage AI Innovations, Inc. | Vector embeddings and reranking for candidate, job, client, and marketplace search and matching. | Search queries and the text profiles or record summaries needed to create embeddings or rerank results. | United States. |
| Deepgram, Inc. | Speech-to-text transcription for dictated input, submitted audio, and live call transcription. | Audio selected or recorded for transcription and the resulting transcript. | United States by default; regional processing may vary where a contracted regional endpoint is configured. |
| ElevenLabs | Text-to-speech and candidate-facing AI voice screening. | Screening instructions, candidate conversation audio, transcripts, and text selected for speech synthesis. | United States and other provider sub-processor locations. |
| LiveKit, Inc. | Real-time video interview rooms, media transport, recording, and live-call infrastructure. | Participant identity, room metadata, audio, video, recordings, and live transcripts where the feature is used. | The configured LiveKit service region and provider sub-processor locations. |
| Resend, Inc. | Transactional and outbound customer email delivery, including password reset and sign-in emails, candidate correspondence, and digests. | Email addresses, message subject and body, and delivery metadata (bounces, complaints). | United States. |
| Vercel, Inc. | Application hosting, serverless compute, and edge delivery for the Lovelio web app and APIs. | HTTP requests and responses in transit and short-lived runtime logs. | United States, with a global edge CDN. |
| Inngest, Inc. | Background job and workflow queue for resume parsing, application assessment, webhook dispatch, and scheduled emails. | Job payloads for async work, which may contain candidate identifiers and references to stored records. | United States. |
| Functional Software, Inc. (Sentry) | Error monitoring and performance telemetry for the web app and API. | Error stack traces, request metadata, and user identifiers. Resume text and candidate PII are not sent to Sentry. | United States. |
| Stripe, Inc. | Subscription billing and payment processing for paid Lovelio plans. | Billing contact name and email, plan and invoice data. Card details are submitted directly to Stripe and are not stored by Lovelio. | United States. |
| Recall.ai, Inc. | Video meeting attendance and transcription for interview recording across Zoom, Google Meet, and Microsoft Teams. | Meeting audio and video, transcripts, and participant metadata for interviews the customer has opted to record. | United States. |
| Meta Platforms, Inc. | WhatsApp Cloud API delivery for connected recruiter conversations and candidate interview messages. | Phone numbers, message content, delivery metadata, and user-submitted WhatsApp documents where the feature is used. | Global Meta infrastructure. |
| WorkOS, Inc. | Single sign-on (SAML and OIDC) and directory sync for enterprise customers. | User identity assertions received from the customer identity provider during sign-in, and directory sync events where enabled. | United States. |
| Upstash, Inc. | Redis caching layer for company context, webhook subscription lookups, and API key authentication. | Short-lived cache entries keyed by company and user identifiers. No resume content is stored in the cache. | United States. |
| Logo.dev | Company logo and public brand enrichment during customer onboarding. | Publicly available company domains and returned brand assets. No candidate PII is sent to Logo.dev. | United States. |
| Firecrawl | Web crawling for company website enrichment during onboarding. | Publicly available company URLs and returned page content. No candidate PII is sent to Firecrawl. | United States. |
| Crustdata Technologies Inc. | Company enrichment for customer onboarding, employer research, and market intelligence. | Company domains and the public company information returned for those domains. | United States. |
| Serper | Web and news search for company intelligence and market-opportunity research. | Search queries, including company or market terms, and the public search results returned for those queries. | Global processing, including outside the European Economic Area. |
| Google Maps Platform | Place and location search in address and location fields. | Location search text, selected place details, and request metadata. | Global Google infrastructure. |
| Apify | Public web data collection for Lovelio market intelligence and employer research features. | Public job, employer, and market-source URLs and the public page data returned from those sources. | European Union and provider sub-processor locations. |
Customer-controlled integrations
The following integrations are not Lovelio sub-processors. The customer authorises each connection themselves, and the third-party provider processes data on the customer's behalf (under the customer's own agreement with that provider), not on Lovelio's behalf.
| Integration | Why it is not a Lovelio sub-processor |
|---|---|
| Slack | The customer's own Slack workspace. The Lovelio Slack app is installed via OAuth per workspace. Messages between Lovelio and the workspace are governed by the customer's agreement with Slack. |
| Google Calendar | The customer's own Google account. Each recruiter authorises calendar access per user via OAuth. |
| Google Workspace, Microsoft Entra, and other SAML or OIDC identity providers | The customer's identity provider. Lovelio consumes identity assertions during sign-in. The identity provider is controlled by the customer and its agreement with the provider. |
| X (formerly Twitter) | The customer's own X account, connected to auto-post job ads. Posting is subject to the customer's agreement with X. |
| The customer's own LinkedIn account, where connected for job distribution. | |
| Brainy and Referio | Customer-selected job-board distribution providers. A customer supplies or authorises its own provider connection, and job or application data sent through that connection is governed by the customer's agreement with the provider. |
| Zoom, Google Meet, and Microsoft Teams | The customer's own video meeting accounts. Lovelio only attends meetings that the customer invites it to. Where the customer has enabled recording, transcription is performed via Recall.ai (listed above as a Lovelio sub-processor). |
Changes to this list
Lovelio will provide at least 30 days' notice before onboarding any new sub-processor or making a material change to this list. Customers with a data processing agreement in place can raise objections in writing before the change takes effect. Notice is delivered by email to the billing contact on record and posted as an update to this page.
Questions
For questions about this list, data processing agreements, or security documentation, contact hello@lovelio.ai.