VeloDB BYOC Addendum

Effective Date: June 15, 2026

Last Updated: June 15, 2026

This VeloDB BYOC Addendum (the "BYOC Addendum") applies only when an Order Form, online checkout flow, marketplace order, private offer, statement of work, or other ordering document accepted by VeloDB identifies the ordered Services as bring-your-own-cloud, customer-managed cloud, customer cloud, or a similar deployment model ("BYOC").

This BYOC Addendum supplements the VeloDB General Terms and Conditions, the applicable Cloud Addendum, and the other documents incorporated into the Agreement. Except as modified by this BYOC Addendum, the Agreement remains in effect. Capitalized terms not defined in this BYOC Addendum have the meanings given in the Agreement.

If this BYOC Addendum conflicts with the Agreement for BYOC-specific subject matter, this BYOC Addendum controls for that subject matter. If this BYOC Addendum conflicts with the Data Processing Addendum regarding Processing of Customer Personal Data, the Data Processing Addendum controls for that subject matter. If an executed Order Form includes customer-specific BYOC terms, the Order Form controls for the conflicting customer-specific subject matter.

1. Definitions

"BYOC Data Plane" means the warehouse compute, storage, cache, networking, identity, key-management, agent, monitoring, logging, and related resources deployed in or connected to the Customer Cloud Environment for the applicable BYOC Services, as described in the Order Form or Documentation.

"BYOC Services" means VeloDB Services provided under a BYOC deployment model, including applicable provisioning, management, orchestration, monitoring, support, maintenance, security, update, and service components.

"Control Plane" means VeloDB-controlled systems, consoles, APIs, services, workflows, accounts, tools, and infrastructure used to provision, manage, monitor, secure, support, bill, administer, or operate BYOC Services.

"Customer Cloud Environment" means the cloud account, project, subscription, resource group, virtual network, storage resources, identity and access resources, keys, logs, security controls, and other cloud resources that Customer owns, controls, or makes available for BYOC Services.

"Customer Cloud Provider" means the third-party cloud provider that Customer selects or uses for the Customer Cloud Environment.

"Operational Data" means operational, technical, telemetry, diagnostic, configuration, account, security, support, audit, billing, and usage records generated by, submitted to, or relating to BYOC Services. Operational Data excludes Customer Data in identifiable form except to the extent Customer Data appears in logs, support materials, diagnostic materials, query materials, configuration records, or other records submitted by Customer or generated by enabled features.

"Support Access" means VeloDB personnel or systems access to the Customer Cloud Environment, BYOC Data Plane, Operational Data, or Customer-provided materials for support, maintenance, troubleshooting, security, incident response, service operation, or similar purposes.

2. BYOC Service Model

2.1 BYOC Deployment. Subject to the Agreement, the applicable Order Form, and this BYOC Addendum, VeloDB will provide BYOC Services that allow Customer to deploy or operate VeloDB-managed service components in or connected to the Customer Cloud Environment.

2.2 Order Form Scope. The applicable Order Form or ordering record identifies the purchased Services, subscription term, deployment model, cloud provider, region or supported location, usage limits, support tier, commercial terms, and any customer-specific exceptions. BYOC technical details may be further described in Documentation, approved support materials, security materials, offboarding materials, or customer-specific exhibits, but those materials do not create additional contractual commitments unless expressly incorporated into the Agreement or applicable ordering record.

2.3 Control Plane and BYOC Data Plane. BYOC Services may involve both VeloDB-controlled Control Plane components and Customer-controlled BYOC Data Plane resources. VeloDB uses the Control Plane to provide, operate, secure, monitor, support, bill, and administer the BYOC Services. Customer remains responsible for the Customer Cloud Environment and Customer-controlled configurations.

