メインコンテンツまでスキップ

VeloDB Cloud Addendum

Effective Date: June 3, 2026

Last Updated: June 15, 2026

This VeloDB Cloud Addendum (the "Cloud Addendum") is incorporated into and supplements the VeloDB General Terms and Conditions, and governs Customer's access to and use of VeloDB Cloud when VeloDB Cloud is ordered or used under the Agreement. Except as modified by this Cloud Addendum, the Agreement remains in effect. Capitalized terms not defined here have the meanings given in the Agreement.

1. Additional Definitions​

"Acceptable Use Policy" means the VeloDB Acceptable Use Policy incorporated into the Agreement, an Order Form, or an approved customer-facing policy location.

"Cloud Service" or "VeloDB Cloud" means VeloDB's cloud-based data warehouse service, including related management consoles, APIs, support functions, and service components made available by VeloDB.

"DPA" means the VeloDB Data Processing Addendum.

"SLA" means the VeloDB Cloud Service Level Agreement.

"Support Terms" means the support terms, if any, stated in an Order Form, a VeloDB Support Services Policy, approved customer-facing support materials, or another support policy location incorporated into the Agreement.

"Logging and Telemetry Controls" means approved VeloDB Documentation, a DPA schedule, Security Addendum section, Order Form provision, support workflow, or customer-specific exhibit that describes logging, telemetry, Usage Data, or operational records applicable to the Cloud Service.

"Retention Schedule" means approved VeloDB Documentation, a DPA schedule, Order Form schedule, offboarding guide, or customer-specific exhibit that describes retention, deletion, backup, export, or offboarding treatment applicable to the Cloud Service.

2. Access to VeloDB Cloud​

2.1 Right to Use. During the applicable Order Form term, VeloDB grants Customer the right to access and use VeloDB Cloud for Customer's internal business purposes, subject to the Agreement, this Addendum, the Documentation, and any usage limits in the Order Form.

2.2 Service Levels. Eligible paid production VeloDB Cloud clusters are subject to the SLA to the extent stated in the SLA and applicable Order Form. BYOC Services are covered by the SLA only when the applicable Order Form, checkout flow, marketplace order, service plan, or other accepted ordering record expressly references the SLA or identifies the applicable BYOC Services as covered. VeloDB may update the SLA from time to time, provided that updates will not materially diminish the service level commitment for an active Order Form term unless required by law or agreed by Customer.

2.3 Support. Support for VeloDB Cloud, including support channels, response targets, severity levels, exclusions, and diagnostic handling, is governed by the applicable Support Terms.

2.4 Changes to the Cloud Service. VeloDB may modify features, functionality, infrastructure, and APIs of VeloDB Cloud to improve, secure, maintain, or comply with laws affecting the Cloud Service. VeloDB will use commercially reasonable efforts to avoid materially reducing core functionality during an active Order Form term.

3. Customer Responsibilities​

Customer is responsible for:

  • selecting and configuring clusters, regions, capacity, networking, identities, credentials, access controls, and optional features;
  • ensuring that Customer Data and Customer's use of VeloDB Cloud comply with laws and the Acceptable Use Policy;
  • maintaining Customer-controlled backups, exports, and disaster recovery arrangements where appropriate;
  • securing Customer applications, systems, cloud accounts, endpoints, and networks connected to VeloDB Cloud;
  • promptly notifying VeloDB of suspected unauthorized access to Customer's account or clusters; and
  • using VeloDB Cloud in accordance with Documentation and any applicable Order Form limits.

4. Additional Restrictions​

Customer will not use VeloDB Cloud to process restricted or regulated data, including protected health information, payment card data, children's data, biometric data, or data subject to specialized industry or legal regimes, unless VeloDB has confirmed support for that use case in writing and the parties have executed any required additional terms.

Customer will not use VeloDB Cloud to perform unauthorized security testing, stress testing, or benchmarking, or to interfere with the operation of VeloDB Cloud or other customers' use of the service.

5. Usage Data and Operational Data​

