← All legal documents

Subprocessor Registry

Subprocessor Registry

Last updated: 2026-07-15 Version: 1 Applies to: all LighChat clients (web, desktop, mobile).

⚠️ Draft. Requires legal review and placeholder completion before publication.

To provide the service, [LEGAL ENTITY NAME] (the "Operator") engages providers (subprocessors) that act on its behalf under agreements ensuring a level of data protection no lower than required by applicable law (Art. 28 GDPR; Art. 6(3) of Russian Federal Law 152-FZ). Below is the list current as of the version date. Some operations are performed on servers outside the Russian Federation — see the Privacy Policy and the Consent to Personal Data Processing (cross-border transfer section).

Legend: client-direct — the request is made directly from the user's device (the provider is exposed to the user's IP address); backend — the request is made by the Operator's server (the user's IP is not exposed to the provider).

1. Cloud infrastructure and platform

SubprocessorJurisdictionData categoriesPurpose
Google LLC (Firebase Authentication)USAemail, phone, password hash, user identifier, OAuth profile, session tokens, IPRegistration, authentication, session management
Google LLC (Cloud Firestore, Realtime Database)USA (realtime DB — EU region)account data, messages, chat metadata, presence, settings, IPPrimary storage and low-latency layer
Google LLC (Cloud Storage for Firebase)USAmedia (photos, video, voice, documents), avatarsStorage of user content
Google LLC (Cloud Functions)USAdata passed to server callsServer-side logic
Google LLC (Firebase Cloud Messaging)USApush tokens, user identifier, notification bodyPush notification delivery (web, Android)
Google LLC (Firebase App Check / reCAPTCHA Enterprise)USAIP, browser fingerprint, attestation tokenProtection against automated abuse
Google LLC (Firebase Remote Config, App Hosting, Cloud Build)USAapp-instance-id, IP, web requestsFeature configuration, web hosting, builds

2. Analytics and diagnostics (only with separate consent)

SubprocessorJurisdictionData categoriesPurpose
Google LLC (Google Analytics / GA4, BigQuery)USAusage events, pseudonymized identifier (hash), IP, device typeProduct analytics in aggregated form
Google LLC (Firebase Crashlytics)USAcrash stacks, device model, OS version, IPMobile app crash diagnostics
Google LLC (Looker Studio)USAaggregated metrics (non-identifying)Internal analytics dashboards

The user identifier is pseudonymized (hashed) before being sent to analytics services; the raw identifier is not transmitted to them.

3. Communications: phone verification and email

SubprocessorJurisdictionData categoriesPurposeMethod
Telegram (Telegram Gateway)UAE / UKphone number, verification codePhone verification (primary channel)backend
Resend Inc.USAemail, message body (codes, service notices)Transactional emailbackend
Apple Inc. (APNs)USAVoIP push tokens, user identifierCall push notifications on iOSbackend

4. Media and content

SubprocessorJurisdictionData categoriesPurposeMethod
Giphy Inc. (Meta)USAsearch query textGIF/sticker searchbackend (via Operator's proxy)
Translated Srl (MyMemory)Italy / EUsearch query textQuery translation for GIF searchbackend (via Operator's proxy)
Song lyrics provider (LRCLIB)EUtrack artist and titleDisplaying song lyricsclient-direct
CDN (jsDelivr, unpkg)globalIP (loading libraries/models)Delivery of client resources (maps, video processing)client-direct
Apple Inc. (Apple Maps), YouTube (Google LLC)USAaddress/coordinates (deep-link), IP (embed)Opening maps, link previewsclient-direct

5. Voice and video calls (WebRTC)

SubprocessorJurisdictionData categoriesPurposeMethod
Media server (self-hosted LiveKit on a rented VPS)Netherlandsaudio/video of group meetings, IP, access tokenGroup meeting transport (SFU)client-direct
Metered Inc. (TURN)Canadarelayed call media stream, IPs of partiesRelay when direct connection is impossibleclient-direct
Google LLC (STUN)USAIP (ICE network path discovery)Establishing a direct connectionclient-direct

6. App stores and distribution

Apple App Store (Apple Inc., USA), Google Play (Google LLC, USA), and direct download of the desktop version — distribution of the app and updates.

7. Other recipients as required by law

Data may be disclosed to authorized government authorities in the cases and manner provided by applicable law, and, upon reorganization of the Operator, to its legal successor while preserving processing terms.


Appendix. Russian-contour subprocessors

For a future version of the Service intended for users in the Russian Federation, the set of subprocessors will differ: infrastructure and primary data recording will be located within the Russian Federation; phone verification and other operations will use Russian providers (including SMS/flash-call providers and Russian sign-in services). In the current (global) version of the Service these providers are not used. The list for the Russian contour will be published as a separate appendix upon its launch.


*The Operator reserves the right to engage new subprocessors, notifying of changes by updating this document. Material changes are communicated to users as provided by the Privacy Policy.*