Back to Home

Beta Terms

Effective date: September 21, 2026. DoThat is a pre-release beta. This page says what that means for you, in one place, rather than as a clause inside the Terms. DoThat is operated by DoThat AI Ltd (company number 17351077), registered in England and Wales. Questions go to legal@dothat.com.

Read this first

The two that catch people out: beta data may be deleted at any time, and if you deploy a Goblin to anyone outside your organisation you must give them your own terms first.

1. What "beta" means here


DoThat is pre-release. It is not generally available, it carries no service level, and it is provided entirely as-is — we do not warrant that it will run uninterrupted or error-free, and we have no obligation to maintain, support, update or fix it. Features may change, break, or be withdrawn without notice, and we will tell you about material changes where we reasonably can. We are not promising a release date, and nothing on this site should be read as a commitment to build something you have not seen working. Beta access is under a signed Beta Participation Agreement; this page says what it means, and that agreement is what governs.

2. Your data during the beta


While the beta notice is displayed, platform data — including your account, your Goblins, your Datasets and conversation history — may be deleted at any time, without notice and without liability to you. This is a real risk, not boilerplate. Do not put anything into DoThat that you cannot afford to lose, and keep your own copies of anything that matters. Your content is yours: we do not own it, and we process it under our Data Processing Addendum. We will not use it — your prompts, your chats, your files, or anything a Goblin generates from them — to train, fine-tune or improve any AI model, ours or anybody else's, other than a Goblin you build in your own account, and we hold our own people and our subcontractors to the same promise. The models your Goblins run on are either served to the platform by Google inside our Google Cloud environment under our agreement with Google, or, where a model is served directly by its provider, under our agreement with that provider as a sub-processor listed in our Data Processing Addendum; in each case that agreement says the data you send to the model is not used to train the provider's own models. If the beta ends for you, you have 30 days to export everything, and we securely delete it within a further 30 days — unless the law or a regulator requires us to keep it, in which case we go on protecting it under the Addendum and delete it once that requirement ends.

3. Deploying to your own customers and users


You may deploy a Goblin beyond your own organisation during the beta — to your customers, your members, the public — and many participants do. If you do, you are its publisher. Before anyone outside your organisation first interacts with it — on a public or link-shared page, in an embed, over email or through a messaging channel — you must show them, and have them accept, terms of use and a privacy notice you issue; linking to your own terms and privacy policy is enough. Those terms must at least name you as the publisher and as the person answerable for the Goblin and its answers, say that we are not a party to them and give the end user no warranty, tell them that answers are generated by artificial intelligence and may be wrong, that they must not rely on an answer without checking it, and that they must not rely on one for a legal, financial, medical or other regulated decision without independent professional advice, set out acceptable use that is no less restrictive than the limits in the next section and the model providers' own policies, limit your own liability to your end users in a way that actually works in your hands, let us enforce the disclaimer, no-reliance, acceptable use and liability terms directly against the end user under the Contracts (Rights of Third Parties) Act 1999, and cover data protection — including a privacy notice that names you as the controller and us as the processor and points to our list of sub-processors. The platform has this built in and records each acceptance against the version of the terms accepted. Those terms are yours: you are responsible for their content and enforceability, we are not a party to them, and you indemnify us against claims arising from them or from failing to impose or enforce them.

4. What you must not build during the beta


You must not use the platform or a Goblin for medical diagnosis, emergency services, or anything safety-critical; to make decisions with legal or similarly significant effects on people without appropriate human review; to give regulated legal, accounting, tax, medical or financial advice unless you are authorised to give it and remain responsible for it; to make automated credit, lending, insurance, employment, housing or eligibility decisions without human oversight and compliance controls; or in any way that breaches the law or your regulator's guidance. You must also follow — and make sure your own users and your end users follow — the acceptable use and prohibited use policies of the model providers whose models you reach through the platform, as those policies change from time to time; where one of them is stricter than the list above, it wins. Which models you can use may depend on your use case, and we may restrict, withdraw or substitute a model for a particular Goblin or use case where a model provider or one of those policies requires it. Where a Goblin is deployed in a domain in which its answers could be taken as legal, financial, medical, tax or other professional advice, you must make sure it shows end users a prominent disclaimer that its answers are not professional advice and should be independently verified before anyone relies on them. Using DoThat does not reduce your own professional, legal or regulatory obligations, and you remain responsible for every decision made with a Goblin you built.

5. Paying during the beta


Paying for a plan does not change the position above. What paying changes is your usage allowance and limits — nothing more. Fees are payable in advance and are not refundable for a change of mind; if we end the beta for you other than for your breach, we refund the unused part of what you have paid. If that trade is not right for you, wait for general availability.

6. Feedback and confidentiality


Tell us what breaks — it is the most useful thing you can do during a beta, and it genuinely shapes what gets built. Feedback you send us we may use freely, without obligation or payment to you. Do not include anything confidential in it. The beta agreement is mutually confidential and we ask participants not to publish details of how the platform works while it is pre-release; that does not stop you demonstrating or deploying your own Goblins to your own customers and users.

7. Liability during the beta


Because this is a pre-release pilot, liability is allocated accordingly: we are not responsible for how you configure, test, validate or deploy a Goblin, for the accuracy or legality of your own data, for any answer a Goblin gives, for your compliance with the rules of your own sector, or for decisions anyone takes in reliance on the platform. We also exclude liability for lost, corrupted or unavailable data — except where that is caused by our own breach of the agreement or of the Data Processing Addendum, our negligence, or our failure to keep appropriate security measures in place, and even then our liability stays subject to the cap. Our total liability is capped at the greater of £100 and the fees you have paid us in the 12 months before the claim. You indemnify us against third-party claims arising from your own data, from how you configure, test, validate, deploy or use a Goblin, from a Goblin's answers or decisions taken in reliance on them, from using the platform in breach of the agreement, from deploying a Goblin to your own customers and users or from your own end-user terms, from breaking any law, regulation, regulatory guidance or sector rule that applies to your business, your Goblins or your end users, and from any claim your own customers or end users bring about a Goblin, its answers, or a product or service you offer using one — except where the loss is caused by our breach or our negligence. That indemnity sits outside the liability cap and is not counted towards it. Nothing excludes liability that cannot lawfully be excluded, including death or personal injury caused by negligence and fraud.

8. When the beta ends


Either side can end beta participation at any time on written notice, and either side can end it immediately for a material breach that is not put right within 10 business days. We may suspend or restrict your access immediately — to the platform, or to a particular Goblin, model or feature — where we reasonably believe there has been unauthorised access to or use of the platform; that you, one of your users or an end user is breaking the limits above or a model provider's policies, or is using the platform or a Goblin in a way that is unlawful, harmful or likely to expose us or a model provider to liability or reputational harm; that a model provider, our hosting provider or the law requires it, or that it is needed to stop our access to a model or hosting service being throttled, suspended or terminated; or that it is needed to protect the security, integrity or performance of the platform or of our other clients. If we do suspend you, we will tell you as soon as we reasonably can, keep the suspension to what is reasonably necessary, and work with you to sort it out. When DoThat becomes generally available this notice is withdrawn and the Terms of Service apply without the beta position. We will tell existing users before that happens, and we will not quietly convert a beta account into a paid commitment.

Questions about this page? Reach us through our Contact page.

Back to Home