Contract changelog

Terms of Service, version 2.9 (previously 2.2)

• 2.3 (2 Sep 2026): clause 9.2 states a two-month maximum; clause 21.1 takes gross negligence outside every limitation of liability; clause 24.1a is new and governs the transition period; clause 24.2 says when the deletion period begins.
• 2.4 (10 Sep 2026): the Service is now also open to consumers (clause 1.3 recast); the new section 32 states clause by clause what applies differently to consumers; the withdrawal notice is added as a related document.
• 2.5 (11 Sep 2026): the new clause 6.6 makes clear that a person's account type applies to the workspaces that person owns, and that membership in another Customer's workspace does not change that Customer's contract.
• 2.6 (16 Sep 2026): clause 4.3 distinguishes between entrepreneurs and consumers (consumers give a name and e-mail address, no company details); clause 6.6 states that an invited person joins a workspace only by accepting the invitation through the link in the invitation e-mail, even if that person already has an account.
• 2.7 (7 Oct 2026): clause 24.2 states that a deletion started by the Customer first archives the account for 30 days – access ends at once, nothing is recorded or shown any more, and it can be restored on request – and that permanent erasure at once can be chosen; deleted projects and workspaces are archived in the same way. The 30-day period for erasure is unchanged.
• 2.8 (16 Oct 2026): clause 24.1a now describes what actually happens when a paid subscription ends – the account continues on the Free Plan, the previous retention period applies for 30 days, projects beyond the limit are paused – instead of a transition period in which the account would be readable only; clause 24.2 says when the contract ends. Clause 6.5 says that only free accounts that do not belong to a workspace of a paying customer are deleted for inactivity. Further alignment with the technical state: clauses 4.2 (which checksums are recorded), 5.1 and 17.1 (draft offer texts and support assistance by the language model), 7.4 (duration of automatic blocks, shortened retention for free accounts suspected of abuse), 20.4 (canvas, frames, shadow DOM), 21.6 (log retention), 24.5 (exceptions to processing in the EU) and the page header (the account type is chosen at registration). Also in 2.8: clauses 4.2 (the record concerns every customer; the most recent acceptance is kept for as long as the account exists; older entries fall after the period from the respective acceptance), 7.1 and 13.4 (no restore, handling of backup copies), 7.4 (duration of automatic blocks follows the configured block duration), 11.2 (exception of regional release), 14.2 and 24.5 (the provider of the storage location does not receive the keys), 14.4 (routes to the information page), 17.1 (checking generated texts for figures), 19.5 (support hours), 24.1a (grace period as a minimum), 24.2 (every ground on which the contract ends, longest period in our systems) and the new clause 32.12 (further deviations for consumers, for example on price increases, late-payment interest, termination of the Free Plan, transfer of the contract and public statements about the Service).
• 2.9 (27 Oct 2026): the new clause 17.4 requires every automatically generated text to be checked by a person before it is used, in particular before it is shown to visitors or sent to anyone in the Customer’s name – a wrong statement or a wrong price in the name of a shop is a statement of the shop; clause 21.2 excludes liability for damage arising from using such text unchecked.

Data Processing Agreement, version 1.6 (previously 1.3)

With 1.4 the exception for the off-site backup in section 6 has lapsed, because since 5 September 2026 the copy is held in Google Cloud Storage in Warsaw under the Google Cloud Data Processing Addendum; new sentence that generated texts are phrased on our own hardware. With 1.5 (7 Oct 2026) section 9 states that a deletion started by the Customer archives first and erases permanently after 30 days, at once if chosen. With 1.6 (16 Oct 2026) the recording archive is named as part of the backup (since 6 Oct 2026); section 5 describes the transport paths accurately (encrypted from the internet, unencrypted within the own local network to the database and cache); sections 2 and 4 name the categories of data processed and the handling of IP addresses and URLs in full; section 9 names the shorter periods for bot sessions and the deletion of unused free accounts. Also in 1.6: section 2 names the subject matter, purpose and types of data; section 4 names the duties where processing is required by law and where an instruction is unlawful, regional release and the web server logs; section 6 describes how sub-processors are bound by contract and the form of an objection; section 7 names the information page for end users; section 9 names return or erasure at the controller’s choice.

List of sub-processors, version 1.5 (previously 1.2)

With 1.5 (16 Oct 2026): the Stripe row names all data transmitted and says that payment processing is not yet in operation; the Namecheap row names every kind of e-mail sent; the reCAPTCHA row names every form; the backup row names the recording archive; the VAT ID check with VIES is listed as a recipient that is not a sub-processor. Also in 1.5: the backup row attributes the keys to MousePlayer, the statements on acceptance of the terms are identified as statements of MousePlayer, and section 3 states the form of an objection. With 1.4 (24 Sep 2026) the Namecheap row names outgoing e-mail through Namecheap Private Email and the data sent with it. With 1.3: the backup row names Google Cloud Storage in Warsaw (since 5 September 2026) and the deletion of the earlier copies on 6 September 2026; the reCAPTCHA row no longer contradicts it; the operations row names the machines that run the language model; the sentence on notification says where the notice appears.

Why

We aligned the documents with how the Service actually works, opened it to consumers, moved the backup to a location covered by a data processing agreement, and protected deletions against mistakes without extending the period. With the versions of 16 October 2026 we checked the texts against the technical state once more and corrected them wherever they described more or something other than what the Service actually does.