CloudDock Terms of Service

Effective Date: December 2025
Jurisdiction: State of California, United States

1. Acceptance of Terms

1.1 Acceptance and Updates.
By creating an account or using any part of CloudDock (including browsing the Dashboard, queuing, launching, or accessing a container), you agree to be bound by these Terms of Service (“Terms”) and our Privacy Policy (together, the “Agreement”). If you do not agree, do not use the Service.

We may update the Agreement from time to time. For material changes, we will provide notice inside the product, including:

• a notice in the Dashboard notification center;
• a mandatory in-product prompt or banner that you must dismiss or otherwise interact with.
We may also provide notice by email or other reasonable channels. Unless a different effective date is stated in the notice, the updated Terms and Privacy Policy take effect when they are posted. Your continued access to or use of the Service after the effective date of any update (including continuing to use CloudDock after seeing the in-product notice) constitutes your acceptance of the updated Terms and Privacy Policy.

1.2 Age and Contractual Capacity.
The Service is intended for natural persons who are at least 16 years old. If a jurisdiction requires you to be 18 to enter into contracts or enjoy certain consumer protections, then within that jurisdiction we offer the Service only to individuals who are 18 or older. We do not knowingly provide the Service to anyone below the local age of majority.

1.3 User Types.
The Service is intended for natural persons who are at least 16 years old. If a jurisdiction requires you to be 18 to enter into contracts or enjoy certain consumer protections, then within that jurisdiction we offer the Service only to individuals who are 18 or older. We do not knowingly provide the Service to anyone below the local age of majority.

1.4 Dispute Resolution.
In the event of a dispute, both parties will first attempt to resolve it through good-faith negotiation. If negotiation fails, litigation must be brought in a court located in California (see Section 8).

1.5 No Warranty.
CloudDock is provided “as is” and “as available.” We make no warranties of merchantability, fitness for a particular purpose, uninterrupted use, or error-free operation; you use the service at your own risk (see Section 10).

2. Service Model & Account Usage

2.1 Launch & Allocation.
After you select a GPU group and runtime duration in the Dashboard, the system automatically assigns an available machine within that group. The specific machine is allocated by CloudDock’s scheduler and may change between sessions.

2.2 Concurrency Limit.
Each account may run only one instance at a time. Exceptions for education or promotional events require a complete project or lesson package and written approval from CloudDock; any extra concurrency, credits, duration, or GPU group will be specified in that written confirmation.

2.3 Queue & Claim.
When resources are scarce, you may be placed in a queue. When your turn arrives you have a fixed claim window (currently 5 minutes) to start your instance. If you do not confirm within that window, the slot is forfeited and you must re-queue.

2.4 Runtime Duration, Extension (“Extend”) & Changes.

• (a) Initial duration.
  When you launch a session, you choose an initial duration. The corresponding fee for that duration is calculated and reserved or deducted as described in Section 5.
• (b) Extension feature.
  CloudDock currently supports a limited “Extend” feature that allows you to lengthen the runtime of a running session. An extension request is processed automatically by the system and cannot be overridden by customer support.
• (c) Non-reversible once confirmed.
  Once you confirm an extension, it is irreversible: you cannot shorten, cancel, or roll back the additional time, and you are billed for the extended duration in accordance with Section 5.
• (d) Hard conditions for extension.
  An extension may only be granted if all of the following conditions are met at the time of the request:
  1. Time buffer: More than 5 minutes remain before the current scheduled end time of the session.
  2. No active queue: No other user is currently queued for that GPU group.
  3. No maintenance window: The machine or group is not in a scheduled maintenance window for the period that would be covered by the extension.
  4. Group maximum duration: The extension will not cause the total booked duration for that session to exceed the maximum per-order runtime that CloudDock sets for the relevant GPU group.
  If any of these conditions are not satisfied, the extension request will be denied, and support staff cannot force it through manually.
• (e) Effect on the order.
  A successful extension increases the total runtime of the current order (session) for billing and refund purposes. It does not create a new, separate order; it modifies the duration of the existing one.
• (f) Per-group caps and adjustments.
  Maximum per-order runtimes, extension limits, and whether “Extend” is currently available for a given GPU group may be displayed in the Dashboard or documentation and may be changed by CloudDock at any time to reflect operational or risk-control needs.
• (g) Pre-end reminders and visibility.
  Approximately 15 minutes before the scheduled end time, CloudDock Intelligent Dog™ will trigger a desktop notification inside the container (for example via XFCE) reminding you to save your work or extend the session if eligible. The Dashboard also shows the scheduled end time and remaining time for your current session. You are responsible for monitoring these indicators and taking any desired action; the absence of additional reminders does not entitle you to compensation beyond what is described in Section 5 and Annex A.

2.5 Pause / Suspend.
Mid-session pause or suspension (without billing) is not supported. Any future features that simulate pausing (e.g., hibernation) will be documented separately and may be subject to additional conditions or pricing.

2.6 Resource, Network & Privilege Restrictions.
To maintain platform stability and security, CloudDock may impose rate limits, bandwidth quotas, I/O quotas, outbound-port blacklists, IP blocks, or other technical restrictions. Circumvention is prohibited.
Without limiting Section 4, you must not:

• attempt to obtain or use unauthorized root or elevated privileges inside the container;
• create or use VPNs, proxy tunnels, reverse tunnels, or similar mechanisms to “punch holes” through network isolation;
• perform any behavior intended to bypass network restrictions, quotas, or monitoring, including scanning internal or external networks, attempting privilege escalation, or launching network attacks from your instance.

Violations may result in immediate termination of the session, seizure and audit of the container, and account-level enforcement (see Sections 3, 4, and 7).

2.7 Mining & Power Modifications.
Mining workloads are neither optimized nor guaranteed; if they impair the platform we may throttle, lower priority, or deny scheduling. Overclocking, undervolting, power-limit modifications, “shunt mods,” or similar alterations are strictly forbidden. Detecting such behavior will result in permanent suspension and forfeiture of any remaining balance (except where prohibited by law).

2.8 Availability & SLA.
We use commercially reasonable efforts to maintain availability. The formal service-level objective, measurement rules, and discount credits are described in Annex A (SLA & Credits).

2.9 Billing & Dispute Tie-in.
Billing, refunds, and dispute handling follow Section 5. During payment investigations or chargebacks, CloudDock may take necessary risk-control measures, which may include temporary freezes on instances or accounts.

2.10 Taxes.
Prices are quoted tax-exclusive. If applicable taxes are required by law, CloudDock may collect and remit them or require you to self-remit, as described in Section 5.

2.11 Dynamic Pricing.
CloudDock reserves the right to dynamically adjust pricing for different GPU groups, users, promotions, or time periods at any time, consistent with applicable law. The effective price for a session or extension is the price displayed at the time you confirm the launch or extension, as further detailed in Section 5 (including any future per-segment “top-up” billing rules). Previously launched sessions are not repriced retroactively.

2.12 Right to Refuse Service.
Subject to applicable law, CloudDock may decline to open an account, accept a payment, process a top-up, or provide access to the Service for any individual, organization, or group, including for reasons related to abuse history, fraud risk, sanctions or export-control compliance, or other legitimate business concerns. This right is in addition to CloudDock’s rights to suspend or terminate accounts under Section 7.5.

3. Container Lifecycle & Watchdog Monitoring

3.1 Shutdown Determination.
“Normal shutdown” currently refers only to automatic shutdown when the countdown expires. If a console “Stop” button is introduced later, using it will also be deemed normal. Any other shutdown is considered abnormal (including crashes, watchdog termination, in-container commands such as shutdown/halt/poweroff, or host-level interruption).

3.2 Seizure & Retention Scope (Abnormal Events).
Upon an abnormal event, CloudDock creates a read-only snapshot of the container and its disk image and retains relevant audit logs (event metadata, process/session state, runtime parameters, and similar technical artifacts) as described in these Terms and the Privacy Policy. During an ongoing investigation, CloudDock may temporarily suspend or restrict your account, freeze related sessions, or refuse new launches if we reasonably believe this is necessary to protect the platform, even before a final conclusion is reached.

3.3 Retention Period.
For general anomalies, seized artifacts are typically retained for up to one (1) year and then deleted or anonymized. For severe violations (for example, content involving minors, actual network attacks, or serious security incidents), CloudDock may retain certain artifacts long-term or permanently, including archived copies, to the extent permitted or required by law.

3.4 Notification & Investigation Outcomes.
We do not proactively notify you while an investigation is in progress. Once a conclusion has been reached, we will endeavor to communicate the outcome using your primary contact identity or default contact method associated with your account (see Section 7.4), for example via in-app ticket, Dashboard message, or the bound support channel. Depending on the findings, outcomes may include: no action; a warning; reversal of restrictions; permanent account suspension; and/or further legal steps.

3.5 Watchdog Actions & Internal Briefing.
At this stage, when CloudDock Intelligent Dog™ or related safeguards detect qualifying abnormal behavior, the affected instance will normally be immediately terminated and seized in accordance with Section 3.2. The system also prepares an internal incident summary (for example, basic reason codes, timestamps, and classification) for support and operations staff, so that customer-service personnel can see why a session was stopped even if they cannot view full forensic logs. Future iterations may introduce more granular, tiered responses (such as alert → throttling → termination) as our detection stack evolves.

3.6 Forensic Access.
CloudDock does not enter or inspect your container while it is running. Only after seizure may authorized personnel access the snapshot in read-only mode, under strict access control and audit. Access is limited to the smallest set of personnel necessary to perform security review, abuse investigation, or compliance work.

3.7 Monitoring Scope.
We conduct behavioral and runtime-parameter monitoring, which may include CPU/GPU temperature and utilization, memory/VRAM usage, disk/IO metrics, process states, and indicators of abnormal privilege escalation or suspicious workloads (such as repeated failed privilege escalations or patterns consistent with scanning or attacks). To prevent circumvention, we do not disclose specific detection rules. The general categories of data collected are described in the Privacy Policy.

3.8 Emergency Threats.
When there is an imminent threat to personal safety or similar emergency, we may take preservation measures and cooperate with law enforcement or competent authorities as required by law. In such cases, certain emergency actions may be taken immediately without prior notice.

3.9 Log Access.
Users have no right to access or export audit logs, watchdog logs, or other forensic materials. Summaries may be communicated at CloudDock’s discretion, but the underlying records remain internal.

3.10 Security & Storage Location.
Seized and retained data are encrypted at rest and subject to least-privilege access controls. They are typically stored in facilities located in California, USA, or in other jurisdictions where our infrastructure providers operate, as further outlined in the Privacy Policy.

3.11 Use of Anonymized Forensic Data for Security Improvement.
If CloudDock reasonably determines that an incident involves attacks, abusive behavior, or material violations of these Terms (for example, prohibited network scanning, exploitation attempts, or privilege escalation attacks), CloudDock may, to the extent permitted by law:

• anonymize the relevant seized container snapshot and associated technical artifacts; and
• use the resulting, de-identified data to strengthen CloudDock Intelligent Dog™ or other security/AI systems (for example, to improve detection models or rules).

Such use is limited to what is necessary for security and abuse-prevention purposes. In practice, this typically focuses on process listings (similar to ps) and shell command history or metadata, plus minimal contextual system information. As described in the Privacy Policy, CloudDock does not use this process to inspect your web browsing history, online accounts, or unrelated personal content.
Except for the minimal artifacts retained for these security purposes, the container will be handled in line with normal lifecycle rules (for example, eventual deletion of the full image after the retention period). For precise information about the categories of data that may be collected and retained, please refer to the CloudDock Privacy Policy.

4. Prohibited Activities / Acceptable Use Policy (AUP)

For purposes of this Section, “illegal” or “unlawful” conduct or content is determined by applicable law, including California law and U.S. federal law. If content or behavior is illegal under those laws, it is considered illegal for use on CloudDock.

4.1 Prohibition on Public-Facing Services.
You may not offer services to the public or operate as a public node (web server, public API, proxy, VPN, Tor node, reverse tunnel endpoint, etc.) on top of CloudDock without CloudDock’s prior written permission.

4.2 Container Isolation, Host Access & Intranet Breach.
You must respect platform isolation. You may not:

