--- title: "Sub-processors and Third-Party Services" slug: "sub-processors" updated: 2026-10-21T07:25:16Z published: 2026-10-21T07:25:16Z canonical: "learn.servitly.com/sub-processors" --- > ## Documentation Index > Fetch the complete documentation index at: https://learn.servitly.com/llms.txt > Use this file to discover all available pages before exploring further. # Sub-processors and Third-Party Services This page lists the third parties involved in the processing of Customer Data when using the Servitly DPS. It distinguishes between: 1. **Sub-processors engaged by Servitly**: Third parties that Servitly itself engages to deliver the DPS and that process Customer Data on Servitly's behalf. 2. **Third-party services enabled by the Customer**: External services that the Customer chooses to connect to the DPS through plugins, using its own accounts and credentials. 3. **Services contacted by the end user's browser**: External resources loaded directly by the browser or mobile app of DPS users, depending on the Customer's configuration. Only the parties in Section 1 are sub-processors of Servitly within the meaning of Article 28 of the GDPR. ## Sub-processors engaged by Servitly | Sub-processor | Service | Purpose | Data processed | Location | Transfer safeguards | | --- | --- | --- | --- | --- | --- | | Amazon Web Services EMEA SARL | Cloud infrastructure (compute, storage, databases, DNS, SNS) | Hosting and operation of the DPS – EU region | All Customer Data. | Ireland (eu-west-1) | Processing within the EU | | Amazon Web Services Hong Kong | Cloud infrastructure (compute, storage, databases) | Hosting and operation of the APAC region. Only for Customers who explicitly request it in the Commercial Offer. | All Customer Data of the only customers hosted in the APAC region. | Hong Kong SAR (ap-east-1) | Standard Contractual Clauses | | Microsoft Ireland Operations Ltd | Microsoft Azure cloud infrastructure | Hosting and operation of the DPS – EU region; Development and Staging environments. | All Customer Data. | Germany (Germany West Central) | Processing within the EU | | MongoDB, Inc./Ltd | Managed MongoDB | Storage of entity objects. (insights, events, actions, work orders, tickets, audit logs) | Any Customer Data involved in the processed entities | Azure Ireland (northeurope) | Processing within the EU | | Zendesk, Inc. | Ticketing System [help.servitly.com](http://help.servitly.com) | Management of support requests opened by the Customer | Name, email address, content of support requests. | Ireland | Processing within the EU | The legal addresses of the cloud providers are listed in [Cloud Providers](/v1/docs/dps-architecture#cloud-providers). Information on the applicable jurisdictions and on the safeguards against international governmental access is available on the [Data Act Transparency](/v1/docs/data-act-transparency) page. ## Third-party services enabled by the Customer The DPS includes plugins that allow the Customer to integrate external services. These plugins are disabled by default and are activated and configured by the Console user (*Integrations / Plugins*), using the Customer's own accounts, credentials and API keys. When a plugin is enabled: - The provider of the integrated service acts based on the contract between the Customer and that provider, and is not a sub-processor of Servitly. - Servitly transmits Customer Data to the service only to the extent required by the plugin configuration, which constitutes the Customer's documented instruction; - The Customer is responsible for entering into the appropriate agreements with the provider (including, where required, a data processing agreement and transfer safeguards) and for informing data subjects. | Plugin | Provider | Data typically transmitted | | --- | --- | --- | | [Android Push](/v1/docs/android-push) | Google (Firebase Cloud Messaging) | Device token, notification content | | [iOS Push](/v1/docs/ios-push) | Apple (Apple Push Notification service) | Device token, notification content | | [SMS](/v1/docs/sms) | Amazon Web Services (Amazon SNS), Customer's AWS account | Phone number, message content | | [Infobip](/v1/docs/infobip) | Infobip | Phone number, email address, message content, voice call data | | [Stripe](/v1/docs/stripe) | Stripe | Billing details, order and subscription data (payment card data is collected directly by Stripe) | | [Azure Active Directory](/v1/docs/azure-active-directory) | Microsoft (Microsoft Entra ID) | User identifiers and authentication data | | [OpenID Connect](/v1/docs/openid-connect) | Identity provider chosen by the Customer | User identifiers and authentication data | | [PingOne](/v1/docs/pingone) | Ping Identity | User identifiers and authentication data | | [MS Dynamics 365](/v1/docs/ms-dynamics-365) | Microsoft | Customers, locations, products, tickets, work orders | | [Salesforce](/v1/docs/salesforce) | Salesforce | Customers, locations, products, tickets, work orders | | [ServiceMax](/v1/docs/servicemax) | ServiceMax | Customers, locations, products, tickets, work orders | | [Partner Provider](/v1/docs/partner-provider), [Thing Provider](/v1/docs/thing-provider) | System chosen by the Customer | Partner and product master data | | [InfluxDB](/v1/docs/influxdb) | InfluxData or Customer's own instance | Metric Data | | [Snowflake](/v1/docs/snowflake) | Snowflake | Metric Data and Application Data | | [OpenWeatherMap](/v1/docs/open-weather-map) | OpenWeather | GPS coordinates of locations | | [AWS IoT Core](/v1/docs/aws-iot-core) | Amazon Web Services, Customer's AWS account | Product identifiers, Metric Data, commands | | [Azure Service Bus](/v1/docs/azure-service-bus) | Microsoft, Customer's Azure account | Product identifiers, Metric Data, commands | | [Everyware Cloud](/v1/docs/everyware-cloud), [Lemonbeat](/v1/docs/lemonbeat), [JMF Connector](/v1/docs/jmf-connector) | Respective IoT platform provider | Product identifiers, Metric Data, commands | | [Vodafone GDSP](/v1/docs/vodafone-gdsp) | Vodafone | SIM identifiers, connectivity status | | [Alexa](/v1/docs/alexa-1) | Amazon | Product identifiers, commands, status | | [Google Home](/v1/docs/google-home) | Google | Product identifiers, commands, status | ## Services contacted by the end user's browser Some DPS components load resources directly from external services when a page is displayed. In these cases, the external service receives technical data from the user's browser or app (such as IP address and user agent), but no Customer Data is sent by the DPS Backend. | Component | Service | Notes | | --- | --- | --- | | [Map widget](/v1/docs/map-widget) | OpenStreetMap tile servers (default) or the provider configured by the Customer (*Map Layer URL*) | Map tiles loaded by the browser | | [Calendly widget](/v1/docs/calendly-widget) | Calendly | Only if used in the Customer's templates | | [Wistia widget](/v1/docs/wistia-widget) | Wistia | Only if used in the Customer's templates | | [Google Analytics](/v1/docs/googleanalytics) | Google | Only if configured by the Customer | | [Google reCAPTCHA](/v1/docs/two-factor-authentication#google-authenticator-configuration) | Google | Only if configured by the Customer | | Chart-based widgets ([Time Series Chart](/v1/docs/time-series-chart-widget), [Bar Chart](/v1/docs/bar-chart-widget), [Benchmark](/v1/docs/benchmark-widget), [Status Diagram](/v1/docs/status-diagram-widget), [Metric State Diagram](/v1/docs/metric-state-diagram-widget), [Daily Summary Grid](/v1/docs/daily-summary-grid-widget), [XY Chart](/v1/docs/xy-chart-widget), [Scatter Chart](/v1/docs/scatter-chart-widget), [Heat Map](/v1/docs/heat-map-widget), [Pie Chart](/v1/docs/pie-chart-widget)) | amCharts | Only if used in the Customer's templates | > [!NOTE] > Updates to this page > > This page forms part of the Agreements referred to in the [Terms and Conditions](/v1/docs/terms-and-conditions) page, and it is updated whenever the infrastructure services change. Any update to this page will be marked with the effective date, in accordance with the schedule set forth in Servitly’s Terms and Conditions.