Terms of Service

1. Your account

You create an account with your work email and a password, and confirm the email before the workspace opens. You are responsible for keeping your password and API keys secure and for activity in your workspace.

The person who creates a workspace is its owner. The owner can invite people by email as admins or members, up to 50 people. An invitation link works once, only for the invited email, and expires after 7 days. Owners and admins manage billing; members can use the workspace but cannot see or change the card, billing address, bills or transactions, and can reveal or revoke only the API keys they created. The owner is responsible for the workspace and its members.

Accounts are for business use. You confirm that you are authorised to accept these terms for the organisation you work for.

2. Prepaid credits and holds

Your workspace has a credit balance in US dollars. You buy credits in any amount of at least $1. Credits are added only after the payment processor confirms the payment, and they can be used only by your workspace. Credits are not a deposit with, or a payment to, any of our subprocessors. Credits do not expire. There is no self-service refund of unused credits; contact us about unused credits.

Before you start work you see an estimate. An estimate is for planning only and is not the charge.

• Training. Starting a run requires available credits of at least the estimate plus 25%. That amount is held from your credits when the run starts. A hold is not a charge, and it is not a spending cap: the final charge is based on verified usage and can be higher than the hold.
• Serving. Starting a deployment holds one active hour plus 25% at the rate shown when you deploy, and the hold grows before each further active hour. If your credits cannot cover the next hour, the deployment is stopped.

You can redeem a credit code we issue to you once per workspace. Codes may expire.

3. Charges and your card

• Training is charged after it finishes, on the run's verified usage at the rate shown when you started it, rounded up to the cent. A later price change never applies to a run you already started. A run that fails before training starts is not charged. A run that fails after training started is charged for the usage it verifiably consumed.
• Serving is charged for active GPU time at the hourly rate shown when you deployed. Start-up time and time scaled to zero are not charged.
• Card on file. A saved card is required before you start training. You add it on the payment processor's hosted page; the processor stores the card. By saving a card you authorise us to charge it (a) when a verified bill exceeds your available credits, for the difference, with a minimum single charge of $0.50 (any amount above the difference is added to your credits), and (b) for automatic top-ups, only if you turn them on.
• Bills are settled in full or not at all. If your credits and card do not cover a verified bill, it stays pending and new training waits until it is settled. We never take part of a bill and never collect your bill from another customer.
• You cannot remove your card while a run is in progress, a bill is pending or a card payment is being processed.
• Prices are shown in the workspace before you start. When our upstream prices change, new estimates, training starts and deployments are paused until our prices are updated; work that is already running continues.
• Monthly statements and payment receipts are available in Billing. Prices exclude any taxes that apply.

4. Spend limits and tiers

Every workspace has a monthly spend limit, counting this calendar month's (UTC) charges plus credits currently held. Tier 1 allows up to $500 a month; tier 2 up to $5,000 once your total charges reach $500; tier 3 up to $50,000 once they reach $5,000. You can set a lower limit of your own. When the limit would be passed, new training and deployments are refused and a running deployment stops before the hour that would pass it. Training that is already running is not stopped and is billed normally, so the limit is a safeguard, not a guaranteed cap. Contact us for a higher limit.

5. Acceptable use

You must not use the service to:

• upload data you do not have the right to use for training, evaluation and serving — the workspace asks you to confirm these rights before a run is created;
• train or serve a model in breach of law, of the licence of the base model you choose, or of the usage policies of the providers that run training and inference;
• upload malware, or content that is unlawful, infringing, or sexual content involving minors;
• access or attempt to access another customer's workspace, data, keys or bills, probe or disrupt the service, or work around its limits, holds or billing;
• share API keys outside your organisation or resell access to the service without our written agreement.

Do not upload special categories of personal data, health records or payment card numbers unless we have agreed this with you in writing.

6. Your data and your models

You own the datasets you upload, the fine-tuned model weights trained from them, and the outputs your models produce, subject to the licence of the base model and the terms of the providers that run training and inference. You give us a limited licence to process this material only to provide the service to you: preparing training, validation and test splits, training, evaluating, serving, billing and support. We do not use your datasets to train models for anyone else.

Fine-tuned weights are stored in our account with the training provider and served from there. The workspace does not currently offer a weights download; contact us to arrange a handoff. How we handle data, and how to ask for deletion, is in the Privacy policy and the Data processing addendum.

7. Confidentiality

Each party keeps the other's non-public information confidential, uses it only for this relationship, and shares it only with people and subprocessors who need it and are bound to protect it. This does not cover information that is public, already known, independently developed, or that must be disclosed by law (with notice where allowed).

8. Third-party services

We use the subprocessors listed on the Subprocessors page for hosting, storage, authentication, training and inference, payments and email.

9. Warranty disclaimer

The service is provided “as is” and “as available”. Estimates, evaluation scores and tiers are information, not promises. Evaluation scores are measured on your held-out test examples and may not reflect other data. We do not warrant that tuning will improve your model, lower your costs, or that the service will be uninterrupted or error-free. To the extent the law allows, we disclaim all implied warranties, including merchantability, fitness for a particular purpose and non-infringement.

10. Limitation of liability

To the extent the law allows, neither party is liable for indirect, incidental, special or consequential damages, or for lost profits, revenue or data, and each party's total liability arising from these terms is limited to the amounts you paid us in the 12 months before the claim. These limits do not apply to your payment obligations, to a breach of the acceptable use section, or to liability that cannot be limited by law.

11. Suspension

We may suspend new work, serving or access, with notice where practical, if you breach these terms, if your use creates a security or legal risk, or if a payment is refunded or disputed. A refunded or disputed payment places a billing hold on the workspace: no new paid work can start until it is resolved. A pending bill blocks new training until it is settled.

12. Termination

You can stop using the service at any time: stop your deployments, then ask support@attempts.ai to close the workspace and delete its data. We may end these terms on 30 days' notice, or at once for a serious breach. Verified bills for work that has already run remain payable. Deletion follows the Privacy policy; billing records are kept as required for accounting.

13. Changes

We may update these terms. We will post the new version here with its effective date and tell workspace owners by email before a material change takes effect. Continuing to use the service after that date means you accept the change.

14. Governing law

The governing law and the courts that hear disputes will be stated here once the contracting entity is finalised.

15. Contact

Email support@attempts.ai.