2.4 Documentation and Changes. Customer will follow applicable BYOC Documentation for deployment, configuration, operation, security, updates, architecture, and offboarding. VeloDB may update BYOC features, prerequisites, deployment methods, service components, architecture materials, and Documentation to improve, secure, maintain, or comply with laws affecting BYOC Services. During an active Order Form term, updates will not materially reduce Customer's rights or VeloDB's obligations for the ordered BYOC Services unless required by law, expressly permitted by the applicable Order Form, or agreed by Customer.

3. Customer Cloud Environment

3.1 Customer Responsibility. Customer is responsible for the Customer Cloud Environment, including cloud accounts, projects, subscriptions, regions, networking, firewalls, routes, private connectivity, identity and access management, service accounts, roles, keys, encryption settings, logs, backup policies, monitoring, cloud provider costs, cloud provider terms, and customer-managed security controls.

3.2 Required Permissions and Resources. Customer will grant and maintain the permissions, roles, credentials, keys, tokens, endpoints, agents, policies, trust relationships, and network access reasonably required for VeloDB to provide BYOC Services. Customer is responsible for ensuring that those permissions and resources remain valid, accurate, and sufficient during the applicable Order Form term.

3.3 Customer Changes. Customer will not modify, revoke, delete, disable, rotate, restrict, or otherwise change required resources, permissions, keys, network paths, endpoints, agents, policies, trust relationships, or configurations in a way that materially impairs BYOC Services, creates security or service-integrity risk, or prevents VeloDB from providing support, unless Customer coordinates the change with VeloDB as described in the Documentation, Order Form, or approved offboarding process.

3.4 Customer Cloud Provider. Customer's use of the Customer Cloud Provider is governed by Customer's agreement with that provider. VeloDB is not responsible for the Customer Cloud Provider, Customer's cloud costs, Customer's cloud provider outages, Customer's cloud provider terms, or Customer's cloud provider configurations, except to the extent VeloDB expressly agrees in an Order Form.

4. Data Boundary and Operational Data

4.1 Customer Data. As between the parties, Customer retains ownership of Customer Data. Customer is responsible for Customer Data and for configuring the BYOC Services and Customer Cloud Environment in accordance with Customer's data governance, security, privacy, backup, export, retention, and compliance requirements.

4.2 No Blanket Residency Statement. BYOC deployment may place warehouse compute, storage, or other data-plane resources in the Customer Cloud Environment. That placement should not be read as a blanket statement that all data, logs, metadata, query records, diagnostic records, support materials, Operational Data, or related records remain only in the Customer Cloud Environment, Customer's virtual private cloud, or a selected region. Any data residency, access, transfer, location, retention, or support statement is subject to the Agreement, DPA, Security Addendum, Subprocessor List, Documentation, enabled features, support workflow, offboarding treatment, and applicable Order Form.

4.3 Operational Data. VeloDB may collect, receive, generate, access, process, store, and use Operational Data to provide, monitor, secure, support, troubleshoot, analyze, bill, administer, and improve BYOC Services. Operational Data may include control-plane metadata, operational telemetry, metrics, logs, configuration records, account records, user records, query metadata, diagnostic records, support records, access audit records, session records, command logs, billing records, and other records relating to the operation or use of BYOC Services.

4.4 Sensitive Operational Data. Operational Data may include Customer Data, Customer Confidential Information, or Customer Personal Data depending on Customer's configuration, enabled features, logs, diagnostic materials, support requests, query text, metadata, attachments, or other submitted materials. Customer Data remains Customer Data if it appears in Operational Data. Operational Data that constitutes Customer Personal Data is processed in accordance with the DPA.

4.5 Usage Data. VeloDB may use Usage Data and Operational Data as described in the Agreement. VeloDB will not disclose Usage Data or Operational Data to third parties in a form that identifies Customer or Customer Confidential Information except as permitted by the Agreement, DPA, this BYOC Addendum, or Customer's written instructions.

5. Support Access and Diagnostics

5.1 Support Workflow. VeloDB may provide support for BYOC Services as described in the applicable Order Form, Support Policy, Documentation, support materials, or approved support workflow. Support Access may be required to investigate, troubleshoot, maintain, secure, restore, or improve BYOC Services.

