Subprocessors

Version 1.2, last updated March 12, 2026 

Modular Solutions relies on a small number of carefully selected third‑party service providers (“subprocessors”) to help us deliver, support, and enhance our policy administration platform. These subprocessors perform limited data‑processing activities on our behalf.  

Please note that this list does not include subprocessors where our clients own the relationship, such as the optional vendors in our Solutions Exchange. For these third parties, we only connect via our clients’ credentials and the client manages the relationship.  

As a Canadian company serving insurance carriers, mutuals, MGAs, and brokers across Canada and beyond, we take the security and privacy of customer data seriously. Our platform is designed to provide full policy lifecycle management while enabling insurers to streamline operations, automate processes, and leverage their data responsibly. When we engage third‑party providers to support these services, we do so only after assessing their security, privacy, and operational practices. 

All subprocessors listed below are contractually required to protect customer data and operate in accordance with applicable data‑protection laws. This list is reviewed regularly and updated whenever we add or remove subprocessors or materially change how we use them. 

Current Subprocessors Used by Modular Solutions

Below is the list of subprocessors that process customer data on our behalf. We select Canadian processing regions wherever available to support data residency expectations for the Canadian P&C insurance industry. Some subprocessors operate on multi‑region cloud infrastructures. In these cases, processing location depends on the region we configure (we choose Canada where possible). 

Microsoft Azure 

Azure provides the cloud infrastructure that hosts and runs our policy administration platform. This includes secure compute, storage, networking, and database services required for daily system operations. Azure operates data centers across global regions, including Canada Central (Toronto) and Canada East (Quebec), allowing us to maintain Canadian data residency wherever possible.  

Azure’s platform enables us to reliably deliver high‑availability services, scale on demand, maintain redundancy, and meet security requirements aligned with cloud industry standards. 

Processing Location: Data may be processed in Canada Central (Toronto) or Canada East (Quebec). 

Microsoft Azure DevOps 

Microsoft Azure DevOps is our cloud‑based software development lifecycle (SDLC) platform, used by our engineering team to manage repositories, work tracking, pipelines, artifacts, testing, and release automation. It provides secure version control, CI/CD processes, backlog and sprint management, and project governance features that support reliable and auditable development of our policy administration platform. 

Azure DevOps stores and manages several categories of data such as source code, work items, test results, and pipeline artifacts. These data types remain within the organization’s selected geographic region unless otherwise required by support operations, legal compliance, or use of preview features. 

Azure DevOps allows organizations to choose their data residency region at the time of account creation. Customer data is stored within the region selected or be default, in the nearest available region. 

Processing Location: Canada 

Tailscale 

Tailscale is a zero‑configuration mesh VPN service that provides secure internal networking across our infrastructure. We use Tailscale to establish encrypted, identity‑based connectivity between our internal systems, including Kubernetes clusters, development environments, administrative systems, and internal tools. This allows our team to access internal resources without exposing them publicly, while ensuring authenticated and encrypted device‑to‑device communication. 

Tailscale uses a combination of cloud infrastructure providers to operate its control plane and its global fleet of DERP relay servers. These subprocessors handle client device metadata, node information, and configuration information but not private VPN traffic, which is encrypted end‑to‑end. 

Processing Location: United States 

Sentry 

Sentry is an application monitoring and error‑tracking platform that we use to capture software logs, runtime errors, stack traces, performance metrics, and uptime/availability signals across our systems. This allows us to proactively detect issues, troubleshoot root causes, monitor service performance, and maintain the reliability of our platform. 

Processing Location: United States 

Canada Post 

Canada Post provides Address Complete, an address-verification and autocomplete service embedded into the Modular Solutions platform. We use this to validate Canadian mailing addresses at the point of data entry. This integration improves data accuracy, reduces invalid or incomplete addresses, and helps prevent downstream errors in policy issuance, billing, and correspondence.  

