Nexly uses the providers below for specific service functions. A provider receives only the categories of data needed for its role. Actual processing may depend on which features a customer enables.
Core service providers
| Provider | Purpose | Primary region or processing scope | Data involved |
|---|---|---|---|
| Railway | Cloud hosting and managed infrastructure | Primary deployment: Netherlands | Account, analytics, support, and operational service data |
| Vercel | Marketing site and help-center hosting | Provider-controlled | Web requests and deployment logs |
| Cloudflare | Object storage and edge delivery | Storage location hint: Eastern Europe; edge processing may occur globally | Uploaded profile and property images, plus delivery request metadata |
| Resend | Transactional email | Ireland | Email address, message content, and delivery metadata |
| Polar | Checkout, merchant-of-record billing, subscriptions, tax, and invoices | Provider-controlled | Account, customer, subscription, invoice, and payment-related data |
| Sentry | Error monitoring and product diagnostics | Provider-controlled | Technical diagnostics, masked interface activity, and pseudonymous account identifier |
AI model providers
When a customer uses AI Insights, Nexly may send the prompt and necessary analytics context to the selected provider. Available providers depend on Nexly configuration and model availability.
| Provider | Purpose | Data involved |
|---|---|---|
| Anthropic | Language-model inference | Prompt and selected analytics context |
| OpenAI | Language-model inference | Prompt and selected analytics context |
| Gemini language-model inference | Prompt and selected analytics context | |
| xAI | Grok language-model inference | Prompt and selected analytics context |
| DeepSeek | Language-model inference | Prompt and selected analytics context |
Supporting technology
Nexly uses the MaxMind GeoLite2 database locally to derive country, region, and city from an incoming IP address. Nexly does not send each visitor request or IP address to MaxMind for lookup, so this local database use is not listed as a data subprocessor.
SDK packages are distributed through public package registries: JavaScript packages through npm, the Dart/Flutter package through pub.dev, and the Swift package through Swift Package Manager (resolved from GitHub). Package download requests are handled by each registry under its own relationship with the downloader; none of these registries receive customer analytics events from Nexly.
Changes and questions
Nexly may add or replace providers as the service changes. Material updates will be published on this page. Questions or reasonable data-protection objections can be sent to mail@nexly.to.
Last updated: July 10, 2026