5.2 Customer Assistance. Customer will reasonably cooperate with VeloDB support requests, including by providing information, logs, access, approvals, diagnostic materials, configuration details, reproduction steps, or configuration changes reasonably needed to resolve support issues, security issues, or service incidents.

5.3 Access Controls. VeloDB will use commercially reasonable administrative, technical, and organizational controls for VeloDB-managed Support Access, as described in the Agreement, Security Addendum, Order Form, Documentation, Support Policy, or approved customer-facing security materials.

5.4 Customer-Specific Support Restrictions. Customer-specific statements that support is limited to specified locations, personnel, time windows, approval workflows, diagnostics-only access, no-offshore access, U.S.-only access, or other access restrictions apply only when stated in the applicable Order Form, approved support workflow, customer-specific exhibit, or signed written commitment.

6. Security and Shared Responsibility

6.1 VeloDB Responsibilities. VeloDB is responsible for VeloDB-controlled components of BYOC Services, including applicable Control Plane security controls, service orchestration, service monitoring, support workflows, and VeloDB-controlled Operational Data, as described in the Agreement, Security Addendum, Order Form, and Documentation.

6.2 Customer Responsibilities. Customer is responsible for Customer-controlled components, including the Customer Cloud Environment, Customer Data, customer-managed identities, customer-managed keys, customer-managed network controls, customer-managed logs, customer-managed backup and recovery, customer applications, customer integrations, Customer Cloud Provider settings, and Customer's use of BYOC Services.

6.3 Security Events. Security Incident notice obligations for Customer Personal Data are described in the DPA. Customer is responsible for notifying VeloDB promptly of security events, suspected unauthorized access, compromised credentials, cloud provider incidents, or configuration changes that may affect BYOC Services.

7. Subprocessors and Third-Party Services

7.1 Subprocessors. VeloDB may use Subprocessors to provide BYOC Services as described in the DPA and applicable Subprocessor List.

7.2 Customer Cloud Provider Classification. For Customer-controlled cloud accounts, subscriptions, projects, networks, storage, keys, logs, identities, and other Customer Cloud Environment resources, Customer's selected Customer Cloud Provider is generally Customer's direct provider. The same cloud provider may separately act as VeloDB's Subprocessor for VeloDB-controlled systems, control-plane services, support workflows, monitoring, billing, account administration, diagnostics, or other Service components that VeloDB controls, as described in the applicable Subprocessor List or approved service materials.

7.3 Customer-Enabled Services. Customer is responsible for third-party services, integrations, identity providers, notification destinations, monitoring tools, data sources, data sinks, marketplaces, and other services that Customer enables, controls, or connects to BYOC Services, unless VeloDB expressly agrees otherwise in an Order Form.

8. Service Levels and Support

8.1 SLA Applicability. BYOC Services are covered by the VeloDB Cloud Service Level Agreement only when the applicable Order Form, checkout flow, marketplace order, service plan, private offer, or other accepted ordering record expressly references the SLA or identifies the applicable BYOC Services as covered by it.

8.2 BYOC SLA Scope. If BYOC Services are covered by the SLA, the SLA applies only to VeloDB-controlled service components, VeloDB-managed service operations, and causes within VeloDB's reasonable control. SLA exclusions include unavailability caused by Customer, the Customer Cloud Environment, Customer Cloud Provider, Customer-controlled configurations, Customer-managed keys, Customer networks, Customer applications, customer-selected capacity or availability topology, customer-side infrastructure logs or alerts, or other causes outside VeloDB's reasonable control. Public BYOC documentation or availability guidance does not create an SLA, service credit remedy, recovery time objective, recovery point objective, multi-availability-zone commitment, or disaster-recovery commitment unless expressly incorporated into the applicable ordering record.

8.3 Support. VeloDB will provide support for BYOC Services in accordance with the applicable Order Form and Support Policy. Support commitments may depend on Customer cooperation, Customer Cloud Environment availability, Customer Cloud Provider availability, and Customer's maintenance of required permissions and configurations.