• attempt container escape or exploit the container runtime to access the host OS, hypervisor, management plane, or other tenants;
• mount or attempt to mount host volumes, host devices, or volumes belonging to other users or system components;
• attempt to read, modify, or interfere with any infrastructure management network or internal control plane;
• perform any form of intranet penetration, lateral movement, port mapping, P2P routing, or tunneling intended to break network isolation or access internal systems not expressly exposed to you.

Any such attempts are considered severe violations and may result in immediate termination, seizure of the container, and permanent account suspension.

4.3 Scanning, Attacks & Credential Abuse.
You may not:

• perform port scanning, fingerprinting, vulnerability scanning, penetration testing, or similar reconnaissance;
• launch or participate in DDoS/DoS, reflection/amplification attacks, flood traffic, malicious “stress testing,” or similar attack traffic;
• conduct brute-force, credential-stuffing, password-spraying, dictionary attacks, session hijacking, or similar attempts against any service (whether on CloudDock or elsewhere).

4.4 Malware & Abuse Tooling.
You may not upload, host, generate, train, or distribute malware, backdoors, keyloggers, C2 infrastructure, botnets, or any other code that is primarily designed or commonly used for malicious purposes. This includes using CloudDock to develop, test, or operate such tools, even if you claim it is “for research” but lack explicit written authorization and legal basis.

4.5 Spam, Harassment & Offensive Conduct.
You may not:

• send spam, message bombing, or any unauthorized automated mass messaging or harassment;
• use CloudDock-controlled forums, community servers, support channels, or any in-service communication feature to send threats, slurs, hate speech, or seriously offensive content;
• create usernames, account names, project names, or other identifiers on CloudDock that contain obvious slurs, profanity targeting individuals or groups, or similarly abusive wording.

If you direct harassing, hateful, or seriously offensive language at CloudDock staff or customer support (for example in tickets or support chats), CloudDock may, in its discretion, refuse to continue providing support, restrict or suspend your account, or decline to provide further services to you, in addition to other remedies under these Terms.

4.6 IP Infringement, Unlawful Content & Prohibited Training.
You may not use CloudDock to:

• infringe third-party copyrights, trademarks, patents, trade secrets, or other intellectual-property rights;
• upload, store, generate, train on, or distribute content that is illegal under California or U.S. federal law (including, without limitation, content involving minors, non-consensual intimate imagery, or incitement to violence), whether inside containers, on CloudDock-managed forums, or on any server or resource under CloudDock’s control;
• train, fine-tune, or otherwise adapt models on datasets that you know or reasonably should know contain unlawful content or content that violates third-party IP or contractual rights;
• run, host, or serve models or applications whose primary purpose is to generate, distribute, or facilitate such unlawful or rights-violating content.

You are solely responsible for ensuring you have the necessary rights (including IP rights and content permissions) to the data and models you use on CloudDock.

4.7 Unauthorized Scraping & Data Collection.
High-frequency scraping, automated data collection, or similar activity that bypasses or circumvents robots.txt, rate limits, access controls, or other technical or contractual restrictions is prohibited. This applies both to CloudDock’s own properties and to third-party sites or APIs you target from within your container.

4.8 Mining & Power Modifications.
Mining workloads are permitted but not optimized or guaranteed. If mining degrades platform performance, CloudDock may throttle, lower priority, or deny scheduling for such workloads. Overclocking, undervolting, power-limit modifications, “shunt mods,” or similar hardware-level changes are strictly forbidden. Detection of such behavior may result in permanent suspension and forfeiture of any remaining balance (except where prohibited by law).

4.9 Circumvention Ban.
You may not bypass or attempt to bypass any technical, billing, or security controls, including but not limited to:

• quotas or limits (CPU, GPU, memory, I/O, storage, bandwidth);
• network or port blocks, firewalls, or routing rules;
• watchdog monitoring, logging, or runtime hooks;
• authentication, authorization, or token/identity checks.

Attempted circumvention is treated as a violation even if you claim it was only for “testing” or “experimentation.”

4.10 Identity, Account Sharing & Resale.
Sub-letting, reselling, sublicensing, or operating large numbers of accounts on behalf of others is not allowed. Accounts are for individual use only (see Section 7). Using the same payment source to top up multiple accounts is not, by itself, a violation, but discount qualifications and special pricing are tied to individual eligibility and may not be shared or resold. Circumventing such limits is handled under Sections 6.7 and 4.13.

4.11 Third-Party Apps, Models & Developer Terms (App Store).
When you install or use an app, model, or other component from the CloudDock App Store or similar catalog:

• you understand that many such items are developed and maintained by third-party developers, not by CloudDock;
• you must comply with any terms of service, license agreements, and privacy policies published by those third-party developers for their apps, models, or services;
• your relationship regarding those apps/models is primarily between you and the third-party developer.

CloudDock is not responsible for your breach of any third-party developer terms and is not liable for any loss, damage, or dispute arising from your separate relationship with such developers. However, if your use of a third-party app or model violates law or these Terms, CloudDock may still take enforcement action under Section 4.13.

4.12 Third-Party License Compliance (Open Source & Models).
Pre-installed open-source software, models, and weights within any image or instance are governed by their respective licenses. You must not use or configure any such components in a manner that violates their original license terms (for example, RAIL, non-commercial licenses, AGPL network clauses, or similar). Violation of third-party licenses constitutes a material breach of these Terms and will be handled under this Section and Section 11.4. CloudDock merely provides technical hosting and assumes no legal obligations for your licensing compliance.

4.13 Enforcement Actions.
CloudDock may, in response to actual or suspected violations of this AUP or other parts of the Terms:

• throttle or restrict certain workloads or features;
• deny scheduling, refuse launches, or cancel queues;
• terminate and seize instances for audit;
• temporarily suspend or permanently ban accounts;
• forfeit remaining balances where permitted by law (particularly in cases of intentional abuse or malicious activity); and/or
• pursue legal remedies, including reporting to relevant authorities.

The specific response will depend on severity, frequency, and risk to the platform and other users.

5. Pricing, Billing, Refunds & Taxes

5.1 Balance & Prepayment.
The Service operates on a prepaid wallet model. You must maintain a sufficient positive balance before launching or extending any session. Launches and extensions are blocked if your balance is insufficient.

5.2 Billing Start.
Billing for a session begins the moment you click “Start” in the console and the system begins allocating the instance (see Section 2.1). Billing continues until the scheduled end time of the order, including any approved extensions.

5.3 Deduction Method; Extensions; Minimum Unit.

• (a) Initial booking.
  Before launch, the total price for the initial requested duration is calculated and the full amount is deducted or reserved from your balance in one go.
• (b) Extensions (“Extend”).
  If you use the “Extend” feature (see Section 2.4), each approved extension constitutes an additional billed segment of the same order. The incremental price for the extension segment is calculated at the then-current hourly rate for that GPU group at the time you confirm the extension, and is deducted from your balance immediately.
• (c) Minimum billing unit.
  The minimum billing unit for both initial bookings and extension segments is one (1) hour. CloudDock may allow you to specify durations in finer increments (for example, 0.5 hours), but any partial hour may be rounded up to a full billable hour.
• (d) Order-level treatment.
  For refund and accounting purposes, an order that has been extended is treated as a single continuous session made up of one or more billed segments (initial booking + any extensions).

5.4 Voluntary Stop.
Currently, there is no user-facing “Stop” button that terminates a session early. If such a button is introduced in the future, pressing it will be treated as a voluntary stop and will not entitle you to any refund of remaining time, even if the scheduled end time has not yet been reached. Extension segments, once confirmed, are irreversible (see Sections 2.4 and 5.3).

5.5 Non-User Interruption, Force Majeure & 24-Hour Refund Cap.

• (a) General rule.
  If a session is interrupted without your fault (for example, due to CloudDock infrastructure issues or force majeure events as defined in Section 8.6), CloudDock may grant a refund based on the percentage of the session that had elapsed at the time of interruption:
  • < 50% of the booked duration elapsed → up to 100% refund;
  • < 80% of the booked duration elapsed → up to 50% refund;
  • ≥ 80% of the booked duration elapsed → no refund.
• (b) 24-hour maximum per order.
  For any single order (including any extensions to that order), the maximum refundable amount under this Section 5.5 is capped at the price corresponding to at most twenty-four (24) hours of usage. Earlier portions of a longer-running session are not refundable under this clause, even if the total booked duration exceeds 24 hours.
• (c) User backup duty.
  By running long sessions, you acknowledge and agree that you are responsible for backing up critical data at least once every 24 hours. CloudDock is not responsible for data loss beyond that 24-hour window and will not refund more than the amount corresponding to the last 24 hours of the order.
• (d) Weighted-average price for mixed-rate orders.
  If an order contains multiple billed segments at different hourly rates (for example, initial booking at one price and later extensions at a higher or lower price), the refundable amount under the percentages above is calculated using the weighted-average effective hourly price for that order, based on all segments up to the point of interruption, subject to the 24-hour cap.
• (e) Form of refund.
  Any approved refund under this Section is issued as a credit to your CloudDock account balance (see Section 5.7). If an automatic refund is not applied, you must contact human support within a reasonable period for manual review.

5.6 Watchdog Termination.
If CloudDock Intelligent Dog™ or other safeguards terminate your session due to suspected or confirmed violations of these Terms or the AUP, the event is treated as a user breach and no refund is owed. If you appeal and CloudDock’s audit reasonably concludes that no violation occurred and the termination should be treated as non-user interruption, CloudDock may, at its discretion, apply the refund logic of Section 5.5 to that order.

5.7 Refund Form.
Any refunds, credits, or compensation are issued solely as non-transferable, non-withdrawable, non-interest-bearing account balance. They may not be redeemed for cash.

5.8 Balance Validity.
Account balance does not expire, unless required by applicable law.

5.9 Price Changes, Running Sessions & Extensions.

• (a) General price changes.
  CloudDock may change prices for any GPU group, user segment, promotion, or time period at any time, consistent with applicable law.
• (b) Effect on queued or unlaunched sessions.
  Queued or unlaunched sessions always adopt the rate in effect at the time you confirm the launch.
• (c) Running sessions (initial booking).
  If CloudDock changes prices while your session is already running, the price for the already-billed portion (your initial booking and any extensions confirmed before the change) will not be retroactively increased or decreased. You will not be charged extra or refunded solely because a global price changed mid-session.
• (d) Extensions after a price change.
  If you extend a session after a price change takes effect, the extension segment will be billed at the new rate in effect at the time you confirm the extension, as described in Section 5.3(b).
• (e) Refund calculation with mixed rates.
  If a refund applies to an order that includes segments billed at different rates (for example, launch at the old price and later extension at the new price), the refund is calculated on the weighted-average effective price for the order, as described in Section 5.5(d). You do not receive separate refunds per rate tier.
• (f) Abuse of extension for refund manipulation.
  If CloudDock reasonably determines that you have used the “Extend” feature primarily to manipulate refunds or inflate the effective average price in anticipation of a potential refund (for example, repeatedly extending immediately before requesting a non-user-interruption refund), CloudDock may:
  • exclude some or all extension segments from the refund calculation;
  • deny refunds for the affected order; and/or
  • restrict your eligibility for certain future refund or goodwill policies.
  For this specific type of behavior, CloudDock will not, solely on this ground, permanently suspend your account or confiscate your existing balance. However, other serious or repeated violations may still be addressed under Sections 4.13 and 7.5.

5.10 Discount Stacking.
Coupons and bespoke discounts may be combined with each other unless stated otherwise, but may not be combined with student pricing. EDU-tier GPU groups do not participate in general coupon promotions unless expressly stated.

5.11 Payment Methods.
Currently, only Zelle is accepted for top-ups. Credit/debit cards, bank wires, PayPal, foreign currencies, and third-party wallets are not accepted at this time. CloudDock reserves the right to refuse funds or reverse credits that it deems abnormal or high-risk.

5.12 Payment Investigation / Chargebacks.
While a payment-network inquiry, dispute, or chargeback is ongoing, service is generally maintained until resolution. If there is significant risk or legal compulsion, CloudDock may temporarily freeze instances or accounts. If a transaction is deemed malicious, fraudulent, or abusive, CloudDock may permanently suspend the account and forfeit remaining balance, except where prohibited by law.

5.13 Taxes.
Prices are tax-exclusive. Where required by law, CloudDock may collect and remit applicable taxes on your behalf and itemize them on an invoice, or require you to self-remit and self-report as appropriate.

