These DigitalOcean Signals Public Preview Terms (“Terms”) govern Customer’s use of Signals, an intelligence layer that captures production traces from Customer’s AI agents and inference to provide behavioral and operational insights, automated evaluation datasets, and simulation scenarios. These Terms supplement the DigitalOcean Terms of Service Agreement (including Service Terms) or such other written agreement between DigitalOcean, LLC (“we,” “us,” “DigitalOcean”) and Customer (“Customer”) governing Customer’s use of our Services (the “Agreement”), including the Data Processing Agreement (“DPA”). If there is a conflict between these Terms and the DPA on a data-protection matter, the DPA controls.
Capitalized terms not defined herein shall have the meanings set forth in the Agreement or DPA.
a. Trace. A record of an agent or inference interaction, which may include End User prompts/inputs, agent calls to tools and databases (including parameters), retrieved data, intermediate steps, LLM responses, and associated metadata (timestamps, identifiers, latency, cost, error states).
b. Session. A set of Traces grouped as belonging to a single End User interaction or conversation.
c. Signal. A derived attribute, label, score, or classification produced by applying logic or models to Traces or Sessions (e.g., “frustrated end user,” “satisfied end user,” “tool-parameter failure,” cost/performance flags).
d. End User. An individual or system whose interactions with Customer’s agent or models generate Traces. End Users are Customer’s users, not DigitalOcean’s.
e. Resource Region. The data-center region Customer selects for storage and processing of its cloud resources.
When enabled, Signals processes:
a. Trace content, including the full text of End User prompts/inputs, agent tool and database calls and their parameters, retrieved content, LLM responses, and reasoning/intermediate steps;
b. Session groupings and metadata; and
c. Signals derived from the above.
Trace content is processed in raw form. Trace content may therefore contain Personal Data or special-category/sensitive data if such data is present in the underlying agent and inference interactions. For Personal Data contained in Trace data:
a. Customer is the Controller and determines the purposes and means of processing its End Users’ data;
b. DigitalOcean is the Processor and processes Trace data solely to deliver the Signals features and solely upon Customer’s documented instruction to enable the Signals feature; and
c. The DPA governs DigitalOcean’s processor obligations, including confidentiality, security, sub-processing, assistance with data-subject requests, breach notification, and deletion/return of personal data.
By enabling Signals within the DigitalOcean Console, Customer explicitly consents to DigitalOcean processing Traces solely for the purpose of:
a. Ingest and Store: Collecting production interaction Traces from designated AI agents or models.
b. Analyze and Annotate: Processing Traces to generate behavioral and operational metrics.
c. Generate Derived Assets: Create evaluation datasets and simulation scenarios.
d. Service Improvements: Using anonymized, aggregated Usage data to improve the Service.
DigitalOcean processes Trace data and Signals to:
a. Group Traces into Sessions and annotate Signals;
b. Make Sessions and Signals available to Customer through dashboards, filtering, and search;
c. Enable Customer to reuse qualifying Traces for Customer’s own purposes (e.g., model evaluations, simulations);
d. Detect behavioral and operational issues in Customer’s agentic and inference workflows; and
e. Operate, secure, troubleshoot, and improve the Signals feature for Customer.
a. No Cross-customer Use: DigitalOcean does not use Customer’s Trace data or Signals to train any of its Hosted Models or to develop products for other customers, and does not combine Customer Trace data with other customers’ data.
b. Redaction: DigitalOcean applies an automated redaction engine to sensitive attributes in Traces (including PII) as displayed to Customer in the Console — and internally for trace data exported as datasets into Simulations and Evaluations. Customer acknowledges that automated redaction is not infallible, that Customer remains responsible for data entered into its agents and inference sessions, and that this feature does not satisfy Customer’s compliance obligations under HIPAA, PCI-DSS, or other industry-specific regulations.
c. Selective Opt-In: Customer controls which inference sessions and agents have Signals enabled. Customer may disable data collection at any time via the DO Console.
d. Data Minimization: We utilize “Signal-Based Sampling.” Rather than storing 100% of raw traffic, we intelligently surface only the most informative sessions (e.g., failure patterns or complex trajectories), reducing Customer’s data footprint.
a. Retention: Traces collected for Signals are subject to DigitalOcean’s standard data retention protocols. Customer may request the deletion of a session trace from Signals (through the Signals configuration page in the control panel).
b. Non-Disclosure: DigitalOcean will not use Customer’s raw, un-anonymized Traces to train foundation models for other customers. Data is used exclusively for the purpose of generating Customer’s Signals metrics, evaluation datasets, and scenarios.
Customer acknowledges and agrees that:
a. Customer is responsible for determining whether processing Trace data is appropriate for its use case and regulatory environment, and for configuring or instructing its models and agents and End Users accordingly.
b. By enabling Signals, Customer confirms it has a lawful basis for the capture and processing of Trace data for its End Users (e.g., consent, legitimate interests, or contractual necessity, as applicable), and has provided any required notices to End Users.
c. Restricted Data. Signals is not designed or authorized for Restricted Data. “Restricted Data” means Protected Health Information (PHI) subject to HIPAA, cardholder data subject to PCI-DSS, and [other categories to be defined by DigitalOcean]. Customer must not enable Signals for any inference sessions or agents that processes Restricted Data. DigitalOcean does not offer a Business Associate Agreement for Signals and makes no representation that Signals is HIPAA- or PCI-DSS-compliant. If Restricted Data nonetheless appears in Traces, Customer must promptly delete the affected Sessions using the Console tools, and DigitalOcean disclaims all liability for such data.
d. Customer may disable Signals at any time to stop further Trace capture.
The Preview Offering is a Beta Service. The warranty disclaimers, exclusions of damages, and limitation of liability applicable to Beta Services under the Agreement (including Section 8.6) apply to the Preview Offering and are incorporated by reference. These Preview Terms supplement, and do not limit, the provisions in the Agreement. Nothing in these Preview Terms expands DigitalOcean’s liability beyond, or limits any disclaimer, exclusion, or cap set forth in the Agreement.