Dataceen Terms of Service

Effective date: 18 October 2026

1. The agreement

1.1 These Terms of Service (“Terms”) are an agreement between you and Dataceen AB, organisation number 559529-9016, Engelbrektsgatan 9, 411 27 Göteborg, Sweden (“Dataceen”, “we”, “us”), for the use of dataceen.com, Studio, the Dataceen MCP server, the API, and the systems and applications published with them (together, the “Service”).

1.2 The Terms consist of these terms, the Data Processing Agreement, which applies whenever we process personal data on your behalf, and the pricing page. Our Privacy Policy explains how we handle personal data as a controller.

1.3 You accept the Terms by creating an account, by drafting a model without an account, or by using the Service in any other way. If you accept on behalf of an organisation, you confirm you have authority to bind it, and “you” means that organisation.

1.4 Dataceen is a service for businesses and professionals. You must be at least 18. If you are a consumer under the law of your country, the mandatory rights that law gives you apply regardless of anything in these Terms.

1.5 A separate written agreement with Dataceen, such as an enterprise agreement, takes precedence over these Terms where they conflict.

2. Definitions

• Model: the description of a business you design in Dataceen: its entities, relationships, rules and scopes.
• System: what exists once a model, or a scope of it, is published: its database, API, MCP server, SDKs, documentation, search and events.
• Scope: a named subset of a model that a role, application or agent is allowed to see and change.
• Customer content: the sources, models, scopes, rules and instructions you submit, and the code, applications and other output generated for you, including generated code in your repository.
• System data: the records held in your systems and the data your applications and their users send to them, including example data.
• Credits: prepaid units used to pay for usage-based parts of the Service. One credit is one euro cent of usage.
• AI output: anything the Service generates with AI models, including drafted models, example data and application code.
• Dataceen materials: Studio, the generator, the platform, the MCP server and API software, documentation, templates and everything Dataceen develops to provide the Service, but not your customer content or system data.

3. Accounts, organisations and drafting without an account

3.1 Your account. Keep your account details accurate and your sign-in secure. Everything done with your account is your responsibility, including actions an AI agent takes through the MCP server or the API with your sign-in or your application’s credentials.

3.2 Organisations. An organisation in Studio is controlled by its owners. They decide who is a member, which scopes each member and application has, and they can remove members. Models, systems and repositories created in an organisation belong to the organisation, not to the member who created them.

3.3 Drafting without an account. You can draft models through the MCP server without an account, as many as you like, with up to two new models a day from each network address. A draft is kept for 30 days and then deleted. No system is created from a draft until you claim it by signing up for a free trial account; the system is then created in that account, and these Terms apply to it as to any other. Your account’s first system, including its first application, is built and hosted without a card, within the limits on the pricing page. Drafting without an account is provided as it is, with no guarantee of availability, and we may limit or end it at any time. Don’t put real personal data in a draft.

4. Using Dataceen

4.1 Your right to use the Service. We give you a non-exclusive, non-transferable right to use the Service during the term of these Terms, for your own business and to build, run and make available the systems and applications you create with it, including to your own customers and users.

4.2 Acceptable use. You may not, and may not let anyone else:

• use the Service in breach of law, export controls or sanctions, or to store or process data you have no right to process;
• put special categories of personal data (health, biometric, and similar) or payment card data into the Service unless a written agreement with us allows it;
• attack, overload, probe or bypass the security, scopes, rate limits or credit metering of the Service or of other customers’ systems;
• upload malicious code, or use the Service to build systems meant to defraud, harass, impersonate or harm others;
• resell or sublicense access to Studio or the builder MCP server itself, as opposed to the systems you build;
• copy, reverse engineer or extract the generator or the Service’s underlying models and prompts, or use the Service to build a competing model-to-system generator;
• use automated tools to create accounts or drafts in bulk, or to get around the daily draft limit.

4.3 Using an AI agent to build and operate systems through the MCP server is permitted and expected; the agent’s use counts as yours.

5. Credits, payment and taxes

5.1 Credits. AI work in the Service (drafting a model, applying changes, example data, building and changing applications) is paid for with credits. One credit is one euro cent. Each plan includes a number of credits per month; beyond those, credit packs are bought in Studio as one-time payments through Stripe, whose terms apply to the payment itself. Prices and included amounts are on the pricing page. Hosting, API calls and MCP calls are not paid in credits: each plan includes allowances for them, with usage beyond an allowance billed at the listed rates on the next invoice.

5.2 How a run is charged. Before a build or other paid run starts, the Service shows its estimate and holds that amount. When the run finishes, it settles to the actual spend and releases the rest. A run that fails costs nothing. A run you stop yourself is charged for the work done until then.

