Terms of Service

The plain-English contract for using Decolla during early access. The TL;DR below is the honest summary; the numbered sections are the detail.

TL;DR — the short version

What you're agreeing to. Decolla plans and — only on your explicit instruction — deploys Microsoft Intune and Entra configuration into a Microsoft 365 tenant that you control and are authorised to administer. Connecting a tenant deploys nothing. Every write requires you to confirm the specific batch, and policies are created unassigned — nothing reaches a user or device until an assignment is made, and if you use Decolla's own assignment step, that too runs only after its own separate, explicit confirmation. In return, you agree to a short set of professional obligations: connect only tenants you are authorised to administer, review every plan before you confirm it, validate in a pilot group before broad assignment, and don't use the service to attack anything.

What you should know. Decolla is in early access: it is provided as-is, features will change, and our liability is capped at the fees you paid us in the 12 months before a claim — which during unpriced early access may be nothing, so your own review of each plan matters. You can disconnect a tenant at any time from inside the product, which invalidates the stored credentials immediately. The company behind Decolla is The Cloud Platform Limited, registered in England and Wales, and these terms are governed by the law of England and Wales. If anything here doesn't make sense, ask us via the contact page and we will explain it in plain English.

1. Acceptance of these terms

1.1 Agreeing by use. By accessing or using the Decolla service — including the website at decolla.app, the portal at cockpit.decolla.app, and the API at api.decolla.app (together, the "Service") — you agree to be bound by these Terms of Service (the "Terms"). If you do not agree, do not connect a tenant and stop using the Service.

1.2 Business use and authority. Decolla is a business tool for IT administrators and managed service providers. By accepting these Terms you confirm that you are acting in the course of business, and — if you accept on behalf of an organisation — that you have authority to bind that organisation. These Terms are a business-to-business contract; they are not aimed at consumers.

1.3 Companion document. Our Privacy Statement explains what personal data we hold and why. It is incorporated into these Terms by reference. If these Terms and the Privacy Statement conflict on a data-handling point, the Privacy Statement wins for that point.

2. Who we are

Decolla is a product of The Cloud Platform Limited, a company registered in England and Wales. The Cloud Platform Limited owns and operates the Service and is the party you contract with under these Terms. Everywhere else you see the product, it is branded Decolla — the company name appears in legal documents like this one.

For any question about these Terms, contact us via the contact page. We do not publish direct email addresses; the contact page is the canonical route and it reaches us.

3. Definitions

In these Terms, the following capitalised words have the meanings given below.

• "We", "us", "our" — The Cloud Platform Limited, trading the product as Decolla.
• "You", "your" — the person or organisation using the Service, including any administrator acting on that organisation's behalf.
• "Tenant" — a Microsoft 365 tenant that you control and are authorised to administer.
• "Connection" — the delegated Microsoft consent an authorised administrator grants so Decolla can act in a Tenant. Decolla acts only as the signed-in administrator, only under the Microsoft Graph permissions consented to, and a Connection is revocable at any time by disconnecting.
• "Plan" — a build plan Decolla prepares for your review: the set of Intune and Entra configuration objects it proposes to create in a Tenant, before anything is written.
• "Deploy" — the act of executing a Plan (or part of one) against a Tenant, which happens only after your explicit per-batch confirmation (§5).
• "Assignment" — the act of attaching deployed configuration to users or devices in a Tenant so it takes effect, whether performed in your Microsoft admin tools or through Decolla's own gated assignment step (§5.3).
• "Early Access" — the current pre-general-availability period, during which the Service is unpriced and provided as-is (§4.3).
• "Waitlist" — the signup list at decolla.app for access to the Service during Early Access.

4. The Service

4.1 What Decolla does. Decolla plans and — on your explicit instruction — deploys Microsoft Intune and Entra configuration into a Tenant. The workflow is deliberately two-stage: first Decolla builds a Plan you can read; then, and only if you confirm, it Deploys that Plan step by step via the Microsoft Graph API under the permissions you consented to. Each Deploy produces a job history record, including per-step results, so you have an audit trail of what was created.

4.2 What Decolla does not do. Decolla creates configuration objects in your Tenant. It does not read your end users' device content, files, or messages, and it takes no action in a Tenant except in execution of a Plan you have confirmed.