5.14 Currency & Exchange.
USD is the sole settlement currency. If you use a third-party exchanger to fund in another currency, exchange rates, fees, and failure risk are between you and that third party.

5.15 Negative Balance.
Negative balances are not permitted. If, due to an error, your account shows a negative balance, CloudDock may correct the balance and may decline new launches or extensions until the balance is restored.

5.16 Top-Ups via Transfer (Zelle) – Confirmation, Unclaimed Funds & Ownership.

• (a) User Confirmation Required.
  Because CloudDock currently relies on manual verification of Zelle and similar transfers (see Section 5.11), you must, after completing a top-up, promptly contact CloudDock through an official support channel and provide:
  1. your CloudDock username; and
  2. either (i) a transaction ID or reference as shown in your banking app, or (ii) a clear screenshot of the transfer (with sender name, amount, and date visible).
  Until CloudDock has received and matched this information, the transfer will not be credited to any account balance and will remain in a pending / unassigned state.
• (b) Unclaimed Transfers (30-Day Window).
  If CloudDock receives a transfer that cannot be reliably matched to a CloudDock account (for example, missing username, unclear reference, or no user contacting support):
  • CloudDock will hold the transfer in an unclaimed state for up to thirty (30) days from the date the funds are received;
  • during this period, CloudDock may request additional information from anyone claiming the transfer (for example, extra screenshots, transaction IDs, or the primary contact identity under Section 7.4); and
  • the transfer will not accrue interest and will not be usable for launching sessions until attribution is confirmed.
  After this 30-day period, CloudDock has no contractual obligation to continue tracking or holding unclaimed transfers. Where legally and technically feasible, CloudDock may:
  • attempt to return the funds to the originating payment channel, or
  • credit or reverse the amount according to its internal risk-control and accounting policies.
• (c) Leaked Transfer Information & Disputed Ownership.
  If you leak or share your transfer information (for example, screenshots, transaction IDs, or payment references) and a third party uses that information to falsely claim a top-up:
  • you may request that CloudDock investigate the ownership of the transfer;
  • CloudDock will review available evidence in good faith (including payment records, timestamps, prior top-up history, primary contact identity under Section 7.4, and any other relevant context);
  • however, CloudDock is not responsible for losses arising from your disclosure of payment details, and is not liable to compensate multiple parties for the same transfer.
  In the event of conflicting claims over the same transfer, you agree that:
  • CloudDock’s good-faith determination of which account the transfer belongs to, or whether it should be refunded or reversed, shall be final and binding to the extent permitted by law; and
  • CloudDock may refuse to credit the transfer to any account until the dispute is resolved or may treat the transfer as unclaimed under Section 5.16.2.
• (d) Security Recommendation.
  You should never post or share full payment screenshots, transaction IDs, or other sensitive transfer details in public channels or with untrusted parties. CloudDock will only use such information to:
  • verify that a payment was made; and
  • match it to the correct account for the purpose of updating your balance.

6. Education Programs & Discounts

6.1 Eligibility (Individuals & Organizations).
CloudDock offers education pricing and education-only GPU groups for qualifying users:

• Individuals: K–12 and higher-education teachers, lecturers, teaching assistants, and students currently enrolled in higher education (college-level or above) may apply for individual “education discount” status.
• Organizations / clubs: Recognized school clubs, labs, classes, or departments may apply for organization-level education arrangements.

Unless otherwise stated in a written agreement, all accounts are still opened as individual accounts (see Section 7.1). An “organization” account is simply an individual account operated on behalf of an organization by an authorized person.

6.2 Verification Documents.
To apply for education status, CloudDock may require one or more of the following:

• Teachers / staff: institutional email domain, staff/teacher ID card, or official employment letter;
• Students: student-ID card photo, institutional email, or enrollment verification.

CloudDock may request updated documentation at renewal or any time abuse is suspected.

6.3 Education Discount (Students & Staff).
Once approved, eligible students and staff may receive an education discount on qualifying GPU groups (for example, a flat percentage off the standard hourly rate for non-EDU groups). The exact discount level and which groups are eligible may be published in the Dashboard or documentation and may be changed by CloudDock at any time, consistent with Section 5.9. Education discounts:

• may not be stacked with certain other promotions (such as bespoke deals or coupons) unless expressly allowed; and
• do not automatically apply to education-only GPU groups (see Section 6.4).

6.4 EDU-only GPU Groups (“3060 For Education™”).
The “3060 For Education™” group and any similar EDU-only GPU groups are reserved for:

• verified teachers/staff using CloudDock for genuine educational or classroom purposes; and
• approved school clubs or organizations under a written agreement with CloudDock.

Individual students may not directly access EDU-only groups. Access to these groups must be manually enabled by CloudDock support and used only for the agreed educational scope (for example, teaching, coursework, supervised projects, or club activities) and not for private or commercial workloads.

6.5 Classroom Concurrency, Reservations & Organization Terms.
After submitting a complete lesson plan, syllabus, or project description, educators or school clubs may request:

• higher concurrency limits during specific time windows;
• reserved launch windows for certain GPU groups; or
• other special arrangements.

Any such concurrency, reservation quotas, or additional rights will be documented in a separate written agreement or order form. In case of conflict, that written agreement prevails for the specific organization program, while these Terms otherwise remain fully applicable.

6.6 Validity, Renewal Cycle & Annual Reset.
Education status (for both students and staff) is typically valid for up to one year. In addition:

• Education discount eligibility is reset annually on or after 1 August (00:00 UTC).
• CloudDock may process renewals slightly later than 1 August for operational reasons, but will not apply a new annual education status earlier than 1 August (00:00 UTC).
• You must re-verify your eligibility each year to continue receiving education pricing or EDU-group access.

6.7 Abuse, One-ID-One-Account Rule & Sanctions.

• (a) One ID = One account.
  Each unique education ID (including student IDs and teacher/staff IDs) may be bound to only one CloudDock account at a time. You may not use the same education ID to obtain or share education discounts across multiple accounts.
• (b) Linked-account abuse.
  If CloudDock reasonably determines that the same education ID has been used to approve or support multiple accounts (for example, one person registering several “student” accounts), CloudDock may:
  • suspend or terminate any or all affected accounts;
  • permanently revoke education-eligibility for that ID; and
  • confiscate remaining balances associated with those accounts to the extent permitted by law.
• (c) Misuse of education pricing or EDU groups.
  Using education discounts or EDU-only GPU groups for clearly non-educational, private, or commercial purposes (for example, reselling capacity, running unrelated business workloads, or lending the account to non-eligible users) is considered abuse. CloudDock may:
  • revoke education status;
  • remove access to EDU-only GPU groups;
  • retroactively adjust or deny discounts; and
  • take enforcement actions under Sections 4.13 and 7.5.

6.8 Corporate / Enterprise Misuse.
Enterprise or organizational accounts (including those opened under an education agreement) must not be used to mask purely personal or unrelated commercial work under the guise of “education.” Using a corporate or institutional account to obtain education pricing for private projects, or letting non-eligible individuals use that account, is prohibited and may result in suspension, loss of discounts, and other enforcement actions.

6.9 Display & Pricing.
Once education status is approved:

• the Dashboard will display any applicable education pricing for the logged-in user;
• EDU-only GPU groups will appear only for users with the required teacher/organization rights; and
• changes to eligible groups or discount levels may be reflected in real time without prior notice, subject to Section 5.9.

6.10 Data Retention for Education Verification.
For education-status verification, CloudDock may retain:

• name, school or institution, education ID (student or staff ID; typically stored in plaintext for anti-abuse purposes), and status/expiry dates;
• copies of ID photos or documents for up to thirty (30) days after approval, after which such images are deleted;
• minimal metadata about the fact and timing of prior approvals, to prevent repeated abuse.

These records are kept only as long as necessary to operate and protect the education program, in line with the Privacy Policy.

6.11 Age Alignment.
Student pricing is intended for higher-education students. In jurisdictions where the local age of majority or other legal requirements are higher (for example, 18+), CloudDock will only provide the Service and apply education discounts to users who meet those local legal age requirements.

6.12 Cross-Border Use & Enforcement.
Education programs are available globally, subject to compliance checks, sanctions rules, and risk control. CloudDock may refuse, restrict, or terminate access to education discounts or EDU-only GPU groups for any user, ID, or organization that, in CloudDock’s reasonable judgment, violates these education terms, applicable law, or related agreements. Sanctions may include revocation of education status, removal from EDU-only groups, suspension of accounts, and other measures allowed under these Terms.

7. Account Ownership, Names & Limitations

7.1 License Nature.
Your CloudDock account is licensed, not sold. You are granted a personal, non-exclusive, non-transferable, revocable license to access and use the Service in accordance with these Terms. Legal ownership of the account and underlying infrastructure remains with CloudDock.

7.2 Credential Security, Presumption of Control & Compromised Contacts.
You are solely responsible for:

• safeguarding your login credentials (username, password, security question answers); and
• securing your primary contact channel (for example, the payment sender identity, email, or messaging handle used for support and recovery; see Section 7.4).

To the maximum extent permitted by law:

• CloudDock is entitled to presume that all actions taken from your logged-in account, including launches, extensions, installations from the CloudDock App Store, and in-service communications, are authorized by you, unless and until you provide credible evidence of unauthorized use;
• if your primary contact channel or email is compromised and an attacker uses it to reset your password, change settings, or send instructions to CloudDock support, CloudDock is not liable for resulting account changes, content posted, or consequences, as long as CloudDock reasonably believed it was dealing with the legitimate account holder at the time.

If illegal, infringing, or seriously offensive content is sent, uploaded, or generated from your account or via an App Store app associated with your account, it is presumed to be your responsibility, even if you later claim the account was “hacked,” unless you can provide sufficient evidence of compromise and timely notification to CloudDock. You may be held fully responsible for such content, including potential legal liability under applicable law.
CloudDock will, however, make reasonable efforts to assist you in:

• improving account security (for example, by publishing security guidance or enabling additional protections); and
• freezing or restricting an account once you report a suspected compromise, consistent with operational and legal constraints.

7.3 Two-Factor Authentication (2FA).
CloudDock does not currently require 2FA but reserves the right to introduce optional or mandatory 2FA or similar security measures in the future. If enabled, you must keep any 2FA devices or tokens secure. Failure to do so may result in the same consequences as compromised passwords (see Section 7.2).

7.4 Primary Contact Identity & Recovery.
The social account, payment sender identity, email address, or other contact method first used to complete a successful top-up or substantive support interaction may be recorded as your primary contact identity. CloudDock may rely on that identity to:

• verify you during recovery;
• accept account-change instructions (including resets); and
• deliver important notices.

If you later lose control of this primary contact identity, you must inform CloudDock as soon as possible. Until you do so, CloudDock may reasonably treat instructions from that channel as authorized. CloudDock is not responsible for misuse or damage caused by a compromised primary contact identity prior to your report, but will use reasonable efforts to assist in locking or recovering the account thereafter.
Upon verified provision of a new contact method, CloudDock may update or transfer the primary contact identity or allow co-management, in its discretion.

7.5 Termination, Right to Refuse Service & Balance.
CloudDock may suspend or terminate accounts at any time where it reasonably believes there is:

• a violation of these Terms or the AUP;
• abuse, fraud, or chargeback risk;
• legal or regulatory requirements; or
• other legitimate business or security concerns.

CloudDock also reserves the right, subject to applicable law, to refuse to open or continue servicing any particular account or user, even in the absence of a specific violation, for example where the behavior toward staff is abusive or where risk is deemed unacceptable.
Consequences may include:

• temporary suspension or permanent termination of the account;
• revocation of discounts or education status;
• forfeiture of remaining balances where permitted by law (particularly for intentional abuse or fraudulent behavior); and/or
• reporting to relevant authorities.

If CloudDock terminates an account without fault on your part, unused prepaid balance may be refunded as described in Section 5. If termination is due to your fault, CloudDock may decline to refund any remaining balance, consistent with applicable law.

7.6 Account Deletion.
Self-service deletion is not currently available. Requests for closure or deletion may be submitted via support. CloudDock will process such requests in line with applicable laws and the Privacy Policy. Certain minimal records (for example, anti-abuse logs, compliance data, and accounting records) may be retained even after account closure, as permitted by law.

