Legal
NearMax Office Subprocessors
Version 2026-10-17 | Last updated: October 17, 2026
Scope
Effective October 17, 2026. This page lists providers that process Customer or Caller personal data for NearMax to provide Office. A provider is used only when its related feature is used or connected. NearMax remains responsible for its subprocessors as stated in the Data Processing Addendum.
Current subprocessors
| Provider | Purpose |
|---|---|
| Railway | Application and database hosting |
| Twilio | Telephone numbers, calls, recordings and call transport |
| Anthropic | NearMax-managed AI language processing |
| Voyage AI | NearMax-managed knowledge base embeddings |
| Amazon Web Services (AWS SES) | Transactional email delivery |
| Sentry | Error monitoring with Office data scrubbing |
| Calendar synchronization when connected | |
| Microsoft | Calendar synchronization when connected |
| ElevenLabs | Text-to-speech for fixed Office prompts |
Providers that are not NearMax subprocessors
Stripe processes NearMax Customer billing information, not Customer or Caller data for Office, so it is not an Office subprocessor.
A bring-your-own model provider, including OpenAI, Azure OpenAI, Anthropic or AWS Bedrock, processes data under its own agreement with the Customer. It is the Customer's vendor, not a NearMax subprocessor for that use. A provider may therefore have a different role when NearMax supplies it as part of the managed service and when the Customer connects it directly.
Changes
NearMax will give Office Customers at least 30 days' notice before adding or replacing a subprocessor that processes personal data, as described in the Data Processing Addendum. Questions may be sent to hello@nearmax.com.