VeloDB may collect and use Usage Data, including operational metrics, service logs, query metadata, feature usage information, diagnostic information, and security signals, to provide, maintain, secure, support, and improve VeloDB Cloud. Detailed categories, sources, destinations, retention periods, access controls, customer controls, and subprocessor treatment for logs, telemetry, control-plane metadata, query records, alert payloads, diagnostics, and support records may be described in approved Logging and Telemetry Controls, the Retention Schedule, the Security Addendum, the DPA, Documentation, an Order Form, or a customer-specific exhibit. Those materials do not expand this Cloud Addendum unless expressly incorporated into the Agreement or an applicable Order Form. Usage Data does not include Customer Data in identifiable form and will not be disclosed to third parties in a form that identifies Customer except as permitted by the Agreement.

Operational data, logs, telemetry, query records, alert payloads, support records, or diagnostics that constitute Customer Data or Customer Personal Data are handled in accordance with the Agreement, DPA, and applicable Security Addendum. Query results are Customer Data to the extent they contain Customer Data and are not general Usage Data.

6. Security and Shared Responsibility​

VeloDB maintains security controls for VeloDB-controlled components of VeloDB Cloud as described in the applicable Security Addendum, DPA, Order Form, or approved security materials. Customer remains responsible for Customer-controlled configurations, accounts, credentials, access permissions, customer cloud environments, applications, and data pipelines connected to the Cloud Service.

For bring-your-own-cloud or customer-managed deployment models, responsibilities may be further described in an Order Form, the VeloDB BYOC Addendum, security appendix, or Documentation.

7. Suspension​

VeloDB may suspend access to VeloDB Cloud as described in the Agreement. VeloDB may also suspend an affected cluster, account, or workload if Customer's use materially degrades VeloDB Cloud, creates a material security risk, violates the Acceptable Use Policy, exceeds agreed usage limits, or may cause material harm to VeloDB, Customer, other customers, or third parties.

8. Data Export, Return, and Deletion​

Customer is responsible for exporting any Customer Data it needs to retain using available VeloDB Cloud functionality during the applicable subscription term and any post-termination access period, if any, stated in the Order Form, Documentation, DPA, or an approved offboarding guide. Applicable Documentation, an approved offboarding guide, or a customer-specific offboarding exhibit may describe supported export methods, backup treatment, post-termination access windows, and customer-controlled cleanup steps. After expiration or termination, VeloDB may disable access to the Cloud Service and delete Customer Data from VeloDB-controlled systems according to the DPA, Retention Schedule, standard deletion practices, and applicable law, unless retention is required by law. Backup, archive, security, audit, legal, tax, accounting, support, dispute, and legal-hold records may follow separate retention or deletion treatment.

Customer is responsible for deleting or deprovisioning resources, backups, keys, and data residing in Customer-controlled cloud accounts or systems, where applicable.

9. Third-Party Services and Cloud Providers​

VeloDB Cloud may interoperate with third-party services, cloud providers, marketplaces, identity providers, data sources, and customer-selected integrations. VeloDB is not responsible for third-party services that Customer enables or controls, except to the extent VeloDB has expressly agreed otherwise in the Agreement.

10. Precedence​

If this Cloud Addendum conflicts with the General Terms and Conditions, this Cloud Addendum controls for VeloDB Cloud. If an executed Order Form includes customer-specific cloud service terms, the Order Form controls for the conflicting customer-specific subject matter. If the BYOC Addendum applies and conflicts with this Cloud Addendum for BYOC subject matter, the BYOC Addendum controls for that BYOC subject matter. If this Cloud Addendum conflicts with the DPA regarding Processing of Customer Personal Data, the DPA controls for that subject matter. If this Cloud Addendum conflicts with the Security Addendum regarding security controls for Customer Personal Data, the Security Addendum controls for that subject matter.

11. Updates​

Updates to this Cloud Addendum are handled under the Agreement. During an active Order Form term, updates will not materially reduce Customer's rights or VeloDB's obligations for VeloDB Cloud unless required by law, expressly permitted by the applicable Order Form, or agreed by Customer.