Skip to content
Sign in Start free

Last updated: October 7, 2026

Sub-processors

The service providers we use to run Layvchat that may access personal data while doing so.

This document is also available in Turkish. If the two versions differ, the Turkish version prevails.

1. About this list

The providers below deliver part of the Service and may access personal data while doing so. Each accesses only the data it needs for its job and is bound by contractual data protection obligations.

Chat content is never sent to an AI provider, including for AI features, so there is no AI provider on this list.

2. Infrastructure

  • Hosting provider (data center). Purpose: servers, database and file storage. Data: all account and Customer Data
  • Cloudflare, Inc. Location: USA (global network). Purpose: domain, encrypted connections, attack protection and visitor country detection. Data: traffic to the Service and IP addresses

3. Email

  • Resend. Location: USA. Purpose: sending account emails (verification, password, invitations, security alerts, reminders), chat transcripts, offline replies and ticket emails; receiving email sent to customers’ support addresses. Data: sender and recipient addresses, message content and attachments

4. Only if used

  • Google LLC. Location: USA. When: if you use Sign in with Google (Google account ID, name and email address) or if push notifications are on in the Android mobile app (Firebase Cloud Messaging: notification token and notification content)
  • Expo (650 Industries, Inc.). Location: USA. When: only if push notifications are on in the mobile app. Purpose: relaying notifications to the phone’s notification service. Data: notification token and notification content (title, visitor name and, if the agent chooses, a short message preview)
  • Apple Inc. Location: USA. When: only if push notifications are on in the iOS mobile app (Apple Push Notification service). Data: notification token and notification content
  • Telegram. Location: UAE and other countries. When: only if the Customer turns on Telegram notifications. Data: notification texts (for example, a new chat alert with a short message preview)

Webhook addresses and API clients the Customer sets up itself are not our sub-processors; those transfers happen on the Customer’s instructions and responsibility.

5. Notice of changes

We notify workspace owners by email at least 30 days before adding a new sub-processor to this list. The right to object and the process are in the Data Processing Addendum.