4.3 Early Access. The Service is in Early Access. That means, honestly: features may change or be withdrawn, rough edges exist, no payment is currently taken, and the Service is provided "as is" and "as available", without warranty of any kind to the fullest extent the law allows. The review-then-confirm workflow in §5 exists precisely because the Service is young — use it.

5. The consent model — nothing deploys without you

This section is the heart of these Terms, and we hold ourselves to it.

5.1 Connecting deploys nothing. Creating a Connection gives Decolla the ability to act in your Tenant; it does not cause any action. No configuration is created, changed, or deleted as a consequence of connecting alone.

5.2 Every write needs your explicit confirmation. Each Deploy requires a fresh, explicit, per-batch confirmation from you inside the product. Reviewing a Plan is not confirmation; only the confirmation step itself authorises the write. There is no bulk or standing authorisation.

5.3 Policies are created unassigned — and assignment is its own gated act. Configuration objects Decolla creates are created unassigned: nothing Decolla deploys reaches a user or device until an Assignment is made. You can make that Assignment yourself in your Microsoft admin tools — or, where the product offers it, through Decolla's own assignment step, which runs only after a further, separate, explicit confirmation dedicated to assignment (distinct from the Deploy confirmation in §5.2; there is no bulk or standing authorisation for Assignment either, and Decolla never assigns as a side-effect of deploying). Either way, Assignment is your decision, made in your Tenant, under your control.

5.4 Decolla acts as you. Decolla operates under delegated Microsoft consent, acting only as the signed-in administrator and only within the Graph permissions that administrator consented to. Disconnecting the Tenant invalidates the stored credentials and ends Decolla's ability to act (§11.1).

6. Your obligations

You agree that you will:

• Connect only Tenants you are authorised to administer. You must hold, and keep holding, genuine authority over every Tenant you connect. Using the Service to access or configure a tenant without authorisation is a serious breach of these Terms — and likely of the law.
• Review every Plan before confirming it. You are responsible for reading each Plan and for the effect of the configuration you choose to Deploy and assign in your Tenant.
• Pilot before broad assignment. Validate deployed configuration in a pilot group before assigning it broadly. The product is designed around exactly that workflow.
• Stay within Microsoft's terms. Your use of the Service in a Tenant must comply with the Microsoft agreements that govern that Tenant.
• Provide accurate information in any form you submit (waitlist, contact, in-product feedback).
• Not attack the Service — no attempts to gain unauthorised access to the Service or its infrastructure, no probing or vulnerability-testing without our written invitation, no scraping, and no automated abusive traffic.

If you breach this §6 we may suspend or terminate your access under §11.2. For serious breach — above all, connecting a tenant you are not authorised to administer — we may do so immediately and without prior notice.

7. Waitlist

7.1 What joining means. Joining the Waitlist is free, asks only for your email address, and creates no purchase contract and no obligation on either side. It records your interest and lets us tell you about the Service and offer you access.

7.2 No promises on timing. Being on the Waitlist does not guarantee access by any date, or at all — we admit users as Early Access capacity and stability allow. We will not pretend otherwise.

7.3 Leaving. You can ask to be removed from the Waitlist at any time via the contact page, and we will remove you. How waitlist data is stored and deleted is covered in the Privacy Statement.

8. Availability and changes to the Service

8.1 No availability commitment during Early Access. We work to keep the Service available and reliable, but during Early Access we offer no service-level commitment. The Service may be interrupted, degraded, or suspended for maintenance, safety, or matters outside our reasonable control — including outages at Cloudflare (which hosts the Service) or Microsoft (whose Graph API the Service depends on).

8.2 We may change the Service. We may add, change, or remove features at any time during Early Access. Where a change materially affects how the Service behaves against connected Tenants — in particular anything touching the consent model in §5 — we will tell connected users before the change takes effect. We will never weaken the §5 consent model silently.

8.3 Your fallback is always yours. Everything Decolla creates lives in your Tenant, under your control. If the Service is unavailable, your deployed configuration continues to exist and operate in your Tenant regardless — Decolla is not in the path between your devices and Microsoft.

9. Intellectual property

