Data Collection Disclosure
Version 1.0 — effective [date of publication]
This page is the Data Collection Disclosure referenced in the AlertD Software License Agreement for AWS Marketplace (the “License Agreement”). It forms part of the agreement between AlertD and each buyer under Sections 1.2, 1.3 and 13.7 of the License Agreement, and it is Schedule A to that agreement. Capitalized terms have the meanings given in the License Agreement.
AlertD may update this page as described in Sections 7.8.3 and 12.15 of the License Agreement. The version number and effective date above change with each update, and prior versions are available on request.
AlertD is deployed into your AWS account. It also depends on services AlertD operates, and it transmits data from your deployment to those services as described here. Collection of Diagnostic Data and Support Access cannot be disabled.
1. What the Product collects and transmits
1.1 Diagnostic Data
The Product packages the following categories from its working data and transmits them to AlertD’s telemetry service on a recurring schedule. Each transmission covers the most recent data within the window shown, subject to a total size limit per transmission.
| Category | Contents | Default window |
|---|---|---|
| Application logs | Operational logs of the Product, which may include request metadata, error messages, and identifiers of Users and AWS resources | 25 hours |
| Plan and scheduler records | Records of the Product’s automated jobs, their timing and outcomes | 25 hours |
| Telemetry events | The System Data events in section 1.2, as stored locally, including the identifiers of Users who performed each action | 25 hours |
| Log collection buffers | Copies of your AWS log data staged by the Product for analysis | 25 hours |
| Log samples | Samples of your AWS log lines retained for pattern analysis | 25 hours |
| Infrastructure change records | Records of changes to AWS resources in your environment, derived from AWS CloudTrail and resource inventories | 25 hours |
| Cost analyses | Cost and savings analyses of your AWS usage | 25 hours |
| Health evaluations | Results of the Product’s health and compliance evaluations of your AWS resources | 25 hours |
| Model inputs and outputs | The prompts sent to and responses received from the Product’s artificial-intelligence models, including the system instructions, the User’s query, and the AWS resource data, logs and tool results included in the prompt | 25 hours |
| Conversation records | Users’ queries to the Product’s conversational features, the Product’s reasoning and actions, and its responses, stored under an identifier derived from the User’s email address | 25 hours |
| Legacy prompt archive | Historical records of your own model invocations in your AWS account, where the Product was configured to collect them | 25 hours |
Diagnostic Data includes Buyer Data, including the contents of AWS resources the Product has been granted access to, and Personal Data of Users, including their email addresses and activity within the Product. No redaction is applied before transmission.
1.2 System Data
The Product sends the following to AlertD’s telemetry service in near real time.
| Category | Contents | Frequency |
|---|---|---|
| Installation identity | Your AWS account identifier and name, AWS Organization identifier, installation identifier and installation URL, attached to every transmission | Every event |
| Service health | CPU, memory, network, storage and uptime metrics of the Product’s own infrastructure | Every 5 minutes |
| Lifecycle events | Startup, shutdown, update and license-verification events, including error details on failure | As they occur |
| Usage events | Logins, page views and feature use within the Product, keyed by a User identifier and role; messaging-integration interactions, including the User identifier and a link to the conversation; email delivery outcomes | As they occur |
| Configuration synchronization | Confirmation that remotely delivered configuration was applied | Hourly |
| Update polling | Requests to the update channel, which carry your AWS account identifier | Every 15 minutes |
| Pricing requests | Requests for AWS price data, which identify the AWS services and regions in use | As needed |
1.3 Data passing through AlertD-operated services
The following data transits services AlertD operates. It is not retained beyond operational logs.
| Service | Data in transit |
|---|---|
| Authentication service | Identity-provider authorization codes; the identity attributes returned by the provider, including name, email address, avatar and organization memberships; access and refresh tokens for source-code hosting integrations |
| Notification service | Recipient email addresses and the full content of messages sent by the Product, including account and password-reset messages |
2. Why it is collected
AlertD uses the data above for the Permitted Purposes set out in Section 7.2.3 of the License Agreement:
- providing, operating, securing, supporting and maintaining the Product and the Vendor Services;
- diagnosing, reproducing and remediating defects, security vulnerabilities and performance problems, whether reported by you or detected by AlertD, including across AlertD’s customer base;
- measuring and analyzing the use, adoption, cost and performance of the Product;
- developing, testing, evaluating, calibrating and improving the Product and AlertD’s other products and services, including their models, prompts, classifiers, pricing and features;
- billing and subscription administration; and
- creating Derived Data.
AlertD does not sell Buyer Data or Identifiable System Data, does not disclose them to third parties other than the Sub-Processors listed below and AlertD Personnel bound by confidentiality obligations, and does not use Buyer Data to train a machine-learning model that is made available to third parties, other than as Derived Data.
3. Where it is stored and for how long
Diagnostic Data and System Data are stored in the United States, in AlertD’s Amazon Web Services environment, and are deleted automatically on the following schedule.
| Data | Retention |
|---|---|
| Diagnostic Data | 7 days from receipt, then deleted; deletion completes within one further day |
| System Data | 30 days from receipt, then deleted; deletion completes within one further day |
| Derived Data | Indefinitely |
On your written request to the notice address in the License Agreement, AlertD will, within a reasonable period, provide a copy of the Diagnostic Data then held for your installation or delete it, other than Derived Data, data in backups that are deleted in the ordinary course, and data AlertD is required by law to retain. See Section 7.10 of the License Agreement.
4. Services AlertD operates and Sub-Processors
The services AlertD operates that the Product depends on, and the Sub-Processors with access to Buyer Data or Personal Data, are listed in Vendor Services and Sub-Processors, which is Schedule B to the License Agreement. Changes to the Sub-Processor list are published there at least 30 days before they take effect.
5. Your controls
Configuration options affecting collection, if any, are described in the product documentation. As of this version:
- Automatic updates may be disabled by a deployment parameter.
- You may supply your own mail server, which removes the notification service from the data path.
- Diagnostic Data collection, Support Access and the authentication service cannot be disabled or replaced.
6. Support Access
The Product includes accounts, administrative interfaces and remote functions reserved for AlertD Personnel for the maintenance, support and operation of the Product. AlertD Personnel may use them to access your installation, including Buyer Data within it and the AWS credentials granted to the Product, for the purposes in Section 7.2.3(a) and (b) of the License Agreement, at any time and without prior notice. See Section 7.9 of the License Agreement.
Version history
| Version | Effective | Change |
|---|---|---|
| 1.0 | [date of publication] | Initial publication |