1. Who we are
This policy explains how DataSpires, Inc. (“DataSpires”, “we”, “us”) collects, uses and protects personal data. DataSpires, Inc. is a Delaware corporation with its registered office at c/o Corporation Service Company, 251 Little Falls Drive, Wilmington, Delaware 19808, USA. We operate from London, United Kingdom, and Dar es Salaam, Tanzania. You can contact us about privacy at info@dataspires.com.
2. What this policy covers
This policy covers personal data we handle when you:
- visit dataspires.com, our documentation or other sites that link to this policy
- create an account or use the Dashboard, the DataSpires SDK (the dataspires Python package), the Models API, Jobs or deployed Endpoints
- top up your wallet, sponsor student compute, join a waitlist, or contact us
- use Market Intelligence, the Africa Compute Atlas or other directory features
Words with capital letters, such as Customer Data, Job and Endpoint, have the meanings given in our Terms of Service.
3. Our two roles: controller and processor
When we are the controller. We decide how and why your account, billing, usage, support and website data is used, so we are its controller. Most of this policy describes that data.
When we are the processor. Customer Data is the data, code, datasets, prompts and models you put into Jobs, Endpoints or the Models API. It can include personal data about other people, such as text in a training dataset or details from your app’s users. For that data, you, or your organisation, are the controller. We process it only to provide the Service, as set out in the Terms of Service and any data processing agreement we sign with you. If your personal data is in a dataset or app run by one of our customers, contact that customer first. We will help them respond to you.
We do not train on your data. We do not use Customer Data, prompts or outputs to train or improve our own or third-party models unless you opt in.
4. What we collect
You give us:
- Account details: name, email address, password (stored hashed), organisation or institution, role, country, and student or researcher status if you claim those benefits.
- Billing details: billing name, address, top-up amounts and transaction history. Card details go straight to our payment processor, Stripe. We never see or store full card numbers.
- Communications: messages you send us, support requests, waitlist sign-ups, sponsorship enquiries and feedback.
We collect when you use the Service:
- Usage and Job metadata: Jobs and Endpoints you create, GPU type and count, time limits, run times, costs, status, error messages, and the models you pick.
- API and SDK data: API key identifiers (not the full key), request timestamps, token counts, SDK version, IP address and Python environment details sent with requests.
- Models API logs: prompts and outputs, kept for up to 30 days for billing, abuse prevention and debugging.
- Device and website data: IP address, browser and device type, pages visited, referring site and approximate location from your IP, collected through cookies and similar tools (Section 12).
We receive from others:
- Your institution or organisation, if it gives you access through an organisation account or sponsored Credits: your name, email and allocation.
- Stripe, which tells us whether a payment succeeded and gives us fraud signals.
- Sign-in providers, if you sign in with one: your name, email and profile picture.
We do not knowingly collect special-category data, such as health or ethnicity, about our account holders. Please don’t send it to us. Customer Data that contains such data is covered by Section 3.
5. How we use it, and our legal bases
UK and EU data protection law requires a legal basis for each use. South Africa’s POPIA, Kenya’s Data Protection Act, Nigeria’s NDPA and Tanzania’s PDPA set similar conditions.
| Purpose | Data used | Legal basis |
|---|---|---|
| Create and run your account; run Jobs, Endpoints and the Models API | Account, usage, API and Job data | Contract |
| Charge your wallet, issue receipts, keep tax records | Billing and usage data | Contract; legal obligation |
| Show cost estimates, enforce limits, apply the failed-Job rule | Usage and Job data | Contract |
| Check student, researcher and sponsorship eligibility | Account data, institutional email | Contract; legitimate interests |
| Keep the Service secure; detect fraud, abuse and key leaks | API, usage, device data and Models API logs | Legitimate interests; legal obligation |
| Support and service messages (billing, security, changes to terms) | Account data, communications | Contract; legitimate interests |
| Improve the Service from aggregated usage, such as GPU demand and error rates | Usage data, de-identified where possible | Legitimate interests |
| Website analytics | Device and website data | Consent, where the law requires it |
| Product news and marketing emails | Name, email | Consent, or legitimate interests for existing customers; you can opt out at any time |
| Comply with law, respond to legal requests, enforce our Terms | Any relevant data | Legal obligation; legitimate interests |
Where we rely on legitimate interests, we have weighed them against your rights. You can ask us for details or object (Section 11).
6. Automated decisions
We use automated checks to block suspected fraud, abuse or key leaks, for example by pausing a key that shows unusual spend. These checks do not produce legal or similarly significant effects without a person reviewing them. If one affects you, contact us and a person will review it.
8. International transfers
We are a US company working from the UK and Tanzania, and our providers are in several countries, so your data will be processed outside the country where you live. Today Jobs run in India and the United States. As more capacity becomes cost-competitive we may add other regions, including in Africa, and we will update the list in Section 7.
When we transfer personal data out of the UK, the EU, South Africa, Kenya, Nigeria or Tanzania, we use the safeguards those laws require. For the UK and EU, these are the UK International Data Transfer Agreement or Addendum and the EU Standard Contractual Clauses, or an adequacy decision where one exists. You can ask us for a copy of the relevant safeguard.
9. How long we keep it
| Data | Kept for |
|---|---|
| Account details | While your account is open, then deleted within 30 days of closure |
| Customer Data (datasets, checkpoints, models, logs) | While your account is open or until you delete it, then within 30 days of closure |
| Models API prompts and outputs | Up to 30 days |
| Billing and transaction records | 7 years, for tax and accounting law |
| Support and other communications | Up to 3 years after the last contact |
| Security and access logs | Up to 12 months |
| Website analytics | Up to 14 months |
Backups are overwritten on their normal cycle. We may keep data longer if the law requires it or to resolve a dispute. Aggregated data that no longer identifies anyone may be kept indefinitely.
10. Security
We protect personal data with encryption in transit, hashed passwords, access controls and least-privilege access for staff, and isolation between customer workloads. We also monitor for leaked or misused API keys, and require the same standards from our providers. No system is perfectly secure. If a breach is likely to put your rights at risk, we will tell you and the regulators as the law requires. Protect your own password and API keys, and tell us at once if you think one is exposed.
11. Your rights
Depending on where you live, you may have the right to:
- access the personal data we hold about you and get a copy
- correct data that is wrong or incomplete
- delete your data, which you can also do by closing your account
- take your data with you in a portable format, for example by exporting Job outputs and metrics
- object to processing based on legitimate interests, and to direct marketing at any time
- restrict processing while a complaint is looked at
- withdraw consent where we rely on it, without affecting what we did before
- not be discriminated against for using these rights
To use any of these rights, email info@dataspires.com from your account email. We will answer within one month, or sooner if your local law requires it. We may need to verify your identity first. For Customer Data we process for an organisation, we will pass your request to that organisation and help it respond.
13. Children
The Service is not for children under 16. Students aged 16 or 17 may use it only through an account provided by their school, university or programme, as the Terms of Service allow. We do not knowingly collect data from children under 16. If you believe we have, contact us and we will delete it.
14. Students, institutions and sponsors
If your university, course or programme gives you access, it is responsible for telling you how it uses data from your account. Its administrators can see your Jobs, usage and spend. Eligibility checks use your institutional email and any proof you choose to send us, and we keep only what we need to confirm you qualify. Sponsors see aggregate figures, such as GPU-hours used by country or field, not your identity, unless you agree.
15. Changes to this policy
We will post any update here with a new “Last updated” date. If a change materially affects how we use your data, we will tell you by email or in the Dashboard before it takes effect.
16. Contact and complaints
Privacy questions and requests: info@dataspires.com
Post: DataSpires, Inc., c/o Corporation Service Company, 251 Little Falls Drive, Wilmington, Delaware 19808, USA
If you are unhappy with how we handled your data, please contact us first so we can try to put it right. You can also complain to your local data protection authority, for example:
- UK: Information Commissioner’s Office (ico.org.uk)
- EU: the supervisory authority in your country
- South Africa: Information Regulator
- Kenya: Office of the Data Protection Commissioner
- Nigeria: Nigeria Data Protection Commission
- Tanzania: Personal Data Protection Commission
