Terms of Service

These Terms of Service (“Terms”) govern your access to and use of the Dibbla platform, including the web application at app.dibbla.com, the Dibbla CLI, the Dibbla Desktop App, and related APIs (collectively, the “Service”), operated by Dibbla AB (“Dibbla,” “we,” “us,” or “our”), a company registered in Sweden.

By creating an account or using the Service, you agree to be bound by these Terms. If you do not agree, do not use the Service.

1. The Service

Dibbla is a platform for building, deploying, and running the applications and AI agents your organisation builds with a code assistant of its choice. You bring the code; the Service builds it, runs it, and gives it what it needs to be used in an organisation: a URL with TLS, sign-in and access control, managed PostgreSQL databases and storage buckets, secrets, custom domains, logs, a code review of every deployment, scheduled checks, an AI gateway that meters every model call, an audit log, and a portal where your users find the apps they may open. The Service also includes a workflow engine for agentic workflows, a maintenance agent you can switch on per app, and an AI connector through which an agent of your choosing can operate the platform (see Section 5).

Features, integrations, plan limits, and pricing may change as the Service evolves. We will notify you of material changes that affect your use. Self-hosted or dedicated deployments of the platform are governed by a separate agreement.

2. Accounts

To use the Service you must create an account by signing in with a supported authentication provider (currently Google or Microsoft). You are responsible for maintaining the security of your account and for all activity that occurs under it.

You must provide accurate information and promptly update it if it changes. We reserve the right to suspend or terminate accounts that violate these Terms or that we reasonably believe are being used fraudulently.

3. Your Data

Customer Data means everything you put on the Service and everything your applications produce there: the source code and container images of your applications, the contents of your databases and storage buckets, your secrets and configuration, your workflows and their run history, and the data that your own users and customers enter into or generate in your applications. You retain all rights to your Customer Data, including all intellectual property in the applications you build.

You grant Dibbla a limited licence to host, build, run, process, and display your Customer Data solely to provide and operate the Service. We will not use your Customer Data to train general-purpose AI models or share it with third parties except as described in our Privacy Policy.

Where Customer Data contains personal data about your users or customers, you are the controller of that data and Dibbla processes it on your behalf and on your instructions as a processor under the GDPR. Our Data Processing Agreement forms part of these Terms and governs that processing: instructions, security, sub-processors, breach notification, and deletion when the agreement ends. By accepting these Terms you also accept the Data Processing Agreement. You are responsible for having the rights and legal basis you need for the data you upload or collect, and for what your applications do with it. Do not use the Service for special-category personal data (e.g. health records) unless we have agreed to it in writing.

4. Acceptable Use

You agree not to:

• Use the Service for any unlawful purpose or in violation of any applicable law or regulation.
• Attempt to gain unauthorised access to the Service, other accounts, or related systems.
• Interfere with or disrupt the integrity or performance of the Service.
• Reverse-engineer, decompile, or disassemble any part of the Service.
• Use the Service to send spam, distribute malware, or engage in any form of abuse.
• Resell or redistribute the Service without our prior written consent.

Reasonable use of resources

The Service is built for running the applications and agents your organisation actually uses, and its plans are priced on that basis. Compute, memory, storage, and network are shared resources, and your plan sets limits on them. You agree not to use the Service for workloads whose main purpose is to consume those resources rather than to serve your organisation — for example cryptocurrency mining, proof-of-work or similar computation, distributed computing projects, load testing or scanning of systems you do not own, bulk scraping, or operating a general-purpose proxy, VPN, or file-hosting service — and not to run automated model calls in a loop with no purpose beyond generating usage. We may limit, pause, or stop a workload that consumes far more than its plan provides for or that degrades the Service for others, and we will tell you when we do so.

We may suspend or terminate your access if you breach these terms.

5. Third-Party Integrations and AI Connectors

The Service allows you to connect to third-party services (e.g. Google Workspace, Microsoft). Your use of those services is governed by their own terms and privacy policies. We are not responsible for the availability, accuracy, or practices of third-party services. You authorise Dibbla to access those services on your behalf only to the extent required by the integrations you enable.

Model calls your applications make through the Service's AI gateway are passed to the model provider you have chosen (e.g. Anthropic, OpenAI, or a provider you bring), are metered and attributed to your organisation, and are subject to that provider's usage policies as well as these Terms.

The Service also exposes an AI connector — a Model Context Protocol (MCP) endpoint that lets an AI agent of your choosing act on the Dibbla platform on your behalf. Connecting an agent creates an OAuth grant that is bound to you, to one organisation, and to the exact set of permissions you approved on the consent screen. Two things follow that you are responsible for:

• You are accountable for what a connected agent does under your grant. Actions taken through the connector are performed as you, are attributed to you in the audit log, and are subject to the same organisation policies — including deployment review — as anything you do yourself.
• Approve only the permissions the agent needs. Consent defaults to read-only; write and destructive permissions have to be approved deliberately, and destructive actions require a separate bound confirmation on top of the permission.

You can disconnect a connected agent at any time. What we hold, what an agent can reach, and how revocation works is described in the AI connectors section of our Privacy Policy.