7.7 Subletting, Sharing & Resale.
You may not sublet, resell, or mass-operate accounts on behalf of others. Accounts are intended for individual use. Lending your account, sharing credentials, or reselling capacity in ways that bypass CloudDock’s pricing, education programs, or enterprise offerings is prohibited and may result in suspension, removal of discounts, and other enforcement actions.

7.8 Payment Source & Discounts.
Using the same payment source (for example, the same bank account or Zelle identity) to top up multiple accounts is not inherently a violation. However:

• discount qualifications (including education discounts and bespoke pricing) apply only to the individually approved person or ID; and
• you may not use a single education or eligibility proof to support multiple accounts (see Section 6.7).

Circumvention of discount rules is treated as abuse of the relevant program and may trigger revocation of benefits and broader enforcement under Sections 4.13 and 6.7.

7.9 Account Names, Security Questions & Offensive Content.
Your account name, display name, and security question(s) must not contain obvious slurs, hateful or harassing wording, or other seriously offensive content, and must not use reserved or system-reserved terms (for example, pretending to be “CloudDock Support” or similar).
CloudDock may, in its reasonable discretion:

• change or sanitize your account name if it contains offensive or reserved wording; and/or
• reset or require you to change security questions that contain offensive content or violate policy.

After such a change, CloudDock will endeavor to notify you using your bound contact method (such as Dashboard notifications or your primary contact identity), but may implement the change immediately if necessary for safety or operational reasons.

7.10 Responsibility for Third-Party Apps & Terms (App Store).
When you install or use any third-party app, model, or integration from the CloudDock App Store or similar catalog:

• you are entering into a separate relationship with that third-party developer under their own terms of service, license, and privacy policy (see Section 4.11);
• CloudDock is not a party to that separate contract and does not guarantee your compliance with it.

To the maximum extent permitted by law:

• any use of a third-party app or model from your account—including actions performed by scripts, automation, or other individuals you allowed to access your environment—is presumed to be your use, unless you can provide convincing evidence of unauthorized access as described in Section 7.2;
• if your use of a third-party app or model violates the third party’s terms or licenses, that dispute is between you and the third-party developer, and CloudDock is not responsible for resulting claims, penalties, or losses.

If your use of a third-party app also violates law or these Terms (for example, by generating unlawful or abusive content), CloudDock may still take enforcement action under Sections 4.13 and 7.5, regardless of any separate dispute between you and the app developer.

8. Legal & Jurisdiction

8.1 Governing Law & Courts.
These Terms and any dispute or claim arising out of or in connection with them are governed by the laws of the State of California, U.S.A., without regard to its conflict-of-law principles. The parties agree to the exclusive jurisdiction of the state and federal courts located in California for all disputes arising out of or relating to the Service, subject to the negotiation requirement in Section 8.2.

8.2 Negotiation First.
Before commencing any lawsuit, the parties must attempt in good faith to resolve the dispute informally for at least fourteen (14) days after one party provides written notice of the dispute to the other (via the contact channels described in Section 20). If no resolution is reached within this period, either party may proceed to litigation in accordance with Section 8.1.

8.3 Class Action & Jury Waiver.
To the fullest extent permitted by law, both you and CloudDock:

• waive any right to participate in a class action, class arbitration, or similar representative proceeding; and
• waive any right to a jury trial in any dispute arising out of or relating to the Service or these Terms.

8.4 Severability & Survival.
If any provision of these Terms is held invalid or unenforceable by a court of competent jurisdiction, that provision will be enforced to the maximum extent permissible and the remaining provisions will remain in full force and effect. Provisions relating to fees and taxes, privacy and monitoring, limitations of liability, indemnities, governing law, jurisdiction, and intellectual-property rights will survive termination of your account or cessation of the Service.

8.5 Export Controls & Sanctions.
You represent and warrant that you are:

• not located in a jurisdiction that is subject to comprehensive U.S. embargoes or sanctions;
• not a person or entity listed on any U.S. or other applicable sanctions or restricted-party list; and
• not using the Service on behalf of any such sanctioned or restricted party.

You agree not to export, re-export, or transfer the Service, or any portion thereof, in violation of applicable export-control and sanctions laws.

8.6 Force Majeure (Including Large-Scale Network Attacks & DDoS).
CloudDock will not be liable for any delay, degradation, or unavailability of the Service that results, in whole or in part, from force majeure events, including but not limited to:

• natural disasters (such as earthquakes, fires, floods, or storms);
• power outages, physical infrastructure failures, or regional network interruptions;
• major incidents or outages affecting cloud providers, data centers, ISPs, or backbone networks on which CloudDock reasonably depends;
• government actions, regulatory restrictions, or changes in law;
• labor disputes, strikes, or civil unrest; and
• large-scale cyber incidents, including distributed denial-of-service (DDoS) attacks or other malicious traffic or exploits that materially disrupt CloudDock’s own systems or those of its upstream providers, even if such attacks are directed at CloudDock or its IP space specifically.

Where a force majeure event interrupts a running session, any session-level remedies are limited to those described in Section 5.5 (Non-User Interruption & 24-Hour Cap) and Annex A (SLA & Credits). Downtime caused by force majeure is excluded from SLA calculations under Annex A and does not create any additional liability for CloudDock beyond the credits or refunds expressly described in these Terms.

9. Privacy, Tokens & Monitoring

9.1 Data Categories
CloudDock handles several broad categories of data when you use the Service, including:

• Account data: username security questions , hashed password (never stored in plain text), basic profile fields, and recovery factors (such as security answers stored in hashed or encrypted form).
• Runtime telemetry: limited technical metrics needed to operate and protect the platform (for example CPU/GPU utilization, memory/VRAM usage, process states, and similar);
• Audit & security data: watchdog logs, seizure artifacts for abnormal events (see Section 3), IP addresses, and device fingerprints collected for anti-abuse;
• Education verification data: education IDs (student or staff), institution name, and expiry dates, along with short-term storage of ID photos or documents (see Section 6.10).

More detailed information about these categories and how they are handled is provided in the CloudDock Privacy Policy, which forms part of these Terms.

9.2 Telemetry & Runtime Monitoring.
CloudDock uses runtime telemetry and behavioral monitoring only to the extent reasonably necessary to:

• operate and schedule resources;
• maintain stability and capacity planning; and
• detect, investigate, and prevent abuse or security incidents (see Section 3 and Section 4).

Routine telemetry for normal sessions is generally used in aggregated or short-lived form and is not retained longer than needed for operational and security purposes. Normal, successful shutdowns do not retain shell/process logs or file contents (see Section 3.1).

9.3 Normal vs. Abnormal Session Logs.
For normal shutdowns, CloudDock does not retain detailed shell command logs or full process histories from your container. For abnormal events (for example crashes, watchdog terminations, or serious suspected violations), CloudDock may seize read-only snapshots and associated audit logs as described in Section 3, subject to the retention periods and security measures set out there and in the Privacy Policy.

9.4 Tokens, Cookies & Session Authentication.
CloudDock uses JSON Web Tokens (JWTs) and, in some cases, cookies to manage sessions and authenticate access:

• Application login typically uses JWTs stored in a security-conscious way as part of the web session.
• When you connect to a remote desktop or similar session, CloudDock may set short-lived cookies whose sole purpose is to authenticate that session and allow the reverse proxy or remote-display stack to verify your identity.
• These cookies are designed to expire automatically when the session ends or shortly thereafter and are not used for cross-site tracking, behavioral advertising, or third-party ad profiling.

Token and cookie use is limited to authentication, session management, and security; it is not used to build third-party advertising profiles.

9.5 Third-Party Infrastructure (Including Cloudflare & cloudflared).
CloudDock uses third-party providers to deliver and protect the Service, which may include:

• hosting and compute (for example cloud providers or data-center operators);
• content delivery, DDoS protection, and firewalling (for example Cloudflare, including cloudflared tunnels or similar mechanisms); and
• basic logging and operational monitoring.

These providers may process IP addresses, request headers, and limited connection metadata in order to deliver and secure traffic. CloudDock engages such providers under written terms, discloses only what is technically necessary, and applies a least-privilege approach. Details and provider lists are further described in the Privacy Policy and may be updated from time to time.

9.6 Anti-Abuse IP & Device Fingerprints (Login/Registration Only).
For security purposes, CloudDock may collect and process IP addresses and limited device or hardware fingerprints in connection with:

• registration,
• login / authentication, and
• account recovery or password reset flows.

These identifiers are not collected for general browsing or normal in-service use, and are used only to:

• detect and mitigate abuse (for example, excessive registration attempts, credential-stuffing, or automated attacks);
• apply IP-level or device/hardware-level blocks or rate limits where necessary; and
• protect CloudDock and other users from fraud, account takeover, or large-scale attacks.

CloudDock does not use these identifiers for advertising or unrelated profiling. Subject to applicable law and legitimate security needs, such security-related IP and device-fingerprint records are generally retained for no more than 180 days, after which they are deleted or anonymized on a rolling basis. CloudDock applies a least-privilege, need-to-know approach to who can access this data.

9.7 Data Access, Export & Requests.
Self-service data export tools are not currently provided. Depending on your jurisdiction and applicable law, you may be able to:

• request access to certain account information;
• request correction or deletion; or
• ask questions about how CloudDock handles security and anti-abuse data.

Requests are handled through the support channels described in the Privacy Policy and Section 20, and must be balanced against CloudDock’s obligations to maintain logs needed for security, anti-abuse, and compliance.

9.8 Post-Termination Retention.
After your account is closed or terminated, CloudDock may retain:

• normal operational records and accounting data for statutory periods;
• security and abuse-related artifacts (including logs from abnormal events) for the retention periods described in Section 3 and the Privacy Policy; and
• minimal records indicating that an account or education ID has been permanently restricted, to prevent re-registration abuse.

CloudDock will not retain data longer than necessary for the purposes described in these Terms and the Privacy Policy, except where longer retention is required by law.

9.9 Minors & Age Restrictions.
The Service is intended for users who meet the minimum age requirements set out in Section 1.2. CloudDock does not knowingly collect personal information from children under the relevant age of consent. If CloudDock learns that an underage user has created an account in violation of these Terms, CloudDock may delete the account and handle the associated data in accordance with applicable law and the Privacy Policy.

10. Liability, Disclaimers & Indemnity

10.1 General Disclaimer (“AS IS” / “AS AVAILABLE”).
To the maximum extent permitted by applicable law, the Service is provided on an “AS IS” and “AS AVAILABLE” basis. CloudDock and its owners, employees, and partners:

• make no warranties or representations of any kind, whether express, implied, or statutory, including but not limited to warranties of merchantability, fitness for a particular purpose, non-infringement, quiet enjoyment, or suitability for your specific use case;
• do not guarantee that the Service will be uninterrupted, timely, secure, or error-free, or that any defects will be corrected; and
• do not warrant that any particular GPU group, image, app, model, or feature will continue to be available, or will remain compatible with your workflows, for any specific period of time.

You understand that you use CloudDock at your own risk, including any risks associated with running third-party software, open-source components, or models inside the containers.

10.2 No Responsibility for User Content, Datasets or Third-Party Apps.
CloudDock does not and cannot monitor all content, datasets, or applications you run inside your container. To the maximum extent permitted by law:

• you are solely responsible for all data, prompts, models, weights, outputs, and other content you upload, generate, train, or distribute using the Service;
• CloudDock is not liable for any consequences arising from your use of third-party apps, models, or integrations, including those obtained from the CloudDock App Store, nor for your compliance with their terms (see Sections 4.11, 4.12, 7.10, and 11.4);
• if a third-party developer or rights holder brings a claim against you based on your use of their app/model, that dispute is between you and them, not CloudDock.

10.3 Data Loss, Downtime & Backup Duty.
You acknowledge and agree that:

• compute workloads can fail, sessions can end unexpectedly, and data stored solely inside a running container may be lost due to crashes, watchdog actions, force majeure events, or other circumstances described in Sections 3, 5, and 8;
• you have an explicit duty to back up important data at least once every 24 hours (see Section 5.5), and CloudDock is not responsible for any loss of data older than that 24-hour window;
• any refunds or credits for non-user interruptions are limited strictly to those described in Section 5.5 (including the 24-hour cap) and Annex A (SLA & Credits).

CloudDock is not liable for losses arising from:

• your failure to maintain appropriate backups;
• use of experimental or beta features;
• reliance on specific uptime or performance beyond what is explicitly described in Annex A.

