1. Acceptance of these Terms
These Terms of Service (“Terms”) are a legally binding agreement between you (“you”, “your”) and DataSpires, Inc., a Delaware corporation (“DataSpires”, “we”, “us”, “our”). They govern your access to and use of the Service defined in Section 2.
You accept these Terms when you create an account, install or authenticate the SDK, call the Models API, or otherwise use the Service. If you do not agree, do not use the Service. If you accept on behalf of an organisation, you confirm that you have authority to bind it, and “you” includes that organisation.
How the Service works. DataSpires operates the platform, the SDK, the dashboard, the Models API and your deployed endpoints, and you contract with DataSpires for them. We run your jobs and serve models on GPU and inference capacity that we source from vetted third-party infrastructure partners (“Compute Partners”). Today these are located in India and the United States. As capacity elsewhere, including in Africa, becomes cost-competitive, we may route jobs there without any change to your code. You do not need a separate agreement with any Compute Partner.
2. Definitions
- “Account” means the account you create to use the Service, including any API keys issued to it.
- “Compute Partner” means a third party that supplies GPU, inference, storage or data-centre capacity that DataSpires uses to deliver the Service.
- “Customer Data” means data, code, containers, datasets, prompts and other material you submit to the Service.
- “Dashboard” means the web interface at dataspires.com for creating, monitoring and managing Jobs, Endpoints, your Wallet and your Account.
- “Directory Services” means Market Intelligence, the Africa Compute Atlas, the Marketplace listings, the Spire advisor and other information we publish about third-party compute, cloud and credit programmes.
- “Documentation” means the technical documentation linked from our website and other technical material we publish.
- “Endpoint” means a model you deploy through the Service and serve as a live API.
- “Job” means a training, fine-tuning, pre-training, generation, inference or custom-container workload you submit through the SDK or Dashboard.
- “Models API” means our unified model gateway at models.dataspires.com, compatible with the OpenAI and Anthropic API formats.
- “Outputs” means results the Service returns to you, including generated text, logs, metrics, checkpoints and Trained Models.
- “SDK” means the DataSpires Python client distributed as the dataspires package on PyPI.
- “Service” means the SDK, Dashboard, Jobs, Endpoints, Models API, Directory Services, Documentation and all related features, together with any future features we make available under these Terms.
- “Third-Party Model” means a model made available through the Service that was created by someone other than DataSpires, such as Qwen, Llama, Gemma, GPT-OSS, GLM, DeepSeek, Nemotron, SmolVLM, YOLO or ResNet.
- “Trained Model” means model weights, adapters or checkpoints produced by a Job you run.
- “Wallet” means the prepaid USD balance on your Account, and “Credits” means value in your Wallet, whether purchased or granted.
3. Eligibility and accounts
3.1 Eligibility. You must be at least 18, or the age of majority where you live if higher. You may be 16 or 17 only if you use the Service through an account provided by your school, university or programme, with their permission. You must be legally able to enter a contract, and not barred from the Service by law or by an earlier suspension.
3.2 Registration. You must give accurate, current information when you register and keep it up to date. One person or organisation may not open multiple Accounts to obtain extra free usage or Credits.
3.3 Students and researchers. To receive student, research or sponsored benefits you may need to register with an institutional email address or provide proof of eligibility. Those benefits are for non-commercial education and research only. If you misstate your eligibility we may withdraw the benefits, bill you for discounted usage at standard rates, and close your Account.
3.4 Organisation and cohort accounts. An institution, lab, course or company may give you access through an organisation account or a shared pool of Credits. The organisation’s administrators may then see your Jobs, usage, spend and related metadata, and may set limits on or remove your access. The organisation is responsible for its members’ use of the Service.
3.5 Security. You are responsible for your credentials and API keys and for all activity under your Account. Tell us promptly at info@dataspires.com if you suspect unauthorised access. We may suspend an Account we reasonably believe is compromised.
3.6 Verification. We may verify your identity, organisation or eligibility at any time. If you do not provide the information we request, we may suspend or close your Account.
4. The Service
4.1 What we provide. Through the SDK and Dashboard you can upload or reference data, run Jobs on on-demand GPUs, monitor logs and metrics, download Outputs, build and run your own containers, and deploy Trained Models as Endpoints. Through the Models API you can call paid and free models with a DataSpires API key.
4.2 Licence. Subject to these Terms, we grant you a limited, non-exclusive, non-transferable, revocable right to use the Service for your own business, research or educational purposes. The SDK may also be distributed under an open-source licence. Where it is, that licence governs your use of the SDK code itself, and these Terms govern your use of our hosted Service.
4.3 Jobs. Each Job runs on the GPU type, GPU count and time limit you choose. A Job stops when it reaches its time limit, when your Wallet runs out, or when you cancel it. Checkpointing and resume are provided on a best-effort basis. Multi-GPU capacity depends on availability. Training-mode presets and model fit guidance are estimates, not guarantees.
4.4 Directory Services. Market Intelligence, the Africa Compute Atlas, the Marketplace and Spire describe third-party providers, cloud regions and credit programmes. They are for information only. A listing is not an endorsement, and any arrangement you make with a listed third party is between you and them.
4.5 Beta and coming-soon features. Features labelled beta, preview or coming soon (for example team and cohort pools) may change, have limits or be withdrawn, and are provided as-is.
4.6 Changes to the Service. We may add, change or remove features, models, GPU types or regions. We will give reasonable notice of changes that materially reduce what you have paid for. API changes are covered in Section 7.4.
5. Wallet, pricing and billing
5.1 Pay as you go. You pay for the Service by topping up your Wallet in US dollars. The minimum top-up is shown in the Dashboard (currently USD 5.00). Jobs, Endpoints and Models API usage draw from your Wallet balance.
5.2 GPU pricing. GPU prices follow live supply. Our public pricing page shows the lowest current price per GPU-hour for each GPU type, and the Dashboard shows the exact rate available to you. The price for a Job is locked when you launch it. Multi-GPU Jobs are billed per GPU. Before a Job starts we show its maximum cost (GPUs × hourly price × time limit). You are billed for the time the Job actually uses, up to that maximum.
5.3 Failed Jobs. If a Job fails because of a fault on the DataSpires side, you are not charged for it. If a Job fails because of your code, data, container or configuration, you are charged for the GPU time used. Our logs determine the cause. If you disagree, contact us within 30 days and we will review it in good faith.
5.4 Models API. Models API usage is metered in tokens and charged at the per-million-token input, cached-input and output rates shown for each model. Models marked free carry no token charge but are subject to rate limits and fair use. We may change, limit or withdraw any free model at any time.
5.5 Endpoints, storage and transfer. Deployed Endpoints, storage and data transfer are billed as shown on the pricing page at the time of use. Where no charge is shown, none applies, but we may introduce one on 30 days’ notice.
5.6 Price changes. We may change prices at any time. Changes do not affect a Job already launched. For Endpoints, storage and other ongoing charges we will give at least 30 days’ notice of an increase.
5.7 Payments and taxes. Payments are processed by Stripe or another third-party processor under its own terms. Prices exclude taxes, duties and bank or currency-conversion fees, which you are responsible for. Where we must collect tax, we will add it at checkout.
5.8 Credits. Credits are a prepaid balance for the Service only. They are not money, a deposit or e-money. They carry no interest, cannot be withdrawn as cash, and cannot be transferred between Accounts except through features we provide (such as organisation pools). A Wallet balance expires if your Account has no activity for 12 consecutive months. We will email you at least 30 days before that happens.
5.9 Refunds. You may request a refund of a purchased, unused Wallet balance within 30 days of the top-up, less any non-refundable processor fees. After 30 days, purchased Credits are non-refundable, except where we are at fault (Section 5.3), for fraudulent charges, or where the law requires otherwise. Granted, promotional and sponsored Credits are never refundable. Send refund requests to info@dataspires.com.
5.10 Negative balances and failed payments. If usage exceeds your balance, for example while a Job is finishing, you owe the difference. We may pause or stop Jobs and Endpoints when your balance reaches zero. If a payment fails or is reversed, we may suspend the Service, freeze Credits bought with that payment and recover amounts owed. Raising an unjustified chargeback may lead to Account closure.
5.11 Paid plans. Some features, such as premium Market Intelligence, may require a paid plan. Plan fees are charged in advance for each billing period and renew until cancelled. You may cancel at any time, effective at the end of the current period. No refunds are given for partial periods unless the law requires it.
6. Acceptable use
You must use the Service lawfully and in line with these Terms, the Documentation, and the licence and use policy of any Third-Party Model you use. You must not, and must not let anyone else:
- break any law or infringe anyone’s intellectual property, privacy or other rights
- create, train on, store or distribute child sexual abuse material, or any content that sexualises minors
- develop or deploy malware, or use the Service to attack, probe or gain unauthorised access to any system, including ours or a Compute Partner’s
- use the Service to develop chemical, biological, radiological, nuclear or other weapons, or for unlawful surveillance
- generate or distribute fraud, spam, phishing, or deceptive content that impersonates real people or organisations
- train or deploy a model in order to remove or bypass the safety restrictions of a Third-Party Model in breach of its licence
- mine cryptocurrency, run proof-of-work, or use GPUs for anything other than your declared workloads
- resell, sublicense or share access to GPUs, Endpoints, the Models API or API keys, except through an organisation account or with our written permission
- open multiple Accounts, rotate keys, or otherwise get around rate limits, quotas, free-tier limits or billing
- interfere with or overload the Service, or try to reach Compute Partner infrastructure directly instead of through the Service
- reverse engineer the hosted Service, except where the law allows it or an open-source licence permits it
- scrape the Directory Services in bulk, or use them to build a competing directory
- process personal data without a lawful basis, or upload special-category or health data unless you have the consents and safeguards the law requires
- use sponsored, student or educational Credits for commercial work, production deployments or training commercial models
We may investigate suspected breaches. We may stop Jobs, take Endpoints offline, remove content, revoke keys, or suspend Accounts where we reasonably believe this Section has been breached. Where it is lawful, we may report illegal activity to the authorities.
7. SDK, API and API keys
7.1 Access. The SDK, Dashboard and Models API are accessed with DataSpires API keys (for example keys beginning dsp_live_). The same key works with the OpenAI-compatible and Anthropic-compatible endpoints of the Models API.
7.2 Keys. API keys are confidential. Do not embed them in public code, notebooks or client-side apps. You are responsible for all usage and charges on your keys. Revoke a key straight away if it may be exposed. We may revoke keys that are compromised or misused.
7.3 Limits. We may apply rate limits, concurrency limits, quotas, maximum Job lengths (currently 10 hours per Job), limits on GPUs per Job, upload limits (currently around 800 GB per dataset) and spending limits. These may be described in the Documentation or shown in the Dashboard.
7.4 Changes and deprecation. We may update the SDK and APIs. For breaking changes to a stable API or SDK major version, we will try to give at least 90 days’ notice. That notice does not apply where a change is needed for security, legal reasons, or because a model provider or Compute Partner withdraws a model or capacity. Older SDK versions may stop working once deprecated.
7.5 Compatibility. Compatibility with OpenAI or Anthropic formats covers the documented request and response shapes only. It does not mean we are affiliated with or endorsed by those companies, or that every parameter they support is supported.
8. Models, Outputs and Endpoints
8.1 Third-Party Models. Third-Party Models are made available under their own licences and acceptable use policies, for example the Llama, Gemma or Qwen licences. You are responsible for reading those terms and complying with them, including any limits on commercial use, attribution, user numbers, or use to train other models. Requests to some models in the Models API are served by third-party inference providers on our behalf.
8.2 Your Outputs. As between you and DataSpires, you own your Outputs, including Trained Models produced from your Customer Data. Your rights in a Trained Model remain subject to the licence of the base model it was derived from.
8.3 AI limitations. Model Outputs are generated automatically. They may be inaccurate, incomplete, biased, offensive or similar to content produced for others. Do not rely on Outputs as the sole basis for medical, legal, financial, safety-critical or other high-stakes decisions without appropriate human review. You are responsible for how you use Outputs and for checking them before you rely on them.
8.4 Endpoints. When you deploy an Endpoint, you are responsible for the application it powers and for your end users. That includes giving your end users any required notices or terms, and making sure your use complies with Section 6 and the base model’s licence. Endpoint availability, latency and throughput are not guaranteed unless a separate written service-level agreement applies. We may scale down, rate-limit or suspend an Endpoint that breaches these Terms or threatens the stability of the Service.
8.5 Model availability. We may add, change or remove models from the registry or the Models API, including when a model provider changes its terms or withdraws a model. Speed and context figures we publish are typical values, not guarantees.
9. Customer Data
9.1 Ownership. You keep all rights in your Customer Data. You give DataSpires and the subcontractors acting for us a worldwide, non-exclusive licence to host, copy, process, transmit and display Customer Data. This licence is only for providing, securing and supporting the Service for you and for complying with law.
9.2 No training on your data. We do not use your Customer Data, prompts or Outputs to train or improve our own or third-party models unless you opt in. We may use aggregated, de-identified usage data, such as GPU hours, error rates and model popularity, to operate and improve the Service.
9.3 Where data is processed. To run your Jobs and Endpoints, we transfer Customer Data to Compute Partners and inference providers. These are currently in India and the United States. Account and billing data may be processed in other countries where we or our service providers operate, including the United Kingdom and the European Union. We protect these transfers with contractual safeguards where the law requires them. If you need data processed only in a particular country, contact us before uploading it.
9.4 Security. We use commercially reasonable technical and organisational measures. These include encryption in transit, access controls and isolation between customer workloads, and we require Compute Partners to meet appropriate security standards. No system is perfectly secure. You are responsible for securing your own code, containers, keys and any Endpoint you expose.
9.5 Retention and deletion. Uploaded datasets, checkpoints, Trained Models and logs are kept while your Account is active, unless you delete them sooner or the Documentation states a shorter retention period. Models API prompts and outputs may be logged for up to 30 days for billing, abuse prevention and debugging. Within 30 days after you close your Account or it is terminated, we delete Customer Data from active systems. Backups are overwritten on their normal cycle. We may keep data longer where the law requires it. Keep your own copies of anything you need.
9.6 Personal data. Our Privacy Policy explains how we handle personal data about you. Where you upload personal data about others, you are the controller and we act as your processor. You confirm you have a lawful basis and any required notices or consents. That includes compliance with laws such as the EU and UK GDPR, South Africa’s POPIA, Kenya’s Data Protection Act, Nigeria’s NDPA and Tanzania’s PDPA. Organisations can request a data processing agreement at info@dataspires.com.
9.7 Legal requests. We may disclose Customer Data where the law requires it. Where we are permitted to, we will tell you first so you can object.
10. Sponsored compute and education programmes
10.1 Sponsors. Individuals and organisations can sponsor compute for students and researchers, for example through “Sponsor student compute”. Sponsorships are voluntary and non-refundable once allocated. Sponsors may suggest criteria such as country, institution or field. DataSpires decides final allocation unless a written agreement says otherwise. DataSpires is not a charity. Whether a sponsorship is tax-deductible depends on your circumstances and any intermediary used, and we make no promise that it is.
10.2 Recipients. Sponsored, student and educational Credits are for non-commercial learning and research only. They cannot be transferred or exchanged for cash. They may expire on the date shown when they are granted. We may withdraw them if they are misused, if eligibility lapses, or when the programme ends.
10.3 Availability. Sponsored Credits depend on available funding. Programmes may change or end at any time, so do not rely on them for time-critical work.
10.4 Recognition. Recipients may be asked to acknowledge support in publications or presentations. We may publish aggregate statistics about the programme and, with their permission, name sponsors and participating institutions.
11. Intellectual property
11.1 Our rights. DataSpires and its licensors own the Service, including the platform, orchestration software, Dashboard, Documentation, Directory Services data and our trademarks. We reserve all rights not expressly granted. Open-source components remain under their own licences.
11.2 Restrictions. Except as these Terms or an applicable open-source licence allow, you must not copy, modify, sell, rent or create derivative works of the hosted Service. You must not remove proprietary notices or use the DataSpires name or logo without our permission.
11.3 Feedback. If you send us suggestions or feedback, we may use them freely without any obligation to you.
11.4 Copyright complaints. If you believe material on the Service infringes your copyright, email info@dataspires.com with the information required by 17 U.S.C. § 512(c)(3). We will respond in line with the US Digital Millennium Copyright Act and other applicable law, and may suspend repeat infringers.
12. Confidentiality
Each party may receive non-public information from the other that is marked confidential, or that should reasonably be understood to be confidential (“Confidential Information”). Customer Data is your Confidential Information. The receiving party will use Confidential Information only for the purposes of these Terms. It will protect that information with at least reasonable care and share it only with personnel, advisers and subcontractors who need to know it and are bound by similar duties.
These duties do not apply to information that is or becomes public without breach, was already known to the receiving party, was independently developed, or was lawfully received from a third party. If the law requires disclosure, the receiving party will give notice where it is permitted to and disclose only what is required.
13. Disclaimers
13.1 As is. To the maximum extent the law allows, the Service, Outputs, Third-Party Models and Directory Services are provided “as is” and “as available”. DataSpires disclaims all implied warranties, including merchantability, fitness for a particular purpose, non-infringement, and uninterrupted or error-free operation.
13.2 No guarantees on results. We do not guarantee that any Job will finish, converge or reach any accuracy. We do not guarantee that GPU capacity of a given type will be available, or that Outputs will be accurate, lawful or fit for your purpose.
13.3 Third parties. We choose Compute Partners and model providers with care. We are not responsible for Third-Party Model licences, the conduct of third parties listed in the Directory Services, or third-party services you connect to the Service, such as Colab, Kaggle, Hugging Face or cloud storage.
13.4 Directory data. Market Intelligence, Atlas and Marketplace information may be incomplete, out of date or wrong, including prices, credit amounts and eligibility rules. Check it with the third party before you rely on it.
13.5 Consumer rights. Some laws do not allow certain warranties to be excluded. If you are a consumer, nothing in these Terms affects rights you have that cannot be excluded or limited by contract.
14. Limitation of liability
14.1 Excluded losses. To the maximum extent the law allows, neither party is liable for indirect, incidental, special, consequential or punitive damages. Neither party is liable for loss of profits, revenue, goodwill or data, or for the cost of substitute services. This applies even if a party was told such losses were possible.
14.2 Cap. To the maximum extent the law allows, each party’s total liability arising out of or relating to these Terms or the Service is capped. The cap is the greater of (a) the amounts you paid to DataSpires in the 12 months before the event giving rise to the claim, including Wallet top-ups, and (b) USD 100.
14.3 Exceptions. Sections 14.1 and 14.2 do not limit your payment obligations or your liability for breaching Section 6 or for your indemnity under Section 15. They also do not limit either party’s liability for fraud, or for death or personal injury caused by negligence, or any other liability that cannot be limited by law.
14.4 Basis of the bargain. Our prices reflect these allocations of risk. If you need a service-level agreement or higher liability limits, contact us about an enterprise agreement.
15. Indemnification
You will defend, indemnify and hold harmless DataSpires and its affiliates, officers, employees and Compute Partners against third-party claims, and related losses and reasonable legal costs, arising from:
- your Customer Data, or your use of Outputs and Endpoints, including claims by your end users
- your breach of these Terms, of Section 6, or of a Third-Party Model licence
- your breach of law or of a third party’s rights
We will tell you promptly about any claim, let you control its defence, and give reasonable help at your expense. You may not settle a claim in a way that imposes obligations on us without our consent. We may join the defence with our own counsel at our own cost.
16. Term, suspension and termination
16.1 Term. These Terms apply from when you first use the Service until your Account is closed.
16.2 By you. You may stop using the Service and close your Account at any time from the Dashboard or by emailing info@dataspires.com. Refunds on closure follow Section 5.9.
16.3 By us. We may suspend or terminate your access immediately if you materially breach these Terms, create a security or legal risk, fail to pay, or if the law requires it. We may close Accounts that have been inactive for 12 months or more. We may also end the Service or your Account for any reason on 30 days’ notice. If we do so other than for your breach, we will refund any purchased, unused Wallet balance.
16.4 Effect. On termination your right to use the Service ends, running Jobs and Endpoints stop, and amounts owed remain payable. You have 30 days to download your Customer Data and Outputs before we delete them under Section 9.5. Sections 5 (for amounts owed), 8.2, 8.3, 9.5, 11 to 15, 18 and 20 survive termination.
17. Changes to these Terms
We may update these Terms. We will post the new version with a new “Last updated” date. For material changes, we will give at least 30 days’ notice by email or in the Dashboard before they take effect. Changes needed for legal reasons or for new features may take effect sooner. If you continue to use the Service after changes take effect, you accept them. If you do not agree, stop using the Service and close your Account.
18. Disputes and governing law
18.1 Informal resolution first. Before starting formal proceedings, contact us at info@dataspires.com and give us 30 days to try to resolve the dispute.
18.2 Governing law. These Terms are governed by the laws of the State of Delaware, USA, without regard to its conflict-of-laws rules. The UN Convention on Contracts for the International Sale of Goods does not apply.
18.3 Arbitration. Any dispute that is not resolved informally will be finally resolved by binding arbitration under the LCIA Rules. There will be one arbitrator, the seat will be London, United Kingdom, and the language will be English. Hearings may be held remotely. The arbitrator may award costs to the successful party. Either party may seek urgent injunctive relief, or relief for misuse of intellectual property or Confidential Information, in any competent court. Either party may also bring an individual claim in a small-claims court.
18.4 Individual claims only. To the extent the law allows, claims may be brought only individually, not as a plaintiff or class member in any class, collective or representative proceeding. Each party waives any right to a jury trial.
18.5 Time limit. To the extent the law allows, a claim must be brought within one year after it arose.
18.6 Consumers. If you use the Service as a consumer and live in a country whose law gives you the right to bring claims in your local courts, or to benefit from local consumer protection, nothing in this Section removes that right.
19. Export controls and sanctions
The Service, including GPU compute and models, is subject to export control and sanctions laws, including those of the United States, the United Kingdom, the European Union and the United Nations. You confirm that you are not located in, or ordinarily resident in, a comprehensively sanctioned country or region. You also confirm that you are not on a restricted-party list, and not owned or controlled by anyone who is. You must not use the Service for any end use those laws prohibit, including weapons development, or give access to anyone barred from receiving it. We may block access or stop Jobs where we need to comply.
20. General
20.1 Entire agreement. These Terms, our Privacy Policy, the pricing page and any order form or enterprise agreement make up the whole agreement between us about the Service. If they conflict, a signed enterprise agreement prevails, then these Terms.
20.2 Assignment. You may not assign these Terms without our written consent. We may assign them to an affiliate, or in connection with a merger, acquisition or sale of assets.
20.3 Subcontractors. We may use subcontractors, including Compute Partners, inference providers and payment processors, to provide the Service. We remain responsible for our obligations under these Terms.
20.4 Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control. That includes outages of power, internet, cloud or Compute Partner capacity, government action, war, unrest, pandemics and natural disasters. Payment obligations are not covered.
20.5 Severability and waiver. If a provision is unenforceable, it will be enforced to the extent possible and the rest stays in effect. A failure to enforce a provision is not a waiver.
20.6 Relationship. The parties are independent contractors. These Terms create no partnership, agency, employment or joint venture.
20.7 Third-party rights. No one other than you and DataSpires has rights under these Terms, except the indemnified parties under Section 15.
20.8 Notices. We may send notices to the email address on your Account or through the Dashboard. Legal notices to us must go to info@dataspires.com, with a copy by post to DataSpires, Inc., c/o Corporation Service Company, 251 Little Falls Drive, Wilmington, Delaware 19808, USA. Notices are effective when received.
20.9 Language. These Terms are written in English. If we provide a translation and it conflicts with the English version, the English version prevails.
20.10 US Government users. The Service is “commercial computer software” and “commercial computer software documentation” under 48 C.F.R. § 12.212. Government users receive only the rights set out in these Terms.
21. Contact
DataSpires, Inc. c/o Corporation Service Company, 251 Little Falls Drive, Wilmington, Delaware 19808, USA
Email: info@dataspires.com · Website: www.dataspires.com · LinkedIn: linkedin.com/company/dataspires
For billing, Job or Endpoint issues, email us with your Account email and the Job or Endpoint ID.
