Subprocessors

Version 0.2-draft · Effective 28/07/2026

Draft — under legal review. This text has not yet been reviewed by a lawyer and is published for review purposes only. It does not yet form a binding agreement. Please check back before relying on it.

Lawyer consent requiredthis document was CHANGED from the version supplied to us, and must be signed off before it leaves draft. What changed and why: the supplied text read "Examples include cloud hosting, payment gateways... the current list should be maintained by the Company", which is an instruction to us rather than a statement a customer or regulator can rely on. It has been replaced with the five subprocessors actually in use, verified against the codebase. Their hosting regions still need to be confirmed and added.

Effective Date: July 28, 2026

We use the following subprocessors to provide the Services. We update this list when vendors change.

| Subprocessor | Purpose | |---|---| | Supabase | Database, authentication and file storage | | Vercel | Application hosting | | Razorpay | Payment processing (India) | | Resend | Transactional email | | Google (Gemini API) | AI text and image generation | | Google (Firebase Cloud Messaging) | Push notifications to the mobile app | | LiveKit | Carries voice and video during a call. Media passes through; it is not recorded or stored by us |

Where you supply your own AI provider key, that provider processes your prompts instead of Google, under their own terms.

[Lawyer: each subprocessor's hosting region must be confirmed and stated here. The DPDP Act restricts cross-border transfer to notified countries, and enterprise buyers ask for regions in writing.]

We remain responsible for our subprocessors' performance under the Data Processing Addendum.

Contact: admin@dlqtechnos.com