Terms, refunds and privacy

Effective 5 September 2026. These apply to gpu.swarmdo.com, its API, SDK, CLI and MCP server (together, "the service"). Questions: support@swarmdo.com.

Terms of service

By creating an account or using the API you agree to these terms. If you use the service on behalf of a company, you confirm you may bind that company to them.

What the service is

SwarmDo GPU sells access to GPU compute, autoscaling model endpoints, hosted model APIs and storage, billed against prepaid credit. Capacity is sourced from a pool of infrastructure providers; instances, endpoints and models are presented under SwarmDo identifiers and addresses, and the provider behind any given resource is not disclosed.

Your account

• Keep your password, API keys and two-factor device secret. Anything done with your keys is done by you; rotate a key immediately if it may have leaked.
• You must be at least 18 and able to enter a contract.
• We may suspend or close an account for non-payment, fraud, abuse, or a chargeback, and may stop resources that are running against a negative balance.

Your content and models

You keep all rights to the code, models, data and outputs you run or generate. You grant us only the rights needed to operate the service (store, transmit and run them on your instruction). We do not use your inputs or outputs to train models.

Availability

The service is provided as-is. Interruptible GPUs can be reclaimed at any time; on-demand capacity can fail or be unavailable. Where you subscribe to an SLA tier, its uptime target and the credits for missing it are the sole remedy for downtime.

Liability

To the extent the law allows, our total liability for any claim in a twelve-month period is limited to the amount you paid us in that period, and we are not liable for indirect or consequential loss, lost profits, or lost data. Nothing here limits liability that cannot be limited by law.

Changes

We may change these terms; material changes are announced in the dashboard at least 14 days before they take effect. Continued use after that date is acceptance.

Billing and refunds

• Prepaid credit. You add credit by card (Stripe) and usage is deducted per second of work, per clip, per request or per million tokens, at the prices shown in the dashboard when the work runs. The minimum top-up is $5.
• Automatic top-up. If you enable it, a saved card is charged the amount you set when your balance drops below your threshold. Charges are limited to one per fifteen minutes and six per day, and the rule switches itself off after three failed charges.
• Refunds. Unused prepaid credit is refundable on request to the original payment method, less any credit granted free of charge, within 90 days of purchase. Credit consumed by usage is not refundable. Charges caused by a fault on our side (for example a failed job that was still billed) are reversed in full; write to support with the request or job id.
• Disputes. Contact us before opening a card dispute; a dispute filed without contact may lead to account suspension while it is investigated.
• Taxes. Prices exclude VAT, GST or sales tax where applicable; tax is added at checkout where we are required to collect it.

Acceptable use

You may not use the service to: break the law or another party's rights; mine cryptocurrency; attack, scan or overload networks or systems you do not own; generate content that is illegal, sexualises minors, or is intended to defraud, harass or deceive; evade metering or credit controls; or resell raw capacity while misrepresenting its origin to your own customers. We may stop workloads that breach this and are not obliged to refund the credit they consumed.

Privacy

What we collect

• Account data: email, password hash, optional two-factor secret, team membership, role.
• Billing data: ledger entries, Stripe customer and payment-method identifiers, and a card brand plus last four digits when you save a card. Full card numbers never reach our servers.
• Usage data: the resources you create, request counts and durations, metering, and audit events, kept for billing and reconciliation.
• Request contents: prompts, inputs and outputs pass through our proxy to run the work. Request logs for serverless endpoints keep timing, status and sizes, not bodies. Hosted-model outputs are returned to you and are not retained by us beyond the call.

How we use it

To run and bill the service, to detect fraud and abuse, to send transactional email (verification, receipts, low-balance and failure notices), and to meet legal obligations. We do not sell personal data and do not send marketing email without consent.

Who else sees it

Payment processing is by Stripe under its own privacy terms. Infrastructure providers receive only what is needed to run your workload; they do not receive your account identity. Hosting and email providers process data on our instructions.

Retention and your rights

Account and ledger records are kept while the account exists and for the period tax law requires afterwards. You can export your audit log and transactions from the dashboard, and can ask us to correct or delete personal data; billing records we must keep by law are retained but no longer used for anything else.

Contact