5.3 Expiry and refunds. Credits included with a plan are for that month and do not carry over. Purchased credits are valid for 12 months from purchase. They are not refundable or exchangeable for money, except where the law requires it or section 10.4 says otherwise. Credits are not a deposit or a payment instrument.

5.4 Plans. The Service is sold as plans described on the pricing page: a free trial, Studio seats (developer and consumer), production per model, dedicated systems in three sizes, hosted either in your own cloud account or by Dataceen for a hosting fee, and Enterprise Private under a separate annual licence. Each plan states what it includes: models, model size, hosted applications, included credits and usage allowances. Seats and published models are counted automatically and billed monthly per company, in EUR excluding VAT; VAT is added at checkout based on your country. A model counts while it is published; a draft does not. Allowances reset monthly. You can cancel a seat, a production model or a dedicated system any month: billing stops at the end of the paid period, and a cancelled system is retired after a grace period of 30 days during which you can export its data. Prices can change with at least 30 days’ notice; a change applies from your next billing period.

5.5 Records. Your credit history in Studio shows every hold and settlement. Tell us within 60 days if you think a charge is wrong; we correct metering errors.

5.6 Taxes. Prices are excluding VAT. You pay any VAT and similar taxes that apply. Business customers in the EU outside Sweden provide a VAT number so the reverse-charge rules apply.

6. Your content, ownership and repositories

6.1 What is yours. You own your customer content and your system data, including your models and the code generated for you: SDKs, applications and anything else in your repository. We claim no ownership of them.

6.2 What we may do with it. You give us a non-exclusive licence to host, copy, process and transmit your customer content and system data only as needed to provide the Service to you, to keep it secure, and as the law requires. We do not use your customer content or system data to train AI models, for advertising, or to build products for others. Processing of personal data in it follows the Data Processing Agreement.

6.3 Usage data. We may use technical data about how the Service is used (which tools are called, timings, errors, credit use) to run and improve the Service, in aggregated or de-identified form where it leaves our systems. It never includes the content of your models or the records in your systems.

6.4 Repositories. Generated code for each model lives in a private repository in Dataceen’s GitHub organisation. You can invite GitHub users to it as administrators at any time. You can also transfer the repository to a GitHub account or organisation you choose: after the transfer it is entirely yours, Dataceen pushes nothing more to it, and republishing or changing an application no longer updates that code. A transfer cannot be undone by us.

6.5 Third-party code. Generated code may include open-source libraries. Each keeps its own licence, listed in the repository; you comply with those licences.

6.6 What is ours. Dataceen materials remain ours, together with all improvements to them. Generated code you own does not give you rights to the generator that produced it.

6.7 Your responsibility for content. You are responsible for having the right to everything you submit: sources, documents, specifications and the personal data in them.

7. AI output and example data

7.1 Dataceen uses AI to draft models from your sources, generate example data, and build and change applications. AI output can be wrong or incomplete. That is why Dataceen shows you the drafted model to review before it is built: you are responsible for reviewing models, scopes and generated applications before you rely on them, and for testing them before production use.

7.2 Don’t rely on AI output without appropriate human review where an error could affect health, safety, legal rights or significant financial decisions.

7.3 AI output for similar sources may be similar for different customers. We do not promise that it is unique or free of third-party rights, beyond what section 11.3 covers.

7.4 Example data is generated and fictional. Any resemblance to real people or companies is coincidental. Don’t treat it as real records, and remove it before a system goes into production if it shouldn’t be there.

8. Hosted systems and availability

8.1 Storage. Your system data is stored either by Dataceen in the EU, in Sweden and Belgium, or in a database you run. When you run the storage, you are responsible for its availability, backups and security; Dataceen is responsible for the Service’s side of the connection.

8.2 Addresses. Systems and applications hosted by Dataceen get addresses under dataceen.com. Those addresses belong to Dataceen. We change or withdraw one only to stop abuse, impersonation or a trademark conflict, or where the law requires it, and except in urgent cases we give 14 days’ notice. Use your own domain for anything that must keep its address.

8.3 Availability. We work to keep the Service available and tell you in advance about planned maintenance where we can. Unless a separate agreement includes a service level, the Service has no guaranteed uptime. Parts of it depend on hosting, identity, GitHub and AI providers we don’t control.

8.4 Changes to the Service. We develop the Service continuously and may change features. We give at least 30 days’ notice before removing a feature you pay for, or changing a published system’s generated API or MCP tools in a way that breaks existing clients.

8.5 Beta features. Features marked beta, preview or experimental may change or end without notice, are provided as they are, and are outside any service level.

9. Third-party services and AI hosts

