--- title: "CubePath Terms of Service | CubePath" description: "These Terms of Service are the master contract between CubePath Inc. and every customer of CubePath. They apply to every Service we offer, now or in the future." language: en source: https://cubepath.com/terms --- # CubePath Terms of Service | CubePath **Version 2026-11.** The effective date of this version is shown where it is published. These Terms of Service are the master contract between CubePath Inc. and every customer of CubePath. They apply to every Service we offer, now or in the future. Product-specific rules are in the Service Terms. The Service Terms, the SLA and the AUP are Schedules 1, 2 and 3 at the end of this document. Please read them together. ## 1\. Definitions Capitalized terms have the meanings below. The Schedules and the other documents of the Agreement use the same meanings unless they say otherwise. - **Account**: the login identity of an individual User. - **Account Data**: information about you and your Users that we process to run our relationship with you, such as contact, billing, payment and identity verification details and support communications. It excludes Customer Content and Service Data. - **Acceptance Deadline**: the date by which an Owner or Admin must accept a new version after a Material Change (Section 19.2). - **Admin**: an Authorized User with the Organization role that can manage the Organization, including billing and acceptance of updated terms. - **Agreement**: the documents listed in Section 2.1. - **AI Features**: Services or features that use machine learning models, including the AI Gateway, the Control Panel assistant and AI-assisted support. **AI Input** means what you or your End Users submit to an AI Feature, and **AI Output** means content an AI Feature generates in response. - **API**: the programming interfaces through which the Services can be used, including the REST API at . - **Applicable Law**: all laws, regulations, court orders and binding government requirements that apply to a party, a Service or its use, including data protection, consumer protection, export control, sanctions and tax laws. - **Authorized User**: a User whom you allow to access your Organization, with a role such as owner, admin, member, billing or viewer, or another role shown in the Control Panel. - **AUP**: our Acceptable Use Policy in Schedule 3. - **Balance**: the prepaid funds of an Organization, kept in US dollars, consisting of the **Cash Balance** (the part funded by your payments) and Credits. - **Beta Service**: any Service or feature labeled beta, preview, early access, experimental or similar. - **Billing Period**: the period for which a Fee is charged or an Invoice issued, such as an hour, a calendar month or the term of a Commercial Plan or Order Form. - **Business Customer**: any Customer that is not a Consumer. **Consumer** means an individual acting for purposes outside their trade, business, craft or profession. - **Commercial Plan**: an Organization-level plan, currently Free, Pro, Business and Enterprise (or as renamed), that carries entitlements, limits and Plan Credits. - **Confidential Information** and **Excluded Claims**: have the meanings in Sections 11.1 and 16.3. - **Control Panel**: the web dashboard at . **CLI** means cubecli, our command-line tool. **MCP Server** means the CubePath Model Context Protocol server, which lets AI clients act on an Organization with the permissions of the User who authorizes them. - **Controller**, **Processor** and **Personal Data**: have the meanings in the data protection law that applies. For US state privacy laws, "service provider" and "contractor" correspond to Processor. - **CubePath Materials**: our software, platform, APIs, Control Panel, Documentation, trademarks, designs and related intellectual property rights, excluding Customer Content and Third-Party Offerings. - **Credentials**: passwords, API tokens, OAuth tokens, SSH keys, access keys, kubeconfigs, BMC credentials and any other means of access. - **Credits**: any non-cash value added to the Balance, namely **Promotional Credits** (from promotions, codes or coupons), **Plan Credits** (granted monthly with a Commercial Plan), **Referral Credits** (from the referral program) and **Service Credits** (granted under the SLA). - **Customer**, **you**: the individual or legal entity that accepts the Agreement for an Organization. If a company owns the Organization, the company is the Customer. - **Customer Content**: all data, software, files, configurations, images, websites, models, prompts and other content that you or your End Users upload, store, process, transmit or generate using the Services, including AI Input and AI Output. It excludes Account Data and Service Data. **Customer Personal Data** means Personal Data within Customer Content. - **Documentation**: the technical and usage documentation at and in the Control Panel. - **Emergency**: a situation that threatens the security, integrity or availability of the Services, other customers or third parties, or that requires immediate action by Applicable Law. - **End User**: anyone who accesses Customer Content or services you build on the Services, other than your Authorized Users. - **Fees**: the amounts charged for the Services, including usage, subscription and plan charges, one-time fees and support fees. **Invoice** means a document from CubePath requesting payment of Fees. - **Feedback**: suggestions, comments and ideas about the Services that you give us. - **Material Change**: a change to the Agreement that reduces your rights or increases your obligations in a way that is more than minor, other than the additions in Section 19.3\. Price changes follow Section 7.7. - **Model Provider**: a third party that provides an AI model that an AI Feature uses or makes available. - **Order Form**: a written or electronic order or agreement signed or accepted by you and CubePath that describes specific Services, prices, term or special terms. - **Organization**: the customer workspace in the Control Panel that holds Resources, the Balance, billing details and members. Each Organization is one customer for contract purposes. - **Owner**: an Authorized User with the highest Organization role, including the right to accept updated terms, manage billing and manage other Authorized Users. - **Pricing Page**: and the prices shown in the Control Panel at the time of order or use. - **Privacy Policy**: our Privacy Policy at . - **Resource**: any instance of a Service that you create or order, such as a server, IP address, bucket, cluster, database, zone, key or load balancer. - **Retention Period**: a period during which we keep Customer Content or Resources after Suspension or Termination before deleting them, as stated in Sections 8 and 9. - **Security Incident**: a breach of security of the Services that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Content. - **Service Data**: technical data generated by the operation of the Services, such as metrics, logs, traffic metadata, usage records and telemetry. Service Data excludes logs and other records of your End Users' requests that we process on your behalf in a Service such as the CDN or DNS; those records are Customer Content. - **Service Page**: the product page of a Service on cubepath.com. - **Service Terms**: our Service Terms in Schedule 1. - **Services**: every product, service, feature, tool, API, software, Control Panel function, support service and program that CubePath makes available, now or in the future, paid or free, generally available or a Beta Service. - **SLA**: our Service Level Agreement in Schedule 2. - **Suspension**: a temporary restriction, in whole or in part, of access to or operation of Services or Resources. **Termination** is the end of the Agreement or of a Service, and **terminate** has a matching meaning. - **Third-Party Offering**: software, models, services or content provided by a third party and made available through the Services, such as operating system images and licenses, marketplace applications, Helm add-ons and models available through the AI Gateway. - **User**: an individual who has an Account. "Include" and "including" are not limiting. In Sections 1 to 23, a reference to a Section is to one of those Sections unless another document is named. In a Schedule, a reference to a Section is to a Section of that Schedule unless another document is named. ## 2\. The Agreement ### 2.1 Documents that make up the Agreement The Agreement between you and CubePath Inc. consists of: 1. these Terms of Service ("Terms"), which are Sections 1 to 23 of this document; 2. the Service Terms (Schedule 1); 3. the SLA (Schedule 2); 4. the AUP (Schedule 3); and 5. any Order Form. The Service Terms, the SLA and the AUP are Schedules to these Terms and are published with them as one document: they carry the same version, and accepting the Terms accepts them. Each of them remains a separate document of the Agreement for Section 2.2\. The Agreement also includes any document that one of these documents expressly incorporates. The Agreement also includes the Pricing Page and the order and checkout screens of the Control Panel (for prices, billing models, limits and renewal terms), and the parts of the Documentation to which the Service Terms refer for limits, retention, backup frequency and export formats. If any of them conflicts with a document in the list, the document in the list prevails. This document is published at . ### 2.2 Order of precedence If documents of the Agreement conflict, the following order applies, from highest to lowest: 1. an Order Form, only for the terms it expressly overrides; 2. the Service Terms, for the Service concerned; 3. the SLA, for service levels and Service Credits; 4. the AUP; and 5. these Terms. However, no document other than an Order Form signed by CubePath can change Sections 15 (Warranties and Disclaimers), 16 (Limitation of Liability), 17 (Indemnification) and 21 (Governing Law and Disputes) of these Terms. Section 20 (Consumers) always applies to Consumers and prevails over every other document, including an Order Form, to the extent it protects mandatory rights. ### 2.3 Order Forms CubePath and a Customer may agree on an Order Form for negotiated terms, such as Enterprise plans, IP Transit, Cloud Gateway, committed terms, custom service levels, support commitments or a different liability cap. An Order Form is governed by these Terms. It overrides these Terms and the other documents only where it says so expressly. An Order Form takes effect when both parties have signed or electronically accepted it, or on the date it states. An Order Form is not a separate master agreement: the Terms apply to every Customer, including those with an Order Form. ### 2.4 The Privacy Policy is not part of the Agreement The Privacy Policy describes how we handle personal data. It is a notice, not a contract, and it is not part of the Agreement. Nothing in the Privacy Policy changes your rights or our obligations under the Agreement. ### 2.5 Language The Agreement is written in English. The English text is the original and the only binding text. We may publish translations, for example in Spanish, for information only; a translation has no legal effect. If a translation differs from the English text, the English text applies. ## 3\. Accounts, Organizations and Eligibility ### 3.1 Eligibility You must be at least 18 years old (or the age of majority where you live, if higher) and have the legal capacity to enter into the Agreement. By accepting the Agreement you confirm this, and we rely on your confirmation. If we learn that a User is under that age, we may close the Account and any Organization that depends on it. You may not use the Services if Applicable Law prohibits you from receiving them, or if we have previously terminated the Agreement with you for cause and have not agreed in writing to a new relationship. ### 3.2 Acting for an organization If you accept the Agreement for a company or other entity, you represent that you have authority to bind it, the entity is the Customer, and we may rely on that authority. If you do not have authority, you are personally responsible for the Agreement and the Fees. ### 3.3 Organizations, roles and Authorized Users An Organization owns Resources, holds the Balance and is billed. You act through Users who hold roles in the Organization. Owners and Admins can invite and remove Authorized Users, manage billing details and accept updated terms. You are responsible for the roles you grant, for the acts and omissions of your Authorized Users and for keeping the list accurate. We act on instructions from the Owners registered for the Organization. If Owners or Admins disagree, or someone claims control of an Organization, we are not obliged to resolve the dispute, and we may suspend requested changes (such as changes to ownership, payment details, Credentials or deletion of Resources) until the people involved settle it or a court of competent jurisdiction decides it. On the death or incapacity of an individual Owner, we deal with a person who shows legal authority to act for them. Moving a Resource or project between Organizations is not self-service; we may do it at an Owner's request if each affected Organization's Owner confirms and we are satisfied it is legitimate, and we may refuse or charge for it. ### 3.4 Verification and fraud prevention We may require identity, business or payment verification before or after you create an Organization or order a Service. For example, we may require a verification deposit with the first payment of a new Organization (credited to the Balance and subject to Section 7.9), additional card authentication, document checks for two-factor authentication recovery or an email address change, or information about beneficial owners. We may use automated fraud screening and third-party risk signals to decide whether to accept a signup, ask for more verification or decline a promotion. We may refuse, limit or end Service for risk reasons without giving the details of our screening. If an automated decision declines your signup or payment, you may write to [support@cubepath.com](mailto:support@cubepath.com) for review by a person. Before we change the email address of an Account, reset two-factor authentication, recover an Account or transfer ownership of an Organization, we may require reasonable proof of identity and authority, and we may refuse if the proof is not sufficient. After a recovery or change, we may temporarily restrict changes to Credentials and destructive actions. ### 3.5 Credentials and account security You are responsible for keeping your Credentials, and those of your Authorized Users, secure and confidential, and for using the security features we offer, such as two-factor authentication, where your risk calls for them. You are responsible for all activity under your Organization and your Credentials, whether or not you authorized it, including activity by tokens, OAuth clients, MCP clients, scripts and AI agents that you or your Authorized Users create or authorize. Notify us promptly at [support@cubepath.com](mailto:support@cubepath.com) if you suspect unauthorized use. We may freeze, revoke or rotate Credentials that we reasonably believe are compromised or misused, and we may ask you to take steps to regain control. ### 3.6 Multiple Accounts and Organizations One User may belong to several Organizations, and one Organization may have several Users. Each Organization is a separate customer relationship with its own Balance, limits and Fees. You may not create or use additional Accounts or Organizations to evade resource limits, quotas, verification, a Suspension or Termination, a chargeback or payment dispute, or to obtain Promotional Credits more than once. If you do, we may suspend or terminate all of the Accounts and Organizations involved and remove the Credits. ## 4\. The Services ### 4.1 Scope, including future Services The Agreement applies to every Service. We may launch new Services, new features and new categories of Services at any time. A new Service is covered by the Agreement from the day it becomes available to you, without any change to these Terms. The Service Terms say which rules apply to which Service. Where nothing more specific is published for a new Service, Section 4.2 explains which rules apply. ### 4.2 Service Terms and Service Categories The Service Terms are organized in two layers: 1. **Part A, Service Categories**: rules that apply to every Service in a category, such as Unmanaged Infrastructure, Managed Services, Network and Security Services, Edge Services, AI Services, Developer Tools and Automation, Third-Party Offerings and Programs. Each category says what CubePath operates and what you are responsible for. 2. **Part B, Specific Services**: one section for each Service that has its own rules. Each section names the category it belongs to. A Service that has no section in Part B belongs to the category that its Service Page or Documentation names. If no category is named, the Service is treated as Unmanaged Infrastructure, it has no SLA, and the rules for Beta Services apply if the Service is labeled beta, preview or early access. We may add a section to Part B for a new Service, or a new category to Part A, at or before launch. These additions take effect when we publish them and apply only to the new Service or category. They are not a Material Change and do not need your acceptance. A change that reduces your rights for a Service you already use follows Section 19\. The SLA covers only the Services listed in its table; every other Service has no SLA. Adding a Service to the SLA takes effect when we publish it. ### 4.3 Responsibility model: unmanaged and managed **Unmanaged Infrastructure.** For Services in the category Unmanaged Infrastructure (for example Cloud VPS and Dedicated Servers) we operate the underlying hardware, virtualization, network and Control Panel. You administer everything inside the Resource: the operating system, software, configuration, patches, security, backups and licenses. We do not administer, monitor or support your software or workloads, or provide system administration inside your Resource. **Managed Services.** For Services in the category Managed Services we operate the Service up to the scope described in its section of the Service Terms and in the Documentation (for example engine updates, the control plane or replication). You remain responsible for your data, schemas, queries, workloads, applications, content, the access controls you configure, your Credentials and your configuration choices. We do not support your software, workloads or content running on a Managed Service unless an Order Form says so. **Support.** Support is described in the Service Terms, Section B.26\. It covers the platform, the Control Panel, the network, hardware and billing. Unless an Order Form states response times, they are not guaranteed. ### 4.4 Beta Services A Service or feature that the Control Panel, the website or the changelog labels beta, preview, early access, experimental or similar is a Beta Service. Beta Services are provided "as is", are excluded from the SLA and from support commitments, may contain defects, and may be changed, limited or withdrawn at any time. Fees for Beta Services, if any, are the rates shown in the Control Panel. If you have stored data in a paid Beta Service, we will use reasonable efforts to give advance notice before withdrawing it, except where immediate withdrawal is required for security, legal or abuse reasons. ### 4.5 Third-Party Offerings Third-Party Offerings are provided by third parties, not by CubePath, under the third party's terms, which you agree to follow. This includes operating system images and licenses, marketplace applications, Helm add-ons and models available through the AI Gateway. Unless the Service Terms say otherwise, we are responsible only for the initial installation of images and applications that we install, and we provide Third-Party Offerings without warranty. Where we supply a license as part of a Service price, we may pass through the vendor's end-user terms and suspend the license if you breach them. You are responsible for any license a Third-Party Offering requires that we do not supply, and for its configuration, updates and security. We may stop offering a Third-Party Offering, for example if the third party withdraws it. ### 4.6 Changes to Services and deprecation We may change, improve, replace or discontinue Services and features, and retire versions, templates, plans, models and locations. If we discontinue a Service or a material feature you use, or retire a version in a way that stops your Resources from working, we will give reasonable advance notice, by email or in the Control Panel, unless a shorter period is required for security, legal or abuse reasons or because a third party has withdrawn what the Service depends on. The Service Terms, Part A.12, describe deprecation and end-of-life. If we discontinue a Service for which you prepaid Fees, we refund the prepaid Fees for the period after discontinuation (not Credits). ### 4.7 Resource limits Services are subject to limits and quotas, such as numbers of servers, IP addresses, vCPUs, memory, disk, zones, rules, members, requests and API calls. Limits depend on the Service, the Commercial Plan and the verification status of the Organization, and are shown in the Control Panel, the Pricing Page or the Documentation. We may grant or refuse requests for higher limits at our discretion and may require justification and verification. Rate limits protect the platform and may apply to the API, CLI, MCP Server and other Services. "Unlimited" and "unmetered" are not literal: the Service Terms and the AUP describe the fair use that applies. ### 4.8 Free Services Some Services, features or tiers are free or are included in a paid Service or Commercial Plan. Free Services have no SLA, are provided "as is", and we may change, limit or withdraw them at any time. They are subject to the Agreement and the AUP like any other Service. ## 5\. Your Responsibilities ### 5.1 Customer Content You are solely responsible for Customer Content: for its accuracy, quality, legality and security, for having all rights, licenses and consents needed to use it with the Services, and for all claims and harm that arise from it. We do not review Customer Content before it is stored or served, except as described in Section 14. ### 5.2 Compliance with law You must comply with Applicable Law in connection with your use of the Services and Customer Content, including laws on privacy, consumer protection, intellectual property, electronic communications, export control and sanctions, and any laws specific to your industry. You decide whether the Services and the location of your Resources suit your data and your legal and regulatory duties. The Services are not designed or certified for any particular regulatory regime unless the Service Terms or an Order Form say so, and you may not store regulated data (for example payment card data, health data or classified information) unless you have made sure that the Service and your configuration meet the rules that apply. Unless an Order Form says so, we do not sign business associate agreements, and the Services are not offered for protected health information under HIPAA, for cardholder data that requires PCI DSS compliance by us, for technical data controlled under the International Traffic in Arms Regulations, or for government data that requires FedRAMP authorization. ### 5.3 End Users and your customers If you offer services to End Users or other third parties on or through the Services, you are responsible for them and for their acts and omissions as if they were your own. You must have your own terms with them and, where required, a privacy notice, and you must handle their requests, complaints and legal notices. We provide support only to our direct customers. The AUP states the rules for hosting third parties and reselling. ### 5.4 Acceptable Use Policy You and your End Users must follow the AUP at all times. The AUP is part of the Agreement. ### 5.5 Security of your Resources You are responsible for the security of your Resources and Customer Content. This includes strong Credentials, patching, firewalls and access rules, encryption choices, monitoring and the configuration of the security features we offer. Resources that you leave exposed or that are compromised may be used to attack others. Section 8.2 explains how we may respond. You must notify us without undue delay at [support@cubepath.com](mailto:support@cubepath.com) of any Security Incident or compromise of your Resources that affects or may affect the Services, other customers or us, and give us the information we reasonably need. ### 5.6 Backups You are responsible for your backup strategy and for testing that you can restore your data. Backups and snapshots that we sell are an optional convenience feature, not a guarantee of recovery or of application consistency. They have the frequency, retention and limits stated in the Service Terms and the Documentation, and they are not a substitute for independent copies that you keep outside the Service. Some Services, such as Object Storage, are not backed up by CubePath. We are not responsible for the loss of data that results from your failure to keep your own backups, except as stated in Section 16. ### 5.7 Automated access, API, MCP and AI agents You may use the Services through the API, CLI, Terraform provider, MCP Server, OAuth connected apps, scripts and other automation, including AI agents. Whatever acts with your Credentials or with the permissions of your Users acts for you. You are responsible for every action it takes, including creating, changing and deleting Resources, and for the resulting Fees, whether or not you intended the action. Limit tokens to the scopes needed, restrict them by IP address where you can, review and revoke access you no longer need, and test automation before using it on production data. You can revoke tokens and connected apps at any time in the Control Panel. We may apply rate limits and block clients that harm the Services. ## 6\. CubePath Access to Customer Content and Resources We do not administer, monitor or access the contents of your operating system, applications or data as part of the Services. You alone are responsible for them. We may nevertheless access a Resource or its management interfaces, and in some cases the content on it, only in these cases: 1. **Your requests and your actions.** At your request, or through actions that you start in the Control Panel, API, CLI or MCP Server, for example console access, rescue mode, password reset, operating system reinstall, restore or migration. 2. **Operating the platform.** To operate, secure and protect the platform, including hardware diagnostics, virtualization and storage management, and out-of-band management (BMC or KVM) of dedicated servers. 3. **Diagnosis.** To diagnose a problem that you report, which may include viewing a read-only image of the console screen, without keyboard or mouse input. 4. **Abuse and security.** To investigate or stop suspected violations of the AUP, Security Incidents or abuse, which may include suspending the Service, viewing a read-only image of the console, and restricting access to specific content. 5. **End of Service.** To wipe storage when a Service is terminated or a server is returned. 6. **Law.** Where Applicable Law or valid legal process requires it (Section 14.5). We log staff access to Resources. We do not use that access to read, copy or use Customer Content for any other purpose. Nothing in this Section obliges us to monitor Customer Content or to look for illegal activity. ## 7\. Fees, Billing and Payment ### 7.1 Billing models You agree to pay all Fees for the Services you use. We bill under these models, and the model of each Service is the one on its Pricing Page or Control Panel order screen: 1. **Hourly, from the Balance**: charged for each hourly (or shorter) Billing Period while the Resource exists, as the Service Terms describe. Some Resources are billed while stopped. 2. **Recurring Invoice**: charged by Invoice in advance, monthly or for longer periods, for example for dedicated servers, add-ons, IP Transit and prepaid terms. 3. **Usage-based**: charged from the Balance by measured use, such as traffic, requests, storage or tokens. 4. **Commercial Plan subscription**: a recurring charge for a Commercial Plan (Section 7.12). 5. **One-time fee**: for example setup or paid support fees. 6. **Committed term under an Order Form**: Fees and payment terms as the Order Form states. Prices and rates are shown on the Pricing Page or in the Control Panel and are not repeated in the Agreement. Fees are stated in US dollars. ### 7.2 Balance and prepaid Services The Balance is a US dollar ledger. Hourly and usage-based Services are deducted from the Balance, and you are responsible for keeping it positive while you hold Resources billed from it. When the Balance reaches zero or less while the Organization has billable Resources, Section 8.1 applies. The Control Panel shows the part of the Balance available to spend; part may be temporarily unavailable, for example funds from a top-up not yet confirmed. Top-ups are subject to the minimum and maximum amounts shown in the Control Panel. Some Credits may be restricted to certain Services, as the Service Terms or the Control Panel show. The Balance earns no interest and is not a bank deposit. ### 7.3 Invoices Where a Service is billed by Invoice, we issue the Invoice in advance, normally about 10 days before the due date, and you must pay it by the due date shown. Invoices are available in the Control Panel and are sent to the billing contact you register. Bank-transfer payments are credited when we confirm receipt. If an Invoice is not paid on time, Section 8.1 applies, and we may charge late-payment costs where the Invoice or an Order Form says so and Applicable Law allows. **Automatic renewal.** Recurring Invoice Services (including dedicated servers, add-ons, IP Transit and prepaid terms) and Commercial Plans renew automatically for a period equal to the one you bought, at the price shown at renewal, until you cancel. Before you buy we show, at checkout and next to the payment button, that the Service renews automatically, the renewal price, the renewal period, the date by which you must cancel, and how to cancel. You consent to renewal by selecting the renewal option or the checkbox provided for it; this consent is separate from your acceptance of the Agreement. After you buy, we send you an email confirming these terms and how to cancel. For terms of one year or longer we send a reminder by email between 30 and 7 days before renewal. You can cancel online in the Control Panel at any time; cancellation takes effect at the end of the paid period and you keep the Service until then. We charge no fee to cancel. If the Control Panel shows a cancellation cutoff date earlier than the renewal date, it is shown next to the cancel option. ### 7.4 Automatic charges and Auto-reload If you enable the following features, you authorize us and our payment providers to charge your selected payment method each time without further confirmation, until you disable the feature: 1. **Auto-reload**: when the Balance falls to the threshold you set, we charge the amount needed to reach the target you choose, within any monthly cap you set. It can run when the Balance is negative, and there is a cooldown between charges (currently 24 hours). 2. **Automatic payment of Invoices and plan renewals**: we charge your default payment method about 5 days before the due date. You can disable these features in the Control Panel at any time, for future charges. Not all payment methods support automatic charges. A failed charge does not remove the amount you owe. ### 7.5 Payment methods and currency We accept the payment methods shown at checkout, which currently include payment cards (processed by Stripe), PayPal and bank transfer against an Invoice. Availability may vary by country, amount and risk, and we may refuse a payment method or require verification of a payment we reasonably suspect to be fraudulent. If you pay in another currency, the payment is converted at the exchange rate shown at payment and you bear conversion costs and bank fees. Refunds are made in the currency of the original payment, so the amount returned may differ from the amount credited to the Balance. ### 7.6 Taxes Fees exclude taxes, duties, levies and withholdings ("Taxes"), unless the price shown says it includes them. You are responsible for all Taxes arising from your purchase and use of the Services, other than taxes on our net income. If we must collect Taxes, we add them to the Invoice or charge. If you must withhold Taxes from a payment, you will increase the payment so that we receive the amount we would have received without the withholding. If you are exempt from a Tax, you must give us valid tax details or exemption documents before the Invoice is issued. Prices shown to Consumers include the Taxes the law requires us to include. ### 7.7 Price changes We may change prices. For an increase that affects a Service you already use, or the renewal of a Commercial Plan, we give at least 30 days' notice by email, in the Control Panel or both, and the increase applies to your use after the notice period. New orders use the prices current at the time of the order. A decrease, or the price of a new Service, may apply immediately. An Order Form may fix prices for its term. If you do not accept an increase, you may delete the affected Resources or cancel under Section 9.2 before it applies, without penalty, and you receive a refund of prepaid Fees for the period after cancellation. ### 7.8 Credits Credits have no cash value, are not refundable or transferable, and may be restricted to certain Services. Plan Credits expire on the first day of the month after they are granted, and Promotional Credits on the date shown for the promotion. Referral Credits and Service Credits follow the rules of the program or SLA that grants them. The Control Panel shows the order in which Cash Balance and Credits are used. Promotion codes may carry extra conditions, such as a minimum deposit. Credits are forfeited when they expire, when your Organization is closed or terminated (except that unused Service Credits are first applied to Fees you owe, as the SLA, Section 4.3, provides), and, if granted with a payment that is refunded or charged back, to the extent of that payment. We may remove Credits obtained through abuse, fraud or breach of the Agreement. ### 7.9 Refunds 1. **Unused Cash Balance.** You may ask [support@cubepath.com](mailto:support@cubepath.com) for a refund of the unused Cash Balance. We refund to the original payment method where possible, otherwise by another reasonable means. We may refuse or limit a refund, for example where we reasonably suspect fraud or abuse, where the payment is older than the payment provider allows to be refunded, where the law requires it (including anti-money-laundering and sanctions rules), or where the funds came from adjustments we made. We may deduct non-recoverable fees charged by the payment provider. Refunds are subject to amounts you owe us and to any open Dispute. 2. **New customers.** Within 7 days of its first payment, a Customer that has had no previous CubePath services, or none for at least 180 days, may ask for a refund of the amount paid. We keep an administrative fee of 5% of the refunded amount, with a minimum of USD 1. 3. **Dedicated servers.** Fees for a dedicated server are not refundable after the server has been delivered. If we do not deliver an ordered server within 72 hours after we confirm your payment, or if you cancel the order before provisioning starts, we refund the amount paid in full. 4. **Commercial Plans.** Fees for a paid period of a Commercial Plan are not refunded on downgrade or cancellation. A cancellation takes effect at the end of the paid period. If you cancel after a renewal has been charged automatically but before the renewal date, we refund that charge in full (Service Terms, Section B.25.3). 5. **Not refundable.** Credits, fees for Resources already used, setup fees once the work is done, and Fees for periods that have started are not refundable, except where the Agreement expressly provides for a refund or where the law requires one. Refunds in other cases are at our discretion. A refund is not a waiver of any right we have. ### 7.10 Chargebacks and payment disputes If you intend to dispute a charge with your card issuer, bank or payment provider (a "Dispute"), please contact [support@cubepath.com](mailto:support@cubepath.com) first so we can fix the problem, and cooperate in good faith to resolve the Dispute. While a Dispute is open we may suspend the Organization's Services (Section 8.2). When the payment provider withdraws the disputed amount, we deduct it from the Balance, and if the Balance becomes zero or negative Section 8.1 applies. If the Dispute is decided in our favor or the funds are returned, we credit the amount back. If it is decided against us, the amount stays due, and you reimburse the fees the payment provider charges us for the Dispute and an administrative fee of USD 25, to the extent Applicable Law allows. We never delete your data because of a Dispute alone; deletion follows only Section 8.1\. We keep the records we need to answer the Dispute until it is closed. ### 7.11 Billing errors and invoice disputes If you believe an Invoice or charge is wrong, notify [support@cubepath.com](mailto:support@cubepath.com) promptly after its date, with the details. We will review it and correct any error by refund or credit to the Balance. You must pay the undisputed part by the due date, and Section 8.1 still applies to it. We may correct our own billing errors, including undercharges, within a reasonable time after we find them. This Section does not limit rights that Applicable Law gives you. ### 7.12 Paid support and other fees Paid support is charged as shown when you order it. For example, an urgent-priority ticket carries the fee shown when you open it (currently a flat fee charged to the Organization's payment card). The fee pays for priority handling by on-call staff and does not guarantee resolution in any period. If an urgent ticket cannot be created after the fee is charged, we refund the fee. Other paid services and one-time fees are charged as shown on the Pricing Page, in the Control Panel or in an Order Form. **Commercial Plans.** Commercial Plans are priced in US dollars and renew automatically for the term you chose unless you cancel before the renewal date. A term discount applies only to its term. Section 7.3 states how renewal is disclosed, consented to, reminded and cancelled. Cancellation or downgrade takes effect at the end of the paid period. If a plan Invoice is unpaid, the Organization returns to the Free plan 14 days after the due date and the subscription is cancelled 30 days after that. An unpaid plan never causes Suspension of other Services. An unpaid plan order expires after 7 days. Enterprise plans are governed by their Order Form. Details are in the Service Terms, Section B.25. **Bandwidth.** Included transfer is shown on the Pricing Page. Excess VPS transfer is billed per GB at the Pricing Page rate, measured per calendar month. Dedicated servers shown as unmetered have no overage charges but are subject to the fair use rules in the Service Terms. IP Transit is sold as ports at a fixed monthly price unless an Order Form says otherwise. ## 8\. Suspension ### 8.1 Suspension for non-payment **Prepaid Services.** When the Balance reaches zero or less and the Organization has billable Resources, we may suspend the Organization's Services. Suspension stops Resources; it does not delete them. Resources that store data and keep being billed while suspended, such as Object Storage buckets and VPS Snapshots, remain billable. **Invoiced Services.** Suspension may start the day after the due date, or after any grace period shown in the Control Panel or the Order Form. **Retention and deletion.** After a Suspension for non-payment: 1. reserved (unassigned) floating IP addresses may be released 5 days after Suspension; 2. compute Resources (servers, clusters, databases, load balancers and gateways) may be deleted, and dedicated hardware reclaimed and wiped, no earlier than 15 days after Suspension and only after at least 5 days' prior notice by email; and 3. stored data (Object Storage, snapshots and backups) may be deleted no earlier than 45 days after Suspension, after notices by email. These periods are Retention Periods. They are the earliest times for deletion, and we may keep Resources longer. Paying the amount due lifts a Suspension for non-payment but not one for another reason. Deletion is permanent and we cannot promise recovery. A new Service falls into the class (compute, stored data, reserved IP addresses, or DNS and configuration) that matches its function, and the Service Terms may state it. DNS zones and configuration are not suspended for non-payment. An Order Form may set different terms for Organizations that are billed on terms that do not suspend for low Balance. ### 8.2 Suspension for AUP, security, legal or Emergency reasons We may suspend all or part of the Services, a Resource, an Account or an Organization, immediately, when: 1. we reasonably believe that the AUP or the Agreement has been breached; 2. we reasonably believe that your Resources or Credentials are compromised, are being used to attack others, or threaten the Services, other customers or third parties; 3. there is an open payment Dispute or we reasonably suspect fraud (Section 7.10); 4. Applicable Law, a court, a regulator or a government authority requires it, or requests it in an Emergency; or 5. there is an Emergency. Where the circumstances allow, we will give you notice and an opportunity to fix the problem before or promptly after Suspension. We may act without prior notice when notice would increase harm, when the law requires, or for content such as child sexual abuse material. We keep the scope of Suspension as narrow as is reasonable, for example by restricting access to specific content or Resources. Paying an amount due does not lift a Suspension for AUP, security or legal reasons. Where we restrict content or Services because of illegal content or an AUP breach, Section 14.3 applies. ### 8.3 Effect of Suspension During a Suspension, Resources may be stopped, access may be blocked, and you may be unable to create or change Resources. Fees continue to accrue only for Resources that remain billable while suspended, such as Object Storage buckets and VPS Snapshots (Section 8.1), and for any Resource that an Order Form or the Service Terms say remains billable. A Suspension does not end the Agreement and is lifted when the reason is resolved to our reasonable satisfaction. The SLA does not apply during a Suspension. ### 8.4 Data retention during Suspension We keep Customer Content on suspended Resources as Section 8.1 states, and for other Suspensions for as long as the reason requires, taking account of evidence preservation and legal requirements. We may allow limited access to export data during a Suspension but are not obliged to. ## 9\. Term, Termination and Deletion ### 9.1 Term The Agreement starts when you accept it and continues for as long as you have an Organization, unless it is terminated earlier under this Section. An Order Form may set a fixed term. Commercial Plans and other recurring Services renew as stated in Section 7.12 and the relevant Order Form. ### 9.2 Cancellation of Resources and Services You may stop an hourly Resource at any time by deleting it in the Control Panel, the API or the CLI. Deletion ends hourly charges from the time the Resource is deleted. Deletion is irreversible, and deleted data may not be recoverable. To cancel a Service billed by Invoice, cancel in the Control Panel before the renewal cutoff date shown there (normally 5 days before the renewal date); if you cancel after that date, the next period is due unless the law gives you a right to cancel. This cutoff does not apply to Commercial Plans, which you can cancel until the renewal date with a full refund of a renewal already charged (Section 7.9(4)). If you do not accept a Material Change or a price increase, you may terminate the affected Services, or the Agreement, as Section 19.4 and Section 7.7 describe. ### 9.3 Closing your Organization You may close your Organization by asking [support@cubepath.com](mailto:support@cubepath.com) (or in the Control Panel, once that function is available) after you have deleted all Resources. We may refuse or postpone closure while amounts are due, a Dispute is open or we must preserve data. Credits are forfeited on closure. If an unused Cash Balance remains at closure, we send a notice to the registered email addresses and refund it under Section 7.9 on your request. We may refuse a refund only for the reasons in Section 7.9(1). ### 9.4 Termination by CubePath We may terminate the Agreement, an Organization or any Service: 1. for convenience, on 30 days' written notice, refunding prepaid Fees for the period after termination and the unused Cash Balance; if the termination ends a generally available Service that you use, Section 4.6 also applies; 2. immediately, if you materially breach the Agreement and do not fix the breach within 10 days after notice (or immediately if it cannot be fixed); 3. immediately, for violations of the AUP, as the AUP provides; 4. immediately, if the law, a court or a regulator requires it, or continuing would violate Applicable Law (including Section 18); 5. immediately, if you become insolvent or are the subject of bankruptcy or similar proceedings; or 6. for non-payment, following Section 8.1. If we terminate for AUP violations, you remain liable for Fees incurred up to termination. After deducting amounts you owe us and amounts under a pending Dispute, we refund the remaining Cash Balance to the original payment method within 30 days of your request. Credits are forfeited. Section 18 may block refunds where the law requires. For Consumers, termination for convenience requires at least 30 days' notice and a reasonable period to retrieve data under Section 9.6. ### 9.5 Effect of termination When the Agreement or a Service is terminated, your right to use the affected Services ends and we may delete the related Resources and Customer Content after the periods stated below. Amounts owed up to termination remain due. Each party returns or deletes the other's Confidential Information as Section 11.4 describes. We may keep Account Data and records as the law requires or allows. After Termination of the Agreement or of a Service for a reason other than non-payment, we may delete the related Resources and Customer Content in the following classes no earlier than the periods below, counted from the date Termination takes effect, unless the AUP, Section 8.2, Section 14.4 or Applicable Law requires or permits earlier deletion: (a) reserved (unassigned) IP addresses, immediately; (b) compute Resources, 15 days; (c) stored data (Object Storage, snapshots and backups), 45 days; and (d) DNS zones and configuration, together with the closure of the Organization. A new Service falls into the class that matches its function. You may delete any Resource yourself at any time, and Section 9.7 may extend these periods. ### 9.6 Data export and deletion You are responsible for exporting your Customer Content before termination, Suspension or deletion. The Documentation and the Service Terms, Part A.13, describe how to export data from each Service. After termination or deletion of a Resource, we delete Customer Content within the periods in Sections 8.1 and 9.5 and the Service Terms; backups and logs age out in their normal cycles. On request we certify deletion of Customer Personal Data. We may keep Customer Content as long as the law requires or permits, or to protect or defend legal claims, including evidence of abuse. ### 9.7 Survival Sections 1, 2.2, 5.1, 5.3, 6 (as to past access), 7 (as to amounts due), 9.5, 9.6, 9.7, 10, 11, 12, 14.5, 15, 16, 17, 18, 21 and 22, and every other provision that by its nature should continue, survive termination or expiry of the Agreement. ## 10\. Intellectual Property ### 10.1 CubePath property As between you and us, we and our licensors own all rights in the CubePath Materials. The Agreement does not transfer any of them to you. Third-Party Offerings belong to their owners. ### 10.2 Your rights to use the Services While the Agreement is in effect and you pay the Fees, we grant you a limited, non-exclusive, non-transferable, non-sublicensable, revocable right to use the Services for your own business or personal purposes and, within the AUP, to provide services to your End Users. You may not copy, modify or create derivative works of the CubePath Materials, reverse engineer them (except where the law allows despite this restriction), remove notices, or use them to build a competing service. Software we distribute may carry its own license, which then governs that software (Section 10.5). ### 10.3 License to Customer Content You keep all rights in Customer Content. You grant CubePath, and the subcontractors we use under Section 22.4, a worldwide, non-exclusive, royalty-free license to host, store, copy, transmit, process and display Customer Content only as needed to provide, secure, support and bill the Services to you, to comply with Applicable Law and to enforce the Agreement. Section 12.3 describes what we do with Service Data. We do not use Customer Content to train machine learning models (Section 13.3). ### 10.4 Feedback If you give us Feedback, you grant us a perpetual, irrevocable, worldwide, royalty-free license to use it without restriction and without obligation to you. Feedback is not Customer Content, but we will not identify you as its source without your consent. Do not give us Feedback that contains personal data or confidential information. ### 10.5 Open source and CubePath software Some software that we distribute, such as the CLI, the Terraform provider and agent skills, is open source and is licensed under the license of its repository. That license governs your use of that software and prevails over Section 10.2 for it. Services may also include open source components licensed by their authors. Except as a license requires, we provide that software without warranty (Section 15). ### 10.6 Trademarks CubePath, the CubePath logo and the names of the Services are trademarks of CubePath Inc. or its licensors. You may not use them without our written permission, except to truthfully say that you use the Services. We will not use your name or logo publicly as a customer without your consent. ## 11\. Confidentiality ### 11.1 Definition "Confidential Information" means non-public information that one party (the "Discloser") gives the other (the "Recipient") in connection with the Agreement and that is marked confidential or that a reasonable person would understand to be confidential from its nature and the circumstances. Customer Content is your Confidential Information. Non-public information about our systems, security, pricing under an Order Form and Credentials is our Confidential Information. Confidential Information does not include information that (a) is or becomes public without the Recipient's breach; (b) the Recipient already knew without a duty of confidence; (c) a third party lawfully gave to the Recipient without a duty of confidence; or (d) the Recipient develops independently without using the Discloser's Confidential Information. ### 11.2 Obligations The Recipient will use Confidential Information only to perform its obligations and exercise its rights under the Agreement, protect it with at least reasonable care, and not disclose it except to its employees, contractors, advisers, auditors, insurers and (for CubePath) subprocessors who need to know it and are bound by confidentiality duties at least as protective. The Recipient is responsible for their compliance. Section 6 also limits our access to Customer Content. ### 11.3 Compelled disclosure The Recipient may disclose Confidential Information if required by law, court order or a government authority, if it (where legally allowed) notifies the Discloser promptly so that the Discloser can seek protection, discloses only the part that is required, and cooperates at the Discloser's cost. Section 14.5 applies to requests for Customer Content. ### 11.4 Term, return and remedies These obligations last during the Agreement and for 3 years after it ends, and for Customer Content and trade secrets as long as they remain confidential. When the Agreement ends, the Recipient will delete or return Confidential Information on request, except copies required by law or kept in routine backups until they age out, which stay protected. Because unauthorized use or disclosure may cause harm for which damages are inadequate, the Discloser may seek injunctive relief to the extent the law allows. Nothing here stops you from reporting a violation of law to an authority. ## 12\. Data Protection ### 12.1 Privacy Policy Our Privacy Policy explains how we collect and use personal data about you and your Users, including Account Data and Service Data, when we act as a Controller. It is not part of the Agreement (Section 2.4). ### 12.2 Customer Personal Data You are responsible for deciding what Customer Personal Data you put into the Services, for complying with the data protection laws that apply to you, and for the lawfulness of your instructions. If one of those laws requires a written data processing agreement for our processing of Customer Personal Data on your behalf, contact [privacy@cubepath.com](mailto:privacy@cubepath.com) before you put that data into the Services. ### 12.3 Service Data and aggregated data We are the Controller of Account Data and Service Data. We process Service Data to provide, secure, bill, maintain, support and improve the Services, to prevent fraud and abuse, and as described in the Privacy Policy. We may also create aggregated or de-identified data from Service Data and use it for analytics, capacity planning and product development, and we do not attempt to re-identify it. We never use Customer Content for these purposes, and we do not sell Customer Content or Account Data. We process records of your End Users' requests in a Service such as the CDN or DNS only to provide that Service to you and as the Service Terms describe, and we may use aggregated, de-identified statistics derived from them for the security and operation of the Services. **Security Incidents.** If we become aware of a Security Incident, we will notify you without undue delay through the contact addresses registered for your Organization and, where appropriate, our status page, and give you the information reasonably available to us so you can meet your own reporting duties. Laws may require us to report significant incidents to competent authorities, and we may do so; this is not an admission that a particular law applies to us. You must notify us of incidents that affect the Services as Section 5.5 requires. ## 13\. AI Features ### 13.1 What AI Features are AI Features include the AI Gateway (access to models of third-party Model Providers through one endpoint), the Control Panel assistant, and AI-assisted support. The Service Terms, Part A.5 and Sections B.21 and B.22, describe them. Other Services may use AI in the future; this Section applies to them too. ### 13.2 Model Providers AI Input and relevant context are sent to the Model Provider of the model you choose or that the feature uses, and are processed under that provider's terms, usage policies and locations, as the Service Terms describe. You must follow the Model Provider's terms and usage policies for your use of its models. We may add, change, limit, deprecate or disable models and Model Providers at any time, and we are not responsible for a Model Provider's acts or availability except as the Service Terms say. ### 13.3 No training on Customer Content CubePath does not use Customer Content, including AI Input and AI Output, to train or fine-tune machine learning models. The AI Gateway does not store the content of AI Input or AI Output; it stores metadata such as model, token counts, cost, IP address and time. A Model Provider may handle AI Input under its own terms, which you should review. ### 13.4 AI Output AI Output may be inaccurate, incomplete, offensive, biased or similar to other output, and is not professional advice. As between you and us, you own AI Output to the extent the law allows; we do not promise that it is protected by intellectual property rights or does not infringe the rights of others. You are responsible for reviewing AI Output and for decisions based on it, and for disclosing AI-generated content where the law requires. ### 13.5 Your responsibilities You are responsible for AI Input and for having the rights to submit it, for configuring and securing AI agents and clients that use the Services (Section 5.7), and for compliance with Applicable Law, the AUP (Section 8 of the AUP) and the Model Providers' usage policies. You must not use AI Features for uses that Applicable Law prohibits, or for high-risk uses (such as decisions with legal or similarly significant effects on people, or safety-critical systems) unless your use complies with the law that applies, including human oversight and transparency duties. ### 13.6 AI-assisted support and the assistant Our support team may use AI systems to classify and summarize tickets and to draft or send replies, using ticket content and, when needed for diagnosis, console images. Staff oversee these systems. Replies may be generated by AI, and you can ask in the ticket at any time for a human to review or reply. The Control Panel assistant identifies itself as AI, has read-only access to the information of your Organization that it needs, keeps conversations for a limited period and is subject to spend limits, as the Service Terms, Section B.22, describe. ### 13.7 No SLA AI Features have no SLA unless an Order Form says so. ## 14\. Content Moderation, Notices and Legal Requests ### 14.1 How we moderate We do not generally monitor Customer Content. We act on reports, on technical and security signals, on legal requirements and on complaints. We may restrict content or Services when we have a reasonable basis to believe that Customer Content or its use is illegal, violates the AUP or the Agreement, or harms the Services, other customers or third parties. Restrictions can be a warning with a deadline, restricting access to specific content (for example by quarantining, blocking or removing an object or file), restricting a Resource, Suspension (Section 8.2) or Termination (Section 9.4). Reports are handled with a mix of tools and staff review, and a person reviews decisions to suspend or terminate a Service for AUP or illegal content reasons. Suspension for non-payment under Section 8.1 and the network protections that run automatically (such as DDoS mitigation) are applied by automated means. In choosing a measure we consider seriousness, risk, scale, repetition, whether a narrower restriction is enough and any legal requirement. We preserve evidence where required. The AUP, Section 11, describes the process. ### 14.2 Notices of illegal content and copyright Anyone, including non-customers, may report suspected illegal content, abuse or an AUP breach to [abuse@cubepath.com](mailto:abuse@cubepath.com) , including through any web form we publish. A notice should give the location of the content (a URL or IP address), why it is illegal or a violation, the sender's name and email address (unless the report concerns child sexual abuse material or another offense for which the sender may remain anonymous), and a statement of good faith. We confirm receipt when we can identify the sender and tell the sender our decision. When we decide on a notice, we also tell the sender whether the decision was taken by automated means and the redress options available. Copyright notices and counter-notices under the US Digital Millennium Copyright Act (17 U.S.C. 512) follow the AUP, Section 3, and go to [abuse@cubepath.com](mailto:abuse@cubepath.com) or to our designated agent at the address in Section 3.3 of the AUP. We terminate repeat infringers in appropriate circumstances. A person who sends a notice knowing it is false may be liable under the law. ### 14.3 Statement of reasons and complaints When we restrict content or a Service because it is illegal or violates the AUP or the Agreement, we tell the affected Customer, without undue delay and unless the law prevents it: what we restricted and for how long; the facts and circumstances, including whether the decision followed a notice or our own initiative; the legal or contractual ground; whether automated means were used; and how to challenge the decision. You may challenge a decision free of charge for at least 6 months after you receive it, by replying to the notice or writing to [abuse@cubepath.com](mailto:abuse@cubepath.com) , with reasons and evidence. Where practicable, a person who was not involved in the original decision reviews the complaint, and we answer without undue delay. We may withhold details if giving them would put an investigation, an individual or the Services at risk. We apply restrictions in a diligent, objective and proportionate manner, with due regard to the rights and legitimate interests of all parties. Section 21 applies to any dispute that this process does not resolve. ### 14.4 Child safety reporting We have zero tolerance for child sexual abuse material (CSAM) and for content that sexualizes minors. If we obtain actual knowledge of apparent CSAM, we report it to the National Center for Missing & Exploited Children as 18 U.S.C. 2258A requires, and to other competent authorities in the places where the law requires. We preserve the content and related information as the law requires, restrict the content, suspend the Services immediately and without prior notice, and terminate the Agreement. We may disclose Account Data and other data to authorities for this purpose. Nothing in the Agreement limits those reports. ### 14.5 Government and law enforcement requests Except for reports under Section 14.4, we respond to requests for Customer Content or Account Data only through valid legal process from a competent authority sent to [legal@cubepath.com](mailto:legal@cubepath.com) , or as the law otherwise requires. We review each request and seek clarification of, or challenge, requests that are overbroad, unlawful or unclear, and disclose the minimum necessary. Unless the law or a binding order prohibits it, we notify you before disclosing Customer Content so you can seek protection, and we may notify you later when a prohibition ends. Where the law allows, we may disclose information without prior legal process when we believe in good faith that there is an emergency involving danger of death or serious physical injury, and we may preserve data at an authority's request as the law requires. ### 14.6 Points of contact - **Authorities and legal process**: [legal@cubepath.com](mailto:legal@cubepath.com) . - **Abuse reports and notices of illegal content**: [abuse@cubepath.com](mailto:abuse@cubepath.com) . - **Privacy**: [privacy@cubepath.com](mailto:privacy@cubepath.com) . ## 15\. Warranties and Disclaimers ### 15.1 Mutual authority **Each party represents that it has the power and authority to enter into the Agreement.** ### 15.2 Disclaimer **Except for the express commitments in the Agreement, including the SLA, the Services and all CubePath Materials are provided "as is" and "as available". To the maximum extent permitted by Applicable Law, CubePath, its affiliates and its licensors disclaim all other warranties, express, implied or statutory, including any implied warranty of merchantability, fitness for a particular purpose, title and non-infringement, and any warranty arising from course of dealing or usage of trade.** **CubePath does not warrant that the Services will be uninterrupted, error-free, secure or free of harmful components, that data will not be lost or corrupted, that backups, snapshots or DDoS protection will prevent or remedy any loss or attack, or that AI Output will be accurate. The Internet and third-party networks are not under our control, and we do not guarantee their security or performance. Beta Services, free Services and Third-Party Offerings are provided without any warranty by CubePath.** ### 15.3 Your reliance **You acknowledge that, except for fraud or fraudulent misrepresentation, and except for the Pricing Page, the Service Pages and the Documentation to the extent the Agreement refers to them, you have not relied on any statement that is not in the Agreement, and that you are responsible for choosing Services that suit your needs. This Section does not apply to Consumers.** ### 15.4 Mandatory rights **Some jurisdictions do not allow certain disclaimers. In that case, the disclaimers apply to the fullest extent permitted. This Section does not limit the rights that Section 20 preserves for Consumers.** ## 16\. Limitation of Liability ### 16.1 Exclusion of certain damages **To the maximum extent permitted by Applicable Law, neither party is liable to the other for indirect, incidental, special, consequential, exemplary or punitive damages, or for lost profits, lost revenue, lost business or goodwill, or business interruption, in each case arising out of or related to the Agreement or the Services, whatever the theory of liability and even if the party has been advised of the possibility. CubePath is not liable for loss or corruption of Customer Content except where CubePath's breach of the Agreement caused the loss, in which case its liability is limited to the reasonable cost of restoring the content from the most recent backup or copy available to you or to us, and is subject to Section 16.2.** ### 16.2 Cap **CubePath's total liability for all claims arising out of or related to the Agreement or the Services in total for all events that occur in any period of 12 months is limited to the greater of (a) the Fees you paid for the Service that gave rise to the claim in the 3 months before the event that gave rise to the liability, and (b) USD 100\. Your total liability for all claims in any period of 12 months, other than for Excluded Claims, is limited to the Fees you paid or owe for the Services in the 12 months before the event. An Order Form signed by CubePath may set a different cap. CubePath's liability under its intellectual property indemnity in Section 17.2 is subject to a separate cap equal to the Fees you paid for the affected Services in the 12 months before the claim. Service Credits and refunds of Fees that we give for the same event count toward the cap.** ### 16.3 What the cap and exclusions do not limit **Sections 16.1 and 16.2 do not limit (the "Excluded Claims"): (a) liability for fraud or willful misconduct; (b) liability for gross negligence, where the law does not allow it to be limited; (c) liability for death or personal injury caused by negligence; (d) liability that cannot be limited by law; (e) your obligation to pay Fees; (f) your indemnification obligations under Section 17.1; (g) liability arising from your breach of the AUP; and (h) liability toward data subjects under data protection law, and any liability that the Standard Contractual Clauses do not allow to be limited. The intellectual property indemnity has its own cap in Section 16.2.** ### 16.4 Basis of the bargain **The limits in this Section 16 apply to claims in contract, tort (including negligence), statute or any other theory, and even if a remedy fails of its essential purpose. They allocate risk, and the Fees reflect that allocation. Service Credits are the sole and exclusive remedy for a failure to meet the SLA (SLA, Section 9). Claims by Consumers are governed by Section 20.** ## 17\. Indemnification ### 17.1 By you You will defend CubePath, its affiliates and their officers, directors, employees and agents against any third-party claim, demand, regulatory proceeding or action, and indemnify them for the resulting damages, settlements, costs and, where the law allows, fines and reasonable attorneys' fees, to the extent it arises from: (a) Customer Content; (b) your use of the Services, or that of your Authorized Users or End Users; (c) a violation of the AUP or of Applicable Law by you, your Authorized Users or End Users; or (d) a claim by your End Users or customers relating to your services. This applies to the extent that the claim is not caused by our breach of the Agreement. This Section 17.1 does not apply to Consumers. ### 17.2 By CubePath We will defend you against a third-party claim that the Services as provided by CubePath, and used as the Agreement allows, infringe or misappropriate a United States patent, copyright or trademark, or a trade secret, and we will pay the damages and costs that a court finally awards against you or that we agree to in settlement. We have no obligation to the extent a claim arises from: Customer Content; Third-Party Offerings; Beta Services or free Services; use that breaches the Agreement; modifications not made by us; or the combination of the Services with items not supplied by us, if the claim would not exist without the combination. If a claim is made or likely, we may obtain the right for you to keep using the Services, modify or replace them so that they do not infringe, or, if neither is reasonable, terminate the affected Service and refund prepaid Fees for the unused period. This Section 17.2 states our entire liability and your exclusive remedy for infringement claims, subject to the separate cap in Section 16.2. ### 17.3 Procedure The indemnified party must (a) promptly notify the indemnifying party of the claim (late notice only reduces the indemnity if the delay causes harm); (b) give the indemnifying party control of the defense and settlement, except that the indemnified party keeps control of any proceeding brought by a government authority or regulator, and may at any time remove or restrict content or Services as the law or this Agreement requires, without affecting the indemnity; the indemnifying party may not settle in a way that admits fault for, or imposes obligations on, the other party without its consent, which is not to be unreasonably withheld; and (c) cooperate at the indemnifying party's cost. The indemnified party may take part with its own counsel at its own cost. ## 18\. Export Controls, Sanctions and Anti-Corruption ### 18.1 Export controls and sanctions You represent and agree that: (a) you, your Authorized Users and the beneficial owners of your Organization are not located in, organized under the laws of, or ordinarily resident in a country or region that is subject to comprehensive sanctions or embargo by the United States; (b) neither you nor any person that owns 50% or more of you, directly or indirectly, is named on, or owned or controlled by a person named on, a sanctions or restricted-party list of the United States (including the lists of OFAC and the Department of Commerce); (c) you will not use the Services, or allow them to be used, for any end use that is prohibited under the Export Administration Regulations (EAR) or other United States export control or sanctions law, including the development of weapons of mass destruction; and (d) you will not access the Services from, or export or transfer Customer Content to, an embargoed country or region, or to a person in breach of those laws. You must tell us promptly if a representation stops being true. ### 18.2 Our rights We may refuse, restrict, suspend or terminate Services, block payments, and decline to open an Organization, immediately and without liability, if we reasonably believe this Section is breached or that continuing would breach Applicable Law. Where the law requires us to freeze funds or block a payment, we may withhold refunds of Cash Balance for as long as the law requires. We do not promise to screen every customer. ### 18.3 Anti-corruption Each party will comply with applicable anti-corruption and anti-bribery laws, including the US Foreign Corrupt Practices Act, in connection with the Agreement, and will not offer or accept anything of value to improperly influence a decision. ## 19\. Changes to the Agreement ### 19.1 Non-material changes We may update the Terms, the Service Terms, the SLA, the AUP and the other documents of the Agreement. A change that is not a Material Change takes effect when we publish it, with a new version and date. The Terms and the Schedules are one document, so a change to any of them is published as a new version of the whole document. Only the text that changes is a change under this Section 19\. Examples are corrections, clarifications, changes that improve your rights, and changes that Section 19.3 describes. For any such change that affects a Service you use, we also post a notice in the Control Panel or send it to the Owners and Admins by email within 7 days after publication. A change is not a Material Change only if it does not reduce your rights or increase your obligations beyond a minor degree. If you reasonably disagree with our classification, you may use Section 19.4 within 30 days after the notice. ### 19.2 Material Changes For a Material Change we publish the new version with an effective date, and notify the Owners and Admins of each affected Organization by email and in the Control Panel at least 30 days before the effective date. Our default notice is 60 days. The notice states what changes, the effective date and the Acceptance Deadline. An Owner or Admin must accept the new version in the Control Panel ( ) by the Acceptance Deadline. We record each acceptance with its date and time, the version of the text and the accepting User. Until it is accepted, the existing version continues to apply to your existing Resources, which keep running. After the Acceptance Deadline, we may block the creation of new Resources until an Owner or Admin accepts; we do not suspend existing Resources for this reason alone. Continued use of the Services is not acceptance of a Material Change: acceptance is made only in the Control Panel or by signing an Order Form. ### 19.3 New Services and SLA additions Adding a section to the Service Terms for a new Service or a new Service category, and adding a Service to the SLA, take effect when published and apply only to the new Service or category. They are not Material Changes. ### 19.4 If you do not agree If you do not agree with a Material Change, you may terminate the affected Services or the Agreement before the effective date, or, where Section 19.1 lets you use this Section, within 30 days after the notice, by deleting your Resources and, if you terminate the Agreement, closing your Organization under Section 9.3\. We will refund the unused Cash Balance and any prepaid Fees for the period after termination. Credits are not refunded. ### 19.5 Required changes We may make a change sooner, with as much notice as is practical, if it is needed to comply with Applicable Law, or a court or regulator order, to maintain security, or to stop abuse. Such a change may take effect immediately, and a Material Change of this kind can be accepted afterwards under Section 19.2. ### 19.6 Privacy Policy The Privacy Policy is changed under its own notice rule, and not under this Section. ### 19.7 Customers who accepted an earlier version If you accepted an earlier version of the Terms, this version applies to you when an Owner or Admin accepts it, or on the effective date stated in our notice under Section 19.2 if the earlier version allowed us to change it by that notice, whichever is later. For Resources you create after acceptance, this version applies from creation. ## 20\. Consumers If you are a Consumer, nothing in the Agreement limits a right that the consumer protection law that applies to you does not allow you to waive by contract. Where such a law applies, the rest of the Agreement applies to you to the fullest extent that law allows. Sections 15.3 and 17.1 do not apply to Consumers. ## 21\. Governing Law and Disputes ### 21.1 Governing law The Agreement, and all claims arising out of or related to it or to the Services, are governed by the laws of the State of Michigan, United States, without regard to its conflict-of-law rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply. The Federal Arbitration Act (9 U.S.C. 1 and following) governs the interpretation and enforcement of Sections 21.3 to 21.5. ### 21.2 Informal resolution Before starting a claim, a party must give the other written notice of the dispute (to [legal@cubepath.com](mailto:legal@cubepath.com) , if to us) describing the claim and the relief sought, and the parties will negotiate in good faith for 30 days. A claim may not be brought before this period ends, except for the claims in Section 21.4\. The limitation period in Section 21.6 is suspended during the 30-day negotiation period. ### 21.3 Binding arbitration **Any dispute, claim or controversy arising out of or related to the Agreement or the Services that is not resolved under Section 21.2 is resolved only by binding arbitration, and not in court, except as Section 21.4 provides.** The American Arbitration Association (AAA) administers the arbitration under its Commercial Arbitration Rules in force when the arbitration starts, or under its Consumer Arbitration Rules where the AAA decides that those rules apply. The rules are available at . One arbitrator decides the dispute. The seat of the arbitration is Ann Arbor, Michigan, United States, and its language is English. Where the AAA rules allow it, the arbitrator may hold hearings by video or telephone or decide on written submissions alone. The arbitrator decides all questions, including whether a dispute can be arbitrated, except that only a court may decide whether Section 21.5 is valid and enforceable. The arbitrator applies the Agreement, including Sections 15 to 17, and may award relief only to the party that brought the claim and only as needed to resolve that party's individual claim. The award is final and binding, and judgment on it may be entered in any court of competent jurisdiction. Each party pays its own attorneys' fees and costs and its share of the AAA fees as the AAA rules provide, unless the arbitrator decides otherwise as the law or those rules allow. The parties keep the arbitration and the award confidential, except as needed to enforce the award or as the law requires. ### 21.4 Exceptions to arbitration Either party may seek temporary or preliminary injunctive relief in any court of competent jurisdiction to protect its intellectual property, Credentials or Confidential Information, or the security of its systems and network, or to enforce the AUP. ### 21.5 Jury trial waiver and class action waiver **To the extent the law allows, you and CubePath each waive any right to a jury trial and any right to take part in a class, collective or representative action in any dispute arising out of or related to the Agreement.** Claims may be brought only in an individual capacity, and not as a plaintiff or class member in a class, collective, consolidated or representative proceeding. The arbitrator may not combine the claims of several customers, or preside over any class, collective or representative proceeding, without the written consent of all parties. If a court decides that this Section cannot be enforced for a particular claim or remedy, that claim or remedy is separated and decided in the courts of Section 21.7 after the arbitration of the other claims has ended, and the rest of this Section 21 continues to apply. ### 21.6 Limitation period To the extent the law allows, a Business Customer must start any claim arising out of the Agreement within one year after the claim arises. This does not apply to Consumers or to claims for our unpaid Fees. ### 21.7 Courts The state courts in Washtenaw County, Michigan, or the United States District Court for the Eastern District of Michigan have exclusive jurisdiction over any dispute that is not subject to arbitration under this Section 21, and over any action to compel arbitration or to confirm, correct or set aside an award. Each party submits to the personal jurisdiction of those courts and waives objections to venue. An award may be enforced in any court of competent jurisdiction. ## 22\. General Provisions ### 22.1 Assignment You may not assign or transfer the Agreement or any right or obligation under it without our prior written consent, which we will not unreasonably withhold. A change of control of a Business Customer counts as an assignment. We may assign the Agreement to an affiliate or to a successor in a merger, reorganization, acquisition or sale of all or substantially all of the relevant business or assets, and we will notify you. Any other assignment is void. The Agreement binds the permitted successors and assigns. ### 22.2 Notices Legal notices to CubePath must be sent to [legal@cubepath.com](mailto:legal@cubepath.com) and are effective when we receive the email. For a notice of breach, Termination or a claim, please also send a copy by courier or registered mail to CubePath Inc., 122 S. Main St, Suite 255, Ann Arbor, Michigan 48104, United States; the copy does not delay the effect of the email notice. Support, billing, abuse and privacy matters go to the addresses in Section 23. We may give you notices by email to the addresses registered for the Owners, Admins and billing contacts of your Organization, by a notice in the Control Panel, or by posting where the Agreement allows. They are treated as received 24 hours after sending, or on publication if posted. Keep your contact details current and check messages sent to them. Operational notices, such as maintenance notices, go to your registered email addresses and our status page. ### 22.3 Force majeure Neither party is liable for delay or failure to perform caused by events beyond its reasonable control, such as natural disaster, fire, flood, war, terrorism, pandemic, government action, power or telecommunications failure or failure of an upstream carrier, to the extent a provider that maintained the redundancy described in the Documentation could not reasonably have avoided it, or large-scale denial-of-service attacks that exceed the protection the Service is documented to provide, if it uses reasonable efforts to limit the effect and resume performance. This does not excuse payment obligations. If the event lasts more than 30 days, either party may terminate the affected Service on written notice, and we refund prepaid Fees for the period after termination. ### 22.4 Subcontractors We may use affiliates and subcontractors to provide the Services, including infrastructure, hosting, payment and support providers, and we remain responsible for their performance under the Agreement. ### 22.5 Independent parties The parties are independent contractors. The Agreement does not create a partnership, joint venture, agency, franchise or employment relationship, and neither party may bind the other. ### 22.6 No third-party beneficiaries The Agreement benefits only the parties and, for Sections 16 and 17, our affiliates and their personnel, who may enforce those Sections. It confers no rights on any other person, including your End Users. Consumers keep any rights that mandatory law gives them. ### 22.7 Severability If a court of competent jurisdiction finds a provision unenforceable, it will be enforced to the maximum extent permitted and replaced by the nearest valid provision that has an equivalent effect, and the rest of the Agreement stays in force. ### 22.8 Waiver A failure or delay in exercising a right is not a waiver. A waiver is effective only if it is in writing and signed by the waiving party, and applies only to the case concerned. ### 22.9 Entire agreement The Agreement is the entire agreement between you and CubePath on its subject and replaces earlier agreements, proposals and communications on its subject, including earlier versions of the Terms, from the date it applies to you under Section 19.7\. Until then, the version you accepted continues to apply. Your purchase order or other terms do not apply, even if we accept the order. ### 22.10 Electronic communications and signatures You agree to receive notices and records electronically. You agree that clicking to accept, accepting in the Control Panel, and signing electronically are valid signatures and legally binding, under the US Electronic Signatures in Global and National Commerce Act, the Uniform Electronic Transactions Act and equivalent laws, and that our records of acceptance are evidence of it. Electronic copies are as valid as originals. ### 22.11 US Government users The Services are "commercial products" and "commercial services", and any software or documentation is "commercial computer software" and "commercial computer software documentation" under FAR 12.212 and DFARS 227.7202\. US Government customers receive only the rights that the Agreement gives to other customers. ### 22.12 Interpretation Headings are for convenience only. "Including" means "including without limitation". The Agreement is not interpreted against the drafter. A reference to a law includes it as amended or replaced. "In writing" includes email. Periods in days are calendar days. ## 23\. Contact CubePath Inc., a Delaware corporation 122 S. Main St, Suite 255, Ann Arbor, Michigan 48104, United States - Support, billing, refunds and account closure: [support@cubepath.com](mailto:support@cubepath.com) - Abuse reports, copyright notices and notices of illegal content: [abuse@cubepath.com](mailto:abuse@cubepath.com) - Legal notices, authorities and law enforcement requests: [legal@cubepath.com](mailto:legal@cubepath.com) - Privacy requests and data protection questions: [privacy@cubepath.com](mailto:privacy@cubepath.com) - Enterprise, Order Forms and IP allocations above standard limits: [sales@cubepath.com](mailto:sales@cubepath.com) ## Schedule 1\. Service Terms ## How the Service Terms work These Service Terms are Schedule 1 to the Terms of Service (the "Terms") and part of the Agreement between CubePath Inc. ("CubePath", "we", "us") and you. Capitalized terms not defined here have the meanings in the Terms. The Terms apply to every Service. These Service Terms add the rules that depend on what kind of Service you use. ### 0.1 Two layers The Service Terms have two parts. - **Part A, Service Categories.** Part A groups the Services into categories. For each category it says what CubePath operates, what you are responsible for, and which rules apply to every Service in that category. Part A also contains rules that apply across categories (Beta Services, locations, limits, deprecation, and data export and deletion). - **Part B, Specific Services.** Part B has one section for each Service that needs its own rules. Each Part B section begins with the line "Category: ..." naming its Service Category. It adds rules specific to that Service and does not repeat Part A or the Terms. A "Service Category" is a category defined in Part A. The categories are: Unmanaged Infrastructure; Managed Services; Network and Security Services; Edge Services; AI Services; Developer Tools and Automation; Third-Party Offerings; and Programs and Promotions. ### 0.2 Default rule for Services without a Part B section Not every Service has a Part B section. A Service with no Part B section is governed by the Terms, the Part A rules for its Service Category, the Documentation, and the Pricing Page or Control Panel order screen. The following rules decide its category and status. 1. The Service belongs to the Service Category that its Service Page or Documentation names. The category stated on the Service Page or in the Documentation on the date you created the Resource continues to apply to that Resource unless Section 19 of the Terms is followed. 2. If no category is named, the Service is treated as Unmanaged Infrastructure (Section A.1). 3. The Service has no SLA unless the SLA lists it. 4. If the Service is labeled beta, preview, early access or experimental, it is a Beta Service and Section A.9 also applies. 5. Its billing model is the one shown on the Pricing Page or the Control Panel order screen. Billing models are described in Section 7.1 of the Terms. ### 0.3 New Services and new categories CubePath may add a Part B section for a new Service, or a new Service Category, at or before the launch of that Service. Such an addition takes effect when it is published. It applies only to the new Service or category. It is not a change to the terms of any Service you already use, so it does not need your acceptance and is not a Material Change. A new Service Category, a new Part B section and any change to a Service Page or to the Documentation apply to a Service you already use only as this paragraph allows. If the change would move a Service you already use into a different Service Category, or would reduce your rights, remove a commitment or add an obligation for that Service, it is a change to the Agreement and follows Section 19 of the Terms. Corrections, clarifications, new features and changes that do not reduce your rights take effect when published. Adding a Service to the SLA also takes effect when published. The SLA covers only the Services listed in it. ### 0.4 Relation to the Terms and conflicts - If these Service Terms conflict with the SLA, the AUP or the Terms, these Service Terms prevail for the Service concerned, as Section 2.2 of the Terms provides, except that the SLA governs service levels and Service Credits. The exceptions in Section 2.2 of the Terms stay in force: only an Order Form signed by CubePath can change the Terms on limitation of liability, disclaimers, indemnification, governing law and disputes. - Within these Service Terms, a Part B section prevails over Part A for the Service it covers. - An Order Form prevails over these Service Terms only for the terms it expressly overrides. - Nothing in these Service Terms limits rights that mandatory law gives you, including the consumer rights that Section 20 of the Terms preserves. ## Part A. Service Categories ### A.1 Unmanaged Infrastructure Unmanaged Infrastructure is compute and similar infrastructure that you administer yourself. Examples are Cloud VPS, Dedicated Servers, VPS Backups and Snapshots, Availability Groups and operating system images. **A.1.1 What CubePath operates.** CubePath operates the physical hardware, the virtualization layer, the data center network, the platform that creates and manages Resources, and the Control Panel, API, CLI and MCP Server. CubePath repairs or replaces the hardware it owns. CubePath is responsible for these layers as described in the Terms and the SLA. **A.1.2 What you are responsible for.** You are responsible for everything inside the Resource and everything you run on it. This includes: - the operating system, its licensing and its updates and patches; - software, applications, containers and configuration; - security of the Resource, including host firewalls, hardening, malware protection, monitoring, logging and the protection of keys and Credentials; - user accounts and access inside the Resource; - backups of your data, and testing that you can restore them (see Section 5.6 of the Terms); - compliance of your workloads with Applicable Law and the AUP; - changes you make through the Control Panel, API, CLI or MCP Server, including firewall groups, network settings, reinstalls and deletions. **A.1.3 What CubePath does not provide.** CubePath does not administer your operating system, monitor your applications, or troubleshoot your software or workloads. Support covers the platform, the Control Panel, the network, the hardware and billing. CubePath provides managed administration of a Resource only if an Order Form or a Part B section says so. **A.1.4 Access by CubePath.** CubePath does not administer your operating system, monitor your applications or read your files as part of the Services, and does not log in to your operating system except in the cases listed in Section 6 of the Terms. Some functions that you request or that operate the platform act inside or on your Resource, for example the guest agent used for password reset and rescue mode, backups, snapshots, migration and out-of-band management. Examples of access are actions you request or start (such as password reset, rescue mode, reinstall or restore, which can run through the guest agent inside the Resource), diagnosis at your request or to resolve a ticket using a read-only image of the console (without keyboard or mouse input), operation and security of the platform, investigation of AUP violations or Security Incidents, wiping storage when a Resource ends, and legal requirements. Backups and snapshots hold the contents of your disks and are handled only by the platform. Staff access to Resources is logged. **A.1.5 Backups and snapshots.** Backups and snapshots sold by CubePath are an optional convenience feature. **They are not a guarantee of recovery and do not guarantee consistency at application level.** They are stored within CubePath's infrastructure and are not a substitute for your own off-platform copies. Frequency, retention and limits are in Part B and the Documentation. You keep independent copies of important data. **A.1.6 Irreversible actions.** Deleting a Resource, reinstalling its operating system and restoring a backup over a disk are irreversible. CubePath is not responsible for the result of an action that was validly requested with your Credentials and that CubePath carried out as requested. This does not apply to the extent the result was caused by CubePath's own breach of the Agreement or error in carrying out the action. ### A.2 Managed Services Managed Services are Services where CubePath operates the Service itself up to a stated scope. Examples are Managed Databases, Managed Kubernetes (control plane), Object Storage, Load Balancers, NAT Gateways, the Video Transcoder and, where an Order Form says so, other services operated for you. **A.2.1 What CubePath operates.** CubePath operates the Service platform up to the scope described in the Part B section and the Documentation for that Service. Typical items are installing and updating the service software that CubePath chooses to provide, the control plane, replication and failover where the Service offers them, platform-level backups where the Service offers them, certificates that CubePath issues, and monitoring of the platform. If the Part B section and Documentation do not describe an item, CubePath does not operate it. **A.2.2 What you are responsible for.** You remain responsible for: - your data, schemas, queries, indexes, object keys and similar structures; - your applications, workloads, code and content that use or run on the Service; - access control you configure, including users, roles, keys, policies, allow lists and tokens, and the protection of your Credentials; - configuration choices you make, including sizing, retention settings, replication settings and network exposure; - the compatibility of your software with the versions CubePath provides; - independent backups of data you cannot afford to lose, unless the Part B section states what CubePath keeps for you and for how long; - compliance of your use with Applicable Law and the AUP. **A.2.3 Scope of support.** CubePath supports the Service as a platform. CubePath does not support your software, workloads, data design or content. If a problem lies in your workload, CubePath may tell you so and close the case. "Managed" describes what CubePath operates. It does not mean CubePath manages your application, tunes your queries, or is responsible for the correctness of your data. **A.2.4 Maintenance and updates.** CubePath may update, patch, restart, replace or move the components of a Managed Service to keep it secure and working, and may apply minor and patch versions automatically. Where an update can interrupt the Service, CubePath will use reasonable efforts to apply it in the maintenance windows described in the Documentation and to announce it on our status page or by email. Security updates and emergency maintenance may be applied without advance notice. You are responsible for testing your software against new versions and for upgrading to supported versions (Section A.12.5). **A.2.5 Access by CubePath.** Operating a Managed Service requires CubePath staff and systems to have administrative access to the infrastructure on which your data runs, including nodes and virtual machines that hold your data. CubePath uses this access to operate the Service and for the other purposes in Section 6 of the Terms. CubePath does not use it to read or use Customer Content for any other purpose. Staff access is logged. Data stored by a Managed Service may be encrypted. Where Part B states that CubePath holds the encryption keys, CubePath can decrypt that data when operating the Service. ### A.3 Network and Security Services Network and Security Services provide addresses, connectivity, filtering and protection. Examples are IP addresses, Floating IPs and Reverse DNS, Private Networks, Firewall Groups, Dynamic Routes, DDoS Protection, BGP sessions, BYOIP and BYOASN, IP Transit, Layer 2, Cloud Gateway and Tunnels. **A.3.1 What CubePath operates.** CubePath operates its own network, its routers and switches, its upstream and peering connections, the systems that assign addresses and the platform features that apply your network configuration. CubePath operates the CubePath side of each connection or session. **A.3.2 What you are responsible for.** You are responsible for: - the configuration of your own systems and networks, including routing, addressing, firewall rules and filters that you set; - the content and traffic you send and receive, including traffic that leaves a Resource because of your configuration; - the accuracy of information you give for IP allocations, route objects and authorizations; - the effects of rules you create. A rule that blocks traffic to or from your own Resource is a customer cause, not a failure of the Service. **A.3.3 Ownership and use of IP addresses.** IP addresses and ranges that CubePath assigns to you remain the property of CubePath, or of the upstream provider or regional internet registry that allocated them, and you acquire no ownership right over them. You receive a right to use them while you use the Service. You may not transfer or sell them. CubePath may change an assigned address where this is necessary for network operation, security or law, with notice where practical. Requests for allocations above standard limits require a justification that complies with the policy of the applicable regional internet registry (ARIN or RIPE NCC). CubePath may refuse or limit an allocation. When the Service or the assignment ends, you must stop using the addresses and remove them from your DNS records, allow lists, certificates and routing configuration. CubePath may remove reverse DNS records and may reassign the addresses. **A.3.4 Your own addresses and numbers.** Where a Service lets you announce your own IP prefixes or use your own AS number, you must hold the right to use them. You must give the authorizations, route objects and records that CubePath asks for and keep them accurate. CubePath may filter, refuse, limit or withdraw an announcement that is not authorized, is inaccurate, endangers the network or breaks the AUP. You are responsible for misannouncements, route leaks and hijacks that come from your configuration. **A.3.5 Network protection by CubePath.** To protect its network, other customers and third parties, CubePath may rate-limit, filter, null-route or otherwise block traffic to or from any IP address that is under attack, that is attacking, or that otherwise threatens the network. This applies to addresses with paid protection when an attack exceeds the capacity of the protection. CubePath acts without prior notice where this is necessary and tells you afterwards where practical. Measures taken to protect the network are not an SLA failure, as the SLA provides. For an address with paid DDoS protection, the terms of that protection in Part B apply to a null-route or filter applied below the capacity of the protection you bought. Security and filtering features reduce risk but do not stop every attack, and they may block legitimate traffic. You remain responsible for the security of your Resources (Section 5.5 of the Terms). **A.3.6 Third-party networks and providers.** Connectivity to the wider Internet, to carriers, to Internet exchanges and to the networks of other cloud providers depends on third parties. CubePath does not control third-party networks and is not responsible for their performance, availability, routing or filtering. The terms of a third-party provider apply to the part of a Service that third party provides, and you must comply with them. **A.3.7 Fair use of bandwidth.** Where a Service is sold as "unmetered" or "unlimited" or has no overage charge, these words do not mean unlimited capacity. Capacity is shared. Sustained use that degrades the network or other customers, or that exceeds the port speed you bought, is not fair use. In that case CubePath will normally notify you and give you a reasonable time to reduce the use, and may then limit the port or suspend the Service. CubePath may act without prior notice to protect the network or in an Emergency. Part B states any traffic allowance of a Service. ### A.4 Edge Services Edge Services are Services that CubePath operates at points of presence close to Internet users. Examples are the CDN and DNS. Free informational tools such as the status page and the looking glass are provided as Edge Services or Network and Security Services, as Section B.29 states, with no warranty. **A.4.1 What CubePath operates.** CubePath operates the edge software and servers, the points of presence, the control plane that distributes your configuration, and the certificate issuance for domains you connect, as described in the Part B section. **A.4.2 What you are responsible for.** You are responsible for: - the content served through the Service and your right to serve it; - the domain names you connect, your control over them and the DNS records that point them to the Service; - caching, redirect, header, access, firewall, rate limit and geo-blocking rules that you configure, and their effects on your site and your users; - your origin servers, their availability and their security; - the DNS and domain configuration that certificate issuance for your domains depends on (CubePath does not promise issuance, and a failure caused by your configuration is a customer cause); - the legality of your use in the countries where your content is served, including content that is restricted or unlawful in some countries. **A.4.3 CubePath sees traffic in transit.** To provide an edge Service, CubePath terminates connections and may process requests, responses and content in transit. This includes encrypted traffic for which CubePath holds the certificate. Section 6 of the Terms governs this processing. Where visitors to your sites are identified in logs, CubePath acts as your Processor for that data. You must inform your visitors as the law requires. **A.4.4 Global distribution.** Edge Services run in several locations and may handle requests from anywhere. The choice of a data center location in Section A.10 does not confine requests or cached content processed by an Edge Service to that location, except where Part B says so. ### A.5 AI Services AI Services are Services that use machine learning models. Examples are the AI Gateway, the Control Panel assistant and AI-assisted support. Section 13 of the Terms also applies. **A.5.1 What CubePath operates.** CubePath operates the access layer, authentication, metering, billing and rate limiting of the Service. For the AI Gateway, the models are operated by third-party Model Providers, not by CubePath. AI Services are subject to rate limits and spending limits, may be slow or unavailable, and have no SLA. **A.5.2 Model Providers.** When you send AI Input to a model of a Model Provider, CubePath sends it to that Model Provider. The Model Provider processes it under its own terms, usage policies and data practices and in its own locations, which can be in any country. The Documentation links the terms and usage policies of each model offered, and the model catalog shows the Model Provider of each model. You must comply with those terms and policies, and they apply to you for the use of that model. Before you select a model, review where and how its Model Provider handles data. Do not send Personal Data, special categories of Personal Data or regulated data (Section A.10.6) to a model unless the Model Provider's terms and location are suitable for it and you have a legal basis and any transfer mechanism that the law requires. CubePath may add, change, restrict or withdraw models and Model Providers at any time, with notice where practical. **A.5.3 No training by CubePath.** CubePath does not use Customer Content, including AI Input and AI Output, to train or fine-tune machine learning models. CubePath's own AI Features use Anthropic, PBC as their AI provider. A Model Provider's own use of AI Input is governed by its terms for the model you choose. **A.5.4 AI Output.** AI Output is generated by a model. It can be inaccurate, incomplete, outdated, biased or similar to content that others have received. AI Output may not be unique. As between you and CubePath, Sections 10.3 and 13.4 of the Terms address rights in AI Output. **CubePath gives no warranty that it is correct or that it does not infringe the rights of others.** You are responsible for evaluating AI Output before you rely on it and for how you use it. **A.5.5 Your use of AI Features.** You must: - comply with the AUP, including its rules on AI uses, and with the usage policies of the Model Provider; - not use AI Output as the sole basis for decisions with legal or similarly significant effects on a person, or for other high-risk uses, unless you comply with the Applicable Law that governs them; - tell your own End Users that they are interacting with an AI system, or that content is AI-generated, where the law requires it; - have the right to submit the AI Input, and have any legal basis and notices that data protection law requires for Personal Data you submit. **A.5.6 CubePath's own AI Features.** CubePath uses AI Features in its own support and Control Panel. Where the AI Features read Organization data, they use read-only tools and a limited set of data that Part B describes. A reply you receive from support may have been drafted or sent by an AI system under staff oversight. To diagnose a problem, the AI system may use the content of your ticket and, when needed, a read-only image of the console of the Resource concerned. Replies generated by an AI system are identified as such. You can ask for a human to review your case at any time by saying so in the ticket. ### A.6 Developer Tools and Automation Developer Tools and Automation are tools for managing the Services by software. Examples are the API and API tokens, cubecli, the Terraform provider, Agent Skills, the MCP Server and connected apps, Cloud Alerts, notification channels and event delivery. Section 5.7 of the Terms also applies. **A.6.1 What CubePath operates.** CubePath operates the API and MCP Server endpoints, the authorization system and the notification and event delivery systems. CubePath publishes the tools that it distributes (such as cubecli, the Terraform provider and Agent Skills) but does not operate your environment where they run. **A.6.2 You are responsible for your automation.** Actions taken with your Credentials are treated as your actions. This includes actions by scripts, CI systems, Terraform runs, third-party apps you authorize, OAuth clients, MCP clients and AI agents, whether or not you intended the action, and the Fees that result. This includes creating, changing and deleting Resources. You are responsible for the permissions you grant. Grant the narrowest scopes that work, restrict tokens by IP address where the Service allows it, keep Credentials out of source code and logs, and revoke Credentials you no longer need. CubePath may revoke or restrict Credentials it believes are compromised or abused. If you notify CubePath at [support@cubepath.com](mailto:support@cubepath.com) that Credentials are compromised, you are not responsible for Fees from actions taken with those Credentials after CubePath has had a reasonable time to revoke them, unless you or your Authorized Users caused the actions. This paragraph does not apply to a compromise caused by CubePath's breach of the Agreement or by a Security Incident in CubePath's systems, for which you are not responsible. **A.6.3 Automated actions.** You are responsible for the rules, triggers and automations you configure, including any that create or delete Resources, and for the notifications they send. An automation that works as you configured it is not a defect of the Service. Test automations before relying on them. **A.6.4 Delivery of notifications and events.** Notifications and events are delivered on a best-effort basis. CubePath retries a failed delivery where the Service describes retries, which can cause the same notification to be delivered more than once. There is no guarantee of order or timing. A delivery may be duplicated, delayed or missed. Do not rely on them as the only means of learning about events that are critical to you. Your receiving endpoint must handle duplicates and must be secure. CubePath may stop delivery to an endpoint that fails or is abusive. ### A.7 Third-Party Offerings Third-Party Offerings are software, models, services or content that a third party provides and that CubePath makes available with the Services. Examples are operating system images and licenses, control panels, Marketplace applications, Helm add-ons for Managed Kubernetes, AI models of Model Providers, and the network services of carriers and cloud providers. **A.7.1 Third-party terms apply.** Each Third-Party Offering is licensed or provided by its owner under the owner's terms. You agree to follow those terms when you use the Third-Party Offering. As between you and the third party, the third party's terms govern. As between you and CubePath, the Agreement governs, and the rules in this Section apply. **A.7.2 CubePath's role.** For a Third-Party Offering, CubePath makes it available and may install it with default settings. Unless the Service description says otherwise, CubePath is responsible only for making the Third-Party Offering available and for its initial installation. **CubePath does not warrant it, does not administer, patch, tune or support it, and is not responsible for its content, security, license compliance or behavior.** Any claim about a Third-Party Offering is against the third party, to the extent its terms allow. **A.7.3 Licenses.** You are responsible for holding the licenses that your use of a Third-Party Offering requires, except where the Service description or the price states that CubePath supplies the license. Where CubePath supplies a license as part of the price of a Service, CubePath may pass through the vendor's end-user terms and may suspend or withdraw the license if you breach them or if the vendor requires it. Some software images are trial or evaluation editions, and you must obtain and apply a proper license where the vendor's terms require it. A Third-Party Offering may be under an open source license, a source-available license or a commercial license. Those licenses may restrict your use, for example in the way you offer the software to others over a network. ### A.8 Programs and Promotions Programs and Promotions are offers that are not the ordinary sale of a Service. Examples are promotional codes, free credit, hackathons, the referral and affiliate program, and the partner and reseller programs. Part B has rules for specific programs. Each such offer is a "Program" or a "Promotion". **A.8.1 No entitlement.** A Program or Promotion is offered at CubePath's discretion. CubePath may change, suspend or end it, or change its rules, at any time. A change does not take away Credits already granted to you except as these terms provide. Unless the program page says otherwise, you do not acquire a right to receive a program benefit in the future. **A.8.2 Credits.** Credits received from a Program or Promotion have no cash value, are not refundable, are not transferable, may expire, and may be restricted to certain Services, as Section 7.8 of the Terms provides. **A.8.3 Misuse.** You may not obtain a benefit through false information, multiple Accounts or Organizations, self-referral, automated sign-ups, spam or other abuse of the rules. If you do, CubePath may remove the benefit and the Credits, recover amounts paid out, suspend or terminate the Accounts concerned, and refuse future participation. Sections 3.4 and 3.6 of the Terms also apply. **A.8.4 Programs that need a separate agreement.** Participation in a partner, reseller or similar program may need a separate written agreement. The program page then states this. Without it, you may not present yourself as a partner, reseller or agent of CubePath, and you may not resell the Services except as the AUP allows. **A.8.5 Contests, hackathons and endorsements.** A contest, giveaway, hackathon or similar event that offers a prize has its own official rules, which prevail over this Section for that event. It is void where prohibited by law. If you receive a commission, credit or other benefit for referring customers, you must clearly disclose that relationship in each promotion, follow the FTC Endorsement Guides, and comply with the CAN-SPAM Act and equivalent laws in every message you send. CubePath may withhold or reverse a benefit earned through a non-compliant promotion. ### A.9 Beta Services **A.9.1 What is a Beta Service.** A Beta Service is any Service or feature that the Control Panel, the website, the Documentation or the changelog marks as Beta, Preview, Early Access, Experimental or by a similar term. A Service is a Beta Service from the moment it is so marked until CubePath publishes that it is generally available. **A.9.2 Terms of use.** **Beta Services are provided "as is" and "as available".** This disclaimer is in addition to the disclaimers in Section 15 of the Terms. The following apply to a Beta Service unless the Order Form or the Beta Service's own description states otherwise. - The SLA does not apply to a Beta Service, and no Service Credits are owed. - CubePath makes no commitment on availability, performance, support response times, compatibility or continuity. - CubePath may change, limit, suspend or withdraw a Beta Service, or any of its features, at any time. - A Beta Service may have bugs, may lose or corrupt data, and may be unsuitable for production use. You use a Beta Service in production at your own risk. Keep copies of the data you store in it. - Data and configuration may not be kept when the Beta Service ends or becomes generally available, or when it changes. - Limits on the Beta Service may differ from those of a generally available Service, and may change without notice. **A.9.3 Fees.** A Beta Service may be free or paid. If it is paid, Fees are charged at the rates shown in the Control Panel or on the Pricing Page. Payment of a fee does not remove the Beta status or give you an SLA. A Beta Service that is free now may later become paid. CubePath will tell you by email to the Owners and Admins at least 30 days before it starts charging, and will state the price and how to stop. CubePath starts charging for a Resource only if you keep it after that date, and does not start Auto-reload or any other automatic charge for it unless you have already enabled it for your Organization under Section 7.4 of the Terms. If you are a Consumer, CubePath charges you for a Resource of a Service that was free only after you have expressly accepted the price in the Control Panel. If you do not accept it, CubePath may stop the Resource on that date, and Section A.9.4 applies to its data. **A.9.4 Notice of withdrawal.** If you have stored data in a paid Beta Service, CubePath will give you reasonable notice before it withdraws that Beta Service, so that you can export the data (see Section A.13). CubePath may withdraw a Beta Service without notice where immediate withdrawal is needed for security, legal or abuse reasons. For a free Beta Service, CubePath gives the notice that is practical. Prepaid Fees for the unused period of a paid Beta Service that CubePath withdraws are refunded under Section A.12.4. **A.9.5 Transition to general availability.** CubePath has no obligation to release a Beta Service as generally available. When CubePath does, the Service Terms for the generally available Service (including a new Part B section, if any) apply from the date that CubePath states. The generally available Service may have different features, limits and prices from the Beta Service. ### A.10 Locations and data residency **A.10.1 Locations.** CubePath operates Services from data centers in Miami (Florida), Houston (Texas), the Ashburn area (Virginia), Barcelona (Spain) and Amsterdam (Netherlands). Not every Service is available in every location. The Control Panel shows the locations available for each Service at the time of order. CubePath may add locations, and may stop offering a Service in a location in the way Section A.12 provides. **A.10.2 Your choice of location.** When you create a Resource, you choose its location, where the Service offers a choice. Some Services, such as Object Storage, run from a fixed location stated in Part B. Subject to Section A.10.3, CubePath keeps the Resource, and the Customer Content stored in it, in the data center location you chose. CubePath does not move a Resource to another location without your request. CubePath may move a Resource between servers inside the same location, including live migration, for maintenance, balancing or hardware failure. If a move to another location becomes necessary because of an Emergency or a legal requirement, CubePath will tell you as soon as practical. **A.10.3 What stays in the location, and what does not.** Choosing a location does not confine everything. The following may be handled outside the location you chose. - Services that are global by design, such as the CDN and DNS (Section A.4.4), the AI Services (which send AI Input to a Model Provider, Section A.5.2), and the Control Panel, API and billing systems. - Backups, snapshots and similar data of a Service that CubePath keeps at a fixed location stated in Part B. For example, VPS Backups and Managed Database backups are currently stored in Barcelona, and the Object Storage service currently runs from a Barcelona cluster, whatever the location of the related Resource. Part B states these locations. - Support ticket attachments and the library of operating system images, which CubePath stores with a storage provider in the United States. - Data that you copy, replicate, or move between locations, or that your applications send to other places. - Support, security, operation and billing access by CubePath staff and subprocessors located in the United States or in other countries, which can involve remote access to systems in your chosen location. - Service Data and Account Data, which CubePath processes in the United States and other countries as the Privacy Policy describes. **A.10.4 Responsibility for choosing a location.** You decide whether a location is suitable for your data and your legal obligations, including data protection, sector rules, contractual commitments, latency and sovereignty requirements. CubePath does not promise that a location satisfies a particular certification, residency or localization requirement. **A.10.5 Jurisdiction and government access.** CubePath Inc. is a United States company and is subject to United States law, including legal process that can require it to disclose data in its possession or control wherever the data is located. The data centers outside the United States are also subject to the laws of the countries where they are located. CubePath handles government and law enforcement requests as Section 14.5 of the Terms provides. Except for emergency disclosures that the law allows and reports that the law requires (such as reports of child sexual abuse material), CubePath discloses Customer Content only in response to valid legal process. CubePath notifies you unless the law or the order forbids it, and may challenge requests that it considers overbroad or unlawful. Where a Service encrypts data and CubePath holds the keys, as Part B states for some Services, CubePath is able to decrypt that data. If you need protection against access by CubePath or by a government, encrypt your data before you send it to the Service, with keys that only you hold. **A.10.6 Regulated data.** Unless an Order Form signed by CubePath says so, the Services are not designed or certified for data that is subject to special legal security requirements, and you must not use them to store or process such data. This includes protected health information under the U.S. Health Insurance Portability and Accountability Act (HIPAA), payment card data that would place CubePath in scope of the Payment Card Industry Data Security Standard, and data that you are required to keep under a certification, residency or localization rule that CubePath has not agreed to in writing. CubePath does not sign business associate agreements unless an Order Form says so. You are responsible for deciding whether the Services are suitable for your data and for the safeguards that the law requires of you. Personal Data of children, special categories of Personal Data and criminal-offence data may be stored only if you have a lawful basis and have assessed that the security of the Services is appropriate for that data. ### A.11 Resource limits and quotas **A.11.1 Limits.** Services have limits. Examples are the number and size of Resources per Organization, vCPU, memory and disk totals, the number of IP addresses, zones, rules, members, tokens, keys, snapshots or buckets, request and rate limits, file and payload sizes, and the number of concurrent actions. Limits can depend on the Service, the location, the Commercial Plan, the verification status of your Organization and your account history. The Control Panel, the Pricing Page and the Documentation show the current limits, and an error message may tell you when you reach one. **A.11.2 Capacity.** Capacity of hardware, locations and IP addresses is finite. CubePath does not guarantee that you will be able to create a Resource at a particular time, in a particular location or with a particular size. Creating Resources can fail for lack of capacity. CubePath does not reserve capacity for you unless an Order Form says so. **A.11.3 Requests to raise a limit.** You may ask support to raise a limit. CubePath decides at its discretion. CubePath may ask for a justification, verification of identity, business, payment or use, a deposit, or a commitment, and may refuse the request. Some Services, such as dedicated CPU plans and dedicated server plans, can be available only after a limit is raised. **A.11.4 Changes to limits.** CubePath may change limits. If a change would reduce limits you currently use, CubePath will give reasonable notice where practical, and a Resource that already exists above the new limit is not deleted solely because of that change. CubePath may lower or apply a limit at once for security, fraud or abuse reasons, or where the law requires it. ### A.12 Deprecation, end of life and version changes This Section sets out how CubePath ends Services and retires versions and catalog items. Section 4.6 of the Terms also applies. Changes to features, limits and prices follow Sections 4.6, 7.7 and 19 of the Terms. **A.12.1 Discontinuing a generally available Service.** If CubePath decides to discontinue a generally available Service, or a feature of it that you use and pay for, CubePath will give you reasonable notice before the end date, normally at least 90 days. CubePath gives notice by email to the Owners and Admins of the Organizations that use the Service and in the Control Panel or on the website. **A.12.2 Shorter notice.** CubePath may give shorter notice, or none, where this is needed because of a security vulnerability or an Emergency; a legal requirement, an order of a court or authority, or a sanctions or export control restriction; the loss or change of a third-party license, contract or service on which the Service depends, which CubePath could not reasonably avoid; or abuse that threatens the Service. In those cases CubePath will give as much notice as is practical and will say why. **A.12.3 During the notice period.** The Service continues to run. CubePath may stop accepting new Resources of the Service from the date of the notice. You must migrate your data, configuration and workloads before the end date. CubePath may offer migration guidance or tools, but is not obliged to, except where mandatory law or an Order Form requires it. **A.12.4 At the end date.** At the end date CubePath may stop the Service and the Resources that depend on it. CubePath will not delete data stored in the Service until at least 30 calendar days after the end date, unless the law or an Emergency requires it. After that, CubePath deletes the data as the Terms provide. CubePath refunds prepaid Fees for the period after the end date. At your choice, CubePath adds the refund to your Balance or, on request, pays it to the original payment method where the payment provider allows it. Fees for hourly Resources stop on the end date. A discontinuation is not a breach by CubePath. This does not limit rights you have under mandatory law or an Order Form. **A.12.5 Retiring versions and catalog items.** CubePath may add, replace or withdraw operating system images, software and engine versions, Kubernetes versions, instance types, plans and API versions while the Service continues. For these items: - A version that has reached end of life or end of security support with its publisher may be withdrawn at any time. The 90-day period in Section A.12.1 applies to discontinuing a complete Service and does not apply to versions. - Withdrawing a version does not delete or stop existing Resources. New Resources and reinstalls use the versions in the catalog, which may be a newer version than the one you used before. - You are responsible for updating or migrating software that its publisher no longer supports. On Managed Services, CubePath may stop security updates and platform features for a retired version. If a retired version creates a risk for the platform or others, CubePath may require you to upgrade, with the notice that is practical, and may restrict the affected Resource if you do not. - For a major version of a Managed Service engine or a Kubernetes version that its publisher still supports, CubePath supports the versions listed in the Control Panel and may retire a version with the notice that is practical. - CubePath may stop selling a plan to new orders at any time. An existing Resource on a retired plan can continue for as long as CubePath offers the plan. If CubePath ends a plan for existing Resources, Section A.12.1 applies and CubePath will offer a comparable plan where one exists. CubePath may give shorter notice in the cases in Section A.12.2. - The data deletion and refund rules of Section A.12.4 do not apply to retired versions, because the Service continues. **A.12.6 Beta Services and free Services.** Section A.9 governs Beta Services. Section 4.8 of the Terms governs free Services, and CubePath gives the notice that is practical. ### A.13 Data export and deletion This Section applies to every Service that stores or processes Customer Content or configuration. Sections 9.5, 9.6 and 9.7 of the Terms also apply. **A.13.1 Your responsibility.** You are responsible for exporting the data you need before you delete a Resource, cancel a Service, close your Organization, reach the end of a Retention Period, or before a Service ends. Regular exports are a normal part of operating your systems. **A.13.2 What you can export.** "Exportable Data" means the Customer Content that you hold in a Service and the configuration data that you created for your Resources, in the form the Service lets you read or retrieve. You retrieve it with the Control Panel, the API, the CLI, and the standard protocols and tools that the Service supports. Examples: - for servers, the disk contents, copied with standard tools from the running system or from rescue mode; - for Object Storage, the objects, versions and metadata, through the S3-compatible API; - for Managed Databases, the data, through the standard dump, replication and export tools of the engine over the database endpoint; - for Managed Kubernetes, the objects and volumes of your cluster, through the Kubernetes API and its standard tools; - for DNS, CDN, networks, firewall rules and other configuration, the records and settings, through the API or the Control Panel; - for Invoices, Fees and usage, through the Control Panel and the API. The Documentation lists the export procedures, interfaces and data formats for each Service and its known limits. CubePath makes Exportable Data available in structured, commonly used and machine-readable formats where the Service allows. **A.13.3 What is not Exportable Data.** Unless Part B or the Documentation says otherwise, these are not Exportable Data: CubePath's software, platform, source code and the trade secrets in them; Service Data and records that CubePath keeps for its own security, operation, accounting and legal needs, except what the Control Panel or API shows you; backups, snapshots and recovery points in the internal format of CubePath's platform (you can restore them to a Resource and export from there, as Part B allows); assets protected by third-party rights or trade secrets, including Third-Party Offerings; and data of other customers. **A.13.4 Deletion and retrieval periods.** The periods for Suspension, deletion and retrieval are those in Sections 8 and 9 of the Terms. Deletion is permanent. CubePath does not promise to recover deleted data. Backups and snapshots that CubePath keeps age out at the end of the retention period stated for them in Part B. Where this Section provides a data retrieval period (Section A.12.4), CubePath will not delete the data before it ends, except as the law requires, in an Emergency, or for an AUP violation under Section 8.2 of the Terms. CubePath may keep data for as long as the law requires or allows, such as Invoices and accounting records, security logs and evidence of abuse. On request, CubePath confirms deletion in writing. ## Part B. Specific Services This Part B adds rules for individual Services. Each section names the category in Part A that the Service belongs to. The category rules in Part A apply to the Service first, and the section adds only what is specific to it. If a section and Part A conflict for that Service, the section prevails. Where a section describes a feature as available "where the Control Panel shows it", availability, locations, plans and limits are those shown in the Control Panel or on the Pricing Page at the time you order or use the Service. Prices are not repeated here. Sections B.1 to B.12 cover compute, storage, managed and application Services. The remaining Part B sections cover networking, edge, AI, developer, account and program Services. Section A.13 (data export and deletion) applies to every Service in this Part B that stores or processes Customer Content. Regulated data. The Services are not designed or certified for data that is subject to special security rules, such as protected health information under HIPAA, payment card data under PCI DSS, or data controlled under export control or government security rules, unless an Order Form says so. CubePath does not sign business associate agreements unless an Order Form says so. If you store or process such data in the Services, you are responsible for meeting those rules and for the controls they require. ### B.1 Cloud VPS Category: Unmanaged Infrastructure (Part A, Section A.1). **B.1.1 What the Service is.** Cloud VPS is a virtual server that runs on hardware and virtualization operated by CubePath. Plan families (for example General Purpose, High Frequency and Dedicated CPU), sizes and locations are those shown in the Control Panel at the time of order. Some plans, such as Dedicated CPU plans, are available only after a limit increase that we approve under Section A.11. **B.1.2 Billing.** A Cloud VPS is billed hourly from the Balance, with a minimum of one hour and then by full hours. A VPS that is stopped or powered off is still billed. A VPS that is suspended is not billed for compute while the Suspension lasts, but the Fees of related stored data stay as stated in Section B.4\. Billing for a Cloud VPS ends when you destroy it. Public IPv4 addresses are billed separately as described in Section B.13, and IPv6 addresses are included. Each plan includes an amount of data transfer. Transfer above that amount is billed per GB as described in Section B.18\. Optional features such as VPS Backups, VPS Snapshots and port add-ons carry their own charges (Sections B.4 and B.5). **B.1.3 What you administer.** You administer everything inside the VPS: the operating system, software, configuration, patches, firewalls inside the VPS, security, backups, data and licenses. We do not log in to your operating system, install software for you, or troubleshoot your applications. The firewall groups that you configure in the Control Panel are applied by the platform, and a rule that you set incorrectly can cut off access to your own VPS. That outcome is your responsibility. **B.1.4 Console, rescue mode and password reset.** The Control Panel gives you a console with full keyboard and screen control, rescue mode, operating system reinstallation and a password reset function. To perform rescue mode and password reset, and to configure the network of a Windows VPS when an address changes, the platform writes inside your VPS through the virtualization guest agent. This is access to the VPS that you request by using the function. For these functions to work, you must not remove or disable the guest agent or the cloud-init or equivalent initialization software that comes with our images. In rescue mode, we configure a temporary root password and the SSH keys you choose. The temporary password may be sent by email to the notification recipients of your Organization. In rescue mode the VPS boots a rescue system and the platform configures its network, the temporary password and your SSH keys through the guest agent. Email is not a secure channel. Anyone who can read the mailbox of those recipients can read the password. Change the password and end rescue mode as soon as you have finished, and keep the list of notification recipients current. You are responsible for use of the temporary password until you do. **B.1.5 Reinstall, resize and destroy.** Reinstalling a VPS erases the disks of that VPS. Destroying a VPS is irreversible: the VPS, its disks and its VPS Backups are deleted. VPS Snapshots are not deleted with the VPS (Section B.4). Restoring a backup overwrites the current disk. Resizing may require a restart and a short interruption. A resize never makes a disk smaller, so a larger plan cannot be undone to a smaller disk. Actions such as reinstalls, resizes and console sessions are subject to rate limits that protect the platform. **B.1.6 Initialization data.** Cloud-init data that you provide is stored by CubePath and on the node that runs your VPS, and is limited in size as stated in the Documentation. Do not put secrets in it that you are not prepared to have stored. A change of public addresses or private network attachments may cause cloud-init to run again on some older images, which can reset an operating system password or regenerate SSH host keys. **B.1.7 Maintenance and migration.** We may live-migrate, cold-migrate, restart or move your VPS to another node in the same location for maintenance, capacity or hardware reasons. A live migration is intended to be transparent. A cold migration can interrupt the VPS for about a minute or longer. Maintenance is announced as described in the SLA, Section 2, and its effect on Downtime is stated in the SLA, Section 6. **B.1.8 Shared platform.** We may throttle, limit or move a VPS whose sustained use of CPU, disk, memory or network degrades other customers, after notice where practicable and immediately in an Emergency. The AUP, Section 6, applies. **B.1.9 Service levels.** The SLA applies to Cloud VPS. A VPS in an Availability Group follows the SLA and Section B.5. ### B.2 Dedicated Servers Category: Unmanaged Infrastructure (Part A, Section A.1). **B.2.1 What the Service is.** A Dedicated Server is a physical server in a CubePath data center that is assigned to your Organization for the period you pay for. CubePath owns the hardware. You do not acquire ownership of it or of any component. Models, specifications, locations and port speeds are those shown in the Control Panel at the time of order. We may deliver components of the same or better specification than the one ordered. **B.2.2 Billing and delivery.** Dedicated Servers are billed monthly in US dollars on a recurring Invoice. The first period is due when you order, and later Invoices are issued in advance as stated in Section 7.3 of the Terms. Monthly Fees are due whatever your actual use. If we do not deliver within the period stated in Section 7.9 of the Terms, you may cancel and receive the refund stated there. After delivery, Fees paid are not refundable except as the Terms say or the law requires. Add-ons are billed as lines of the server's recurring Invoice. An add-on added during a paid period is invoiced at once for the rest of that period, in proportion to the days left, plus any setup fee, and then renews with the server. An add-on that is cancelled or reduced is not refunded or credited for the paid period, except as the Terms require. An add-on may have a minimum term, which we tell you before you order it, and in that case its cancellation takes effect at the end of the first paid period that ends on or after the end of the minimum term. A Dedicated Server renews automatically for a further monthly period on each renewal date until you cancel. If you have enabled automatic payment, we charge your default payment method for each renewal as described in Section 7.4 of the Terms. You can cancel at any time in the Control Panel without contacting us. A cancellation made at least five days before the renewal date takes effect at the end of the paid period and no further Invoice is issued, as stated in Section 9.2 of the Terms. If an Invoice for the next period has already been issued, we cancel it when you cancel within that time. If you cancel later, the next period is due and the server is cancelled at its end. We do not charge cancellation fees. **B.2.3 Operating system and administration.** We install the operating system you choose from the catalog by network boot (PXE). The installer configures the SSH keys you chose, an administrative (sudo) entry for the installed user and a network-boot-first boot order, so that reinstallation works. You administer everything from that point: the operating system, software, configuration, performance, security, patches, data, backups, licenses and compliance. Reinstalling erases all disks of the server. A Dedicated Server has no automatic backups from CubePath. Operating systems and licenses are covered in Section B.3. **B.2.4 Out-of-band access.** Where a server has a baseboard management controller (BMC) or a KVM device, you may be given time-limited access to it through our proxy. This gives you control of the machine below the operating system, such as power, virtual media, console and sensors. You are responsible for everything you do with that access and for protecting the Credentials. Do not share them. We may revoke or rotate BMC and KVM Credentials at any time, including after termination, a return of the server, or in an Emergency. We read BMC sensor and hardware data to operate the platform, and we may keep logs of BMC and KVM sessions for security, billing and abuse investigation. You must not use the BMC or KVM to reach any device other than your own server, or the management network of CubePath. We may block your access, and isolate the server, if you do. **B.2.5 What CubePath can do.** CubePath operates the hardware, power, network, switch ports, firewall access lists applied at the switch, out-of-band management and the PXE installation system. Section 6 of the Terms describes when we access your server and its management interfaces. In summary, as a matter of routine we do not log in to your operating system and do not read the contents of your disks. We may power-cycle, isolate or suspend a server, boot it into a rescue environment, take a read-only console image, or take other steps to preserve the security and integrity of the platform, as permitted by the Terms and the AUP, including in response to an attack, an Emergency or a legal requirement. **B.2.6 Firmware, BIOS and hardware.** You must not flash or modify firmware (including BIOS, BMC and device firmware), and you must not change BIOS settings related to power delivery, voltage, frequency or overclocking. Damage that results from a breach of this rule is your responsibility. We may charge you for the documented cost of repair or replacement of the affected hardware and may suspend or terminate the Service. You may change other BIOS settings that the BMC makes available to you, at your risk, and you must restore the default boot order needed for reinstallation if you change it. **B.2.7 Hardware faults.** If you suspect a hardware fault, you may use the console, rescue mode and reinstall features to gather information, and you should open a ticket. We investigate suspected platform, network and hardware faults. This may include out-of-band inspection and hardware tests. Hardware replacement commitments are in the SLA, Section 5\. Replacing a faulty component does not restore your data or your operating system. We may take your server offline for repair or replacement and may replace parts or the whole chassis. Keep backups of your data off the server. **B.2.8 Return and data erasure.** When a Dedicated Server is cancelled, terminated or returned, we remove your access, revoke the BMC and KVM Credentials issued to you, and reinstall the server with a wipe routine that discards the storage and overwrites part of it. This routine is not a certified data-sanitization process and does not guarantee that data cannot be recovered with forensic methods. If you need a higher standard, you must erase or cryptographically wipe the disks yourself before cancellation. To the extent the law does not allow us to exclude it, any duty we have to delete Customer Personal Data is not limited by this Section. **B.2.9 Bandwidth.** Port speeds, included transfer and the fair-use rule are in Section B.18\. Add-ons for Dedicated Servers are in Sections B.5 (port speed), B.13 (extra IP addresses), B.15 (DDoS Protection) and B.16 (BGP, BYOIP). Colocation of your own hardware is not part of this Service. ### B.3 Operating System Images and Software Licenses Category: Unmanaged Infrastructure (Part A, Section A.1). **B.3.1 Images are Third-Party Offerings.** Operating system images, templates and ISO images that we make available (together, "OS Images") are built from software published by third parties, each under its own license terms. We add initialization software so the image works with the platform. We do not otherwise warrant OS Images. You agree to comply with the license terms of each OS Image you use. Images are provided as is, and we do not promise that they are free of vulnerabilities. You patch and secure the operating system. **B.3.2 Catalog changes.** The list of OS Images changes. We may add, hide, replace or retire an image or version, for example when a distribution reaches end of life. Resources already running are not changed, but you may not be able to create new Resources or reinstall from a retired image. Some end-of-life versions may remain available as ISO images, and if you use one you accept the risk of software its publisher no longer supports. **B.3.3 Windows Server.** Windows Server images provided by CubePath are evaluation editions published by Microsoft. CubePath does not provide a Windows license, does not charge a Windows license fee, and is not responsible for activation. You must obtain a valid license that covers your use and activate the software, or convert the edition, in line with Microsoft's terms. An evaluation edition stops working or restarts regularly when its evaluation period ends. We are not required to remind you of that date. You are responsible for all use of Microsoft software that does not comply with its license, and we may suspend or remove a Windows image or Resource that infringes the publisher's rights. On Dedicated Servers, Windows is installed without activation, and the same rules apply. You are responsible for confirming with Microsoft or your reseller that your license allows the use you intend on infrastructure operated by a third party, including shared virtualized infrastructure. You indemnify CubePath under Section 17 of the Terms for claims by the publisher that arise from your use of Microsoft software that does not comply with its license. Generic volume license keys that an installer may place on a Windows installation only enable activation against a licensing server (KMS) and do not grant a license. This applies to every Windows edition we offer, including Windows editions that are not Windows Server. Any future image that includes a license sold by CubePath will have its own terms stated on its Service Page. **B.3.4 ISO images and installing other systems.** The ISO images available for a VPS are chosen by CubePath. You cannot upload your own ISO images to a VPS. On Dedicated Servers where the BMC allows virtual media, you may mount your own images through the BMC. You are responsible for their licenses and for any malware they contain. Some ISO images are network appliances or operating systems with their own licenses and terms (for example firewall, router or storage systems), and you must comply with those. We do not provide support for these images or for operating systems that are not listed in the Control Panel. **B.3.5 Reinstallation.** You may reinstall the operating system of a VPS or Dedicated Server from the Control Panel, API or CLI, using the images we make available. Reinstallation erases the disks (Sections B.1.5 and B.2.3). We do not perform manual operating system installation or configuration work inside your Resources. **B.3.6 Default accounts.** The default user of an image and the initial Credentials you set at creation are your responsibility. ### B.4 VPS Backups and Snapshots Category: Unmanaged Infrastructure (Part A, Section A.1). CubePath operates the backup and snapshot platform only. It does not manage what is inside your VPS. **B.4.1 Backups and snapshots are a convenience.** VPS Backups and VPS Snapshots are optional paid tools. They are not a guarantee that any particular data can be recovered. They are not a substitute for your own backups, and you remain responsible for your backup strategy and for testing that you can restore, as stated in Section 5.6 of the Terms. Our liability for loss of data follows Section 16 of the Terms. **B.4.2 What is captured.** Backups and snapshots capture the disk of a running VPS and may not be consistent at application level, for example for a database that is being written to. They contain the whole disk of the VPS, including any secrets, Credentials and Customer Personal Data stored there. You are responsible for that content. **B.4.3 VPS Backups.** You may enable VPS Backups for a VPS. While backups are enabled, a surcharge applies to the hourly rate of that VPS, whether or not a backup has been taken. The platform takes automatic backups at the daily time you choose (UTC) and keeps them for the number of days that you configure, within the maximum shown in the Control Panel. You may also take manual backups, up to the limit shown. VPS Backups are not point-in-time recovery. There is no committed recovery point objective or recovery time objective. Restoring a backup overwrites the current disk of the VPS. You cannot disable backups while existing backups remain. Delete them first. Backups are deleted when you destroy the VPS. We delete backups that exceed the retention you set. **B.4.4 Where backups are stored.** Backups are stored on backup infrastructure operated by CubePath in Barcelona, Spain, whatever the location of the VPS. This is a single backup site. When you enable VPS Backups for a VPS in another location, you instruct us to transfer a copy of its disk to Barcelona. We do not provide a second copy at another site. Section A.10 describes locations and data residency. **B.4.5 VPS Snapshots.** A snapshot is a copy of the disk of a VPS that you keep until you delete it. A snapshot can be taken from a running VPS or created from a backup. A snapshot can be deployed as a new VPS. Snapshots are billed hourly for the storage they use, measured as stated on the Pricing Page. They are not deleted when you destroy the VPS and continue to be billed until you delete them. Snapshots are not available in every location. Deploying a snapshot in a location other than where it is stored moves the data to that location. We apply per-Organization limits on the number and total size of snapshots, which you may request to increase under Section A.11. **B.4.6 Suspension and non-payment.** While your Organization is suspended for non-payment, you can delete backups and snapshots but cannot create or restore backups, and other changes are not available. Backups and snapshots that remain are subject to Sections 8.1 and 8.4 of the Terms: stored data may be deleted no earlier than 45 days after Suspension, after the email notices stated there. Snapshots continue to be billed during Suspension. Deletion is permanent. **B.4.7 Customer Personal Data in backups.** Customer Personal Data that you delete from a VPS remains in its backups and snapshots until the retention you chose expires or you delete them. ### B.5 Availability Groups and Port Add-ons Category: Unmanaged Infrastructure (Part A, Section A.1). **B.5.1 Availability Groups.** An Availability Group is a named group of Cloud VPS in a project that the platform places on different physical nodes in one location (the "spread" strategy). There is no separate charge, but your Commercial Plan may limit the number of groups. Placement on different nodes is a best-effort rule that applies while capacity exists. A migration, a node failure, maintenance or lack of capacity may place two members of a group on the same node for a time. Spread placement reduces the effect of the failure of one node. It does not protect against the failure of a rack, a cluster, a location or a data center, and it does not make your application highly available. You design your application to tolerate the loss of a node. Groups managed by a Managed Kubernetes cluster are read-only. A load balancer can synchronize its targets with a group (Section B.10). The 99.99% commitment in the SLA applies only where the conditions in the SLA, Section 3, are met. **B.5.2 VPS 10 Gbps port add-on.** Without the add-on, the public port of a VPS is 1 Gbps. The 10 Gbps add-on raises the speed of the port. It is provided on a best-effort basis on a shared network. It is not a guarantee of throughput, latency or availability. The add-on is billed hourly from a monthly price shown on the Pricing Page for the location, and it does not change the transfer included in your plan. Transfer above the included amount continues to be billed per GB (Section B.18). A higher port speed lets you use transfer faster, so overage Fees can accrue quickly. There is no spending cap or automatic cut-off, and you are responsible for monitoring your usage. We may send usage alerts as a courtesy. We limit how many times you can add the add-on to a VPS in a day. You can remove it at any time except while the VPS is suspended or where the VPS is a worker of a Managed Kubernetes cluster. The add-on ends when the VPS is destroyed. Fees for add-ons already used are not refunded. **B.5.3 Dedicated Server port add-on.** The 10 Gbps port for a Dedicated Server is a recurring monthly add-on where the Control Panel offers it, subject to switch and location capacity. It is billed on the server's recurring Invoice. ### B.6 Marketplace Applications Category: Unmanaged Infrastructure (Part A, Section A.1). Marketplace Applications are also Third-Party Offerings (Part A, Section A.7). **B.6.1 What they are.** Marketplace Applications are third-party applications that CubePath packages so that they start preinstalled on a Cloud VPS. This includes one-click applications, deployment platforms, automation tools, AI agent applications and images that run models locally. A Marketplace Application is not a separate hosted service. It runs on your VPS, and the VPS is the only thing CubePath bills, unless the Service Page states a license or other charge for the application. **B.6.2 Licenses.** Each application is made by a third party and licensed under its own terms. Those terms may include open-source licenses with obligations (for example network copyleft licenses), source-available licenses that restrict commercial use or competing services, and publisher end-user agreements. You agree to comply with them. You are responsible for deciding whether your use is allowed. **B.6.3 What CubePath does.** CubePath prepares the image and starts the application on your VPS at creation, and links to the application's documentation. That is the whole of CubePath's responsibility for the application. After installation, you are responsible for configuration, updates, security, backups, data and compliance of the application. Words such as "verified", "ready to use", "support included" or "automatic updates" in the catalog describe the initial packaging or what the publisher's software does. They do not mean that CubePath supports, patches, monitors or updates the application. CubePath's support covers the platform as stated in the Terms and in Section B.26, and it does not cover the application. Updates the application installs for itself are the publisher's and are not warranted. **B.6.4 Generated Credentials.** Some applications generate an administrator password or secret key on deployment. The Control Panel shows it to you. You are responsible for saving it, changing it and keeping it secret. We may not be able to show it to you again. **B.6.5 Sponsored projects.** A sponsorship or partnership between CubePath and an open-source project does not make CubePath responsible for, or a guarantor of, that project's software. **B.6.6 AI agent applications.** If you run an AI agent application, you are responsible for the agent's actions, prompts, tools, Credentials for connected accounts (for example messaging, email or code services), generated content and compliance with those services' terms. An agent that you operate is subject to Section 5.7 of the Terms, and the AUP, Section 8\. Using the CubePath AI Gateway from such an application is subject to Section B.21\. Models that you run locally on your VPS have their own licenses, which you must follow. Hardware acceleration such as GPUs is available only where the Control Panel or a Service Page shows it. **B.6.7 Higher-risk applications.** Applications that relay traffic (VPN, proxy), send email, or host game servers carry a higher risk of abuse. The AUP applies to them in the same way as to anything else you run. Advanced DDoS protection may not be offered for certain workloads, including game servers (Section B.15). **B.6.8 Catalog changes.** We may add, change or remove applications. Removing one from the catalog does not affect VPS that already run it. ### B.7 Managed Databases Category: Managed Services (Part A, Section A.2). **B.7.1 What the Service is.** Managed Databases are database instances that CubePath provisions and operates. The engines and versions are those shown in the Control Panel (currently MySQL, PostgreSQL and Valkey) and may change. An instance has one node, or three nodes where a high-availability plan is available. Each node runs on its own virtual machine. Locations and plans are those shown at order. **B.7.2 What CubePath operates.** CubePath provisions the virtual machines and the database engine. It configures replication and failover for high-availability plans. It issues and renews the TLS certificate of the instance endpoint. It runs automatic backups and applies updates as described in this section. It also applies security updates to the operating system of the nodes. CubePath may access the nodes and run administrative commands in the engine to do this, to monitor health and to restore service. This access is for operating the Service. Section 6 of the Terms applies, and we do not use it to read your data for any other purpose. **B.7.3 What you are responsible for.** You are responsible for your databases, schemas, data, queries, users and permissions, connection settings, the design of your application, and its ability to reconnect after an interruption. You must connect with TLS and the certificate verification that the Control Panel shows. You choose the backup time and retention. You decide whether to enable deletion protection. You are responsible for the data you load, including Customer Personal Data. **B.7.4 Limits on access and use.** You do not receive operating system access to the nodes and cannot install your own software, agents or extensions in them, except extensions the Documentation lists as supported. You receive an administrative database user with limited privileges. It does not include privileges over the engine's internal system databases, over replication or over the platform's own accounts. You change engine settings only from the parameters the Documentation allows. **B.7.5 Engine updates.** CubePath applies minor-version updates of the engine and operating system security updates automatically. Weekly maintenance runs on Sundays (UTC). You cannot turn automatic minor updates off. During an update, nodes restart and connections are interrupted for a short time, which can be several seconds or longer on a high-availability instance because failover uses DNS. The weekly maintenance window on Sundays (UTC) is published in the Documentation. Maintenance carried out in that window counts as maintenance announced in advance for the purposes of the SLA, Section 6\. We may announce other updates that we expect to cause a longer interruption by email or on our status page, but we are not required to. The major version of the engine (for example the 8.4 line of MySQL) does not change automatically. We may end support for a version and require you to move to a supported version, with notice as described in Section A.12\. After the end date, we may upgrade or disable the instance. **B.7.6 High availability.** A single-node instance has no high availability: a node failure is an outage until the node is recovered. A three-node instance can fail over to another node. Failover depends on DNS and on the DNS cache behavior of your clients, so connections may be interrupted for tens of seconds. Replication between nodes may be asynchronous, so a failover can lose the most recent writes. This risk is higher for Valkey. High availability protects against the failure of a node. It is not a backup and does not protect against deletion, corruption or errors in your data. **B.7.7 Backups and restore.** Automatic backups are always enabled and cannot be disabled. You choose the daily backup time (UTC) and the retention within the range shown in the Control Panel (currently 1 to 30 days). For MySQL and PostgreSQL, backups together with transaction logs let you restore to a chosen point in time within the retention period. For Valkey, you can restore only to the last daily backup, and you can lose up to 24 hours of writes. A restore creates a new single-node instance. It does not overwrite the existing one. You then move your application to it. Backups are encrypted with a key that is specific to your instance and held by CubePath, and they are stored in CubePath Object Storage in Barcelona, Spain, whatever the location of the instance. The retention you choose sets how far back you can restore. After you delete the instance, its backups are kept for 32 days (Section B.7.8). Backup storage is included in the plan price unless the Control Panel shows a separate charge. We do not promise a recovery time. Backups are a tool and not a guarantee of recovery (Section 5.6 of the Terms). **B.7.8 Deleting an instance.** Deleting an instance permanently destroys its virtual machines and data. Backups of a deleted instance are not deleted with it. Backups that exist when you delete the instance are kept for 32 days after the deletion, whatever retention you chose, and then expire. During those 32 days they can be restored to a new instance, on request to support or through the Control Panel where available. Until they expire, CubePath still holds that data. On your written request we delete these backups earlier where the platform allows it. Deletion protection, if you enable it, prevents deletion until you turn it off. **B.7.9 Billing.** Managed Databases are billed hourly from the Balance, per node and per full hour, at the plan's price. A minimum of one hour applies. Each node's public addresses are included in the plan price. Disk never shrinks when you scale. Your quotas count the nodes, and a maximum number of instances per Organization applies, which you may ask us to raise (Section A.11). **B.7.10 Endpoints and certificates.** Instance endpoints are names under a domain that CubePath owns. Certificates are issued by a public certificate authority, whose terms and rate limits apply. We do not guarantee that a certificate can always be issued or renewed. **B.7.11 Non-payment.** Section 8 of the Terms applies to Managed Databases as compute Resources. Deletion of an instance for non-payment follows the periods and notices stated there. While your Organization is suspended, the virtual machines of the instance are stopped and the instance cannot be changed, although you can still delete it. The instance is not billed while the Suspension lasts. **B.7.12 Service levels.** The SLA applies to Managed Databases, with different commitments for high-availability and single-node instances. ### B.8 Managed Kubernetes Category: Managed Services (Part A, Section A.2). **B.8.1 What the Service is.** Managed Kubernetes provides Kubernetes clusters for which CubePath operates the control plane. The control plane includes the API server, the cluster datastore, certificates and DNS, and the cluster network plug-in. Worker nodes are Cloud VPS in your Organization. Clusters are available in the locations and Kubernetes versions shown in the Control Panel. **B.8.2 Shared control plane datastore.** The control planes of clusters in a location run on infrastructure operated by CubePath, and clusters in the same location may share a datastore. A failure or maintenance event affecting that infrastructure can affect several clusters. **B.8.3 Worker nodes.** Workers are Cloud VPS and are billed as VPS (Section B.1). The operating system, kernel, container runtime configuration and security of the workers are your responsibility, as for any unmanaged VPS. The platform creates, joins, replaces and deletes workers. You manage them through the cluster and not as ordinary VPS. If you change or delete a worker outside the cluster functions, the cluster may stop working, and we are not responsible for the result. Deleting a worker deletes its disk, and any persistent data stored on a worker disk is lost. **B.8.4 Control plane billing.** A standard control plane has no separate charge. A highly available control plane has an hourly charge shown on the Pricing Page. Workers, load balancers (Section B.10), NAT Gateways, private networks and IP addresses are separate Resources with their own charges. **B.8.5 Kubeconfig and your responsibilities.** You receive Credentials with cluster-administrator rights (kubeconfig). Everything you deploy in the cluster belongs to your responsibility: workloads, container images, manifests, namespaces, RBAC, secrets, network policies, persistent data, backups, and the security of your applications. CubePath keeps administrative access to the control plane so it can operate the cluster, join and replace workers, and install or remove add-ons at your request. Section 6 of the Terms applies to that access. **B.8.6 Autoscaling.** If you enable the node autoscaler or node pools with autoscaling, the platform creates and deletes workers within the minimum and maximum that you set. The autoscaler acts with a platform token created in your Organization with the permissions needed to manage workers. You authorize the autoscaler to create billable Resources without further confirmation, and you are responsible for all resulting Fees, including those caused by your workload demands, by errors in your configuration and by limits you set too high. The autoscaler deletes workers when they are no longer needed. **B.8.7 Versions and upgrades.** CubePath supports the Kubernetes versions that the Control Panel lists for new clusters, and it may stop offering a version. We do not promise automatic upgrades of your cluster or a particular support period for each version. When a version reaches the end of its support, we may require you to upgrade, with notice as described in Section A.12, and after the date given we may restrict operations on that cluster. You are responsible for making your manifests and workloads compatible with new versions. **B.8.8 Add-ons.** The Control Panel may offer a catalog of add-ons, for example ingress controllers or certificate managers. They are Third-Party Offerings. They are open-source or third-party software, usually Helm charts, and are provided as is under their own licenses. CubePath installs them at your request with the default version of the catalog and any values you provide. CubePath does not warrant them, support them, or keep them updated. Add-ons use the resources of your own cluster. We may remove an add-on from the catalog. **B.8.9 Backups.** CubePath does not back up the state of your cluster, the Kubernetes objects in it, or the data in your workers' disks. You are responsible for such backups. VPS Backups and Snapshots (Section B.4) apply to workers only if you enable them where available. **B.8.10 Private clusters.** A private cluster has no public addresses on its workers and depends on a private network and a NAT Gateway or another default route to reach the Internet. If you delete or change that route, the cluster loses outbound access. Deleting a cluster does not always delete the private network that was created for it. You delete networks you no longer need. **B.8.11 Abuse.** Traffic from your pods leaves from your worker or NAT addresses and is attributed to you. The AUP applies to everything that runs in the cluster. **B.8.12 Deleting a cluster.** Deleting a cluster is irreversible. It deletes the control plane, the workers and their disks, and related platform Resources such as DNS records and the autoscaler token. Deletion protection, if you enable it, prevents deletion until you turn it off. **B.8.13 Non-payment.** Section 8 of the Terms applies to a cluster and its workers as compute Resources. Suspension of the Organization stops the workers. The control plane may keep running and stays subject to the deletion periods in the Terms. While the Suspension lasts, the cluster cannot be changed, although you can still delete it, a node pool or a node, and neither the workers nor the highly available control plane are billed. **B.8.14 Service levels.** The SLA applies to the Kubernetes control plane as stated there. Workers follow the commitment for Cloud VPS. We make no commitment about add-ons, your workloads, or any monitoring, self-healing or backup function that is not described in the Control Panel or Documentation. ### B.9 Object Storage Category: Managed Services (Part A, Section A.2). **B.9.1 What the Service is.** Object Storage is an S3-compatible service for storing objects in buckets. Tiers, regions and endpoints are those shown in the Control Panel. Today it is offered in a single tier, Infrequent Access, in the region named "eu", hosted in Barcelona, Spain. Other tiers and regions are not offered until they appear in the Control Panel. Buckets do not move between tiers, projects or regions. **B.9.2 Durability and backup.** Data in a bucket is protected against disk and node failure inside one storage cluster by erasure coding. CubePath does not replicate your objects to another site and does not make backups of them. A failure of the cluster or the site can lead to loss of data or a long outage. We do not publish a durability percentage, and nothing in the Agreement promises one. You are responsible for copies that you need. You may configure replication to another bucket or to an external destination where the Control Panel allows it. Replication to an external destination is egress from your bucket and is billed. We do not control the destination. **B.9.3 Encryption and keys.** Objects are always encrypted at rest using server-side encryption with keys managed by CubePath. You cannot turn this off or change it. We also support encryption with a key that you provide with each request. If you use that, we do not keep your key, and if you lose it the data cannot be recovered. Customer-managed key services are available only if the Control Panel shows them. Object names, user metadata and tags are not encrypted. **B.9.4 Access keys, policies and the Control Panel.** You are responsible for your access keys, bucket policies, sharing links, encryption choices, lifecycle rules and retention settings. A key that is lost, leaked or misused is your responsibility. You must revoke it. The Control Panel and API use internal service Credentials to browse, upload and create sharing links for you. Requests made that way are measured and billed like any other request. Public buckets, anonymous access and static website hosting are available only if the Control Panel shows them. If you want to serve objects to the public, you do so through the CDN (Section B.19) and you are responsible for the content you publish. Sharing links are time-limited and give download access to one object. **B.9.5 Billing.** Object Storage is billed hourly from the Balance for the storage you use, for requests (by class) and for data transferred out. A free allowance applies per Organization, per month and per tier, as shown on the Pricing Page. Data transferred in (uploads) and delete requests are not charged. Write and listing requests are charged as requests of the class shown on the Pricing Page. Transfer from a bucket to the CDN is not charged, but other transfer out, including to other CubePath Services, is. Requests from CDN edge servers count as requests. Every stored version of an object is billed until it is deleted, including versions protected by Object Lock. Objects that expire under a lifecycle rule are billed until they are actually removed, which can take up to about 48 hours after the expiry date. A minimum Balance is required to create the first bucket. Event deliveries (Section B.24) are billed as shown on the Pricing Page. **B.9.6 Limits and capacity.** Limits apply to the number of buckets, keys, rules, event destinations, replications, sharing links and the size of objects and requests. They are stated in the Documentation and may be raised under Section A.11\. A soft limit applies to the total stored in a bucket and in an Organization. If you exceed it, we notify you, and if you do not reduce usage within the period stated in the notice, we may pause uploads to that bucket. Reads, listings and deletions continue. Where a storage cluster nears its capacity, we may stop creating new buckets and may restrict writes of Organizations above their soft limit until capacity is restored. Incomplete multipart uploads are aborted after seven days. **B.9.7 Object Lock and legal holds.** Object Lock can be enabled only when a bucket is created. It may be available only to Organizations for which we have enabled it, and only for Business Customers. The following apply to objects protected by Object Lock or a legal hold: - Retention has two modes. In GOVERNANCE mode, a protected version can be deleted before its retention ends by an access key to which you gave the governance bypass permission, by a forced deletion of the bucket that you request with the bypass option, and by CubePath when it removes content under Section B.9.8\. In COMPLIANCE mode, and while a legal hold is in place, neither you nor CubePath can delete a protected version or shorten its retention before the retention period ends or the hold is lifted, except as stated in the exception bullet below. - Retention in COMPLIANCE mode cannot be shortened or removed by you or by any user of your Organization. - Notwithstanding Sections 8 and 9 of the Terms, Suspension, non-payment, closure of your Organization or termination of the Agreement does not shorten a retention period. Storage Fees for protected versions continue to accrue until they expire or are deleted as this Section allows, even if you stop paying, and until then the bucket and its project cannot be deleted. - By enabling Object Lock in COMPLIANCE mode you confirm that you understand that you will owe Storage Fees until each protected version expires, that nobody can shorten the retention, and that the Fees continue if you close your Organization or stop paying. - If Fees are unpaid, they remain a debt that you owe, and we may recover them. - You are responsible for choosing a retention period that you can accept. The maximum retention is shown in the Documentation. If you are a controller of personal data, you are responsible for choosing a retention period that lets you meet your own deletion and erasure obligations. - For versions in COMPLIANCE mode or under a legal hold, as the only exception, CubePath may remove a locked version, or destroy a bucket that holds locked versions, only where a court order or legal requirement leaves no alternative, or to remove content that is illegal or that we reasonably believe is child sexual abuse material. We use a restricted internal procedure and do not wait for retention to end. We tell you by email where the law allows. Fees for a removed version stop accruing when it is removed. - Object Lock is not certified for any regulatory records standard, such as SEC Rule 17a-4, FINRA or CFTC rules. You are responsible for deciding whether it meets your legal requirements. **B.9.8 Abuse, legal process and preservation.** If we reasonably believe that content in a bucket violates the AUP or applicable law, or if legal process requires it, we may quarantine objects, remove specific object versions, block access to a bucket, suspend Object Storage for your Organization, and place a hold on creating new buckets and keys. We notify you by email where the law allows. We may copy affected objects to a restricted internal bucket and keep them as evidence for 90 days, or longer where the law or a legal order requires. We may also place our own legal hold on objects to comply with a preservation order. When we restrict content or Services under this Section, we send you a statement of reasons and tell you how to appeal, as Section 14.3 of the Terms provides, except where the law or a competent authority prohibits it. If we find apparent child sexual abuse material, we report it as required by 18 U.S.C. 2258A and preserve the content for the period that law requires, and the 90 day period above does not shorten it. **B.9.9 Deletion of buckets.** You can delete a bucket when your Organization is suspended. You can delete an empty bucket, or force-delete a bucket and all its contents. A forced deletion is irreversible, and there is no recovery period. A bucket cannot be deleted while it is protected, blocked by CubePath, used as an origin by a CDN zone, or the target of replication. After deletion, the bucket name is reserved for 90 days. Buckets stay billable while suspended. Under Section 8 of the Terms, stored data may be deleted no earlier than 45 days after Suspension for non-payment, after notices, subject to Section B.9.7. **B.9.10 Personal data and content.** You are responsible for the content of your buckets, for having the right to store it and for whether it includes Customer Personal Data. For Customer Personal Data, CubePath acts as your processor. Storage nodes can see object names and metadata. Event notifications and alerts that you configure send object names and metadata to the endpoints you choose. **B.9.11 Service levels.** The SLA applies to Object Storage, measured as stated there. ### B.10 Load Balancers and NAT Gateways Category: Managed Services (Part A, Section A.2). **B.10.1 Load Balancers.** A Load Balancer is a virtual machine running load-balancing software that CubePath operates for you. It has its own public IPv4 and IPv6 addresses included in the price. You configure listeners, protocols, targets, health checks and algorithms through the Control Panel or API. Protocols and limits are those in the Control Panel for your plan, including limits on targets, listeners and connections per second. Targets may be VPS, Dedicated Servers or Availability Groups. **B.10.2 TLS and traffic.** If you use HTTPS listeners, the Load Balancer ends TLS and sees the traffic unencrypted. Certificates you upload, and their private keys, are stored on the Load Balancer. Where the Control Panel offers automatic certificates, they are issued by a public certificate authority whose terms and rate limits apply, and issuance and renewal depend on your DNS records pointing to the Load Balancer. Section 6 of the Terms applies. **B.10.3 Your responsibilities.** You are responsible for your targets, their security and capacity, the health check settings, the content that passes through the Load Balancer, and your configuration. **B.10.4 Billing, deletion and changes.** Load Balancers are billed hourly from the Balance in full hours, with a minimum of one hour, until deleted. Deleting a Load Balancer is irreversible. Its virtual machine is destroyed and its IP addresses are released. Deletion protection, if you enable it, prevents deletion until you turn it off. Configuration changes and software updates can cause a short interruption of connections. **B.10.5 NAT Gateways.** A NAT Gateway lets servers on a private network reach the Internet without public IP addresses of their own. It provides outbound connections only. It does not forward inbound ports. There can be one NAT Gateway per private network. Servers behind it share one public IPv4 address. All outbound traffic of those servers, including abusive traffic, is attributed to that address and to you. Blocklisting of that address by third parties is your responsibility. **B.10.6 NAT Gateway billing and deletion.** NAT Gateways are billed hourly like Load Balancers, and their addresses are included. If you delete a NAT Gateway, the servers and managed clusters that depend on it lose outbound access. Deletion is irreversible. **B.10.7 Non-payment.** Section 8 of the Terms applies to Load Balancers and NAT Gateways as compute Resources. **B.10.8 Service levels.** The SLA applies to Load Balancers and NAT Gateways as stated there. ### B.11 Video Transcoder Category: Managed Services (Part A, Section A.2). **B.11.1 Beta status.** Video Transcoder is a Beta Service unless the Control Panel or our website labels it as generally available. Section A.9 applies. There is no SLA, and we may change, limit or withdraw it. We may withdraw it as stated in Section A.9. **B.11.2 What it does.** Video Transcoder converts video from an input location that you provide (a public web address or an S3-compatible object) to outputs written to an S3-compatible bucket that you provide. Outputs can be files, streaming playlists and segments, thumbnails and animated images. You submit jobs individually or in batches through the Control Panel or API. **B.11.3 Billing.** The Service is free today. We may begin charging for it, for example per minute of processed video, after the notice stated in Section A.9.3\. Jobs that you submit after the date charges begin are charged at the price stated in that notice. We require a verified Organization and a positive Balance to create jobs. **B.11.4 Your credentials.** To read inputs and write outputs, you give us access Credentials for your storage. We store them encrypted and decrypt them to run your job. We do not return them through the API. You should use Credentials that are limited to the input and output buckets that the job needs, can be revoked, and that you rotate. You are responsible for the Credentials and for the cost and security of your storage. Our own Object Storage is one possible destination. **B.11.5 Your content.** You must have all rights needed to process the inputs and produce the outputs, including copyright, Customer Personal Data and publicity rights. For Customer Personal Data in your inputs and outputs, CubePath acts as your processor, even while the Service is a Beta Service. You are responsible for the content under Section 5.1 of the Terms, and the AUP. CubePath does not inspect the content as a matter of course. We keep your video only for the time the job needs, in temporary processing space, and write the outputs directly to your bucket. We keep records of jobs (settings, status, timing and addresses), and CubePath staff can see, cancel and retry any job when needed to operate the Service, investigate abuse or help you. **B.11.6 Codecs and patents.** Video formats and codecs such as H.264, H.265 and AV1 can be covered by patents and by license programs. CubePath does not provide a patent license for your use of them. You are responsible for any license your use requires. The IP indemnification in Section 17 of the Terms does not cover claims that arise from the codecs, formats or settings you choose, or from patent license fees for them. **B.11.7 Input addresses and webhooks.** Inputs must be reachable on the public Internet through http or https. We block addresses in private, reserved and similar ranges. A webhook is attempted once, with a short timeout, and is not retried. Check job status through the API if you need certainty. **B.11.8 Limits and fair use.** Limits apply to concurrent jobs, batch sizes and outputs per job, and are stated in the Documentation. Some settings use a great deal of processing power (for example very high resolutions or some codecs). We may reject, delay, limit or cancel jobs that put the Service at risk. We do not promise a completion time, output quality, or that outputs will play on a particular device. ### B.12 cPanel Servers Category: Unmanaged Infrastructure (Part A, Section A.1). cPanel & WHM is a Third-Party Offering (Part A, Section A.7). **B.12.1 What the Service is.** A cPanel server is a Cloud VPS (Section B.1) or a Dedicated Server (Section B.2) on which CubePath installs the cPanel & WHM web hosting control panel, from a template for a VPS or as an operating system choice for a Dedicated Server. Charges are those of the VPS or Dedicated Server, and the Control Panel order screen or the Pricing Page states whether a cPanel license is included in that price. If it does not say so, no cPanel license is included and you must obtain one from cPanel, L.L.C. CubePath provides the server and installs cPanel. A cPanel server is not a managed hosting service. **B.12.2 No management.** Unless an Order Form expressly says otherwise, CubePath does not administer, update, secure, monitor, tune or support cPanel & WHM, the operating system, hosting accounts, websites, email, DNS zones on the server, migrations, or backups. A cPanel server is a managed service only if an Order Form says so. If an Order Form adds management services, the Order Form defines their scope and any related service levels. **B.12.3 License and trademarks.** cPanel & WHM is licensed by cPanel, L.L.C. cPanel and WHM are trademarks of cPanel, L.L.C. or its affiliates. Your use is subject to cPanel's end-user license agreement and policies, published by cPanel, L.L.C. at the address it makes available for them, which you accept. Where the price of the server includes a cPanel license, the license: - is provided through CubePath for use on that Resource only, and may be tied to the Resource or its IP address; - may not be transferred, resold, sublicensed or used on other servers; - ends when the Resource ends, is suspended for abuse or is terminated, and CubePath may withdraw it if you breach cPanel's terms; and - can be audited by cPanel, and CubePath may give cPanel the information about your Resource that cPanel's license terms require, limited to license data such as the IP address, hostname, license status and software version. We do not give cPanel the contents of your Resource or of your hosting accounts. If a cPanel license stops working because of a change to the Resource or its IP address, restoring it is your responsibility, and we may charge for the work if it needs manual action. **B.12.4 Software versions.** The template may contain a version of cPanel & WHM or of the operating system that is not the latest. You are responsible for updating them. **B.12.5 Hosting for your own customers.** If you use a cPanel server to host websites, email or data for your own customers or other third parties, you do so as an independent business under the AUP, Section 9\. You are responsible for them, for your terms with them, for support to them, and for compliance with data protection law as their controller or processor. CubePath supports you only, and not your customers. You are responsible for outbound email from the server, including spam and the reputation of its IP addresses. Section B.18 describes the outbound port 25 policy. **B.12.6 Backups and service levels.** CubePath does not make backups of a cPanel server unless you buy VPS Backups for a VPS (Section B.4). Backups made by cPanel or by you are your responsibility. The SLA covers the Cloud VPS or Dedicated Server as stated there. It does not cover cPanel & WHM, its services, your websites or your email. ### B.13 IP Addresses, Floating IPs and Reverse DNS Category: Network and Security Services (Part A, Section A.3). **B.13.1 Ownership and license.** IP addresses that CubePath assigns to you, including primary and secondary IPv4 addresses, Floating IPs, extra IPv4 addresses for Dedicated Servers and IPv6 addresses, belong to CubePath (AS26141) or to its upstream providers and are registered with the applicable Regional Internet Registry (for example ARIN or RIPE NCC, depending on the block). We license them to you for as long as the Resource or add-on they are attached to exists. You acquire no ownership right and may not sell, lease, sublicense or transfer them to a third party. You may reassign them between Resources of your Organization where the Control Panel allows it, in the same location. IP space that you own or are authorized to use and bring to CubePath is governed by Section B.16, not by this Section. **B.13.2 Allocation and limits.** The number of IP addresses you can hold depends on the limits of your Organization and your Commercial Plan (Sections A.11 and B.25). Floating IPs can only be assigned to Resources in the same location. Rate limits apply. Regional Internet Registry policy may require us to publish the name, address and abuse contact of the holder of an address block or assignment in the public registry (WHOIS). You authorize this and must keep these details accurate. The primary IPv4 address of a server is released only when the server is destroyed. If you ask for a large number of addresses, we may require a written justification of the intended use that satisfies the policy of the applicable Regional Internet Registry, and we may refuse or limit the request. **B.13.3 Fees.** Floating IPv4 addresses and extra IPv4 addresses are charged at the rates on the Pricing Page from the moment they are reserved until they are released, whether or not they are assigned, except while your Organization is suspended. IPv6 addresses are not charged separately unless the Pricing Page says so. A released address is charged for at least one hour. IPv4 addresses included in a Load Balancer or NAT Gateway plan are not charged separately. Extra IPv4 addresses for Dedicated Servers are a recurring add-on invoiced with the server, normally installed within 48 hours of the order, which is a target and not a commitment. **B.13.4 Reputation and use.** You are responsible for how every address assigned to you is used and for its reputation, including blocklists. Abuse from an address is attributed to the Organization that holds it, including the traffic of all Resources that leave through a shared address such as that of a NAT Gateway. We may remove, replace or restrict an address as the AUP provides. When you release an address we remove its firewall, DDoS and routing configuration and its reverse DNS record, and the next holder inherits none of it. **B.13.5 Reverse DNS.** You may set a PTR record for an IP address assigned to you. PTR records are your responsibility: the name must be valid, must relate to your service and must not impersonate or mislead anyone. We may change or remove a PTR record that violates the AUP. Reverse DNS is free and has no commitment on publication time. ### B.14 Private Networks, Firewall Groups and Dynamic Routes Category: Network and Security Services (Part A, Section A.3). **B.14.1 Private Networks.** A Private Network is an isolated layer 2 segment that you create in one location and use to connect your VPS, Dedicated Servers and Kubernetes nodes in that location. CubePath operates the control plane, the switches and the gateway that serve the network. You decide the addressing, the routes and which Resources are attached, and you are responsible for the security of the traffic inside the network. A Private Network does not include a firewall; use Firewall Groups (Section B.14.4) for filtering. We do not promise that traffic on it is encrypted. **B.14.2 Limits.** Limits on Private Networks and routes are shown in the Control Panel. Networks created for a managed Kubernetes cluster are controlled by CubePath and cannot be edited or deleted manually while the cluster exists. **B.14.3 Deleting a network.** Deleting a Private Network removes its IP assignments, routes and BGP peers. It cannot be undone. **B.14.4 Firewall Groups.** Firewall Groups are reusable sets of allow rules that you assign to VPS and Dedicated Servers. For a VPS they are applied in the hypervisor firewall: inbound traffic not allowed by a rule is denied. For a Dedicated Server they are applied as access lists on the switch port. You write the rules, and a rule that blocks your own access is your responsibility. Rules are applied asynchronously, so a change is not instant, and if applying a change fails the Resource keeps its previous configuration until a later change succeeds. It does not replace the firewall of your operating system. Limits on rules and groups are shown in the Documentation. **B.14.5 Dynamic Routes.** Dynamic Routes let a server in a Private Network exchange routes with the gateway of that network over a private BGP session. For public IP space see Section B.16\. The local AS number is chosen by CubePath, and the AS number you use must differ from it. You are responsible for the prefixes you announce, and CubePath does not verify the ownership of private prefixes. When your Organization is suspended you cannot create or change sessions, firewall groups or routes, but you can delete them. ### B.15 DDoS Protection Category: Network and Security Services (Part A, Section A.3). **B.15.1 Levels of protection.** CubePath offers the following levels, described in the Documentation and in the Control Panel: - **Basic protection.** Automatic filtering at the edge of our network, applied to every public IP address on it, with no settings and at no separate charge. - **Premium protection.** Advanced protection for a Floating IP or for a prefix announced under Section B.16, with a profile you configure (for example protection level, limits by packets or bandwidth, filters by country or AS number, prefix lists and edge firewall rules). It is sold as an add-on, as part of a Commercial Plan entitlement, or by Order Form. The level is set for each address or prefix, in some cases by CubePath staff at your request. - **Remote DDoS Protection.** A service for servers hosted outside CubePath, sold by quote. Traffic is redirected to our network, filtered and returned to you through a tunnel, with or without BGP. A trial may be offered and may be ended at any time. Which levels are available for an address, and the limits that apply (such as the number of rules, prefix lists and entries per list), are shown in the Control Panel and depend on your Commercial Plan or Order Form. **B.15.2 No guarantee.** Mitigation is provided on a commercially reasonable efforts basis. No level of protection guarantees that every attack will be detected or blocked, that traffic will not be delayed or dropped, or that legitimate traffic will not be affected. Premium protection can block your own legitimate traffic if the profile or rules you configure are wrong, and that is your responsibility. The SLA does not cover the effectiveness of mitigation. **B.15.3 Protecting the network.** To protect our network and other customers, we may rate-limit, filter, redirect to a scrubbing system, or null-route (blackhole) the traffic to any IP address that is under attack, including an address with Premium protection when the attack exceeds the capacity of the protection, for as long as we consider necessary. We restore routing as soon as practicable. Whether unavailability caused by an attack or by these measures counts as Downtime is decided by Section 6 of the SLA, which excludes it only to the extent the attack exceeds the DDoS Protection included in or purchased for the Resource. Receiving an attack is not in itself a violation of the AUP. Section A.3.5 applies. **B.15.4 Workloads we decline.** We may decline to offer Premium or Remote DDoS Protection for certain workloads, including game servers and game-hosting workloads, and for other workloads for which we cannot protect the network or other customers. **B.15.5 Remote DDoS Protection.** You confirm that you own the IP space to be protected or are authorized by its holder to redirect it, and you give us the evidence we ask for. We process the redirected traffic, including content in transit, only to filter it and to operate and secure the service. You are responsible for your own infrastructure, your network providers and the tunnel at your end. We make no promise of protection at a particular layer unless your Order Form says so. Commercial terms, capacity and any service levels are those of your Order Form. ### B.16 BGP Sessions, BYOIP and BYOASN Category: Network and Security Services (Part A, Section A.3). **B.16.1 What the service is.** On request and for the fee on the Pricing Page or in your Order Form (normally a monthly fee and a setup fee), CubePath may establish BGP sessions with you and announce IP prefixes and AS numbers that you own or are authorized to use ("BYOIP" and "BYOASN"). The service is attached to another Service, such as a Dedicated Server, IP Transit or a Tunnel. It is set up manually by CubePath staff, normally within 48 hours of the order (a target, not a commitment), and we may refuse any request. **B.16.2 Your rights over the space.** Before we announce a prefix or accept a session with an AS number, you must prove that you hold the right to use it. We may ask for a letter of authorization (LOA) signed by the holder of record, registry records and valid IRR route objects and RPKI ROAs, and for current network operations and abuse contacts. You must keep this information current, and tell us before you lose the right to use the space. You represent that you have, and will keep, the right to announce the space and to authorize us to do so. **B.16.3 Operating modes.** Depending on what is agreed, CubePath originates your prefix from its own AS number, or accepts announcements from your AS number over BGP, or both. Limits on prefixes and session features are in the Documentation or the Order Form, and a session that exceeds the maximum number of prefixes may be shut down automatically. **B.16.4 Filtering and withdrawal.** We may filter, refuse, suspend or withdraw any announcement or session that is unverified, exceeds the agreed limits, causes routing instability, hijacks or misannounces space, or violates the AUP, without notice if we consider it necessary to protect the network or third parties, and with notice otherwise where practicable. **B.16.5 Your responsibility.** You are responsible for the content and use of your space, for the correctness of your BGP configuration and for any consequence of an incorrect announcement, including route leaks and hijacks. An outage caused by your BGP configuration, your equipment or a missing or outdated LOA, IRR object or ROA is a customer cause under the SLA. You will defend and indemnify CubePath against claims by third parties, including the holder of record of the space and operators of affected networks, arising from your announcements, your space or your BGP configuration, as the indemnity in the Terms provides. We may withdraw any announcement at once on a credible complaint from the holder of the space or from an operator of an affected network. **B.16.6 Ownership.** Customer-provided space stays yours. We acquire no right to it, and when the Service ends we withdraw it and remove its filters and DDoS configuration. Reverse DNS delegation for your space can be set to your own servers or to ours, as the Control Panel offers. **B.16.7 Redundancy.** A BGP session is not redundant unless your Order Form or the Documentation says so. At a location with a single edge router, maintenance or failure of that router interrupts the session. ### B.17 IP Transit, Layer 2, Cloud Gateway and Tunnels Category: Network and Security Services (Part A, Section A.3). **B.17.1 Sold by quote.** IP Transit, Layer 2 point-to-point circuits, Cloud Gateway and Tunnels are provisioned manually by CubePath's network team and are sold by quote and Order Form. The Order Form states the location, port or circuit, capacity, fees, term and any service level. These Services are sold only to Business Customers. Delivery dates are estimates. Carriers, Internet exchanges and cloud providers are third parties that we do not control. **B.17.2 IP Transit.** IP Transit is provided over a dedicated port of the speed stated in the Order Form, using BGP, with an AS number and prefixes that you bring. Section B.16 applies to the announcement of your space, which we validate with RPKI. Unless your Order Form says otherwise, you pay a fixed monthly fee for the port and for any committed bandwidth, and usage is not measured to compute the fee. Billing on the 95th percentile of usage applies only if your Order Form says so and describes the method. The term, any renewal, early termination and the fees that remain due are those of your Order Form. **B.17.3 Layer 2.** A Layer 2 circuit carries Ethernet frames between two points in the locations stated in the Order Form, with the VLAN configuration agreed. You are responsible for encrypting what you carry and for your equipment at both ends. **B.17.4 Cloud Gateway.** Cloud Gateway provides private connectivity between your CubePath network and a third-party cloud provider such as AWS (Direct Connect), Google Cloud (Interconnect) or Microsoft Azure. You are responsible for your accounts, services, circuits and charges with that provider, which are third-party services under the provider's own terms, and for the provider's approval of the connection. CubePath is not responsible for the availability, performance, pricing or terms of the provider's side of the connection. Any service level in your Order Form covers only CubePath's equipment and ports up to the demarcation point with the provider, and never the provider's network or services. **B.17.5 Tunnels.** A GRE tunnel connects an endpoint of CubePath with an endpoint of yours and can carry BGP sessions for your space. CubePath's staff create, change and remove tunnels, and the Control Panel shows their state in read-only form. You are responsible for your own endpoint and for the effective MTU of the path. We may suspend a tunnel as described in Section B.16.4\. Fees are as stated in your Order Form. **B.17.6 Service levels.** The SLA does not cover these Services unless your Order Form says so. ### B.18 Bandwidth, Transfer and Email Ports Category: Network and Security Services (Part A, Section A.3). **B.18.1 VPS transfer.** Each VPS plan includes a monthly allowance of public transfer stated in the plan, counted in the direction shown on the Pricing Page. The allowance is measured per calendar month and starts again on the first day of each month. Only traffic over the public network interface counts: traffic over a Private Network does not. Transfer above the allowance is charged to your Balance per gigabyte at the rate on the Pricing Page. We may notify you when you approach or exceed the allowance, but a notice is not a condition of the charge. The 10 Gbps port add-on of a VPS (Section B.5) does not change the allowance and is shared and best effort: it does not guarantee any throughput. Our usage records are the basis for the charge (Section 7.11 of the Terms). **B.18.2 Dedicated Server transfer.** Dedicated Servers have the port speed stated in the plan. Where the plan or the Pricing Page lists a model as unmetered, there is no charge for transfer. Unmetered does not mean unlimited capacity: the port speed is a maximum and not a guaranteed rate, and the model is subject to this Section. Some models have a monthly allowance in terabytes, which is shown when you order. Use is excessive if it uses the port at or near its full speed for most of a month, if it exceeds the monthly allowance or reasonable-use level stated for the model when you order or in the Documentation, or if it degrades the network or other customers. For excessive use we normally notify you, give you a reasonable time to reduce it, and may then limit the speed of the port or suspend the Service. We may act at once and without notice where this is needed to stop an attack, to protect the network or in an Emergency. Section A.3.7 applies. **B.18.3 Outbound email.** To protect the reputation of our network, outbound TCP ports 25 and 465 may be blocked by default on public IP addresses assigned to you. Port 587 (submission) is not affected. You can ask support to unblock these ports for a specific IP address. We decide each request. We may require identity or business verification, a history of payments, a description of your intended use, and that your mail server uses a PTR record that matches its greeting and has SPF, DKIM and DMARC configured. We do not promise to approve a request or to do it within a set time. Opening applies only to the address you named and ends when you release it. We may close it again at any time if the address is used for spam, abuse or in breach of the AUP. Section 5.3 of the AUP also applies, and Section 5 of the AUP applies to email you send. ### B.19 CDN Category: Edge Services (Part A, Section A.4). **B.19.1 The service.** The CDN delivers your content from CubePath's points of presence, currently in Barcelona, Amsterdam, Miami, Houston and Virginia. You create zones, add origins (a server, an external S3-compatible bucket or an Object Storage bucket of your own), configure cache, redirect and header rules, and may use the CDN firewall features, signed URLs and purges. Features, regions, plans and limits are those shown in the Control Panel and the Documentation. **B.19.2 License and content.** You grant CubePath the license in Section 10.3 of the Terms to copy, cache, store and deliver Customer Content through the CDN, in every point of presence, only to provide the Service. You are responsible for the content you serve, your right to serve it and the security of your origins, and you must not point a zone to an origin you are not authorized to use. Notices of illegal or infringing content are handled under Section 14.2 of the Terms and Section 3 of the AUP, and we may suspend or delete the zone, purge its cache or remove content. **B.19.3 Encryption and what we see.** To serve HTTPS traffic for your domain, CubePath terminates TLS at the edge. CubePath systems therefore process requests and responses in unencrypted form, including Personal Data and Credentials that your visitors send, in order to deliver the Service. Secrets you give the CDN, such as S3 credentials for an origin and the secret for signed URLs, are stored by CubePath so that the Service can work. For Personal Data of your visitors that CubePath processes to deliver the Service to you, CubePath acts as your Processor. Request logs, which may include visitor IP address, country, network, user agent and path, are kept for up to 30 days. CubePath derives aggregate counters from them for billing and operation, and, as an independent controller, uses IP addresses and request metadata of its edge network only to detect and mitigate attacks and abuse against the network and its customers, as described in the Privacy Policy. **B.19.4 Certificates and domains.** For a custom domain you must hold the right to use it and point its DNS to the CDN as the Documentation describes. Certificates are issued automatically by a third-party certificate authority (currently Let's Encrypt) and renewed about 30 days before they expire. Issuance and renewal depend on your DNS and on the authority's terms and rate limits, and we do not guarantee them. You may upload your own certificate and must renew it. A custom domain used by a zone cannot be used by another Organization, and after a zone is deleted the domain stays reserved for your Organization for 30 days. If you keep a DNS record that points to the CDN after you delete a zone, you are responsible for any use of that name by others. **B.19.5 Configuration and limits.** Configuration changes reach the points of presence in steps and are not instant. Limits on changes, purges, rules and origins apply, and some are counted for each edge server and not in total. Rules and firewall features are best effort: a rule you configure can block legitimate visitors, and no feature guarantees that a bot or attack will be stopped. **B.19.6 Fees.** The CDN is charged per hour with a base fee for each zone and by the traffic delivered, at the rates on the Pricing Page. Traffic is measured from our records at the point of presence, by region; where no rate is set for a region, the highest rate of the plan applies. Certificates, purges and origins are not charged. Requests made by the CDN to an Object Storage origin are charged as requests under Section B.9. **B.19.7 Suspension and deletion.** While your Organization is suspended for non-payment, or if we suspend a zone for a violation of the AUP, visitors see an error page ("Service Suspended") and the zone is not billed. Paying what is due restores a zone suspended for non-payment. For Section 8.1 of the Terms, a zone belongs to the class of DNS and configuration, except that it is suspended for non-payment as this Section states. Deleting a zone removes its configuration and the certificates created for it, and a deleted zone cannot be recovered. ### B.20 DNS Category: Edge Services (Part A, Section A.4). **B.20.1 The service.** The DNS service provides authoritative DNS for domains you hold. Zones and records are not charged, subject to the limits on zones, records, minimum TTL and other features shown in the Control Panel for your Organization and the zone's tier. Answers are served from CubePath's points of presence by anycast. GeoDNS and health checks are optional features of certain tiers. **B.20.2 What CubePath is not.** CubePath is not a domain registrar and does not sell domain names. You must delegate your domain to our name servers at your registrar, renew the domain there and keep the delegation correct. DNSSEC is not supported. **B.20.3 Authority over a domain.** You may create a zone only for a domain you hold or are authorized to manage. We reserve the name when you create the zone and may verify delegation or control afterwards. We may refuse, suspend or delete a zone for a domain that you do not control, that CubePath reserves, or whose holder shows a better right. To avoid giving someone else control of a name, you must change the delegation at your registrar before you delete a zone, and you must not leave a delegation to us for a zone that no longer exists. Records that point to services that you no longer use (for example a CNAME to a deleted resource) are your responsibility. **B.20.4 Your records.** You are responsible for the content of your records, including records that point to third parties (CNAME, MX, TXT, SRV) and records relevant to security, such as SPF, CAA and TLSA. Do not put secrets or Personal Data in records, which are public. CubePath manages the SOA and apex NS records. **B.20.5 Health checks and failover.** Health checks are a paid option, charged per active check at the rate on the Pricing Page for as long as they are enabled. They are not charged while your Organization is suspended. A check sends probes from our points of presence to the target you configure. You authorize those probes, and you may configure only targets you own or are authorized to probe. When a check fails, the system removes the affected answers automatically without any action by you. A misconfigured check or a blocked probe can remove answers or leave a name with none. You are responsible for the configuration and for the consequences of automatic changes. A health check is not a monitoring service and does not guarantee detection of a failure. **B.20.6 Suspension and closure.** DNS zones are not suspended when your Organization is suspended for non-payment, but we may suspend a zone for a violation of the AUP or on legal grounds. When your Organization is closed or terminated, zones and records are deleted as Sections 8.1 and 9.5 of the Terms provide for DNS and configuration. Deleting a zone also deletes its records and cannot be undone through the Control Panel. Export your records first. ### B.21 AI Gateway Category: AI Services (Part A, Section A.5). **B.21.1 The service.** The AI Gateway is an endpoint compatible with the OpenAI API format, through which you send requests, using an API token of your Organization, to models operated by third-party Model Providers. The Model Providers and models available are listed in the Control Panel and the Documentation. We may add, change, suspend or remove any model at any time, with or without notice. The AI Gateway has no SLA. **B.21.2 Model Providers and your data.** The prompts and files you send (AI Input) and the responses you receive (AI Output) are transmitted to and processed by the Model Provider of the model you choose, including an alternate provider where the Documentation says automatic failover applies. The provider processes them under its own terms, usage policies and data practices, in the locations where it operates, which may be in any country. CubePath does not control the provider's retention or use of your data. The model catalog shows the Model Provider of each model, and the Documentation states what is known about their locations. By sending a request you agree to the terms and usage policies of the provider of the model you use and must comply with them. If you cannot accept a provider's practices, do not use its models. CubePath does not store the content of your prompts or responses in its databases; it keeps only metadata about each request, such as model, tokens, cost, time and source address. **B.21.3 Output.** CubePath is a technical intermediary. It does not create, review or endorse AI Output and does not guarantee that it is accurate, complete, lawful, unbiased or free of third-party rights. AI Output may be wrong. You are responsible for your use of AI Input and AI Output, for informing the people who interact with AI Output as the law requires, and for human review when output informs decisions that have legal or similarly significant effects on a person. You must not use the AI Gateway for uses that the provider's policies or applicable law prohibit. As between you and CubePath, you own AI Output to the extent the law and the provider's terms allow it. **B.21.4 Fees.** The AI Gateway is charged by use, from your Cash Balance, per million tokens at the prices shown for each model on the Pricing Page or in the Control Panel. Prices may differ for input, cached input (cache reads and cache writes) and output, and output includes reasoning tokens. We may change the price of a model. Increases take effect for new requests after at least 30 days' notice under Section 7.7 of the Terms, except that where a Model Provider raises its own price on shorter notice we may pass the increase on from the date it applies to us, giving you as much notice as practical, and you may stop using the model at any time. A minimum Balance is required to make requests. Requests that fail because of an error of the provider are not charged. Before each request we reserve from your Cash Balance the most that the request can cost and release the unused part when it ends, so a request can be refused while other requests in progress hold your Balance. If a connection is closed before the response ends, by you or by a network failure, you pay for the input and for any output already delivered, which may be estimated. If it is closed after the Model Provider received the request but before any output is delivered, you pay the estimated input and one output token. You pay nothing only if the Model Provider did not receive the request. Where the Documentation lets you send a request with your own Model Provider key, the Model Provider charges you under your own agreement with it, we charge no token Fees for that request, and the Model Provider is not a subprocessor of CubePath for that request. Credits, including Promotional Credits, Plan Credits, Referral Credits and Service Credits, cannot be used for the AI Gateway. You are responsible for all use made with your API tokens. **B.21.5 Limits and suspension.** Rate limits and size limits apply and are shown in the Documentation. A Model Provider may restrict or suspend access, including access of CubePath as a whole, because of conduct by a customer. We may therefore restrict or suspend your access to the AI Gateway or to a model if we believe your use violates a provider's policy or the AUP, or puts the access of other customers at risk. Section 13 of the Terms and Section 8 of the AUP apply. ### B.22 Control Panel Assistant and AI-Assisted Support Category: AI Services (Part A, Section A.5). **B.22.1 Control Panel assistant.** The assistant in the Control Panel is an AI Feature that answers questions about how to use the Services, the Control Panel, the API and the CLI, and about your Organization. It is provided at no charge, and it identifies itself as an AI system. To answer, it can use read-only tools that look at data of your Organization that your role allows you to see, such as Balance, Invoices, tickets, activity, AI Gateway usage, members and the brand and last digits of a payment method. It cannot create, change, restart or delete anything for you, and it never receives passwords, tokens, full payment details, the content of abuse reports or attachments. Your questions and the data it needs are sent to our AI provider to produce the answer. Conversation history is kept for up to seven days. Usage limits apply, and we may change or suspend the assistant at any time. **B.22.2 Answers are not advice.** Answers may be incomplete or wrong, and they are not legal, financial or professional advice and not a commitment of CubePath. Check the Documentation and decide for yourself before you act. Nothing it says changes the Agreement or your Fees. **B.22.3 AI-assisted support.** CubePath staff may use AI systems to classify tickets, summarize them, search our knowledge base and draft replies, and in some categories a reply may be sent by an AI system, under rules set and monitored by staff. For this, the AI system may process the text of your ticket, the data of your Organization needed to answer it, and, only when this is needed to diagnose a problem with a Resource, an image of its console, which may contain Customer Content. The AI provider acts as our subprocessor for that Customer Content under Section 22.4 of the Terms. Staff oversee these systems, and a reply that is not sent by the AI system on its own is approved by staff before it is sent. We do not send the content of abuse reports to AI systems. You can ask in a ticket to have it handled by a person. A reply you receive from support may have been written by an AI system. ### B.23 API, CLI, MCP Server and Connected Apps Category: Developer Tools and Automation (Part A, Section A.6). **B.23.1 API tokens.** You may create API tokens for your Organization. A token acts with the permissions of the member who created it, limited by the scopes you choose and by the member's current role, and you may restrict it to a list of IP addresses. A token does not expire, so revoke tokens you do not use. Treat tokens as Credentials. We may reject a token when its creator is no longer an active member or is suspended, when the Organization is closed, or when we believe it is compromised. Some actions, such as accepting updated terms, can only be done by a person signed in to the Control Panel and cannot be done with a token. **B.23.2 Everything done with a token is yours.** Section A.6.2 applies to everything done with your Credentials. API requests are subject to rate limits. Do not use the API to evade limits or to collect data in bulk. **B.23.3 CLI, Terraform provider and Agent Skills.** cubecli, the Terraform provider, the Agent Skills and other tools that CubePath publishes (for example on GitHub) are provided as is and without a commitment of support, availability or compatibility. Each repository's open source license governs its code. The CLI stores your Credentials on your computer, and you must protect them. Agent Skills are written instructions for AI agents, and the agent executes them with your Credentials; an agent that follows them can spend money and delete Resources. **B.23.4 CubePath MCP Server.** The MCP Server lets an AI client act on the Services with the permissions of the user who authorizes it, for one Organization. It accepts tokens and not browser sessions. Access tokens issued through OAuth are short-lived. We may set the server to read-only or turn it off at any time, for example during an incident. You are responsible for the AI clients and agents you authorize, for the instructions you give them, and for everything they do, including destructive actions and Fees. An AI agent can be misled by content it reads, and it can make mistakes. Grant the narrowest scopes that work and revoke access you no longer need. A revoked grant stops working at the next request, and closing your Organization revokes its grants. **B.23.5 Connected apps.** An application can ask you to connect to your Organization using OAuth. Apps registered dynamically are not verified by CubePath, and whoever registers them writes their name and description. Check what you authorize. ### B.24 Cloud Alerts, Notifications and Event Delivery Category: Developer Tools and Automation (Part A, Section A.6). **B.24.1 Cloud Alerts.** Cloud Alerts evaluate rules that you define on metrics of your Resources, about every 30 seconds, and send notifications to the channels you choose. They are an aid and not a monitoring guarantee: an alert may be late, may not be sent, or may be sent when there is no problem, because of the latency of metrics, the state of the platform or the channel. You remain responsible for monitoring the Resources that matter to you. Limits depend on your Commercial Plan. **B.24.2 Automated actions.** If you configure an alert to take an action on a Resource, such as creating or deleting a server, you authorize CubePath to carry out the action when the alert triggers. You are responsible for the rule, the consequences of the action and the Fees it creates. Actions may be delayed, repeated or fail. **B.24.3 Notification channels.** Channels may include email, Slack, Discord and other channels shown in the Control Panel. For webhook channels you give a URL that you control or are authorized to use, and the notifications, which can include names and identifiers of your Resources, are sent to that third-party service under its terms. Email notifications go to the address of the user who created the channel. Delivery is on a best-effort basis, with no guarantee of time or of delivery. We may refuse destinations that point to internal or private addresses. **B.24.4 Bucket event notifications.** If you enable event notifications for an Object Storage bucket (Section B.9), CubePath sends a message to the endpoint you configure for each matching event. Delivery is at least once and not ordered. If your endpoint does not accept a message, we may retry for a limited time and may then discard it. Each event delivered is charged at the rate on the Pricing Page. Section A.6.4 applies. **B.24.5 Budget alerts.** A budget is an amount that you set for the spend of your Organization, or of some of its projects or Services, in a calendar month (UTC). When the measured or forecast spend reaches it, we send an email to the billing contacts of your Organization. A budget is a notice only. It never stops, suspends or limits a Service, and it is not a spending cap. The figures are evaluated about every 15 minutes and can lag behind your actual use, and an alert may be late or not sent. You owe the Fees whether or not an alert was sent. Section A.6.4 applies. ### B.25 Commercial Plans Category: none. Commercial Plans are not part of a Service Category in Part A, so the Terms and this Section apply directly. Section 0.2 of these Service Terms does not apply to this Service. **B.25.1 Plans.** CubePath offers plans for an Organization, currently Free, Pro, Business and Enterprise, as described on the Pricing Page and in the Control Panel. Pro and Business can be bought in the Control Panel. Enterprise, and any plan that staff sell under a contract, are governed by the Order Form. A plan sets entitlements, which are limits and features of other Services (for example alerts, notification channels, DDoS rules and prefix lists, BGP peers per network, availability groups, members and single sign-on), and may include a monthly Plan Credit and a support level. The entitlements are those shown in the Control Panel. If we start to enforce an entitlement that we did not enforce before, we give you at least 30 days' notice. **B.25.2 Prices and billing.** Plan prices are in US dollars, whatever the currency of your Organization, and exclude taxes, which we add where the law requires. A plan is billed in advance for the term you choose (monthly or a longer term with the discount shown at purchase) by a recurring Invoice. The price of a term is fixed when you buy or renew it. A plan activates when payment is confirmed. For a move to a higher plan during a term, we may invoice the difference for the rest of the term. **B.25.3 Renewal.** A plan renews automatically for the same term at the price in force at that time, unless you cancel before the renewal date. By buying a plan you agree to automatic renewal at the time of purchase, and we keep a record of your consent. We show the price and renewal terms before you buy, we give notice of a price increase under Section 7.7 of the Terms, and where the law requires a renewal reminder we send it by email to the Owners and Admins of the Organization within the period the law requires. For monthly terms we send the Invoice before it is due. Where automatic payment is on, the renewal Invoice is charged to your default payment method five days before it is due, and otherwise you must pay it by the due date. If you cancel after that charge but before the renewal date, we refund the charge in full. You can turn off automatic payment in the Control Panel. You can cancel in the Control Panel in the same way you bought the plan, without having to contact support, and you may also cancel through support. **B.25.4 Cancellation and downgrade.** You can cancel or downgrade at any time in the Control Panel or through support. The change takes effect at the end of the paid term, and until then you keep the plan. We do not refund any part of a paid term, including after a downgrade or a cancellation, except where the law requires it, or where your Order Form says so. This does not apply to a renewal charge made after you had cancelled, or that you did not authorize, which we refund. When a plan ends, the entitlements fall to those of the plan you move to. Resources and data are not deleted only because a plan ended, but you may not add configuration above the new limits. If your current configuration exceeds them, we may require you to bring it within the new limits and may disable the excess after notice. **B.25.5 Plan Credits.** A monthly Plan Credit is a Credit. It is added to your Balance each month while the plan is active, expires on the first day of the next month if you do not use it, has no cash value and is not refundable. It cannot be used for the AI Gateway, and it may not be usable for other Services, as the Control Panel shows. Section 7.8 of the Terms applies. **B.25.6 Unpaid plans.** If a plan Invoice is not paid within 14 days after its due date, your Organization returns to the Free plan. If it is still not paid 30 days after that, the subscription is cancelled. An order for a plan that is not paid within 7 days expires. An unpaid plan Invoice by itself never suspends your other Services, but other unpaid amounts may, under Section 8.1 of the Terms. **B.25.7 Changes to plans.** We may change, rename, withdraw or add plans and entitlements. A change applies to you at the next renewal, with notice under Section 7.7 of the Terms, unless it benefits you or the law or security requires an earlier date. Exceptions that staff grant to one Organization create no right for others. Plans do not change the SLA. ### B.26 Support Services Category: none. Support Services are not part of a Service Category in Part A, so the Terms and this Section apply directly. Section 0.2 of these Service Terms does not apply to this Service. **B.26.1 Channels and languages.** Support is provided in English and Spanish through tickets in the Control Panel and by email to [support@cubepath.com](mailto:support@cubepath.com) . Support is available by ticket; response times are not guaranteed unless an Order Form states them. Any target shown in the Control Panel, and any support level that your Commercial Plan includes, is an objective and not a guarantee. **B.26.2 What we support.** We support the Services and what CubePath operates: the platform and the Control Panel, the network, IP addresses and reverse DNS, hardware, out-of-band management, rescue mode, snapshots and backups, DNS, load balancers, Object Storage, billing, and the managed layer of managed Services (for example the control plane of Managed Kubernetes and the engine of Managed Databases). We do not provide system administration inside your Resources. We do not support your operating system, software, configuration, data, content, workloads or Marketplace Applications and other Third-Party Offerings, or help you to recover from your own mistakes in them, although we may give general guidance. Support is for the Organization and its Authorized Users. We do not support your End Users or the customers of a reseller, except as a partner agreement says under Section B.28. **B.26.3 Reinstalling and other work.** Reinstalling an operating system is self-service and not charged, subject to rate limits. We do not support or license operating systems that are not offered in the Control Panel. If we agree to do manual work that is not part of the Services, we tell you the fee before we do it and do it only if you accept. **B.26.4 Urgent tickets.** You may open a ticket with urgent priority if your role has the permission to make payments. The fee shown in the Control Panel when you submit the ticket is charged to the default card of your Organization and not to the Balance. The fee pays for priority handling by on-call staff, who are alerted when the ticket is created. It does not guarantee a response time or a solution. If the ticket cannot be created after the fee has been charged, we refund the fee. Your Commercial Plan may include a number of urgent tickets each month. We may lower the priority of a ticket that is not an urgent incident, but if we do so before on-call staff have handled it, we refund the fee. By submitting an urgent ticket you authorize this one-time charge to the default card of your Organization, in the amount shown before you submit. **B.26.5 Identity and security.** We may ask you to confirm your identity before acting on a request about your Account or Organization. After an email change or two-factor recovery, some actions are blocked for a period. Do not send passwords, tokens or private keys in a ticket. If a ticket needs access to a Resource, the access is under Section 6 of the Terms and the ticket is your instruction to do it. Tickets about abuse or security are opened by CubePath. **B.26.6 Closing tickets and hours.** A ticket we have answered may be closed after 48 hours without a reply; a new reply or a new ticket reopens the issue. Tickets can be submitted at any time. We do not promise that a ticket is answered at once or outside business hours. Support for Beta Services is best effort. ### B.27 Promotions, Credits, Referral and Affiliate Program Category: Programs and Promotions (Part A, Section A.8). **B.27.1 Promotion codes and Promotional Credits.** A promotion code, coupon, bonus, free credit or event grant gives Promotional Credits to your Organization. Each code has its own conditions, shown with the offer, such as eligible new customers only, a redemption period or limit, a minimum deposit, eligible Services, an expiry date, or an exemption from a verification deposit with additional checks. A code can be redeemed once per person, device and Organization, and we may check this with fraud-screening and device-identification services, as described in the Privacy Policy. Promotional Credits expire on the date fixed when they are granted. We usually warn you before, but do not have to. They have no cash value, are not refundable or transferable, and may not be usable for the AI Gateway or other Services. They are applied in the order shown in the Control Panel. **B.27.2 Loss of Credits.** Credits are lost when they expire or when your Organization is closed. If a payment that was linked to a promotion is refunded or charged back, or if it falls below the minimum deposit of the code, we remove the Credits that were granted because of it, up to the amount of that payment. If we find that Credits were obtained by abuse, by creating several Accounts or Organizations, or by a mistake in granting, we may remove them, Suspend the Organization under Section 8.2 of the Terms, and refuse further promotions. **B.27.3 Referral Credits.** If your Organization takes part in the referral offer, the Organization you refer may receive Referral Credits when the conditions of the offer are met, and the offer states whether you also receive anything. The amount, conditions and expiry are shown with the offer. Referring yourself or an Organization you control does not qualify. **B.27.4 Service Credits.** Service Credits are given under the SLA and are governed by it. **B.27.5 Affiliate Program: eligibility.** An Owner or Admin of an Organization that is verified and not suspended may apply to the Affiliate Program. We may accept or refuse any application and end a participant's status at any time. An Organization whose verification deposit was waived needs at least one real payment before it can take part. This Section and the program page are the terms of the Affiliate Program. They form part of the Agreement for the Organization that takes part. If the program page conflicts with this Section, this Section prevails. The affiliate is an independent party, is not CubePath's agent, employee or partner, and receives no personal data of the Organizations it refers. **B.27.6 Commissions.** The affiliate earns a commission, at the percentage shown on the program page, on amounts actually received by CubePath from the Organizations it referred, for the first year after each referred Organization's first payment. No commission is paid on Invoices for Commercial Plans only, on amounts refunded or charged back, on amounts paid with Credits, or on taxes. We may reverse or withhold commissions for refunds, chargebacks, fraud or violation of these terms, including by deducting them from later commissions. Commissions are paid on request, by the methods shown on the program page and above the minimum shown there, after we review the request. The affiliate is responsible for its taxes, and we may ask for tax forms and withhold amounts the law requires. We may change the commission percentage, the minimum payout or the program page prospectively on 30 days' notice. If the affiliate's participation ends, we pay commissions already earned and not reversed or withheld under this Section within the period shown on the program page. **B.27.7 Conduct.** Affiliates must follow the AUP and this Section. They must not refer themselves or an Organization they control, offer sign-up incentives we have not approved, send spam, use misleading advertising, make claims about the Services that we have not made, or use CubePath's marks beyond what we allow. They must clearly disclose their relationship with CubePath when they promote the Services, as advertising law (including the FTC Endorsement Guides) requires, and comply with the law on tracking links and cookies. A referred customer is a customer of CubePath, and the affiliate cannot bind CubePath. We may suspend an affiliate and withhold unpaid commissions where we suspect abuse. ### B.28 Partner and Reseller Programs Category: Programs and Promotions (Part A, Section A.8). **B.28.1 Written agreement needed.** CubePath has programs for partners: publishers of applications for the Marketplace (the Marketplace Partner Program) and companies that resell or white-label CubePath Services (the Partner Program). An application form creates no right or obligation. A partner is accepted only by a separate written agreement signed by CubePath, which may set discounts, branding, support, revenue share and other terms. We may refuse any application. **B.28.2 Using the Services for your own customers.** You may use the Services to run your own business and to serve your own customers, for example as an agency or hosting company, without a partner agreement. You remain fully responsible for your customers and End Users. You must bind them to terms no less protective than the AUP, you must act promptly on abuse complaints about them, and CubePath has no obligation to them. You may include Resources in a hosting, managed or application service that you provide, in which you administer the Resources. You may not resell or sublicense bare access to the Resources, or offer them as an infrastructure product under your own or another brand (for example by giving customers their own Control Panel access, API tokens or administrative control of a Resource), without a partner agreement. If your customers' personal data is processed on the Services, Section 12.2 of the Terms applies between you and CubePath, and you are responsible for your own agreements with your customers. **B.28.3 Marketplace publishers.** A publisher is responsible for its software, its license and its support. Applications it publishes are Third-Party Offerings under Section B.6\. CubePath may package or help package the application, may decline, change or remove it, and gives no warranty on it. Unless the agreement says so, there is no revenue share. **B.28.4 Resellers.** A reseller's customers are the reseller's End Users. The reseller is the point of contact for them, pays the Fees under the agreement and is responsible for what they do on the Services. Support under Section B.26.2 is given to the reseller. Where the partner agreement says that CubePath may give support to the reseller's customers or may show a partner's brand, those terms apply to that extent only. We may suspend a Resource of an End User of a reseller under the AUP, and we tell the reseller when we do. A reseller that brings its own IP space or AS number follows Section B.16. **B.28.5 Conflicts.** The partner agreement overrides these Service Terms only where it says so expressly. Where it is silent, the Agreement applies. ### B.29 Free Tools and Status Page Category: Network and Security Services (Part A, Section A.3) for the network tools and Edge Services (Part A, Section A.4) for the status page. **B.29.1 Free tools.** Looking Glass, the latency and network pages and other free public tools and pages that CubePath offers are provided at no charge, as is, with no warranty and with no commitment of availability, accuracy or support. They show what is seen from CubePath's own equipment and are not a measurement of your Service. Rate limits apply. Do not use them to scan or attack third parties, reflect traffic or load our systems, and we may block any use we consider abusive. We may change or remove them at any time. **B.29.2 Status page.** Our status page shows incidents and maintenance that CubePath staff publish. The uptime bars are calculated from the incidents and maintenance published and not from probes of the Services. The status page may be late or incomplete, and it is not a commitment of CubePath, and not the measurement used for the SLA (Section 7 of the SLA). **B.29.3 Maintenance notices.** We announce scheduled maintenance on the status page. Where the Control Panel supports it for the Service and location concerned, we also send an email to the Owners and Admins of the Organizations affected, normally from [maintenance@cubepath.com](mailto:maintenance@cubepath.com) . An email is a courtesy and is not sent for every Service or location; the notice on the status page is the notice that counts for the SLA, with at least the advance period stated there. Emergency maintenance may be announced during or after it. ## Schedule 2\. Service Level Agreement ## 1\. Scope ### 1.1 What this Schedule is This Service Level Agreement ("SLA") is Schedule 2 to the Terms and part of the Agreement between CubePath Inc. and you, as described in Section 2 of the Terms. It sets out the availability commitments we make for certain Services, the Service Credits you may receive if we miss them, and how to claim those credits. Capitalized terms not defined here have the meanings in the Terms. ### 1.2 Only listed Services have an SLA This SLA applies only to the Services listed in the table in Section 3 (the "Covered Services"). Every other Service has no uptime commitment and no Service Credit under this SLA, even if it is related to a Covered Service or is sold in the same order. Section 3.3 lists the main Services that have no SLA. If a Service is not listed in Section 3, it has no SLA, unless an Order Form states otherwise. ### 1.3 Additions and Order Forms We may add a Service to Section 3 at any time. An addition takes effect on publication and applies only to the added Service. It is not a Material Change (see Section 10.2). An Order Form may give you a different commitment or different credits for the Services it covers. An Order Form overrides this SLA only for what it expressly says. ### 1.4 Who may claim Service Credits are available to the Organization that pays for the affected Resource, as long as it is in good standing (see Section 8.4). ## 2\. Definitions - **Monthly Charges**: for a Resource, the Fees accrued for that Resource in the calendar month in which the Downtime occurred. For Resources billed hourly, this is the sum of the hourly charges for the month. For Resources billed by recurring invoice, it is the recurring Fees for the month. For Resources billed for a period longer than a month, the Monthly Charges are the Fees for that period divided by the number of months in it. Fees included in a Commercial Plan with no separate charge for the Resource are not Monthly Charges. For Managed Kubernetes, the Resource is the cluster's control plane and its Monthly Charges are the Fees accrued in the month for that control plane. Worker nodes are separate Cloud VPS Resources with their own Monthly Charges. For Object Storage, the Resource is the bucket and its Monthly Charges include storage, request and data transfer-out charges for that bucket. For DNS, the Resource is the Organization's DNS service and its Monthly Charges are the Fees accrued in the month for its DNS health checks. If the Monthly Charges of a Resource are zero, no Service Credit is due for it. Monthly Charges exclude Taxes, one-time charges, bandwidth or transfer overage (other than the Object Storage data transfer-out charges stated above), and any amount paid with Service Credits. - **Downtime**: a period of time in which a Covered Service does not meet the availability test in the "What is measured" column of the table in Section 3, as determined under Section 7\. Downtime does not include the periods excluded by Section 6. - **Monthly Uptime Percentage**: for a Resource and a calendar month, the total number of minutes in the month, minus the minutes of Downtime, divided by the total number of minutes in the month, expressed as a percentage. For Object Storage, Downtime is counted in 5-minute intervals as set out in Section 3.1, and the formula above applies to that Downtime. - **Confirmed Hardware Failure**: a fault in a component of a dedicated server (for example a disk, memory module, motherboard, power supply or CPU) that CubePath has confirmed by a BMC alert, by diagnostics, or by hardware tests run in rescue mode. The failure is confirmed at the earliest time one of these confirms it. A suspected fault that is not confirmed is not a Confirmed Hardware Failure. - **Scheduled Maintenance**: maintenance that we announce at least five (5) days in advance by publication on our status page. We may also send an email to the Owners and Admins of the affected Organizations, but the notice on the status page is the notice that counts. Recurring maintenance windows that we publish in the Documentation of a Service (for example the weekly engine update window of Managed Databases) are Scheduled Maintenance, with the notice given by that publication. - **Emergency Maintenance**: maintenance that we cannot announce five (5) days in advance because it is needed to respond to an Emergency, or to remediate a security vulnerability that is publicly disclosed or actively exploited and that affects the Services. Maintenance to repair a failure of our own equipment or software is not Emergency Maintenance. We publish a notice on our status page as soon as practicable. - **Service Credit**: a Credit that we add to your Balance under this SLA, as described in Section 4. - **Resource**: as defined in the Terms. For the availability group commitment in Section 3, the "Resource" is the availability group, and its Monthly Charges are the combined Monthly Charges of the instances in the group. - **Location**: a data center location in which a Resource runs, as shown in the Control Panel. ## 3\. Service Commitments ### 3.1 Commitments table Percentages are Monthly Uptime Percentages, measured per Resource per calendar month. The credit tiers are percentages of the Monthly Charges of the affected Resource. "Below" means lower than the stated percentage. | Service | What is measured | Commitment | Credit tiers | | ------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------- | | Cloud VPS, single instance (including the Floating IP and the public network of the VPS) | The VPS is not running because of a failure of the hypervisor, the node, the power or the network of CubePath, or has no network connectivity from CubePath's network to the VPS's public network interface because of such a failure. | 99.9% | Below 99.9%: 10%. Below 99.0%: 25%. Below 95.0%: 100%. | | Cloud VPS in an availability group (two or more instances, spread placement, same Location) | Measured for the group. The group is available if at least one instance in it meets the availability test for a single VPS. | 99.99% | Below 99.99%: 10%. Below 99.9%: 25%. Below 99.0%: 50%. Below 95.0%: 100%. | | Dedicated Servers: power and network | The server has no power, or no network connectivity between its switch port and CubePath's network, because of a failure of CubePath's power or network equipment. Failure of the server's own components is not Downtime; Section 5 governs it. | 99.99% | Below 99.99%: 10%. Below 99.9%: 25%. Below 99.0%: 50%. Below 95.0%: 100%. | | Dedicated Servers: hardware replacement | Time from a Confirmed Hardware Failure until the failed component is replaced. | Replacement within 24 hours | 5% of the server's Monthly Charges for each additional full 4 hours, up to 100%. See Section 5. | | Managed Databases, high-availability configuration | The database cluster has no primary node that accepts connections on its endpoint because of a failure of CubePath's infrastructure or of the Managed Database platform (including the database engine as installed by CubePath, but not queries, schemas, extensions or workloads you run). | 99.95% | Below 99.95%: 10%. Below 99.9%: 25%. Below 99.0%: 50%. Below 95.0%: 100%. | | Managed Databases, single node | The node does not accept connections on its endpoint because of a failure of CubePath's infrastructure or of the Managed Database platform (including the database engine as installed by CubePath, but not queries, schemas, extensions or workloads you run). | 99.9% | Below 99.9%: 10%. Below 99.0%: 25%. Below 95.0%: 100%. | | Managed Kubernetes, highly available control plane | The Kubernetes API endpoint of the cluster does not respond to valid requests because of a failure of the control plane that CubePath operates. | 99.95% | Below 99.95%: 10%. Below 99.9%: 25%. Below 99.0%: 50%. Below 95.0%: 100%. | | Managed Kubernetes, standard control plane | Same test as above. | 99.5% | Below 99.5%: 10%. Below 99.0%: 25%. Below 95.0%: 50%. | | Object Storage | The error rate of valid requests to the S3-compatible API, measured in 5-minute intervals. The error rate is the number of valid requests that fail with a server-side error (HTTP 5xx) divided by the number of valid requests in the interval. An interval in which the error rate is higher than the threshold we state in the Documentation for Object Storage counts as five (5) minutes of Downtime. That threshold is part of this SLA, and a change that makes an interval less likely to count as Downtime is a change under Section 10.1\. A valid request is an authenticated, well-formed request to an existing bucket that is within your quotas and rate limits. 5xx responses caused by exceeding a rate limit (including SlowDown) are not counted. | 99.9% | Below 99.9%: 10%. Below 99.0%: 25%. Below 95.0%: 100%. | | Load Balancers | The Load Balancer does not accept connections on a configured listener, or does not forward them to a healthy target, because of a failure of the Load Balancer. | 99.95% | Below 99.95%: 10%. Below 99.9%: 25%. Below 99.0%: 50%. Below 95.0%: 100%. | | NAT Gateways | The NAT Gateway does not pass outbound traffic from the private network because of a failure of the NAT Gateway. | 99.9% | Below 99.9%: 10%. Below 99.0%: 25%. Below 95.0%: 100%. | | DNS (authoritative resolution) | Our authoritative name servers fail to answer valid queries for a zone hosted with us. | 99.99% | Below 99.99%: 10%. Below 99.9%: 25%. Below 99.0%: 50%. Below 95.0%: 100%. | | CDN | The CDN fails to serve valid requests for a configured zone because of a failure of the CDN. Errors returned by your origin are not Downtime. | 99.9% | Below 99.9%: 10%. Below 99.0%: 25%. Below 95.0%: 100%. | | Cloud Gateway | Only as set out in an Order Form. | Per Order Form | Per Order Form | | IP Transit | Only as set out in an Order Form. | Per Order Form | Per Order Form | ### 3.2 Notes on the table 1. Managed Kubernetes worker nodes are Cloud VPS. They follow the Cloud VPS commitment, not the control plane commitment. 2. Floating IP addresses and the public network of a Cloud VPS are covered as part of the Cloud VPS commitment. They have no separate commitment. 3. The 99.99% availability group commitment applies only to instances that are members of an availability group with spread placement, in the same Location, at the time of the Downtime. It does not apply to an instance outside a group. The single instance commitment applies to each such instance. 4. A Cloud Gateway or IP Transit commitment under an Order Form covers CubePath's equipment and ports up to the demarcation point with the third party. Third-party networks, carriers, exchanges and cloud provider services are excluded. 5. The commitments for Managed Databases and Load Balancers are measured per Resource. A Resource that is deleted or stopped by you is not measured while it is stopped or deleted. 6. A commitment gives a Service Credit only where Monthly Charges exist under Section 2\. The DNS and standard control plane commitments give a Service Credit only to the extent the Resource has Monthly Charges. ### 3.3 Services with no SLA The following have no SLA and give no right to Service Credits: - Beta Services. - Free Services and free tiers. - AI Features, including the AI Gateway, the Control Panel assistant and AI-assisted support. - Availability of the Control Panel, the API, the CLI and the MCP Server. The exception is an outage of them that is caused by, and is part of, an outage of a Covered Service, which then counts only as Downtime of that Covered Service. - The Video Transcoder. - Marketplace applications, and other Third-Party Offerings. - The effectiveness of DDoS Protection. Protection is a feature, not an availability commitment. - Services, Resources or Organizations under Suspension. - Backups, snapshots, Private Networks, Firewall Groups, BGP sessions, BYOIP, Tunnels, the status page, Looking Glass and other network tools, Cloud Alerts and notification delivery, and bucket event notifications. - cPanel & WHM and the services, websites and email that run on a cPanel server, unless an Order Form adds a service level. The Cloud VPS or Dedicated Server on which it runs is covered as stated in this SLA for a Cloud VPS or a Dedicated Server. - Any Service not listed in Section 3.1. ## 4\. Service Credits ### 4.1 When credits start A credit is due as soon as the Monthly Uptime Percentage of a Resource falls below the commitment for that Resource in Section 3.1\. There is no grace period. The credit is the percentage of the Monthly Charges shown for the tier that applies. Where more than one tier applies, the credit is the highest of those percentages, and they do not add up. ### 4.2 No stacking and caps 1. Credits are measured per Resource. For one Resource and one calendar month, you receive only the single highest credit that applies under this SLA, even if the same Downtime breaches more than one commitment or more than one tier. 2. For an instance that is a member of an availability group, a credit under the group commitment and a credit under the single instance commitment for the same Downtime do not add up: you receive the higher one. 3. The total of all Service Credits for one Resource in one calendar month, from every section of this SLA, including Section 5, is capped at 100% of the Monthly Charges of that Resource. 4. The total of all Service Credits for one Organization in one calendar month is capped at the Fees you paid or owe for that month. ### 4.3 How credits are given We add an approved Service Credit to your Balance within thirty (30) days after we approve it. Service Credits: - are Credits as defined in the Terms, and Section 7.8 of the Terms applies to them; - have no cash value, are not refundable and are not transferable; - expire twelve (12) months after we add them; - may be used only toward Fees for CubePath Services, and are not applied to AI Gateway usage; - are not applied automatically. You must claim them under Section 8; and - when the Agreement ends, unused Service Credits are applied to any Fees you still owe, and the rest expire. ### 4.4 Credits for several months Each calendar month is measured on its own. Downtime in one month does not carry over to the next month. ## 5\. Dedicated Server Hardware Replacement ### 5.1 Commitment If a dedicated server has a Confirmed Hardware Failure, we will replace the failed component within twenty-four (24) hours. The period starts when the failure is confirmed. It ends when the failed component is replaced with an equivalent component, or the server is replaced with equivalent hardware. ### 5.2 What replacement means Replacement means that the faulty hardware is replaced. It does not mean that the operating system, software, configuration or data are restored. If a failed component held your data, such as a disk, you are responsible for reinstalling and restoring from your own backups. Hardware replacement does not include repairs to software, firmware you have changed, or the operating system. ### 5.3 Credit If we replace the failed component after more than 24 hours, you receive a Service Credit of 5% of the server's Monthly Charges for each additional full four (4) hours beyond the 24 hours, up to 100%. A partial period of fewer than four hours earns no credit. Section 4.2 applies: for the same server and month you receive only the highest single credit. For this Section 5, the Monthly Charges are those of the calendar month in which the failure was confirmed, and Sections 8 and 10.3 apply as if the delay were Downtime that occurred in that month. Time during which the replacement is delayed by a cause listed in items 3, 5 or 7 of Section 6 does not count toward the 24 hours or toward the additional hours. ### 5.4 How a failure is confirmed If you think a component has failed, open a ticket and include the results of any diagnostic test you ran, including a hardware test in rescue mode where it is available. If your report includes the result of a diagnostic test that identifies the failed component, the failure is confirmed when we receive the report, unless we show that the result is inaccurate. If your report does not include such a result, we will review it without undue delay and, where we need more information or access, tell you what we need. We will tell you when we have confirmed the failure and the time we recorded. We may confirm a failure earlier from our own monitoring. ### 5.5 Not covered This Section does not apply to: - a fault caused by you, including unauthorized firmware flashing, power or BIOS changes, overclocking or physical damage; - a fault in a component you added or supplied; - time that we cannot replace the component because we need access, a decision or an action from you; and - failures in power or network equipment of CubePath, which are governed by Section 3.1. ## 6\. Exclusions Downtime does not include, and no Service Credit is due for, unavailability to the extent it is caused by any of the following: 1. **Scheduled Maintenance.** There is no fixed monthly hour limit for Scheduled Maintenance. We will try to keep it short and to avoid your Resources where we can. If we announce maintenance on our status page as scheduled but it runs materially longer than announced, the time beyond the announced window counts as Downtime. 2. **Emergency Maintenance**, up to sixty (60) minutes per month for each affected Resource. Emergency Maintenance beyond sixty (60) minutes in a calendar month counts as Downtime for the minutes above the limit. The sixty (60) minutes are counted per calendar month and are not carried over. 3. **Your causes**: your actions or omissions (including resizing, reinstalling, rebooting, migrations you ask for and rescue mode), your configuration, software, applications, content, scripts, automations, API tokens, firewall rules, BGP configuration or routes, resource exhaustion, rate limits, quotas or limits you exceed, security incidents originating from your Resources, and your breach of the AUP or of Section 5 of the Terms. 4. **Denial-of-service attacks** against your Resources, and null-routing or rate-limiting we apply to protect our network. This exclusion applies only to the extent an attack exceeds the DDoS Protection included in or purchased for the Resource, and the Service Terms, Section B.15, apply. 5. **Force majeure**, as defined in Section 22.3 of the Terms. 6. **Third parties outside our control**, meaning failures of the public Internet, of networks and carriers beyond the edge of the network we operate, of DNS resolvers, of certificate authorities, of your own upstream providers, and of the networks and services of cloud providers. This exclusion does not apply to subcontractors, upstream transit providers, internet exchanges, data center and power providers that we choose and use to deliver the Covered Service. 7. **Suspension** of the Resource, the Organization or the Service under Section 8 of the Terms. 8. **Beta Services** and the Services in Section 3.3. 9. **Your software and Third-Party Offerings** running on your Resources, including operating systems, applications and licenses. 10. **New Resources and promotional use**: unavailability of a Resource during the seven (7) days after it was created, and unavailability of a Resource whose Monthly Charges for that month were paid only with Promotional Credits. 11. **Loss of data or content**, including data in backups, snapshots and buckets. This SLA measures availability. It is not a promise about data. ## 7\. Measurement ### 7.1 How we determine Downtime We determine Downtime from our own telemetry. This includes hypervisor and node status, network monitoring, and the incident records we publish on our status page. We also consider in good faith any evidence you send with a claim, such as logs, monitoring records or screenshots with times. Where our telemetry has no record for a period in which our status page shows an incident that affected the Resource, we treat the period of the incident as Downtime. ### 7.2 What we tell you On request, we will give you the start and end times we used to calculate Downtime for the Resources in your claim. ### 7.3 Time Times are measured in minutes, using UTC. A month is the calendar month in UTC. For a Resource that existed for only part of the month, the Monthly Uptime Percentage is measured over the time it existed. ### 7.4 Limits of the data Our telemetry shows the state of our infrastructure. It does not test every Resource from every network. We do not promise measurement from multiple locations. ### 7.5 Disagreement If you disagree with our decision on a claim, you may ask for a review by writing to [legal@cubepath.com](mailto:legal@cubepath.com) within thirty (30) days after the decision, with your evidence. We will review it in good faith and answer in writing within thirty (30) days. Our decision does not limit your rights under Section 21 of the Terms or Applicable Law. ## 8\. How to Claim ### 8.1 Deadline and channel To claim a Service Credit, open a support ticket in the Control Panel or write to [support@cubepath.com](mailto:support@cubepath.com) . Your claim must reach us within thirty (30) days after the end of the calendar month in which the Downtime occurred. We do not consider claims made after that period. This deadline does not limit rights that Consumers have under Applicable Law. ### 8.2 What to include Include: 1. the Organization; 2. the identifiers of the affected Resources; 3. the approximate dates and times of the Downtime; and 4. a short description of what happened. You do not have to measure the duration. We determine it under Section 7\. Evidence you can provide helps, but it is not required. ### 8.3 Our answer We review each complete claim and tell you our decision within thirty (30) days after we receive it. If we approve it, we add the Service Credit to your Balance under Section 4.3. ### 8.4 Good standing You are in good standing if, when the Downtime occurred, your Organization was not under Suspension for non-payment or for a breach of the AUP or the Terms. If an Invoice is overdue when we approve a claim, we apply the Service Credit to the amount you owe. We do not withhold a credit for a Suspension that began after the Downtime, except for a Suspension for fraud. ## 9\. Sole Remedy and Limits ### 9.1 Sole and exclusive remedy Service Credits are your sole and exclusive remedy, and our sole and exclusive liability, for any failure of a Covered Service to meet a commitment in this SLA, including any Downtime or failure to replace hardware in time. This does not limit (a) your right to end the affected Service, including under Section 9.5, (b) liability for fraud, willful misconduct, gross negligence, or any other liability that cannot be limited by Applicable Law, or (c) any claim for a matter other than failure to meet a commitment in this SLA. ### 9.2 Relation to the limitation of liability Service Credits count toward, and do not increase, the limit of liability in Section 16 of the Terms. ### 9.3 No other warranty This SLA is not a warranty that any Service will be uninterrupted or error-free. Section 15 of the Terms applies. This SLA and any Order Form state all of our availability commitments. A statement about availability on our website, in marketing material, in a quote, or by sales or support staff, does not create any other commitment. ### 9.4 Consumers Nothing in this SLA limits the mandatory rights of Consumers under Applicable Law (see Section 20 of the Terms). ### 9.5 Repeated failure If the Monthly Uptime Percentage of a Resource is below its commitment in three (3) calendar months of any six (6) consecutive months, or below 95.0% in any month, you may end that Service by written notice within thirty (30) days after the last such month, and we will refund the unused prepaid Fees for it. This is in addition to Service Credits. ## 10\. Changes ### 10.1 Changes to existing commitments We may change this SLA. Section 19 of the Terms governs changes. A change that reduces the commitments or credits for a Service you already use is a Material Change, and we give you the notice and the right to end the Service that Section 19 of the Terms provides. ### 10.2 Additions We may add a Service to Section 3 at any time. An addition takes effect on publication and applies only to the Service it adds. It is not a Material Change and does not need your acceptance. An addition adds a Service that was not in Section 3.1 and gives you the commitment shown for it. Any change to a row that is already in Section 3.1 is a change under Section 10.1. ### 10.3 Version in force The version of this SLA that governs a claim is the version that applied to the affected Resource under Section 19 of the Terms at the time of the Downtime or, for Section 5, at the time the failure was confirmed. ### 10.4 Contact Questions about this SLA: [support@cubepath.com](mailto:support@cubepath.com) . Legal notices: [legal@cubepath.com](mailto:legal@cubepath.com) . ## Schedule 3\. Acceptable Use Policy ## 1\. Scope and Principles ### 1.1 What this policy covers This Acceptable Use Policy ("AUP") is Schedule 3 to the Terms and part of the Agreement between you and CubePath Inc. ("CubePath", "we", "us"). Capitalized terms not defined here have the meanings in the Terms. The AUP applies to every Service, including Services that are launched after this version is published, and to Beta Services and free Services. It applies to you, your Authorized Users and your End Users. You are responsible for anyone else who uses your Organization, your Credentials or your Resources, as Section 1.3 states. ### 1.2 Principles CubePath runs shared infrastructure and a public network. One abusive Resource can affect other customers, our network and our upstream providers. This AUP lists what you may not do, how we handle reports, and what we do when a rule is broken. The lists are examples, not a complete catalog: a use that is not listed but is unlawful, harms others or threatens the Services is also a violation. ### 1.3 Your responsibility You are responsible for everything done with your Organization and its Resources, including by your End Users, by automated tools, by API tokens, OAuth clients, MCP clients and AI agents you authorize, and by anyone who gains access because you did not secure your Credentials or your Resources. A compromised Resource is still your responsibility, although we take compromise into account when we choose how to respond (Section 11). You are not responsible under this Section for access that results from our breach of the Agreement or from a security failure of the Services that you could not reasonably have prevented. ### 1.4 Unlimited and unmetered Where a Service Page or the Control Panel describes bandwidth or another resource as unlimited, unmetered or without caps, this means that we do not charge per unit for that resource within the limits shown for the Service (for example the port speed you bought for transfer on a Dedicated Server). It does not mean that the resource is infinite. CPU, memory, disk input and output, storage, network capacity and other resources are shared and allocated among customers, and the fair use rules in Section 6.3 and the limits in the Service Terms and your Order Form apply. ## 2\. Illegal and Harmful Content You may not use the Services to store, process, transmit, publish, distribute, link to or otherwise make available any of the following, or to help anyone else do so. ### 2.1 Child sexual abuse material Child sexual abuse material ("CSAM") and any content that sexualizes minors. CubePath has zero tolerance for this content. We suspend the affected Services immediately and without notice to you, preserve evidence, report apparent CSAM to the National Center for Missing & Exploited Children ("NCMEC") as required by 18 U.S.C. 2258A and to competent authorities, and terminate the Agreement. We do not warn you first, and we may be legally barred from telling you about the report. Section 14.4 of the Terms and Section 11.8 of this AUP apply. ### 2.2 Other unlawful content and activity - Content or activity that is unlawful under the laws of the United States, of the state or country where the Resources are located, of the country where you or your Organization are established or resident, or of a country to which you direct the content or activity, including fraud, theft, money laundering, extortion, human trafficking, and the sale or distribution of illegal drugs, weapons or other goods that are illegal to sell. - Content that violates export control and sanctions laws, or that is used by or for persons or places covered by sanctions, as described in Section 18 of the Terms. - Content that is defamatory, threatening, harassing, or that incites violence or hatred against a person or group on the basis of a protected characteristic. - Terrorist content, non-consensual intimate images, and doxxing or other publication of private information to harass or endanger people. ### 2.3 Deception and fraud - Phishing, credential harvesting, fraudulent websites, scams and counterfeit goods. - Impersonating any person, company or government body, or misrepresenting your affiliation with one. - Deceptive practices aimed at CubePath, such as fake identity or payment information, abuse of promotions, or opening Organizations to avoid Suspension or limits (Section 3.6 of the Terms). ### 2.4 Pirated software and unauthorized content Hosting pirated software, cracks or keygens, or distributing copyrighted works without permission. Section 3 applies. ### 2.5 Privacy violations Collecting, publishing or selling personal data in breach of Applicable Law, including stolen databases. You must comply with the data protection and privacy laws that apply to your Customer Content. ## 3\. Intellectual Property and Copyright (DMCA) ### 3.1 Respect for intellectual property You may not use the Services to infringe, misappropriate or violate the copyright, trademark, patent, trade secret, privacy, publicity or other rights of any person. ### 3.2 CubePath as a hosting service provider CubePath hosts content that customers upload and control, and does not select or review it. We respond to notices of claimed infringement under 17 U.S.C. 512 and similar laws as described in this Section. ### 3.3 Notice of claimed infringement If you are a copyright owner or authorized to act for one and you believe content on the Services infringes the copyright, send a written notice to our designated agent. A notice must include all of the following, as required by 17 U.S.C. 512(c)(3)(A): 1. A physical or electronic signature of a person authorized to act on behalf of the owner of an exclusive right that is allegedly infringed. 2. Identification of the copyrighted work claimed to have been infringed or, if one notice covers several works on one site, a representative list of them. 3. Identification of the material claimed to be infringing or to be the subject of infringing activity, and information reasonably sufficient for us to locate it (for example the full URL, IP address, bucket name or CDN domain). 4. Your name, postal address, telephone number and email address, so we can contact you. 5. A statement that you have a good faith belief that the use of the material in the manner complained of is not authorized by the copyright owner, its agent or the law. 6. A statement that the information in the notice is accurate and, under penalty of perjury, that you are authorized to act on behalf of the owner of the exclusive right allegedly infringed. Send the notice to: - Email: [abuse@cubepath.com](mailto:abuse@cubepath.com) (subject line "DMCA notice"). - Post: CubePath Inc., Attn: Designated Copyright Agent, 122 S. Main St, Suite 255, Ann Arbor, Michigan 48104, United States. The contact details above are those of our designated agent. Notices that do not substantially meet the requirements above may not be acted on. By sending a notice you agree that we may forward it, including your name and contact details, to the affected customer. A person who knowingly misrepresents that material is infringing, or that it was removed by mistake, may be liable for damages under 17 U.S.C. 512(f). Send notices about other kinds of illegal content to the same address (Section 10). ### 3.4 What we do with a notice When we receive a notice that substantially meets Section 3.3, we expeditiously remove or disable access to the material, or ask you to do so within a short deadline. We tell the affected customer, forward the notice, and give the customer the chance to send a counter-notice. Where we cannot act on single items, we restrict the smallest part of the Service that we can, if needed the whole Resource. ### 3.5 Counter-notice If you are a customer and you believe the material was removed or disabled by mistake or misidentification, you may send a counter-notice to the address in Section 3.3\. A counter-notice must include all of the following, as required by 17 U.S.C. 512(g)(3): 1. Your physical or electronic signature. 2. Identification of the material that was removed or disabled and the location where it appeared before removal. 3. A statement, under penalty of perjury, that you have a good faith belief that the material was removed or disabled as a result of mistake or misidentification. 4. Your name, postal address and telephone number, and a statement that you consent to the jurisdiction of the federal district court for the judicial district where your address is located (or, if your address is outside the United States, any judicial district in which CubePath may be found), and that you will accept service of process from the person who sent the original notice or that person's agent. When we receive a valid counter-notice, we send a copy to the complainant. Unless the complainant tells us within 10 business days that it has filed a court action seeking an order against you, we may restore the material or end the disabling no sooner than 10 and no later than 14 business days after we received the counter-notice. ### 3.6 Repeat infringer policy We terminate, in appropriate circumstances, the Agreement with customers who are repeat infringers. We consider a customer a repeat infringer when we receive valid notices of claimed infringement for different material hosted by that customer on more than one occasion and the customer did not successfully contest them with a counter-notice. We may apply this rule earlier when infringement is flagrant or commercial in scale. We apply the rule per Organization and do not accept new Organizations from a terminated repeat infringer. We keep a record of notices and counter-notices for this purpose. ### 3.7 Other claims For claims about trademarks, counterfeit goods, defamation or other rights, send a written description of the right, the location of the material, why it infringes and your contact details to [abuse@cubepath.com](mailto:abuse@cubepath.com) . We forward the complaint to the customer. We act ourselves when the claim is clear, a court orders it or the law requires it. We do not decide disputes between you and third parties. ## 4\. Network Abuse ### 4.1 Responsibility for your traffic You are responsible for all traffic that originates from, or is relayed through, your Resources. You may not use the Services in a way that harms the performance, availability or security of the CubePath network, of other customers, or of the networks of our upstream providers, transit providers and peers. ### 4.2 Prohibited network activity You may not: 1. Launch, participate in or facilitate denial-of-service attacks, including by running network stressers or booters, or reflection and amplification infrastructure, or by offering such services to others. 2. Generate attack traffic of any kind, including brute-force and credential-stuffing attempts, and abusive scraping that disrupts a third-party service. 3. Send traffic with forged, spoofed or falsified source addresses (IP spoofing), or otherwise falsify packet headers. 4. Operate, control, host or take part in a botnet, or host command-and-control infrastructure for malware or attacks. 5. Scan IP address ranges or ports of systems you do not own or are not authorized to test (Section 7.2 allows testing of your own Resources and security research under Section 7.4). 6. Operate open proxies, open relays, open resolvers, or any service that others can abuse to hide their origin or to amplify traffic. Operating a proxy or VPN that requires authentication and that you actively control against abuse is allowed. 7. Run Tor relays or Tor exit nodes. You may use Tor as a client. 8. Interfere with other customers' Resources or with the Control Panel, API, CLI or MCP Server, or cause the IP addresses we assign to you to be listed on public blocklists through your activity. ### 4.3 BGP, IP addresses and routing - You may announce only prefixes and AS numbers that you hold the right to announce, and only as authorized by CubePath for the Service (Service Terms, Section B.16). Route hijacking, route leaks and other routing abuse are prohibited, and we may filter or withdraw announcements to protect the network. You are liable for hijacks and misannouncements you cause. - IP addresses we assign remain under the control of CubePath. You may not transfer, sell or sublease them, and you may not assign them to third parties except as Section B.13 of the Service Terms allows. ### 4.4 Attacks against you Receiving an attack is not a violation of this AUP. To protect the network and other customers, we may rate-limit, filter, null-route or otherwise restrict traffic to any IP address under attack, as described in the Service Terms, Section B.15. ### 4.5 Dedicated server hardware On Dedicated Servers you may not flash or modify firmware, or change BIOS or other settings related to power delivery, overclocking or thermal management, unless CubePath authorizes the change through support. Unauthorized changes may be charged to you and may lead to Suspension or Termination (Service Terms, Section B.2). ## 5\. Email and Messaging ### 5.1 Unsolicited and deceptive messages You may not use the Services to send, relay or support unsolicited bulk or commercial messages ("spam"), whether by email, SMS, chat or any other channel. You may not send phishing messages, or manipulate email headers, sender information or message paths to hide the origin of a message. You must comply with email and marketing laws that apply to you, such as CAN-SPAM and the rules on telephone and text messaging. ### 5.2 Sending email lawfully If you send email at scale, you must send only to recipients who agreed to receive it (or where the law allows it), identify yourself, give a working unsubscribe honored promptly, keep valid reverse DNS (PTR) and sender authentication (SPF, DKIM, DMARC), process bounces and complaints, and not buy, rent or harvest address lists. ### 5.3 Outbound SMTP ports To prevent spam, outbound TCP ports 25 and 465 may be blocked by default on public IP addresses we assign. Port 587 (submission) remains open. You may ask support to unblock these ports for a specific IP address. We grant requests at our discretion after we verify your Organization and a documented, legitimate use, and we may ask for more information or conditions. An unblock applies only to the IP addresses named, comes without any promise of timing or deliverability, and we may revoke it at any time, including if the address is used to send unsolicited email or appears on blocklists. The Service Terms, Section B.18 has more on email ports. We are not responsible for email that third parties reject. ### 5.4 Receiving complaints Complaints about email sent from your Resources reach us at [abuse@cubepath.com](mailto:abuse@cubepath.com) and may be forwarded to you. You must handle them as set out in Section 11. ## 6\. Resource Use and Fair Use ### 6.1 Shared resources Cloud VPS, Managed Services, Object Storage, CDN, DNS and other shared Services run on resources that are divided among customers. You may not use them in a way that, in our reasonable judgment, degrades the Service for other customers or for CubePath. ### 6.2 Cryptocurrency mining and sustained compute Cryptocurrency mining, volunteer or grid computing and proof-of-work or proof-of-stake validation are prohibited on Cloud VPS and on any other shared-resource Service, including worker nodes of Managed Kubernetes clusters and Marketplace applications that run on a VPS. Other CPU-intensive or GPU-intensive workloads are allowed on those Services unless they breach Section 6.3 or exceed the CPU allocation described for your plan. On Dedicated Servers, the workloads named in this paragraph, including mining and validation, are allowed only to the extent that they comply with this AUP and do not impair the CubePath network or other customers. Plotting Chia, or running comparable proof-of-space or storage-proof workloads, is prohibited on every type of server and Service, including Dedicated Servers and Object Storage. ### 6.3 Fair use In addition to the limits shown for a Service: 1. Excess use of CPU, memory, disk input and output, storage, connections, requests or other resources that affects other customers or the platform may lead to throttling, shutdown or Suspension of the Resource. 2. For Dedicated Servers listed as unmetered, traffic is subject to the port speed you bought and to fair use. We may limit or suspend traffic that degrades the network or exceeds the contracted port, normally after notice and a chance to reduce it, and immediately in an Emergency (Service Terms, Section B.18). 3. You must not circumvent metering, quotas or rate limits, for example by splitting use across several Organizations, or use free tiers in bulk. ### 6.4 Object Storage and CDN You may not use Object Storage or the CDN as a public file-sharing or piracy distribution service. We may quarantine, block or remove object versions that we reasonably believe violate this AUP or the law, or that legal process requires us to restrict, and keep evidence as set out in Section 11.9\. Object Lock retention in COMPLIANCE mode cannot be shortened or removed by you, and CubePath removes a locked version only in the cases that Section B.9.7 of the Service Terms allows (court order or legal requirement, illegal content or child sexual abuse material); a legal hold stays in place until it is lifted, and billing continues for protected objects (Service Terms, Section B.9). We may suspend a CDN zone, in which case visitors see an error page (Service Terms, Section B.19). ### 6.5 Automated use You must respect rate limits for the Control Panel, API, CLI and MCP Server. Automated systems you operate, including AI agents, must not create, modify or destroy Resources beyond what you authorize, and must not be used to evade a Suspension or a limit. ## 7\. Security, Malware and Unauthorized Access ### 7.1 Prohibited conduct You may not: 1. Access, or try to access, systems, accounts, data or networks without authorization, including those of CubePath and its other customers. 2. Upload, store, run or distribute viruses, malware, ransomware, spyware, trojans, worms, exploit kits or other harmful code, except as part of the testing allowed in Sections 7.2 and 7.4. 3. Bypass, disable or probe the security, authentication, rate limiting, billing, quota, firewall or isolation controls of the Services. 4. Share Credentials with persons you do not authorize, or use the Credentials of another person. 5. Hide a compromise. If a Resource or Credential is compromised, you must secure it promptly and tell us when the compromise affects the Services or others. ### 7.2 Testing your own Resources You may test the security of Resources that you own on the Services (for example penetration tests or vulnerability scans of your own VPS, Dedicated Servers or Kubernetes clusters), as long as the testing: 1. Targets only your Resources, and does not target other customers or CubePath's shared infrastructure, including the Control Panel, API and network equipment. 2. Does not create denial-of-service conditions or traffic that affects the network or other customers. 3. Does not access, modify or delete data of other persons. 4. Complies with the rest of this AUP. You are responsible for any effect of the testing. We may suspend traffic that appears as an attack. For tests that need large volumes of traffic, contact support in advance. ### 7.3 Security of your Resources You must keep your Resources reasonably secure: strong Credentials, patched software, firewall rules, no unnecessary open services, and monitoring of abuse reports. On Unmanaged Infrastructure we do not administer the inside of your Resources and are not responsible for compromises. We may, however, act on a compromised Resource to protect others (Section 11). ### 7.4 Good-faith security research Nothing in this AUP prohibits good-faith security research that follows our vulnerability disclosure program published on cubepath.com, which is incorporated into this AUP by reference. Research that complies with the current version of that program is treated as authorized for the purposes of this AUP. Incidental, minimal access to customer data that cannot reasonably be avoided in order to show a vulnerability, and that is reported promptly and not copied, kept or shared, does not by itself take the research outside the program. Research that does not comply, that deliberately accesses or extracts customer data, that degrades the Services, or that is used to extort or to obtain payment, is not authorized. Nothing here waives CubePath's rights against conduct outside the program, and nothing here gives rights over the systems of third parties. ## 8\. AI Uses ### 8.1 Scope This Section applies to AI Features and to any use of the Services to build, train, host, run or serve AI systems, including use of the AI Gateway, the Control Panel assistant, the CubePath MCP Server, AI agents that act on your Organization, and AI systems you run on your Resources. The other Sections of this AUP also apply to AI Input and AI Output. ### 8.2 Prohibited uses You may not use AI Features, or AI systems on the Services, to: 1. Create, request or distribute CSAM or sexualized content involving minors, including synthetic or AI-generated content. 2. Create non-consensual intimate imagery, or deepfakes of real persons made to deceive, defraud, harass or defame them. 3. Develop or deploy malware, phishing campaigns, scams, large-scale disinformation or tools for unauthorized access. 4. Violate laws on privacy, biometric data or discrimination, or conduct covert mass surveillance or social scoring. 5. Make automated decisions with legal or similarly significant effect on people, or use AI in high-risk fields (such as health, employment, credit, law enforcement, critical infrastructure or education), unless you comply with Applicable Law for that use, including human oversight and any required assessments. 6. Engage in practices that Applicable Law prohibits. 7. Circumvent the safeguards, usage policies, rate limits or access controls of CubePath or of a Model Provider. 8. Resell or share access to the AI Gateway or your API keys with third parties without our written consent. 9. Let an AI agent act on the Services in ways you could not act yourself, or without limits you can control. ### 8.3 Model Providers' policies When you use a model through the AI Gateway, the usage policies of the Model Provider of that model apply to your use of that model. The Documentation for the AI Gateway lists each Model Provider and links to its current policy, and we tell Owners and Admins by email or in the Control Panel when we add a Model Provider or when a Model Provider changes its policy in a way that materially restricts your use. A violation of those policies is a violation of this AUP. We may block requests, disable models or suspend access to the AI Gateway if a Model Provider asks us to, or if we have reason to believe your use violates those policies. ### 8.4 Your responsibility for outputs AI Output may be inaccurate, incomplete, offensive or infringing. You are responsible for reviewing outputs and for the way you use them and distribute them. Where Applicable Law requires it, you must tell people when they are interacting with an AI system or when content is AI-generated, and label synthetic media. ## 9\. Hosting Third Parties and Reselling ### 9.1 Your End Users You may use the Services to host websites, applications and services for your own customers and End Users. You remain fully responsible for their acts and omissions as if they were yours. You must: 1. Bind them to an acceptable use policy that is no less protective than this AUP. 2. Act promptly on abuse complaints that concern them, including by suspending or removing them. 3. Keep enough information to identify the persons who use your Resources and give it to us when lawful and necessary to deal with abuse. CubePath has no obligation to your End Users, and we do not provide support to them. We normally forward complaints about them to you first, and if you do not resolve them we may act on your Resources (Section 11). We may act without forwarding them first in the cases in Sections 3.4 and 11.4. ### 9.2 Reselling and sub-letting You may not resell, sublet or redistribute the Services as a stand-alone service, white-label them, or share Resources between unrelated third parties as a way to avoid fees or limits, except as a CubePath partner or reseller program allows in a separate written agreement (Service Terms, Section B.28) or as an Order Form allows. Building your own product or hosting platform on top of the Services is allowed if you comply with this Section. ### 9.3 Anonymous and high-risk hosting You may not offer anonymous or "bulletproof" hosting, or services whose purpose is to ignore abuse complaints. If you host free or anonymous services for the public (for example free hosting, proxy or VPN services, paste or file upload sites), you must have a working process for abuse reports and identity controls proportionate to the risk. ## 10\. Reporting Violations ### 10.1 How to report Report abuse of the Services, illegal content and violations of this AUP to [abuse@cubepath.com](mailto:abuse@cubepath.com) . Include what lets us find and assess the problem: the URL, IP address or hostname, date and time with time zone, the logs or full email headers that show it, and why it is a violation. We accept reports in English and Spanish. Subject to Section 10.3 and Applicable Law, we decide in our reasonable judgment whether and how to act on a report, and we may not reply to reports that are incomplete, duplicate or abusive. Do not use [abuse@cubepath.com](mailto:abuse@cubepath.com) for customer support. ### 10.2 Copyright notices Use the form and address in Section 3.3. ### 10.3 Notices of illegal content Anyone may tell us that specific content on the Services is illegal. Send the notice to [abuse@cubepath.com](mailto:abuse@cubepath.com) . A notice should contain all of the following: 1. A sufficiently substantiated explanation of the reasons why you allege that the information is illegal content. 2. A clear indication of the exact electronic location of that information, such as the exact URL or URLs, and, where necessary, additional information that helps us identify the illegal content, appropriate to the type of content and to the Service concerned. 3. Your name and email address, except where the notice concerns child sexual abuse or exploitation, in which case you may remain anonymous. 4. A statement confirming your bona fide belief that the information and allegations in the notice are accurate and complete. If your notice contains an electronic contact address, we confirm receipt without undue delay. We process notices in a timely, diligent, non-arbitrary and objective manner, and we tell you our decision and the available routes to challenge it. Staff review decisions to suspend or terminate. We may return notices that lack enough information for completion. ### 10.4 Reports from the authorities Authorities send orders and requests to [legal@cubepath.com](mailto:legal@cubepath.com) . Section 14.5 of the Terms applies. Please mark emergency requests as such in the subject line. We act on valid orders from competent authorities to remove content or to act against illegal content within the time stated in the order, and we preserve removed content as the law requires. ## 11\. Enforcement ### 11.1 Our approach We prefer to resolve problems with you directly where that is safe. The steps below are our usual order, but we may skip, repeat or combine them when the facts require it. We act in proportion to the violation, considering how serious, frequent and harmful it is, whether it appears intentional, whether the Resource was compromised, and whether you cooperated. ### 11.2 Warning with a deadline For most violations we send a notice by support ticket and by email to the Owners and Admins of the Organization. The notice identifies the Resource and the violation and asks you to correct it, usually within 24 hours (shorter or longer depending on the harm). The deadline is a guide, not a promise that we will wait, and nothing is suspended or deleted automatically when it passes, but we may then proceed to Suspension. You must reply to our requests and cooperate with our investigations. For a compromised Resource, tell us what you have done to secure it. ### 11.3 Suspension If you do not correct the violation by the deadline or do not respond, we may suspend the affected Resources, or the Organization when the violation affects it as a whole, as set out in Section 8.2 of the Terms. In a Suspension for abuse, Resources are stopped, isolated or restricted, not deleted. Power actions, reinstall and rescue mode may be disabled, and Fees for Resources that remain billable keep accruing. Paying an overdue balance does not lift a Suspension for abuse. We lift it when we conclude, in our reasonable discretion, that the cause is resolved. We restrict the smallest part of the Services that is practical, for example individual objects, buckets or zones. If we reverse a Suspension under Section 11.7, or if we conclude that the violation did not occur, we return to your Balance the Fees that accrued for the suspended Resources during the Suspension, in the form in which you paid them: as Cash Balance for the part paid from your Cash Balance and as Credits for the part paid with Credits. This is not a Service Credit, and you do not need to make a claim under the SLA. Where it is safe and lawful, we may allow you to export your Customer Content during a Suspension for abuse. ### 11.4 Immediate action We may suspend, isolate, null-route, block or restrict Services immediately and without prior notice when, in our reasonable judgment: 1. The content or activity is CSAM, or notice to you would be unlawful or would put people at risk. 2. There is an active attack, malware, a botnet, phishing, spam in progress or other abuse that is causing or likely to cause harm to the network, other customers or third parties. 3. A law, court order or valid request from an authority requires it, or sanctions, export control or fraud rules require it (Section 18 of the Terms). 4. A Resource or Credential is compromised and continues to cause harm, or the violation repeats after a warning. 5. There is an Emergency. We send you the statement of reasons at the time and in the way that Section 11.6 states. ### 11.5 Termination We may terminate the Agreement, the affected Services or your Organization, as set out in Section 9.4 of the Terms, for serious or repeated violations, violations you do not correct, and conduct that exposes CubePath to a material legal, regulatory or contractual risk, as we explain in our notice. We may refuse Services to a person terminated under this AUP and to Organizations connected to them. You remain liable for Fees incurred up to termination. Any remaining Cash Balance, after deducting amounts you owe us and amounts subject to a pending dispute or chargeback, is handled under Sections 7.9 and 9.4 of the Terms, except where we must keep it by law or it is connected to fraud or sanctions. Credits are forfeited. ### 11.6 Statement of reasons When we remove or disable access to specific content, restrict its visibility, or suspend or terminate Services because content is illegal or conflicts with this AUP, we send the affected customer a clear and specific statement of reasons without undue delay, at the latest when the restriction takes effect. It states: 1. What we restricted and, where relevant, for how long and where. 2. The facts and circumstances we relied on, whether the decision followed a third-party notice (with a summary of it) or our own investigation, and whether automated means helped detect the issue. Staff review decisions to suspend or terminate. 3. The legal ground, or the Section of this AUP or the Agreement that applies, and why. 4. How to challenge the decision: the complaint route in Section 11.7 and, where available to you, out-of-court dispute settlement bodies and judicial redress. We may delay or omit the statement where we have no contact details for you, where the law prohibits it, where an authority asks us not to give it, or where giving it would compromise a criminal investigation or endanger a person. Where we omit a statement for these reasons, we give it as soon as the reason ends, if the law allows. ### 11.7 Complaint to abuse@ This is the internal complaint route described in Section 14.3 of the Terms. If you believe we acted wrongly, email [abuse@cubepath.com](mailto:abuse@cubepath.com) within six months of our notice, quoting the case reference, explaining why and attaching any evidence. Where practicable, a member of staff who was not involved in the original decision reviews it. We decide in a timely, diligent and objective manner, tell you the result and our reasons, and reverse the decision, including by restoring Services or content, if it was wrong. Your other rights under Applicable Law remain. A complaint does not delay immediate action under Section 11.4. ### 11.8 Law enforcement and reporting We may report violations and suspected crimes to law enforcement and other competent authorities, and we cooperate with valid legal process as set out in Section 14.5 of the Terms. We report apparent CSAM to NCMEC and to competent authorities (Section 2.1). We may share information with other providers, registries and abuse-handling organizations where necessary to stop abuse, within the limits of Applicable Law and our Privacy Policy. ### 11.9 Evidence preservation We may preserve data, logs, copies of content and read-only console images of Resources that relate to a suspected violation, even if you delete them or your Organization is suspended or terminated (Section 6 of the Terms). We keep them only as long as needed for the investigation, for legal claims and as the law or an authority requires, and we delete them when those reasons end. Our Privacy Policy states the retention periods for Account Data and Service Data. In Object Storage we may keep a copy of affected object versions as evidence for 90 days, or longer where the law, a legal order, the investigation or a legal claim requires (Service Terms, Section B.9). Content that we report to NCMEC, and the related records, is kept for the period that 18 U.S.C. 2258A requires, which is not shortened by your deletion of the content, by Suspension or by Termination. Preserving evidence is not an admission that the content is illegal. ### 11.10 Costs and liability You are responsible for Fees that accrue during an investigation or Suspension, except as Section 11.3 provides, and for the reasonable, documented costs we incur because of your violation of this AUP. Subject to Section 16 of the Terms and Applicable Law, we are not liable for action we take in good faith and in proportion to the violation under this AUP. This does not limit our obligation to correct a wrongful decision under Section 11.7 or any liability that Section 16.3 of the Terms leaves unlimited. Section 16.3 of the Terms governs whether your liability for breach of this AUP is limited; for Consumers, Section 20 of the Terms applies, and your liability for breach of this AUP is limited to the extent the mandatory consumer law that protects you requires. We have no duty to monitor Customer Content or to act on every violation, and not acting does not waive our rights. ## 12\. Changes We may update this AUP, and the changes follow Section 19 of the Terms. This AUP is published with the Terms at , and each new version carries the version number and date of that document. A change is a Material Change, and follows Section 19.2 of the Terms, if it adds a prohibition, narrows what you may do with a Service you already use, or increases the consequences of a violation. A change that only corrects errors, clarifies wording or adds an example is not a Material Change and takes effect on publication. For Material Changes, we notify Owners and Admins by email and in the Control Panel, and the new version must be accepted in the Control Panel by the Acceptance Deadline. We may change this AUP sooner when the law, a regulator, security or the need to stop abuse requires it. New Services that we launch may come with rules in the Service Terms. Those rules apply to the new Service from the date of publication, as set out in Section 19.3 of the Terms, and are not a change to this AUP for existing Services. ## 13\. Contact - Abuse reports, copyright notices and notices of illegal content: [abuse@cubepath.com](mailto:abuse@cubepath.com) - Legal notices, authorities and law enforcement: [legal@cubepath.com](mailto:legal@cubepath.com) - Complaints about our enforcement decisions: [abuse@cubepath.com](mailto:abuse@cubepath.com) , as set out in Section 11.7 - Support and billing: [support@cubepath.com](mailto:support@cubepath.com) - Privacy requests: [privacy@cubepath.com](mailto:privacy@cubepath.com) - Post: CubePath Inc., 122 S. Main St, Suite 255, Ann Arbor, Michigan 48104, United States - Website: --- **Language.** This document is written in English. The English version is the original and the only binding version. Any translation is provided for information only.