10.4 Limitation of Liability (Cap).
To the maximum extent permitted by applicable law, the aggregate liability of CloudDock for any and all claims arising out of or relating to these Terms or the Service (whether in contract, tort, negligence, strict liability, or any other theory) is limited to the total amount you actually paid to CloudDock for the Service in the three (3) months immediately preceding the event giving rise to the claim.
If you have used the Service for less than three months, the cap will be the total amount you have actually paid to CloudDock for the Service up to the date of the event.
This limitation applies in the aggregate, not per incident or per claim.

10.5 Exclusion of Indirect & Certain Other Damages.
To the maximum extent permitted by law, CloudDock will not be liable for any:

• indirect, incidental, consequential, special, exemplary, or punitive damages;
• loss of profits, revenue, business, goodwill, opportunity, or anticipated savings;
• loss, corruption, or disclosure of data (beyond the limited remedies expressly provided in Sections 5.5 and Annex A); or
• costs of substitute services, equipment, or infrastructure.

These exclusions apply even if CloudDock has been advised of the possibility of such damages, and even if any limited remedy fails of its essential purpose.
Some jurisdictions do not allow the exclusion of certain damages; in those cases, this Section applies only to the extent allowed by the laws of that jurisdiction and does not exclude liability where it is prohibited (for example, for certain kinds of gross negligence or willful misconduct, if applicable law requires liability).

10.6 Sole Contractual Remedies; Relationship to SLA.
Except where mandatory law provides additional non-waivable rights:

• your sole and exclusive contractual remedies for Service unavailability, instability, or interruptions are the refunds and credits described in Section 5 and Annex A;
• you are not entitled to any other monetary compensation, service extension, or remedy for downtime or performance issues beyond what those sections provide.

Nothing in Annex A or this Section creates a guarantee of any particular availability level; Annex A only defines when and how certain credits may be applied if the measured availability falls below the stated target.

10.7 User Indemnity.
To the maximum extent permitted by law, you agree to defend, indemnify, and hold harmless CloudDock and its owners, employees, and partners from and against any and all third-party claims, damages, liabilities, costs, and expenses (including reasonable attorneys’ fees) arising out of or related to:

• your use of the Service, including any content, datasets, or models you upload, train, or generate;
• your violation of these Terms, the AUP (Section 4), or any applicable law or regulation;
• your breach of any third-party license, terms of service, or privacy policy, including those of App Store developers or model providers; or
• any content or conduct arising from your account, except to the extent caused by CloudDock’s own willful misconduct or gross negligence where such liability cannot be excluded by law.

CloudDock may, at its own cost, choose to participate in the defense of any matter subject to indemnification, but this does not relieve you of your indemnity obligations.

10.8 Beta, Pre-Release & Experimental Features.
From time to time, CloudDock may offer:

• beta or pre-release GPU types, container images, or features; and/or
• experimental tooling, integrations, or monitoring mechanisms.

Such features may:

• be subject to stricter usage limits or temporary restrictions;
• be changed, suspended, or discontinued at any time without notice; and
• be less stable or less secure than generally available features.

To the maximum extent permitted by law, additional disclaimers apply to these beta/experimental components: they are offered without any uptime or performance commitments, and any use of them is entirely at your own risk. Unless explicitly stated otherwise in writing, the limitation of liability and exclusions in this Section 10 apply fully to all beta and experimental features.

11. User Content, Third-Party Licenses & CloudDock App Store

11.1 No Ownership Transfer.
CloudDock does not claim ownership of the content, data, models, or outputs you create or upload while using the Service. As between you and CloudDock, you retain whatever rights you already have in your own content.

11.2 Minimal Necessary License to CloudDock.
You grant CloudDock a worldwide, non-exclusive, royalty-free, revocable, limited license solely to:

• (a) provide and operate the Service (including running, storing, copying, and transmitting your workloads as technically necessary);
• (b) maintain security and stability (including abnormal-event retention and auditing as described in Section 3); and
• (c) fulfill legal and compliance obligations (including responding to valid legal process).

CloudDock may create and retain read-only copies or snapshots of your content only as necessary for these purposes.

11.3 Compliance Removal & Enforcement.
If CloudDock receives a legally valid notice, or has a good-faith belief, that any content or workload:

• is unlawful, infringing, or violates these Terms; or
• poses a serious risk to the security or stability of the platform,

CloudDock may remove or restrict access to that content, seize or terminate the relevant instance, or take other enforcement actions under Section 4.13 and Section 7.5.

11.4 Third-Party Licenses (Open Source, Models & App Store Items).
Pre-installed or otherwise available third-party software, open-source components, models, and weights—whether accessed via CloudDock images or installed through the CloudDock App Store—are governed by their respective upstream licenses and terms. You must read and comply with those licenses, including any:

• RAIL or similar model-use restrictions;
• non-commercial or research-only limitations;
• copyleft requirements (for example, AGPL network clauses); and
• any attribution, redistribution, or source-disclosure conditions.

CloudDock merely provides technical hosting, metadata, and installation mechanisms for such third-party items and does not become the legal publisher of those third-party works, except where CloudDock itself is the author or has explicit redistribution rights. CloudDock assumes no liability for your violations of third-party licenses. If commercial or additional licensing is required, you must obtain it directly from the rights holder.

11.5 Role of CloudDock App Store (Source Pointers, Not General Redistributor).

• (a) Source and installation only.
  Except where explicitly stated otherwise, the CloudDock App Store functions primarily as an index and installer that:
  • surfaces metadata (name, description, screenshots, tags, etc.);
  • provides links or configuration to fetch packages from original sources (such as system repositories, pip/conda, Git, model hubs, or vendor sites); and
  • orchestrates installation commands inside your container.
  For third-party apps and models, CloudDock generally acts as a convenience layer pointing to upstream sources, not as a separate redistribution service.
• (b) CloudDock-owned and authorized items.
  CloudDock may publish and redistribute:
  • CloudDock-owned or CloudDock-branded apps, tools, scripts, images, and models; and
  • third-party packages or models for which CloudDock has obtained explicit distribution or bundling rights.
  Such items are provided under the license terms specified in the App Store listing or accompanying documentation.
• (c) Your downstream redistribution.
  If you choose to download, modify, or re-distribute any app, model, or other component obtained via the CloudDock App Store:
  • you are solely responsible for ensuring your redistribution complies with the relevant upstream license;
  • CloudDock does not grant you any additional rights to redistribute third-party code or models beyond what their own licenses provide; and
  • CloudDock is not liable for any claims arising from your downstream distribution or hosting of those components.

12. Branding, Proprietary Materials & IP Use

12.1 Use of CloudDock Names, Marks & Brand.
Without CloudDock’s prior written consent, you may not:

• use CloudDock’s trade names, trademarks, service marks, logos, or any confusingly similar marks;
• present yourself as an official CloudDock representative, partner, or agent; or
• imply endorsement, sponsorship, or partnership by CloudDock.

Factual statements such as “using CloudDock” or “hosted on CloudDock” are permitted, provided they are accurate and not misleading. CloudDock will not use your logo or brand for public promotion without your consent, except where required by law or regulation.

12.2 CloudDock Front-End, Back-End, Apps & Official Materials (No Unauthorized Redistribution).

• (a) Protected materials.
  Unless clearly released under a separate open-source or content license by CloudDock, the following are considered proprietary materials of CloudDock or its licensors:
  • the CloudDock front-end and back-end code (including HTML/CSS/JS, APIs, server-side logic, dashboards, launchers, App Store UI, Training Center UI, etc.);
  • CloudDock’s internal tools and apps shipped inside containers, including CloudDock-branded GUIs, utilities, installers, and management scripts;
  • CloudDock’s official documentation, user guides, SOPs, knowledge-base articles, and similar written materials;
  • CloudDock’s official media assets, including logos, product images, screenshots, promotional graphics, tutorial videos, audio content, and other marketing or training materials; and
  • any other CloudDock-owned source code, binaries, or assets that are not expressly licensed for public redistribution.
• (b) Restrictions.
  You may not, without CloudDock’s prior written permission:
  • copy, reproduce, publicly distribute, mirror, or host these proprietary materials outside your own CloudDock session in a way that makes them publicly available;
  • publish or share CloudDock proprietary source code (including decompiled or reverse-engineered versions) for the front-end, back-end, or CloudDock-owned apps and tools;
  • bulk-export or repackage CloudDock’s documentation, screenshots, or media for use in other products or services; or
  • use CloudDock’s code or official materials as the basis for a competing service without an appropriate license.
• (c) Open-source exceptions.
  If CloudDock explicitly releases certain code or materials under an open-source or other public license, your rights and obligations will be governed by that specific license. In case of conflict, the more permissive explicit license granted by CloudDock for that code or material (for example, a public Git repository under MIT/Apache-2.0) will control over the restrictions in this Section for that item only.

12.3 App Source Code Inside Containers.
The source code of CloudDock-owned applications or tools installed inside your container is proprietary unless explicitly labeled otherwise. You may inspect and use such code only for the purposes of operating the Service for yourself, within the scope of these Terms. You may not:

• copy that code onto public repositories, file-sharing sites, or similar services;
• sell, sublicense, or repackage that code as your own product; or
• distribute it to third parties in violation of this Section.

The source code of third-party apps or frameworks inside your container is governed by their own licenses (see Section 11.4); CloudDock does not override those rights, and you must follow those upstream licenses when redistributing third-party code.

12.4 Enforcement, Remedies & Final Discretion.
Unauthorized use or redistribution of CloudDock’s proprietary code, documentation, media, or other protected materials may result in:

• takedown requests and legal action (including copyright, contract, or other IP claims);
• immediate suspension or termination of your CloudDock account;
• revocation of discounts or special programs; and
• forfeiture of remaining account balance, to the extent permitted by law, in cases of deliberate or commercial misuse.

CloudDock reserves the right, at its sole reasonable discretion and subject to applicable law, to determine the appropriate enforcement measures for violations of this Section 12, including whether to pursue legal remedies in addition to or instead of account-level sanctions.
Nothing in this Section limits your rights under applicable copyright exceptions (such as fair use/fair dealing where recognized by law) or any explicit open-source or content license granted by CloudDock for specific materials.

13. Service Changes, Images & Container Restarts

13.1 Service Changes & Deprecation.
CloudDock may at any time modify, replace, or discontinue any feature, container image, or GPU type. Material changes will be preceded by reasonable notice where feasible; urgent changes (for example security patches) may take effect immediately. Pricing and in-progress sessions are governed by Section 5.9. Compatibility of historical images, drivers, or dependencies is not guaranteed.

13.2 Image Updates; No Rollback Right.

• (a) Ongoing updates.
  CloudDock regularly updates container images, drivers, and base environments (for example to apply security patches, fix bugs, or improve performance). Once an image has been updated or replaced in production, CloudDock:
  • is not obligated to keep older versions available; and
  • has no duty to provide rollback or custom pinning to prior image versions, unless expressly agreed in a separate written agreement.
• (b) Running containers vs. new starts.
  If you already have a container running when an image is updated:
  • your running container may continue using the older in-memory/on-disk image until it is stopped, destroyed, or otherwise ends according to Section 3;
  • any new container you start (including after you manually stop/restart) will be based on the latest available image for that GPU group and configuration. You cannot require CloudDock to start a new container from an obsolete image.

13.3 Container Restart & Data Responsibility.

• (a) User-initiated restarts.
  If you choose to restart a container (for example through the UI, an API, or support request), you acknowledge that:
  • a restart may involve starting a new container instance from the current image;
  • any data stored solely inside the prior container filesystem (including /home, temporary directories, and application data paths) may be lost or reset; and
  • CloudDock is not responsible for preserving or restoring data inside the container across restarts, except where explicitly guaranteed in a separate agreement.
• (b) Backup obligation.
  It is your responsibility to back up important data before restarting a container or making changes that could affect storage. To the maximum extent permitted by law, CloudDock disclaims any liability for loss of in-container data resulting from:
  • your own restart actions;
  • image updates;
  • maintenance events described in Section 14; or
  • normal container lifecycle operations (start/stop/destroy) under these Terms.

13.4 Third-Party Dependencies & Breakage.
CloudDock cannot guarantee that any particular combination of third-party frameworks, drivers, CUDA versions, or apps will continue to work after updates or deprecations. If a third-party dependency breaks due to upstream changes:

• CloudDock will not be liable for resulting downtime or incompatibilities; and
• your remedies, if any, are limited to the credits and refunds described in Section 5 and Annex A.

14. Maintenance Windows, Maintenance Mode & Host Restarts

14.1 Planned vs. Emergency Maintenance; SLA.

• (a) Planned maintenance.
  CloudDock may schedule planned maintenance (for example OS upgrades, hardware checks, or image rollouts). Where feasible, CloudDock will provide at least 24 hours’ notice via in-dashboard notices or your primary contact identity (see Section 7.4).
• (b) Emergency maintenance.
  CloudDock may perform emergency maintenance without prior notice, for example to address critical security issues, hardware failures, or serious instability.
• (c) SLA treatment.
  Downtime or restrictions caused by planned or emergency maintenance are generally excluded from SLA calculations (see Annex A and Section 8.6). Your remedies are limited to those explicitly defined in Section 5 and Annex A.

14.2 Maintenance Mode for Running Orders.

• (a) Effect on current orders.
  When a machine, GPU group, or region enters maintenance mode:
  • existing orders and running containers on that resource are not automatically terminated solely by entering maintenance mode;
  • however, you will not be able to extend those orders via the “Extend” feature while maintenance mode is active.
• (b) No customer control.
  You cannot directly enable, disable, or override maintenance mode. The decision to place resources in maintenance mode is made by CloudDock for operational and safety purposes.
• (c) Interaction with pricing & refunds.
  If maintenance later results in interruption or restart, any refunds or credits are governed by Section 5.5 (including the 24-hour cap) and Annex A, and do not create additional rights.

14.3 Monthly / Long-Term Plans, Reserved Maintenance Hours & ECC Exceptions.

• (a) Reserved maintenance hours.
  For monthly or other long-term plans (for example, month-based reservations or recurring long-running orders), CloudDock reserves up to forty-eight (48) hours per calendar month as maintenance time for the underlying host(s) and infrastructure, unless a separate SLA explicitly provides otherwise.
• (b) Maintenance interval.
  As a guideline, the interval between two maintenance windows for the same long-term host or plan should generally not exceed fourteen (14) days, although actual timing may vary based on operational needs and incident response. CloudDock may, where practical, coordinate with you on suitable timings, but retains final discretion.
• (c) ECC-equipped server groups (exception).
  For server groups that are equipped with ECC RAM and ECC VRAM, CloudDock may perform maintenance in ways that attempt to minimize impact on in-container data (for example rolling restarts, live migration, or other techniques). However, no guarantee is made that all data will survive maintenance unless explicitly stated in a separate SLA.
• (d) Non-ECC server groups – data loss on maintenance.
  For server groups without ECC RAM and/or non-ECC VRAM, host-level maintenance (including OS upgrades, disk reformatting, or host restarts) may involve wiping or recreating container storage. In these non-ECC groups:
  • data stored solely inside containers may be fully lost on each maintenance event; and
  • CloudDock assumes no responsibility for preserving container data across such maintenance. You must treat these environments as ephemeral and regularly back up important data outside the container.

14.4 Advance Notice & Routine Maintenance Requests.

• (a) Advance notice before required maintenance.
  When a mandatory maintenance window is approaching the maximum recommended interval (for example close to the 14-day limit described above) for a long-term plan, CloudDock will endeavor to provide at least 24 hours’ notice to your primary contact identity before performing host-level maintenance, unless emergency conditions make this impossible.
• (b) User-requested routine maintenance.
  For long-term or monthly customers, you may request routine maintenance (for example, a preferred window for host reboot or OS updates) via support. CloudDock will use reasonable efforts to take your request into account when scheduling maintenance, but:
  • specific dates and times cannot be guaranteed; and
  • maintenance still counts toward the monthly reserved maintenance hours in Section 14.3(a).

14.5 Host Restart Requests for Monthly Customers.
Monthly or similar long-term customers may, through support, submit a request to restart a host (for example to clear GPU errors or apply configuration changes). You acknowledge that:

• the exact timing of any such restart is at CloudDock’s operational discretion;
• a host restart may result in termination or recreation of containers on that host and loss of in-container data, particularly on non-ECC groups; and
• CloudDock reserves the right to refuse or postpone restart requests where they conflict with operational stability, other users’ workloads, or security considerations.

Any host restart and resulting impact are subject to the same data-loss and refund limitations described in Sections 5.5, 10.3, 13.3, and 14.3.

15. High-Risk Use Prohibition & Operational Limits

15.1 No Use in High-Risk Environments.
You must not use the Service as a critical or irreplaceable component in any system where failure, interruption, or incorrect operation could reasonably be expected to:

• cause death or serious bodily injury;
• result in significant damage to property or the environment; or
• create major safety hazards or public disruption.

This includes, without limitation:

• life-support or life-sustaining systems;
• real-time control of aircraft, ships, trains, or other mass-transport systems;
• nuclear facilities, critical energy infrastructure, or industrial control systems;
• critical hospital or emergency-response systems;
• weapons or weapons-control systems; and
• any other environment where a reasonable professional would classify the workload as safety-critical.

15.2 Maintenance, Watchdogs & Inherent Interruptions.
You acknowledge that CloudDock is designed as a general-purpose compute and development platform, not as a certified safety-critical system. In particular:

• resources may enter maintenance mode (Section 14), during which extensions are blocked and host-level restarts may occur;
• CloudDock may perform planned and emergency maintenance with the characteristics described in Sections 8.6 and 14 (including 48-hour monthly maintenance windows for certain plans and up to 14-day intervals between host maintenance for long-term plans);
• watchdog and security mechanisms (Section 3) may terminate containers and seize images when violations or anomalies are detected;
• image and dependency updates (Section 13) may change behavior from one session to the next and do not guarantee backward compatibility; and
• force majeure events (Section 8.6), upstream outages, and large-scale attacks (including DDoS) can interrupt service even when CloudDock is operating reasonably.

Because of these operational realities, the Service is not designed or warranted for uninterrupted, deterministic operation in high-risk environments.

15.3 User Responsibility for Redundancy & Safety.
If you nevertheless choose to connect CloudDock outputs to any system that affects real-world operations, you are solely responsible for:

• implementing appropriate redundancy, validation, and safety checks;
• ensuring that failures, restarts, maintenance events, or watchdog terminations cannot directly cause safety-critical consequences; and
• complying with any industry-specific safety or certification standards that may apply.

To the maximum extent permitted by law, CloudDock:

• disclaims any liability for damages arising from prohibited high-risk use; and
• treats any such use as a material breach of these Terms, which may result in suspension or termination of your account under Section 7.5, without additional compensation beyond the limited remedies in Sections 5 and 10 and Annex A.

16. Government & Legal Requests

16.1 Legal Process & Cooperation.
CloudDock will cooperate with valid and binding legal requests (such as subpoenas, court orders, warrants, or equivalent administrative directives) in accordance with applicable law. CloudDock does not voluntarily disclose user information to private parties outside of:

• (a) what is technically necessary to operate the Service (see Section 9 and the Privacy Policy); or
• (b) situations where disclosure is required or expressly permitted by law (for example, to address imminent threats to life or serious bodily harm).

16.2 Scope & Minimization.
When responding to a legal request, CloudDock will:

• verify that the request is facially valid and issued by a competent authority;
• limit disclosure to the narrowest scope reasonably required to comply (for example, specific accounts, time ranges, or artifacts); and
• rely on existing logs and retained materials as described in Sections 3 and 9, without creating custom tracking mechanisms beyond what is necessary to fulfill the request.

CloudDock does not provide law enforcement with “backdoor” access to systems or encryption keys beyond what is legally required.

16.3 User Notification (Where Permitted).
Unless legally prohibited (for example, by a gag order or confidentiality requirement) or where notification would create a clear and imminent risk of harm:

• CloudDock will endeavor to notify the affected user that a request has been received which may involve their account or data; and
• such notice may be delayed if earlier notice would materially interfere with an investigation or create safety concerns.

Notification may be delivered via in-dashboard messages, registered email, or your primary contact identity (Section 7.4).

16.4 Data Preservation & Retention Alignment.
Upon receipt of a valid legal preservation request, CloudDock may preserve relevant data (including abnormal-event snapshots and logs) beyond the usual retention periods in Sections 3 and 9, but only for as long as legally required. Once those legal obligations expire or are lifted, preserved data will be handled in line with CloudDock’s standard retention and deletion practices.

16.5 Costs & Reimbursement.
To the extent permitted by law, CloudDock may seek reimbursement of reasonable costs (such as engineering time, storage, review, or production expenses) from the requesting authority or, where appropriate, from the user whose data is being requested, particularly in civil or private-party matters.

16.6 No Private “Evidence Requests” Outside Legal Process.
CloudDock will not disclose watchdog logs, forensic snapshots, or other internal security artifacts to private individuals solely on the basis of a private dispute. Access to such data will only be granted:

• to competent authorities acting under valid legal process; or
• in limited circumstances where applicable law requires disclosure to the user (for example, certain access rights), as described in the Privacy Policy.

17. Security Research, Bug Reports & Vulnerability Testing

17.1 No Authorization to Attack or Probe the Platform.
The Service is not an open security-testing environment. Nothing in these Terms:

• grants you permission to perform penetration testing, fuzzing, scanning, load/stress testing, or exploit-development against CloudDock’s production systems; or
• overrides the prohibitions in Section 4 (for example, scanning, network probing, and abuse of resources).

Any activity that attempts to “find bugs by breaking the rules,” stress-test red lines, or intentionally bypass technical or policy limitations is treated as a violation of these Terms, not as good-faith research.

17.2 Production-Environment Testing Ban.
You may not:

• run port scans, vulnerability scanners, or exploit toolkits against CloudDock infrastructure;
• create or route synthetic traffic for the purpose of DDoS, load testing, or rate-limit probing;
• attempt to bypass authentication, authorization, or monitoring controls; or
• use other users’ containers, tokens, or data as part of any test, even with their “consent,” unless CloudDock has given you explicit written authorization.

These activities are prohibited regardless of whether your intention is to help or harm the platform.

17.3 Good-Faith Bug Reporting During Normal Use.
CloudDock nevertheless welcomes bug reports and improvement suggestions discovered:

• incidentally, while using the Service within the rules and your own account; and
• without breaching access controls, scanning, or other prohibitions described in Section 4.

If, in the course of normal use, you believe you have found a vulnerability or serious bug:

• you should promptly report it to CloudDock through the official support or security contact channels (as published in the dashboard or documentation);
• you must not publicly disclose exploit details before CloudDock has had a reasonable opportunity to investigate and remediate; and
• you must not further escalate or weaponize the issue (for example, by automating exploitation or attempting to access other users’ data).

Provided that your actions stay within your authorized access, do not cause harm or disruption, and are reported in good faith, CloudDock will not treat such bug reporting as a violation of these Terms.

17.4 Program Changes & Future Policies.
CloudDock may, in the future:

• publish a separate vulnerability disclosure policy or
• introduce a bug bounty or similar program.

Any such program will be documented separately and may impose additional conditions. Until then, these Terms and the AUP control. Claiming to be “testing security” does not excuse conduct that violates Sections 3, 4, 8, or 9.

18. API Terms & Future Changes

18.1 API Availability & Relationship to These Terms.
CloudDock may provide one or more APIs (for example, for management, monitoring, or integration with other tools). Unless and until separate API-specific terms are published:

• your use of any CloudDock API is fully governed by these Terms, including the AUP (Section 4), privacy and monitoring provisions (Section 9), and liability limitations (Section 10); and
• any API access is provided at CloudDock’s discretion and may be modified, limited, or withdrawn at any time without notice.

If CloudDock later publishes API-specific terms, those will apply in addition to these Terms. In case of conflict, the API-specific terms will control for API usage only, while these Terms continue to govern the rest of the Service.

18.2 Keys, Authentication & Rate Limits.
If API keys or tokens are issued:

• each key or token is personal, non-transferable, and revocable;
• you must keep keys confidential and not embed them in public code repositories or client-side code;
• CloudDock may set or adjust rate limits, quotas, and usage caps at any time; and
• attempting to circumvent throttling, rate limits, or access controls (for example by key farming or rotating IPs) is a violation of Section 4 and may result in immediate revocation.

18.3 Permitted Use & Prohibited Activities.
API usage must:

• comply with all restrictions in these Terms (including the high-risk-use prohibition in Section 15);
• not be used to build a competing service that clones substantial CloudDock functionality or UI without a separate written agreement; and
• not be used to abuse, overload, or reverse-engineer CloudDock systems.

Public benchmarking or publishing performance numbers that rely on abusive usage patterns (for example, intentional overloads or violation of rate limits) is prohibited.

18.4 Suspension & Future Updates.
CloudDock may suspend or terminate your API access:

• for any breach of these Terms, including Section 4 or this Section 18;
• when required by law or at the request of competent authorities; or
• for risk-control or operational reasons.

If CloudDock materially expands or changes the API offering (for example, adding programmatic access to billing, queue controls, or remote desktop), CloudDock may:

• update this Section 18 and related documents; and
• give reasonable notice of any new or changed API-specific terms.

Continued use of the APIs after such changes take effect constitutes acceptance of the updated API terms.

19. Assignment & Successors

19.1 No Assignment by You Without Consent.
You may not assign, transfer, or delegate any of your rights or obligations under these Terms—whether by contract, operation of law, or otherwise—without CloudDock’s prior written consent. Any attempted assignment in violation of this Section is void.

19.2 Assignment by CloudDock.
CloudDock may assign or transfer these Terms, in whole or in part, without your consent:

• to an affiliate or group entity; or
• in connection with a merger, acquisition, corporate reorganization, sale of assets, or similar transaction.

CloudDock will provide reasonable notice of any such assignment through one or more of the official notice channels described in Section 20.3. After such assignment, the assignee will assume CloudDock’s rights and obligations under these Terms with respect to the assigned portion.

19.3 Binding Effect.
Subject to the foregoing, these Terms are binding upon and inure to the benefit of the parties and their respective permitted successors and assigns. No third party is intended to be a beneficiary of these Terms except as expressly stated.

20. Entire Agreement; No Waiver; Notices; Relationship

20.1 Entire Agreement & Order of Precedence.
These Terms, together with any annexes (including Annex A and Annex B), policies explicitly incorporated by reference, and any separately executed written agreement between you and CloudDock, constitute the entire agreement between the parties regarding the Service and supersede all prior or contemporaneous understandings, proposals, or representations, whether oral or written.
In the event of any conflict:

1. a separately signed written agreement (if any) between you and CloudDock takes precedence;
2. then these Terms (including Annexes);
3. then any product-specific or API-specific terms;
4. then FAQs or other non-contractual documentation.

20.2 No Waiver.
Failure or delay by CloudDock to enforce any provision of these Terms does not constitute a waiver of that provision or of any other provision. Any waiver must be in writing and expressly state that it is a waiver. A one-time waiver does not constitute a continuing or future waiver.

20.3 Notices & Official Announcements.

• (a) Notices from you to CloudDock.
  Formal notices to CloudDock regarding legal matters, disputes, or termination must be sent via officially published channels or to the email address designated for legal notices (for example, legal@[your-domain]) as specified in the documentation or on the website.
• (b) Notices from CloudDock to you.
  CloudDock may provide notices, updates, and official statements—including changes to these Terms, Privacy Policy updates, SLA announcements, or material service changes—through one or more of the following official channels:
  1. Email sent to the email address associated with your account (if provided);
  2. In-dashboard notices, banners, or notifications within the CloudDock interface; and/or
  3. Messages sent via your primary contact identity as defined in Section 7.4 (for example, the social or messaging account you use for top-up and support interactions).
  Notices delivered via any of the above channels will be deemed received when:
  • sent by CloudDock (for email or primary contact identity), or
  • first made reasonably available to you (for in-dashboard notices).
  You are responsible for keeping your contact details up to date and for regularly checking the dashboard notices.

20.4 Relationship of the Parties.
Nothing in these Terms creates any partnership, joint venture, employment, fiduciary, or agency relationship between you and CloudDock. You and CloudDock remain independent contracting parties. You may not represent that you are an employee, agent, or representative of CloudDock, and you have no authority to bind CloudDock in any way.

20.5 Headings.
Section and subsection headings are provided for convenience only and do not affect the interpretation or meaning of the corresponding provisions.

21. Open-Source Notices & Third-Party Components

21.1 Third-Party Components & Licenses.
The Service and its container images include numerous third-party components, libraries, models, and tools, each of which is governed by its own license (for example, MIT, Apache-2.0, GPL/AGPL, RAIL, or proprietary EULAs). A non-exhaustive overview is provided in Annex B – Open-Source & Third-Party Notices.

21.2 No Modification of Upstream Terms.
Nothing in these Terms is intended to:

• override or reduce the rights granted to you under applicable open-source licenses; or
• expand your rights beyond what those licenses allow.

Where there is a direct conflict between a specific open-source license and these Terms, the more restrictive conditions will apply to that particular component, while these Terms continue to govern the Service as a whole.

21.3 Your Responsibility to Review Upstream Terms.
You are responsible for:

• reviewing the applicable licenses and usage guidelines for third-party software and models you use within your containers; and
• ensuring that your use (including fine-tuning, hosting, or downstream redistribution) complies with those upstream terms.

CloudDock does not provide legal advice. If you are uncertain about your obligations under an open-source or model license, you should consult your own legal counsel.

21.4 Additional Notices & Updates.
CloudDock may update Annex B from time to time to reflect changes in the components or versions used in the Service. Such updates do not themselves modify the terms of any open-source license but are provided for transparency. Continued use of updated images implies your acceptance of the relevant upstream licenses.

21.4 Additional Notices & Updates.
CloudDock may update Annex B from time to time to reflect changes in the components or versions used in the Service. Such updates do not themselves modify the terms of any open-source license but are provided for transparency. Continued use of updated images implies your acceptance of the relevant upstream licenses.

⸻

Annex A — SLA & Credits

A1. Scope of Application

This Annex applies to the CloudDock production environment only during periods when:

• you have clicked “Start” for a session; and
• the corresponding instance is considered in a “Running” or “Scheduling in progress but billed” state under these Terms (see Section 5.2).

Time spent queuing, on standby, or before launch (for example while waiting in a queue or filling in forms) is excluded.

A2. Monthly Availability Target

CloudDock uses commercially reasonable efforts to deliver high availability and measures it on a calendar-month basis.

Monthly Availability =1 − (Downtime Minutes ÷ Total Minutes in the Month) × 100 %

Measurement rules for Downtime Minutes are defined in Sections A3 and A4.

A3. Definition of “Downtime”

A running or billed instance is considered “down” when, due to a failure in CloudDock infrastructure (as opposed to your own network, configuration, or third-party services):

1. it is continuously unable to be scheduled, connect, or stay connected for at least five (5) consecutive minutes; and
2. you are otherwise acting in accordance with these Terms and the AUP.

For SLA purposes, Downtime includes the following scenarios (subject to the exclusions in A4):

A3.1 Established session becoming unavailable.

A session that was previously reachable becomes unavailable for ≥5 consecutive minutes, such that:

• remote desktop, web UI, or primary access channel cannot be established or maintained; and
• telemetry indicates the cause resides in CloudDock infrastructure (for example, host failure, internal routing issues, or control-plane faults), not in your own local network or third-party dependencies.

A3.2 Scheduling failure immediately after “Start”.

A scheduling failure event is defined as follows:

• you click “Start”, the system begins billing in accordance with Section 5.2;
• the Dashboard or control UI indicates that the instance has transitioned into a running / “continue” state (that is, it appears as if the machine is ready to connect);
• despite this, you cannot establish a remote desktop or job session for at least five (5) consecutive minutes; and
• the order is then automatically terminated by the platform (for example, after internal timeout or watchdog checks), without you having had a usable session.

When CloudDock’s logs confirm that this condition was caused by CloudDock-side scheduling or infrastructure issues, and not by your local network or configuration, it is treated as:

• Downtime for SLA calculations; and
• a non-user interruption eligible for refunds or credits under Section 5.5 (see also A8).

In this case, you should contact support and request investigation. Once verified against telemetry and audit logs, CloudDock will process compensation in accordance with Section 5.5 and any applicable caps.

A4. Exclusions (Not Counted as Downtime)

The following are not counted as Downtime Minutes for SLA calculations and do not trigger SLA credits under this Annex:

1. Scheduled or emergency maintenance as described in Section 14 (including maintenance mode, long-term maintenance windows, and host restarts), unless explicitly stated otherwise in a separate SLA.
2. Force majeure events under Section 8.6 (for example natural disasters, power outages, regional network interruptions, large-scale upstream provider failure, or legally mandated shutdowns), including situations where CloudDock infrastructure is indirectly affected by such events.
3. Failures on the user side, including but not limited to:
   • local network or ISP issues;
   • misconfigured client software or protocols;
   • firewall/VPN interference or blocked ports on your side;
   • misconfiguration of images, environment variables, or dependencies inside your own container; or
   • your own high-risk, experimental, or unsupported configurations.
4. Queueing caused by resource scarcity, your failure to confirm within the claim window (see Section 2.3), or any situation where billing has not yet started under Section 5.2.
5. Restrictions, terminations, or suspensions resulting from:
   • violations of the AUP (Section 4);
   • security or risk-control actions (including watchdog terminations under Section 3); or
   • cooperation with law-enforcement or legal requests (Section 16).
6. Stops, restarts, or configuration changes initiated by you (including manual restarts, deliberate shutdowns, image changes, or other voluntary actions), and any data loss associated with such actions.
7. Failures or outages attributable to third-party services or external dependencies, including but not limited to: external model hubs, code repositories, cloud object storage, APIs you call from inside the container, or other Internet services not operated by CloudDock.

A5. Discount Trigger & Window

If, after applying the above rules, CloudDock determines that Monthly Availability for a particular calendar month is below eighty percent (80%), the following discount window applies:

• Trigger: Monthly Availability < 80 % for that month.
• Discount: The following calendar month becomes a discount window. During this window, CloudDock will automatically credit 5 % of every actual charge for newly launched instances back to your account balance (applied per transaction).
• Form: Credits are issued as non-transferable, non-withdrawable, non-interest-bearing account balance in accordance with Section 5.7.
• Duration: The discount window runs only for the following calendar month. Charges incurred outside that period are not eligible.
• No stacking: The SLA discount cannot be combined with other discounts, promotions, or rebates applied to the same spend, including per-session refunds under Section 5.5 (see A7).

A6. Consecutive Monthly Triggers

If Monthly Availability remains below 80 % for multiple consecutive months:

• each triggering month creates its own independent 5 % discount window in the subsequent month;
• these discount windows may fall in different months and do not stack on the same transaction;
• for any given charge, only one SLA discount window can apply.

A7. No Double Compensation

For any overlapping period or the same spend:

• if you have already received a session-level refund or credit under Section 5.5 (for example, for a non-user interruption such as a scheduling failure or mid-session outage),
• then you will not also receive an SLA discount under this Annex for that same spend.

Where both remedies could apply:

• CloudDock will grant the higher-value remedy once (either the per-session refund under Section 5.5 or the SLA credit under this Annex),
• but will not provide both remedies simultaneously for the same usage.

A8. Claims, Scheduling Failures & Reconciliation

A8.1 Automatic application.

Where technically feasible, SLA discounts under this Annex are applied automatically based on telemetry and internal calculations for Monthly Availability.

A8.2 Reporting scheduling failures / non-user interruptions.

If you experience an event that appears to match A3.2 scheduling failure or a similar non-user interruption (for example:

• you click Start,
• billing begins and the UI shows the session as “continue”/running,
• you are unable to connect for ≥5 minutes despite a healthy local network, and
• the order is then automatically terminated by the platform),

you should:

1. Contact support within a reasonable time (for example, within 30 days), providing the relevant order ID, timestamps, and a brief description; and
2. cooperate with support so CloudDock can review logs and determine whether the root cause was CloudDock infrastructure or user/third-party factors.

If CloudDock’s investigation confirms that:

• the issue meets the criteria of a non-user interruption under Section 5.5 and A3.2; and
• the root cause lies in CloudDock infrastructure,

CloudDock will process refunds or credits for that session according to Section 5.5 (including any applicable caps such as the 24-hour refund cap and percentage-based thresholds), regardless of whether the incident by itself triggers the overall Monthly Availability threshold in A5.

A8.3 Manual SLA reconciliation.