9.1 You can connect Dataceen to services you choose: an AI host such as Claude, Claude Code or Cursor, a GitHub account, your own database or identity directory, or a coding agent that builds on the SDK. Those services are governed by your own agreements with their providers. We are not responsible for them, or for what they do with data you let them reach.

9.2 Scopes decide what each application or agent can reach in your systems. Publishing a scope, and handing its MCP server or credentials to an AI host or application, is your decision; publish a narrow scope for each consumer rather than the full model.

10. Suspension and termination

10.1 You can close your account at any time in Studio.

10.2 We may suspend an account, a system or an application immediately where that is needed to stop a security threat, serious abuse, a breach of section 4.2 or illegal content, or where the law requires it. We suspend only what is needed, tell you why, and restore access once the cause is dealt with. You can ask for a person to review an automated suspension.

10.3 We may terminate these Terms with you for a material breach you have not remedied within 14 days of our notice, or immediately for fraud or repeated serious abuse. We may also end the Service for everyone, or terminate for convenience, with at least 90 days’ notice.

10.4 Credits on termination. If you close your account, unused credits lapse. If we terminate for convenience or end the Service, we refund unused paid credits. If we terminate for your breach, unused credits lapse unless the law says otherwise.

10.5 Your data at the end. You can export system data and take over your repositories until the account closes, and for 30 days afterwards on request. After that we delete customer content and system data as the Data Processing Agreement describes. A repository you have already taken over is unaffected.

10.6 Sections 6, 7, 11, 12 and 13 survive termination.

11. Warranties, indemnities and liability

11.1 What we promise. We provide the Service with reasonable skill and care, in line with its documentation, and protect your data as the Data Processing Agreement describes. Beyond that, and as far as the law allows, the Service and AI output are provided as they are, without other warranties, including fitness for a particular purpose.

11.2 Your indemnity. You will defend us against third-party claims arising from your customer content or system data, from your systems and applications as you operate them, or from your breach of section 4.2, and pay the damages and reasonable costs finally awarded.

11.3 Our indemnity. We will defend you against third-party claims that Dataceen materials, as we provide them, infringe that party’s intellectual property rights, and pay the damages and reasonable costs finally awarded. This does not cover claims caused by your customer content, by AI output based on your sources, or by changes you make. If a claim is likely, we may modify the Service or, if that is not reasonable, end the affected part and refund unused paid credits.

11.4 Conditions. The party claiming an indemnity notifies the other promptly, lets it control the defence, and cooperates reasonably.

11.5 Limitation of liability. Neither party is liable for indirect or consequential loss, lost profit, lost revenue or loss of goodwill. Each party’s total liability under these Terms in any 12 months is limited to the greater of the fees you paid us in the 12 months before the claim and EUR 5,000.

11.6 The limits in 11.5 do not apply to liability for gross negligence or intent, to your payment obligations, to the indemnities in 11.2 and 11.3, or where the law does not allow liability to be limited.

12. Illegal content, feedback and publicity

12.1 Reporting content. If you believe a system or application hosted by Dataceen contains illegal content or infringes your rights, report it to legal@dataceen.com with the address, what is wrong and why. We act on reports without undue delay, tell the customer concerned unless that would be unlawful or unsafe, and explain our decision to both. Our point of contact for users and authorities under articles 11 and 12 of the EU Digital Services Act is legal@dataceen.com, in English or Swedish.

12.2 Feedback. If you send us suggestions about the Service, we may use them freely, without obligation to you. Feedback does not include your customer content.

12.3 Publicity. We name you or show your logo as a customer only with your written permission, which you can withdraw at any time.

13. General

13.1 Changes to these Terms. We may change these Terms. For changes that reduce your rights, we give at least 30 days’ notice by email and in Studio; you can close your account before they take effect, and if you do, we refund unused paid credits. Other changes take effect when published.

13.2 Notices. We send notices to the email address of the account owner, or show them in Studio. Send notices to us at legal@dataceen.com.

13.3 Assignment. Neither party may transfer these Terms without the other’s consent, except to a successor of its whole business, with notice.

13.4 Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control.

13.5 Export controls and sanctions. You may not use the Service from, or for anyone in, a country or on a list subject to EU, UK or US sanctions.

13.6 Entire agreement. These Terms, with the documents in 1.2, are the whole agreement about the Service. If a provision is invalid, the rest still applies. Not enforcing a provision is not a waiver of it.

13.7 Law and disputes. These Terms are governed by Swedish law, without its conflict-of-law rules. Disputes are settled by the Gothenburg District Court (Göteborgs tingsrätt) as first instance. Consumers keep the right to bring proceedings where they live.

13.8 Contact. Dataceen AB, organisation number 559529-9016, Engelbrektsgatan 9, 411 27 Göteborg, Sweden · Support: support@dataceen.com · Legal notices: legal@dataceen.com