Skip to Content
LegalVendor Services and Sub-Processors

Vendor Services and Sub-Processors

Version 1.0 — effective [date of publication]

This page is Schedule B to the AlertD Software License Agreement for AWS Marketplace (the “License Agreement”). It lists the services AlertD operates that the Product depends on, and the Sub-Processors that have access to Buyer Data or Personal Data. It forms part of the agreement between AlertD and each buyer under Sections 1.3, 12.14 and 13.34 of the License Agreement and Section III.10 of its Data Processing Addendum. Capitalized terms have the meanings given in the License Agreement.

Changes to the Sub-Processor list are published on this page at least 30 days before they take effect, as described in Section 12.15 of the License Agreement. Buyers who reasonably object on data-protection grounds within that period may terminate under that Section.


B.1 Vendor Services

The Product requires an ongoing network connection from your AWS account to the following services, which AlertD operates. What each one receives is described in the Data Collection Disclosure.

ServiceOperated byHostingFunction
Telemetry serviceAlertDAmazon Web Services, United StatesReceives Diagnostic Data and System Data; stores Diagnostic Data in AlertD’s object storage
Authentication serviceAlertDAmazon Web Services, United StatesPerforms single sign-on with third-party identity providers using AlertD’s registered applications; refreshes source-code hosting tokens
Notification serviceAlertDAmazon Web Services, United StatesSends email on behalf of the Product through AlertD’s email-sending identity
Update channelAlertDAmazon Web Services, United StatesPublishes signed release manifests and images
Configuration serviceAlertDAmazon Web Services, United StatesPublishes signed configuration changes

B.2 Sub-Processors with access to Buyer Data or Personal Data

Sub-ProcessorRoleLocation
Amazon Web Services, Inc.Hosting, object storage, data streaming and email delivery for the Vendor ServicesUnited States
[AlertD’s identity provider]Authentication of AlertD Personnel for Support Access[location]

B.3 Third-party identity providers

When a User signs in through Google, GitHub, GitLab, Atlassian or Microsoft, the authentication service exchanges data with that provider under the provider’s terms. These providers act on the User’s instruction, not as AlertD’s Sub-Processors.

B.4 Content delivery

Users’ browsers load fonts and scripts from Google Fonts and jsDelivr when using the Product. Those services receive the User’s IP address and browser information under their own terms.

B.5 Model providers

The Product’s artificial-intelligence features call Amazon Bedrock in your AWS account by default. If you configure another model provider using your own credentials, that provider processes model inputs and outputs under your agreement with it and is not a Sub-Processor of AlertD.


Version history

VersionEffectiveChange
1.0[date of publication]Initial publication
Last updated on