6. Intellectual Property

The Service, including its software, design, documentation, and branding, is owned by Dibbla and protected by applicable intellectual property laws. These Terms do not grant you any rights to our trademarks, logos, or other brand features. You retain ownership of your Customer Data as described in Section 3.

7. Availability and Support

We aim to keep the Service available and reliable, but do not guarantee uninterrupted access. The Service may be temporarily unavailable for maintenance, updates, or reasons beyond our control. Support is provided on a reasonable-efforts basis via the channels published on our website. For questions about the Service, including AI connector access and abuse reports, write to [email protected].

8. Fees and Payment

Certain features of the Service may require a paid subscription. Pricing, billing terms, and payment methods will be presented to you before you commit to a paid plan. We will provide reasonable advance notice of any price changes. Unless otherwise stated, fees are non-refundable.

9. Limitation of Liability

To the maximum extent permitted by applicable law, Dibbla and its officers, employees, and agents shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or any loss of data, revenue, or profits, arising out of or related to your use of the Service.

Our total aggregate liability for any claims arising under these Terms shall not exceed the amount you paid us in the twelve (12) months preceding the claim, or one hundred euros (EUR 100), whichever is greater.

10. Disclaimer of Warranties

The Service is provided “as is” and “as available” without warranties of any kind, whether express or implied, including but not limited to implied warranties of merchantability, fitness for a particular purpose, or non-infringement. We do not warrant that the Service will be error-free, secure, or available at all times.

11. Indemnification

You agree to indemnify and hold Dibbla harmless from any claims, damages, or expenses (including reasonable legal fees) arising from your use of the Service, your violation of these Terms, or your infringement of any third-party rights.

12. Switching and termination

You may stop using the Service, move to another provider, or move to your own infrastructure at any time. Nothing in these Terms locks you in. This section sets out how it works and reflects Chapter VI of Regulation (EU) 2023/2854 (the Data Act), which applies to Dibbla as a data processing service.

Ending the agreement

You may terminate the agreement at any time by giving notice, either by deleting your organisation in the Service or by writing to [email protected]. The notice period is never longer than two months from the day we receive your notice, and you may choose any earlier date. Fees for a paid plan are charged for the period you actually use the Service and stop at the end of the notice period.

We may suspend or terminate your access if you breach these Terms, if required by law, or if we discontinue the Service. Where reasonably possible, we will provide advance notice, and the rights below to take your data with you apply in that case too.

Switching to another provider

If you tell us you are switching, we will assist you and complete the switch within thirty (30) days of the end of the notice period (the “transitional period”). During the transitional period the Service keeps running as normal, and we keep the same level of security and business continuity as before. If, in a specific case, completing the switch within thirty days is technically unfeasible, we will tell you within fourteen (14) working days of receiving your notice, explain why, and propose an alternative period of at most seven (7) months.

Taking your data with you

Everything you have put on Dibbla can be exported, at any time and without our involvement, in open and machine-readable formats that work without Dibbla:

• Application source code — as a git repository with its full deployment history. Your container images are rebuilt from the Dockerfile in that source by any container runtime; there is nothing Dibbla-specific in them.
• Databases — as PostgreSQL dump archives that restore into any PostgreSQL server.
• Storage buckets — as the files they contain, with their object keys as paths.
• Environment variables and configuration — as dotenv files and your dibbla.yaml service manifest, together with a compose file and a README that describe how the exported parts run together.
• Workflows — as YAML, from the Dibbla CLI.

The dibbla export command in the Dibbla CLI produces the export of an application in one step. Secret values are excluded from an export unless you explicitly request them. The export does not include Dibbla's own platform software, which you do not need to run your applications elsewhere. How to run an exported application on your own infrastructure or at another provider is described at Moving away from Dibbla.

After the agreement ends

Your Customer Data stays available for export for at least thirty (30) days after the transitional period ends (the “retrieval period”). The agreement terminates when the switch has been completed or, if you have not asked us to assist with a switch, when the retrieval period ends. After that we delete your Customer Data, except where we are required by law to retain it, and confirm the deletion to you on request.

No switching charges

We charge nothing for terminating the agreement, for switching, for exporting your data, or for the transfer of data out of the Service. Only the ordinary fees for your plan apply, and only for the period you use the Service.

Where your data is

Your Customer Data is stored and processed on infrastructure in the European Union, as described in our Privacy Policy. We will not move it outside the EU/EEA without the safeguards set out there.

13. Governing Law

These Terms are governed by the laws of Sweden. Any disputes arising under these Terms shall be resolved by the competent courts in Stockholm, Sweden, unless mandatory consumer protection law in your jurisdiction requires otherwise.

14. Changes to These Terms

We may update these Terms from time to time. For material changes, we will provide advance notice via email or through the Service. Continued use of the Service after changes take effect constitutes acceptance of the updated Terms.

15. Severability

If any provision of these Terms is found to be unlawful or unenforceable, it will be severed and the remaining provisions will remain in full force and effect.

16. Contact Us

Dibbla AB
Email: [email protected]
Website: dibbla.com