Subprocessors
This page lists categories and examples of third-party providers that may process data to help VIALINKER AI operate its websites, AI widgets, infrastructure, communications, security and support workflows.
1. Important note
This is a transparency page, not a promise that every provider is used for every customer. Actual subprocessors may depend on configuration, region, channel, service package, integrations and implementation stage.
2. Subprocessor categories
| Category | Purpose | Examples |
|---|---|---|
| Cloud hosting and application infrastructure | Hosting backend services, APIs, staging and production deployments. | Railway or comparable cloud hosting providers. |
| Database and storage | Storing application data, leads, messages, logs, configuration and service data. | PostgreSQL-compatible database providers, managed cloud storage providers. |
| AI model processing | Generating replies, classifying intent, detecting language, summarizing conversations and supporting AI workflows. | OpenAI, DeepSeek, Anthropic or comparable AI model providers, depending on configuration. |
| Email and business communication | Sending or receiving business inquiries, demo requests, pricing requests, support messages and notifications. | Gmail / Google Workspace or comparable email providers. |
| Messaging and notification channels | Sending hot lead alerts, admin notifications or communication messages where configured. | Telegram Bot API, WhatsApp Business providers, Viber providers, Meta APIs or comparable platforms, if enabled. |
| Analytics and pixels | Website analytics, conversion measurement and marketing attribution, if enabled later. | Google Analytics, Meta Pixel, TikTok Pixel or comparable providers, if enabled after consent where required. |
| Security, logging and monitoring | Monitoring uptime, errors, abuse, fraud, performance and security incidents. | Infrastructure logs, cloud provider logs, monitoring or error tracking tools. |
3. Data processed
Depending on service configuration, subprocessors may process contact data, technical data, chat messages, lead data, configuration data, logs, identifiers, timestamps and limited business account information. VIALINKER aims to limit access to what is reasonably necessary.
4. Changes and objections
VIALINKER may update subprocessors as the service evolves. Where required by law or contract, VIALINKER will provide notice or maintain a public update mechanism. Business customers may send reasonable data protection objections to mirn@ukr.net.