Canada Post provides official, Canada‑wide address validation using its national address database, covering all provinces, territories, and recognized address formats. processing occurs within the Canada Post AddressComplete service and its backend infrastructure. 

Processing Location: Canada 

Auth0 (Okta Identity Platform) 

Auth0 provides user authentication, authorization, and identity management. We use it to ensure secure sign‑in experiences for our platform users, enforce multi-factor authentication (MFA), manage access roles, and integrate with enterprise identity providers. Auth0 processes data in the region associated with the tenant configuration using Amazon Web Services for hosting and cloud infrastructure and Snowflake Computing Inc., for data warehoue services. We will be transitioning away from Auth0 in 2026.

Processing Location: Okta Auth0 stores and processes data in the United States, Germany, and Australia. 

Google Maps 

Google Maps aggregates geospatial data from multiple authoritative sources, including satellite imagery, aerial imagery, Street View data, governmental datasets, and third‑party providers.  This data fusion allows Google Maps to deliver highly detailed, continuously updated global maps that support address context, terrain, infrastructure details, and real‑world imagery relevant to insurance workflows. 

This subprocessor is used within our platform to provide visual mapping, interactive geographic context, and map-based visualization tools. It enables users to view policy locations, risk exposures, and other spatial data through embedded maps.  

Google Maps processes map‑related requests through Google’s global mapping infrastructure. Map tiles, imagery, and associated geospatial datasets are served from Google’s worldwide network of data centers, sourced from Google’s multi‑layer imagery pipelines and third‑party data providers. 

Google does not provide region‑specific data residency guarantees for Maps Platform products; map data is processed and delivered through globally distributed systems designed for performance, accuracy, and reliability. This global processing model supports fast rendering and up‑to‑date map content across 220+ countries and regions. 

Processing Location: Global 

Stytch (Twilio) – Migration in Progress 

Stytch is an ETL (Extract‑Transform‑Load) integration service that enables secure data replication from source systems into destination systems such as analytics warehouses or auxiliary tools. We use Stytch to streamline movement of operational or analytics‑related data (e.g., logs, integration data) in a controlled, repeatable, and auditable manner.  

When used with Twilio connectors, Stytch relies on Twilio’s global infrastructure, which includes U.S., Ireland, and Australia regions.  

Processing Location: Twilio provides multiple regions including United States (US1), Ireland (IE1), and Australia (AU1). Processing is most likely to occur in the United States. 

GitHub 

GitHub is a cloud-based code hosting and version-control platform used by our developer team to manage source code, maintain version history, collaborate on software development, and securely store configuration files related to our platform. This helps us maintain high software engineering quality and traceability throughout the development lifecycle. 

GitHub relies on a network of third‑party infrastructure providers including AWS, Cloudflare, Fastly, and Google Cloud for hosting, content delivery, and performance optimization. These subprocessors support GitHub’s ability to serve repositories, metadata, and developer tooling at scale. 

Additionally, GitHub operates its own physical data centers and points of presence, which house storage systems and networking infrastructure designed to provide redundancy, global availability, and high throughput for serving repository data. 

Processing Location: Primarily the United States. 

SendGrid (Twilio) 

SendGrid provides cloud‑based email delivery services used for notifications, system alerts, password reset messages, and workflow communications within the platform. The service ensures reliable delivery, high‑volume scalability, and monitoring of outbound email communications. 

SendGrid primarily processes data in United States data centers, including email activity logs and message metadata.  

Processing Location: Twilio provides multiple regions including United States (US1), Ireland (IE1), and Australia (AU1). Processing is most likely to occur in the United States.   

iClarify 

iClarify is a property‑intelligence and valuation tool used in the Canadian insurance industry to validate residential property information, improve insurance‑to‑value accuracy, and support underwriting workflows. It provides instant access to geo‑coded property intelligence, valuation data, and streetscape imagery, enabling more accurate replacement‑cost assessments. It also validates up to eleven key data elements such as square footage, year built, and construction details based on detailed, localized datasets.  

