Terms of service
The terms for using Typestate. As of 28 September 2026.
The German version governs. This English version is a translation of the German version.
Section 1 Provider and scope
(1) The provider is Lütfi Demirci, trading as "Typestate", Neckarstr. 21, 12053 Berlin, Germany, email hello@typestate.com ("we"). Further details are in the Impressum.
(2) These terms apply to every contract for the use of the Typestate platform: the management interface at platform.typestate.com ("cockpit"), the MCP server at mcp.typestate.com, and the backends and websites we run for the customer (the "service").
(3) Customers can be consumers (section 13 BGB) or businesses (section 14 BGB). Rules that apply to only one of the two groups say so.
(4) The customer's own terms do not apply, even where we do not expressly object to them.
(5) The acceptable use rules and, for businesses, the data processing agreement are also part of the contract.
Section 2 Conclusion of the contract
(1) The presentation of the plans on typestate.com is not a binding offer.
(2) Free plan. The customer makes an offer by sending the sign-up form. The contract is concluded when we open the account. There is no right to have an account opened.
(3) Paid plans. The customer makes an offer by pressing the "order with obligation to pay" button on the order page. Before sending, the customer can check and correct the entries. The contract is concluded when we confirm the order by email.
(4) The contract languages are German and English. We store the contract text. These terms are always available on this page and can be saved and printed. With an order, the customer receives the contract details and these terms in text form.
(5) The customer gives correct details at sign-up and when ordering. When ordering, the customer states whether they act as a consumer or as a business.
Section 3 Services
(1) Typestate is a platform on which the customer describes the business logic of a backend in natural language. The platform translates these descriptions into program code with the help of language models, checks the code, versions every change and runs the result at an internet address. The customer operates the platform through the cockpit or through an AI agent that the customer connects over the Model Context Protocol (MCP).
(2) The description in natural language governs. The platform derives the program code from it. The customer can read the code in the cockpit and over MCP, and cannot change it. The code is not handed over as a separate work.
(3) Every backend has two environments: "Sandbox" for development and testing, and "Live" for operation towards the customer's users. The Free plan has Sandbox only.
(4) The scope, limits and prices of the plans are in the plan overview on typestate.com. The version in force when the contract is concluded governs.
(5) When use reaches the limit of the plan, the platform stops Sandbox. What happens to Live is in the plan overview. At 80 % of the limit the customer receives a warning.
(6) We develop the service further and may change it, as long as the agreed scope of service is kept.
(7) Consumers only: changes to the digital service (section 327r BGB). We may change the service beyond what is needed to keep it in conformity with the contract if there is a valid reason (for example a change of language model or infrastructure provider, a security measure or a legal requirement), the consumer incurs no additional cost, and we inform the consumer clearly and understandably. If the change impairs access or usability more than insignificantly, we inform the consumer at least 30 days in advance in text form. The consumer can then end the contract free of charge within 30 days after the information or after the change, whichever is later.
Section 4 Availability
(1) We do not promise any particular availability. We make efforts to run the Live environment without interruption.
(2) The Live backends run at Cloudflare and stay reachable when the cockpit or the MCP server is not. During a fault of the cockpit the customer cannot change their backends.
Section 5 Prices and payment
(1) The fees follow from the plan overview in force when the contract is concluded. Towards consumers we state the total price including VAT before the order. Towards businesses the prices are exclusive of statutory VAT.
(2) The fees are due monthly in advance. Use beyond the limit of the plan, where the plan overview provides for it, is charged afterwards with the next invoice.
(3) The customer pays through our payment service provider Stripe, with the payment methods offered there. We issue invoices electronically.
(4) If the customer is in default with a payment, we tell the customer so in text form and set a period of at least 14 days. If the customer does not pay within that period, we may block the paid services until payment is made. The open amount remains owed.
(5) Price changes. We announce a price change in text form at least six weeks before it takes effect. It applies only if the customer agrees. If the customer does not agree, either side can terminate the contract as of the date the change takes effect.
Section 6 Term and termination
(1) The contract runs for an indefinite period and is billed monthly.
(2) The customer can terminate a paid plan at any time as of the end of the current billing month. The account then continues on the Free plan unless the customer terminates that as well. We can terminate a paid plan with one month's notice to the end of a month.
(3) The customer can terminate the Free plan at any time. We can terminate it with four weeks' notice.
(4) The customer can terminate in text form, for example by email to hello@typestate.com. Consumers can also terminate through the "terminate contracts here" button once they have concluded a paid contract (section 312k BGB).
(5) The right of both sides to terminate for good cause (section 314 BGB) is not affected. Good cause for us is in particular a serious breach of the acceptable use rules.
(6) A move to a higher plan applies from payment of the pro rata amount. A move to a lower plan applies from the next billing month.
(7) Consumers have a statutory right of withdrawal. The details are in the withdrawal notice.
Section 7 Data after the end of the contract
(1) Until the end of the contract the customer can retrieve their descriptions, tests and settings through the cockpit or their agent, and the records of their backends through their own endpoints. On request we provide the records of the customer's backends in a common, machine-readable format.
(2) When the contract ends, we stop the customer's backends and websites. We keep the customer's data for 30 more days, so that the customer can obtain it or continue the contract. After that we delete it. Copies in backups are overwritten in the regular cycle, at the latest after a further 30 days.
(3) Statutory retention duties, for example for invoices (section 147 AO, section 257 HGB), are not affected.
(4) For personal data that we process on behalf of a business, the data processing agreement takes precedence.
Section 8 Duties of the customer
(1) The customer keeps their access credentials, API keys and agent connections secret. Actions that an agent connected by the customer takes through the MCP server count as actions of the customer. This includes approving changes for Live.
(2) Before each approval for Live, the customer checks whether the backend does what the customer described. The platform translates with language models. It checks the generated code with type checking and tests, but cannot rule out that the code differs from the description.
(3) The customer complies with the acceptable use rules.
(4) The customer does not write personal data of their users into descriptions and tests. Descriptions and tests are sent to language model providers for translation (see the privacy notice).
(5) The customer is responsible for the content and data in their backends and websites, and for the lawfulness of what they do with them towards their users.
Section 9 Rights in content
(1) The customer's descriptions, tests, data and content remain the customer's. The customer grants us the rights we need to provide the service, in particular to store them, to send them to language model providers, to translate them and to run them.
(2) We do not use the customer's content to train language models.
(3) The platform, the SDK, the translation and the generated code remain ours. For the term of the contract the customer receives a simple, non-transferable right to use the service.
Section 10 Warranty
(1) For businesses, the rules of tenancy law (sections 535 ff. BGB) apply accordingly. Liability without fault for defects present when the contract is concluded (section 536a(1), first alternative, BGB) is excluded.
(2) For consumers, the statutory rules on digital products (sections 327 ff. BGB) apply.
(3) The customer reports defects through the cockpit, through their agent or by email.
Section 11 Liability
(1) We are liable without limitation for intent and gross negligence, for injury to life, body or health, under the Product Liability Act, and to the extent of a guarantee we have given.
(2) For slight negligence we are liable only for breach of a material contractual duty, that is a duty whose fulfilment makes the proper performance of the contract possible in the first place and on whose observance the customer may regularly rely. Liability is then limited to the damage that was foreseeable and typical for the contract when it was concluded.
(3) Towards businesses only: in the cases of paragraph 2, liability per contract year is further limited to the fees the customer paid in the twelve months before the event causing the damage, but to at least 1,000 EUR. For loss of data we are liable only for the effort that would have been needed to restore it had the customer made regular backups appropriate to the importance of the data.
(4) Paragraphs 1 to 3 also apply to our vicarious agents.
Section 12 Data protection
(1) How we process personal data as controller is in the privacy notice.
(2) Where a business stores personal data in its backends, we process that data on its behalf. For this the data processing agreement applies, which becomes part of the contract when these terms are accepted.
Section 13 Changes to these terms
We announce changes to these terms in text form at least six weeks before they take effect. They apply if the customer agrees. If the customer does not agree, either side can terminate the contract as of the date the changes take effect.
Section 14 Consumer dispute resolution
We are not willing and not obliged to take part in dispute resolution proceedings before a consumer arbitration board.
Section 15 Final provisions
(1) The law of the Federal Republic of Germany applies, excluding the UN Convention on Contracts for the International Sale of Goods. Towards consumers this choice of law applies only to the extent that it does not deprive them of the protection given by the mandatory provisions of the state in which they have their habitual residence.
(2) If the customer is a merchant, a legal entity under public law or a special fund under public law, the place of jurisdiction is Berlin.
(3) If a provision is invalid, the remaining provisions stay valid.