9. Suspension

VeloDB may suspend BYOC Services or related Control Plane access as described in the Agreement. VeloDB may also suspend or limit BYOC Services if: (a) Customer fails to maintain required permissions, network paths, keys, roles, endpoints, or resources; (b) Customer's configuration creates a material security, legal, operational, service-integrity, or support risk; (c) Customer's use violates the Acceptable Use Policy or applicable law; (d) suspension is required by law or a cloud provider; (e) Customer's use materially exceeds agreed limits; or (f) continued operation may harm VeloDB, Customer, other customers, the Customer Cloud Environment, the Customer Cloud Provider, or third parties. VeloDB will use commercially reasonable efforts to limit suspension to the affected BYOC Services and restore access when the cause is resolved.

Suspension or limitation of VeloDB-controlled components does not transfer responsibility for Customer-controlled resources, Customer Cloud Provider charges, Customer Data, customer-managed backups, customer-managed logs, customer-managed keys, or customer-managed cleanup to VeloDB unless the applicable Order Form states otherwise.

10. Offboarding, Export, and Deletion

10.1 Customer-Controlled Resources. Customer is responsible for exporting, retaining, deleting, preserving, revoking, or deprovisioning Customer Data and resources in the Customer Cloud Environment, including storage, backups, snapshots, logs, keys, identities, endpoints, roles, policies, agents, and deployment artifacts.

10.2 VeloDB-Controlled Records. After expiration or termination of BYOC Services, VeloDB will delete Customer Data from VeloDB-controlled systems in accordance with the Agreement, DPA, applicable retention practices, standard deletion practices, and applicable law, unless retention is required by law or the Agreement. VeloDB-controlled residual records may include service metadata, query metadata, diagnostic or performance telemetry, support or observability data, account metadata, billing records, legal records, audit logs, and support tickets.

10.3 Offboarding Materials. VeloDB may provide public offboarding guidance, BYOC offboarding materials, support-assisted offboarding, or customer-specific offboarding exhibits. Offboarding materials may describe supported export methods, warehouse deletion, backup treatment, access revocation, customer-controlled cloud cleanup, residual records, and written confirmation options. Customer remains responsible for validating that Customer-controlled resources are exported, retained, deleted, preserved, revoked, or deprovisioned in accordance with Customer's requirements before taking destructive actions.

11. Updates

VeloDB may update this BYOC Addendum from time to time by website posting, email, account notice, support portal notice, or another reasonable mechanism. Each published version will identify an effective date or last updated date.

During an active Order Form term, VeloDB will not materially reduce Customer's rights or VeloDB's obligations for ordered BYOC Services unless required by law, expressly permitted by the applicable Order Form, or agreed by Customer.

Customer's continued use of BYOC Services after the effective date of an updated BYOC Addendum constitutes acceptance of the updated BYOC Addendum to the extent permitted by the Agreement and applicable law. If Customer does not agree to an updated BYOC Addendum, Customer may stop using the affected BYOC Services as permitted by the Agreement and applicable Order Form.

12. Relationship to Other Terms

This BYOC Addendum addresses BYOC-specific deployment, responsibility, support-access, service-level, suspension, and offboarding terms. It does not modify the DPA, Security Addendum, Subprocessor List, Support Policy, Acceptable Use Policy, SLA, public Documentation, or any customer-specific Order Form terms except as expressly stated in this BYOC Addendum.

If this BYOC Addendum conflicts with the Cloud Addendum for BYOC-specific subject matter, this BYOC Addendum controls for that subject matter.

If this BYOC Addendum conflicts with the DPA regarding Processing of Customer Personal Data, the DPA controls for that subject matter.

If this BYOC Addendum conflicts with the Security Addendum regarding security controls, the Security Addendum controls for that subject matter.

If an executed Order Form includes customer-specific BYOC terms, the Order Form controls for the conflicting customer-specific subject matter.