9.1 What we own. The Service — including the Decolla name and brand, the software, the configuration catalogue and templates, the website content and guides, and the design of it all — is owned by The Cloud Platform Limited or licensed to us. We grant you a non-exclusive, non-transferable, revocable licence to use the Service for administering your Tenants during your access. You may not copy, resell, reverse-engineer, or systematically extract the Service or its content.

9.2 What is yours. The configuration objects deployed into your Tenant are in your Tenant, under Microsoft's terms and your control — we claim no ownership over your Tenant or its configuration. Your naming values, selections, and other inputs remain yours; we use them only to build and record your Plans and Deploys.

9.3 Feedback. If you send us feedback (including through the in-product widget), you grant us a perpetual, royalty-free, non-exclusive licence to use it to run and improve the Service. Your idea stays yours; we will not sell your feedback to anyone.

10. Liability

10.1 What we never limit. Nothing in these Terms excludes or limits liability for death or personal injury caused by our negligence, for fraud or fraudulent misrepresentation, or for any other liability that cannot lawfully be limited or excluded under the law of England and Wales.

10.2 What we do limit. Subject to §10.1 and to the maximum extent permitted by law: we are not liable for indirect, special, or consequential loss — including loss of profit, revenue, data, or goodwill; and our total cumulative liability arising out of or in connection with the Service is capped at the amount you paid us for the Service in the 12 months before the claim arose.

10.3 The honest consequence during Early Access. No payment is currently taken for the Service, so during unpriced Early Access that cap may be zero. We say this plainly because it is the truth of the bargain: you get a free early-access tool with a deliberately gated deploy model; we get your feedback; and your protection is the review-and-confirm workflow in §5 and §6, which puts every write under your eyes before it happens.

10.4 Your configuration decisions. You — not we — are responsible for the suitability of the configuration you choose to Deploy and assign, and for its effect on your Tenant, your users, and your devices. Decolla proposes; you dispose.

11. Termination and disconnect

11.1 You can disconnect at any time. You may disconnect a Tenant at any time from inside the product. Disconnecting invalidates the stored credentials, and Decolla loses the ability to act in that Tenant. Configuration already deployed stays in your Tenant, under your control — disconnecting does not undo past Deploys.

11.2 We can suspend or terminate for cause. We may suspend or terminate your access to the Service if you breach these Terms (especially §6), or where suspension is reasonably necessary to protect other customers, a Tenant, or the platform. Where reasonable we will tell you why and give you a chance to put it right; for serious or repeated breach we may act without prior notice.

11.3 We can end Early Access. Because the Service is in Early Access, we may withdraw it, in whole or in part, on reasonable notice to connected users. If we do, §11.1 applies: your deployed configuration remains in your Tenant.

11.4 What happens to data. On disconnect, credentials are invalidated. Plans and job history are retained for the life of your account so your audit trail stays intact; deletion of personal data is handled as described in the Privacy Statement.

11.5 Survival. Sections 9 (Intellectual property), 10 (Liability), 13 (Governing law), and any provision that by its nature should survive, survive termination.

12. Changes to these Terms

These Terms are versioned; the version and date appear at the foot of this page. If we make a material change, we will publish the new version here and notify connected users and Waitlist members before it takes effect. Continued use of the Service after the effective date constitutes acceptance. If you do not accept a change, disconnect your Tenants (§11.1) and stop using the Service before the change takes effect. Previous versions are archived internally so we can show you what changed and when.

13. Governing law and general terms

13.1 Law and jurisdiction. These Terms, and any non-contractual obligations connected with them, are governed by the law of England and Wales. The courts of England and Wales have exclusive jurisdiction over any dispute arising out of or in connection with these Terms.

13.2 Entire agreement. These Terms, together with the Privacy Statement, form the entire agreement between you and The Cloud Platform Limited for the Service.

13.3 Severability and waiver. If any clause is found unenforceable, the rest continue in force. If we do not enforce a right straight away, that is not a waiver of it.

13.4 Assignment of these Terms. You may not assign these Terms without our written consent. We may assign them on reasonable notice — for example on a corporate restructure or transfer to a successor entity.

13.5 No partnership. These Terms create no partnership, joint venture, or agency between you and The Cloud Platform Limited.

13.6 Talk to us first. If you have a complaint or a question about these Terms, raise it via the contact page — we would rather explain and fix than litigate.

Version 1.2 · 19 July 2026 · supersedes v1.1 (10 July 2026)