iClarify is powered by Opta Information Intelligence, leveraging the largest national repositories of total loss records and inspection data in Canada. This allows highly accurate replacement‑cost estimates validated by real claims and inspection data across regions. 

iClarify’s data sources and processing are tied to Canadian property‑data, inspection, and claims repositories, which are derived from Canadian total loss records and inspection providers like RMS and ClaimsPro. The tool aggregates, validates, and analyzes residential property data across Canada to produce valuations and property intelligence. 

This subprocessor only applies to our legacy platform (BNude) and is not a subprocessor of the Modular Solutions platform. Some clients may use this via our Solutions Exchange but would fully manage the relationship.

Processing Location: Canada 

FarmRE 

FarmRE is part of an agricultural‑insurance technology ecosystem used within our BNude platform. It supports agricultural risk evaluation by leveraging agri‑insurance tooling and digital ecosystem integrations that enable property, crop, and farm‑related underwriting. Available industry documentation shows partnerships and digital‑insurance enablement for agriculture risk (e.g., via INSTANDA and Farmsure). These platforms focus on farm‑policy creation, underwriting, and risk modeling for agricultural operations.  

This subprocessor only applies to our legacy platform (BNude) and is not a subprocessor of the Modular Solutions platform. Some clients may use this via our Solutions Exchange but would fully manage the relationship.

Processing Location: Canada 

Hubspot  

HubSpot is a customer relationship management (CRM), marketing automation, and sales‑enablement platform. We use HubSpot to manage customer and prospect communications, track support and engagement activity, host certain web forms, and manage non‑platform marketing workflows. HubSpot’s tools enable secure handling of contact information, subscription preferences, consent tracking, and communication history, supporting compliant lifecycle management of customer interactions.  

HubSpot hosts its product infrastructure on Amazon Web Services (AWS) across multiple regions. Customer accounts are assigned a hosting location based on geolocation at signup or by customer selection. Because we prioritize Canadian data residency wherever possible, our HubSpot data is hosted in the Canadian region (Montreal). 

Processing Location: Canada 

Happy Fox 

HappyFox is our customer support ticketing system and knowledge‑base platform, used to manage inbound support requests, track resolutions, and maintain self‑service documentation for our users. It enables structured ticket handling, workflow routing, internal notes, service reporting, and a searchable customer knowledge base. This supports our ability to provide responsive, auditable, and high‑quality support to insurers, MGAs, brokers, and other users of our platform. 

HappyFox provides help desk, live chat, workflow automation, and support infrastructure used across multiple industries. To deliver these services, HappyFox uses several infrastructure and service providers, including cloud hosting, content delivery, language translation (if enabled), and SMS integrations (if enabled). HappyFox hosts its applications and customer data on Amazon Web Services (AWS), with hosting locations in the United States and Germany, depending on configuration. 

Processing Location: Canada and the United States  

Anthropic – Claude 

Anthropic’s Claude is an enterprise LLM service used by product and engineering teams for requirements drafting, solution exploration, code assistance, documentation, and controlled analysis related to product design (including rates, rules scenarios). As such, Claude will be a subprocessor where it is used for product work that may include customer‑related content under enterprise controls. Anthropic offers enterprise security/compliance (e.g., SOC 2 Type 2, ISO 27001/42001, HIPAA‑ready offerings, audit artifacts) via its Trust Center. 

Anthropic states it uses multiple cloud providers and may route customer traffic through the US, Europe, Asia, and Australia; data is stored in the United States by default (unless agreed otherwise). Anthropic and its affiliates/subprocessors may process data for safety review/support/incident response in countries where they operate. 

Processing Location: Primarily the United States. 

 

These services may evolve over time, and this page will be updated to reflect any changes; customers will also be notified via email of any changes to subprocessors.