Subprocessor List
Last updated: 30 October 2026
Contents
This page lists the subprocessors engaged by Molvek OÜ (registry number: 17618773, registered address: Sepapaja tn 6, 15551 Tallinn, Harju Maakond, Estonia, email: info@molvek.com) to provide the Molvek Bot service under the Data Processing Agreement (DPA), together with their processing purpose, categories of data processed and processing location.
1. Infrastructure, AI and Security Subprocessors
| Subprocessor | Service / Role | Categories of Data Processed | Processing Location |
|---|---|---|---|
| Railway | Application, background processing, relational database and cache/queue hosting | Customer and operator account data, conversation and message records, appointment and handoff records, encrypted channel credentials | EU (Netherlands) |
| Amazon Web Services (AWS) | Application, background processing, relational database and cache/queue hosting | Customer and operator account data, conversation and message records, appointment and handoff records, encrypted channel credentials | EU (Germany) |
| Qdrant Cloud | Managed vector database (knowledge-base search index) | Customer knowledge-base text chunks, document titles/metadata and search vectors | EU (Germany) |
| Anthropic | AI language model inference (replies, suggestions, summaries and extraction) | End-user messages, recent conversation context and relevant business knowledge-base passages (not used to train models) | US / Global |
| OpenAI | Text embedding generation for search vectors | Knowledge-base text chunks and knowledge-base search queries (not used for standard chat reply generation) | US / Global |
| Cloudflare | Network security, traffic routing (DNS/CDN) and bot/abuse protection (Turnstile) | Client IP address, HTTP request headers, security and Turnstile verification signals | Global / EU |
2. Customer-Connected Third-Party Channels and Payment Services
The following providers process data within their respective roles and terms when the Customer connects an external channel or completes a payment transaction:
- Meta Platforms (WhatsApp Business Platform, Instagram, Facebook Messenger): Used for message and media delivery when the Customer connects the relevant channel.
- Telegram: Used for message delivery when the Customer connects a Telegram bot.
- Google (Google Calendar API): Used for availability checks and creating/updating appointment events when the Customer enables Google Calendar integration.
- Stripe (
Stripe/Link— Stripe Managed Payments): Acts as the Merchant of Record and payment processor for subscription payments, handling tax calculation, invoicing and collection.