If you believe that SLA credits under this Annex were not correctly applied (for example, Monthly Availability appears to be below 80 % but the discount window did not activate), you must:

• submit a ticket within 30 days after the month in question or after the discount window closes; and
• provide reasonable details (dates, times, and affected sessions).

CloudDock will verify against telemetry and audit logs and, upon confirmation, issue or correct the relevant balance credits within 15 days.

A9. Adjustments & Future Changes

CloudDock may modify the values, thresholds, or scope of this Annex A (for example, the 80 % availability threshold, the 5 % credit rate, or the exact measurement rules) as business and technical conditions evolve. Any material changes will:

• be announced in accordance with Section 1.1 and Section 20.3 (for example, via email, in-dashboard notices, and/or primary contact identity); and
• take effect in the next billing cycle or later, not retroactively.

Your continued use of the Service after such updates take effect constitutes your acceptance of the updated SLA terms.

⸻

Annex B – Open-Source & Third-Party Notices

(Applies to CloudDock Universal 4. Components are pre-installed; CloudDock does not modify upstream source code except where explicitly noted.)

General. All third-party software inside the container remains subject to its own license. Your use of these components—including models, weights, and any inference or training outputs—must comply with both the upstream license and the CloudDock ToS (including, without limitation, Sections 4.14 and 11.4). CloudDock does not provide legal advice. If multiple terms apply, the most restrictive set of terms governs.

A. Base Image & Proprietary Components

• Base image. nvidia/cuda:12.4.1-runtime-ubuntu22.04.
• CUDA / cuDNN / cuSPARSELt. NVIDIA CUDA runtime components (including, but not limited to, libcusparseLt.so.0 installed via cusparselt-cuda-12) are subject to the NVIDIA CUDA EULA and related proprietary terms. Redistribution and usage of these components are governed by NVIDIA’s licenses and, where applicable, the Ubuntu packaging terms.

B. Distribution & System Runtime

• Ubuntu 22.04 LTS (“Jammy”). Collective distribution of numerous open-source packages, each under its own license (including, but not limited to, GPL, LGPL, BSD, MIT, Apache-2.0 and others). Canonical and Ubuntu trademarks apply.
• Docker / container runtime. Where the CloudDock image is used with Docker Engine (community edition), Docker is primarily licensed under Apache-2.0, with some components under other permissive or copyleft licenses.
• Python 3 runtime. Python Software Foundation License (PSF-2.0).
• FUSE / GVFS / related tools. fuse, gvfs, and related components are generally licensed under a combination of GPL and LGPL, as indicated in the upstream packaging.

C. Desktop & Remote Graphics Stack

• X.Org / Xvfb / related X11 utilities. Most X.Org components are under MIT-style licenses; certain utilities may use other OSI-approved licenses.
• Xfce desktop environment. Xfce core and associated plugins use GPL, LGPL, BSD and other permissive licenses, per package metadata.
• Remote desktop & web access.
  • noVNC – MPL-2.0.
  • websockify – LGPL-3.0.
  • x11vnc – GPL-2.0-or-later (with OpenSSL exception).
• Themes & icons.
  • Arc / Arc-Lighter theme – GPL-3.0-or-later.
  • Papirus icon theme – GPL / CC-BY-SA; see upstream project for exact terms.

D. Browsers & User Applications

• Firefox (MozillaTeam PPA, non-snap). MPL-2.0, plus applicable Mozilla trademark policies.

(Note: the Usagi 4.0 Beta5 image no longer ships LibreOffice by default; if you install additional office or productivity applications via the App Store or your own package management, those applications will be subject to their respective licenses.)

E. Machine Learning / Deep Learning Frameworks & Ecosystem

E.1. Jupyter / notebook toolchain (jlab-venv)

• JupyterLab, Notebook, Jupyter Server, ipykernel, ipywidgets.
  Project Jupyter components are generally under the BSD-3-Clause license.
• Plotting & numerics.
  • matplotlib – PSF/BSD-style.
  • NumPy (pinned <2.0) – BSD-3-Clause.
  • SciPy-related components (where present) – BSD-3-Clause.

E.2. PyTorch & core DL stack

• PyTorch / torchvision / torchaudio (CUDA 12.1 / 12.4 builds).
  Licensed under the BSD-3-Clause license, with additional terms for certain included components.
• xFormers (where installed). BSD-3-Clause.
• Triton (2.x CPU/GPU kernel compiler).
  Distributed under an open-source license (permissive, currently BSD-style / Apache-compatible); consult the triton project for current terms.

E.3. Hugging Face & transformer ecosystem

Installed across the Jupyter / training venvs (including jlab-venv, kohya-venv, kohya-sdxl-venv):

• diffusers – Apache-2.0.
• transformers – Apache-2.0.
• accelerate – Apache-2.0.
• datasets / evaluate – Apache-2.0.
• huggingface_hub – Apache-2.0.
• safetensors – Apache-2.0.
• sentencepiece – Apache-2.0 (with additional patents-related terms; see upstream).
• einops – MIT.
• peft – Apache-2.0.

E.4. ONNX & interoperability

• ONNX – Apache-2.0.
• ONNX Runtime – MIT.

E.5. Training stack (Kohya-based SD Training Center)

The CloudDock SD Training Center relies on the upstream kohya-ss / sd-scripts repository and associated libraries:

• sd-scripts – typically MIT-licensed (see upstream repository for the exact license text).
• albumentations – Apache-2.0.
• scikit-image – BSD-3-Clause.
• pytorch-optimizer – Apache-2.0.
• lion-pytorch – MIT.
• prodigyopt – MIT.
• PyYAML – MIT.
• omegaconf – BSD-3-Clause.
• rich – MIT.
• voluptuous – BSD-3-Clause.
• imagesize – MIT.

E.6. Bitsandbytes, CUDA & low-level optimization

• bitsandbytes (0.44.0) – MIT license, with additional GPU-related and patent provisions as described in the upstream project.
• cuSPARSELt – covered by the NVIDIA CUDA licenses (see Section A).

E.7. Experiment tracking & logging

• TensorBoard – Apache-2.0.
• tqdm – MPL-2.0.

F. Scientific Computing, Data Processing & Analytics

(Packages primarily installed into jlab-venv)

• pandas – BSD-3-Clause.
• scikit-learn – BSD-3-Clause.
• seaborn – BSD-3-Clause.
• SymPy – BSD-3-Clause.
• numba / llvmlite – BSD-style licenses.
• xgboost – Apache-2.0.
• lightgbm – MIT.
• catboost – Apache-2.0.
• optuna – MIT.
• mlxtend – BSD-3-Clause.
• polars – MIT.
• duckdb – MIT.
• pyarrow – Apache-2.0.
• fastparquet – MIT.
• csvkit – MIT.
• openpyxl / xlsxwriter – MIT.

G. Computer Vision, Audio & Video

• OpenCV (including opencv-python-headless) – Apache-2.0 (some older builds may be under BSD-3-Clause; consult your specific build info).
• Pillow – Pillow License (permissive MIT-like).
• imageio / imageio-ffmpeg – BSD-2-Clause / MIT.
• moviepy – MIT.
• scikit-image – BSD-3-Clause (also listed in Section E).
• librosa – ISC.
• soundfile – BSD-3-Clause (wrapper around libsndfile, typically LGPL).

H. Web / Application Stack & Internal Services

H.1. General web libraries

• Gradio – Apache-2.0.
• Flask (used by SD Trainer API and CloudDock App Store backend) – BSD-3-Clause.
• Requests – Apache-2.0.

(Some earlier containers shipped FastAPI, Uvicorn, and the OpenAI Python SDK. The Usagi 4.0 Beta5 image focuses on Flask-based services; if you install additional web frameworks via the App Store or pip, their licenses apply independently.)

H.2. Jupyter / Notebook Web UI

• JupyterLab / Notebook / Jupyter Server – BSD-3-Clause.

H.3. CloudDock internal services

• CloudDock Launcher
  These are CloudDock-authored components, distributed under CloudDock’s own terms. They orchestrate A1111, JupyterLab, the App Store, and SD Training Center; they do not by themselves change the license status of the underlying tools.
• CloudDock App Store
  Custom CloudDock service (Flask + requests) which invokes system package managers and installers. The service itself follows CloudDock’s terms; the software you install through it will be governed by each upstream license.
• CloudDock SD Training Center
  CloudDock’s Flask-based web front-end around sd-scripts and the training venvs. The web UI and API are CloudDock code; the underlying training libraries follow their own licenses as listed above.

I. Pre-Installed AI Applications, Models & Extensions

I.1. AUTOMATIC1111 Stable Diffusion WebUI

• AUTOMATIC1111 / stable-diffusion-webui.
  Licensed under AGPL-3.0.

AGPL network clause reminder. If you modify the web UI and make the modified version available for interactive use over a network, you must prominently offer all remote users the complete corresponding source code of your modified version (AGPL-3.0 §13). CloudDock ships an (effectively) unmodified installation and does not assume or satisfy your AGPL obligations when you expose a modified version to others.

I.2. ControlNet & related A1111 extensions

• sd-webui-controlnet plugin. GPL-3.0.
• Annotators and auxiliary models bundled with ControlNet are subject to their own upstream licenses (including, potentially, research-only or restrictive usage clauses). For size, security, or policy reasons, CloudDock may omit some annotator weights or tools; absence of a file in the container does not waive any upstream license that would apply if you later download and add it yourself.

I.3. Pre-installed base model (Stable Diffusion 1.5)

• The container may include the official Stable Diffusion v1.5 checkpoint (or its safetensors-equivalent) as provided by Stability AI / the original rights-holders.
• Such weights are typically licensed under the CreativeML Open RAIL-M license (or a substantially similar “Responsible AI License”) with content and usage restrictions (for example, restrictions against exploiting minors, generating certain categories of harmful content, and so on).
• You are solely responsible for reading, understanding, and complying with the model’s license and any associated usage policy. If you replace or add models (e.g., community LoRA, checkpoints), those assets will be governed by their own licenses and content policies.

I.4. Smart captioning, tagging & CLIP-based tools

The SD Training Center’s “Smart Caption” and related features internally use:

• clip-interrogator – MIT.
• deepdanbooru – MIT.
• timm – Apache-2.0.

These tools may themselves download or depend on upstream CLIP models and other assets which carry additional licenses and usage restrictions; refer to the respective upstream repositories and model cards.

J. System Utilities, Monitoring & Miscellaneous

• psutil (system process & resource inspection) – BSD-3-Clause.
• aria2 (App Store downloader) – GPL-2.0-or-later.
• nvidia-ml-py3, gpustat and similar GPU monitoring helpers – distributed under their own open-source licenses (commonly BSD-style or MIT).
• trash-cli, Thunar / xarchiver, and other shell / desktop utilities – GPL / LGPL / BSD-style licenses per upstream packaging.

CloudDock Intelligent Dog™
Bash and helper scripts are CloudDock-authored security tooling and are distributed under CloudDock’s own terms. While these scripts rely on standard GNU/Linux utilities (ps, bash, coreutils, iptables, etc., licensed under GPL/LGPL or similar), the overall watchdog design, scoring logic, and log handling remain proprietary to CloudDock.

K. Planned: DeepSpeed Suite & LLM Training Add-ons (Future Images)

Some future CloudDock container variants may additionally include a DeepSpeed-based training stack (for LLMs and large models), including but not limited to:

• DeepSpeed – MIT.
• Additional transformer / tokenizer / optimizer libraries (e.g., Hugging Face transformers, tokenizers, or parallelism utilities) – typically Apache-2.0 or MIT.

If and when such components are added to your specific image, they will be documented in the container’s release notes (and visible via pip freeze / conda list). Their use will be governed by their respective upstream licenses in addition to the CloudDock ToS.

L. Non-Exhaustive List & Verification

This Annex B is illustrative, not exhaustive. Packages and versions may be added, removed, or upgraded between builds of the same major image line. To audit the exact set of components present in your running container, you may:

• Inspect installed Python packages (pip list, pip freeze within each venv).
• Inspect system packages (dpkg -l on Ubuntu).
• Review the source repositories or model cards of any third-party assets you download or mount into the container.

Where there is any discrepancy between this Annex B and the actual contents of the image, the actual packaged software and the upstream licenses govern.

Final Note:

By using CloudDock, you agree that we do not know and are not responsible for what you do in your container unless we are legally required to investigate.
We provide compute power, not judgment.