Third Party Index

Snapshot 23029

Document
Terms
URL
https://cleura.com/resources/legal/terms/
Fetched
HTTP status
200
Content type
text/html; charset=UTF-8
Fetch mode
static
Size
366609 bytes
SHA-256 (raw)
e61e50fc984449a9f11204141a42043ad55af9c042634326aa0bf55c4351cbe1
SHA-256 (normalized text)
c51ca2c8e0478bdd592294cac33f816624bb92693e14e12ab811ee11d7c9c90b

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Updated on May 19, 2026
Resources
Get started
Free trial
Regions & Services
Deployment models
Compliant Cloud
Public Cloud
Private Cloud
Tooling
Products◉
Virtual Machines
Server Profiles
Cloud storage
Cloud Networking◉
Virtual Private Cloud
Routers & Floating IP
Load balancer
Security Groups
Site-to-Site VPN
DNSaaSNew
Containers
Container Orchestration
Managed Kubernetes
Managed Services
Managed OpenShift
Managed Database
Professional Services
Cloud Compliance Assessment
Cloud Training
Support
Customer ServiceIncluded
DocumentationIncluded
TutorialsIncluded
Support plans
Service status
Trust Center
How we do it
Our security culture
Technical aspects
Certifications
Company
Brand story
Careers
Sustainability
Quality policy
Environmental policy
Partner Program
Legal
Privacy notice
Website visits, events & marketing
When delivering services
In service cases
Terms
Terms
This page explains the terms that apply to use of Cleura’s cloud services. Customers are typically businesses, public authorities or other organisations.
Online registration and use
A customer can register online to use Cleura Public Cloud, without signing a contract with Cleura drafted specifically for that customer.
In this case, the customer agrees to the following standard terms for the customer’s use of Cleura Public Cloud, together forming the “Agreement” between the customer and Cleura for that use:
Terms of Service for Public Cloud
Data Processing Agreement for Public Cloud
Annex A applies to the processing of cloud workloads
Annex B applies to the processing of Cleura Cloud Management Portal user accounts and API user accounts
Cleura’s sub-processors are listed on the cloud regions and sub-processors page. Cleura’s processing of personal data as a controller is described in Cleura’s privacy notice.
Use covered by a Cleura Master Service Agreement
A customer can enter into a signed contract with Cleura, drafted for that customer, for use of Cleura Compliant Cloud, Public Cloud and/or Private Cloud.
A Master Service Agreement (MSA) is the overarching document of such a signed contract. The MSA explains which services are covered by the contract, and which terms apply to the customer’s use of those services. Such terms may be included as appendices to the MSA, together forming the “Agreement” between the customer and Cleura.
A customer with an MSA for use of Compliant Cloud and/or Private Cloud can still use Cleura Public Cloud. The customer can either register online and accept the standard terms for Public Cloud, or contact Cleura to discuss adding Public Cloud to the scope of the MSA.
Cleura’s sub-processors are listed on the cloud regions and sub-processors page. Cleura’s processing of personal data as a controller is described in Cleura’s privacy notice.
Partner customers
An organisation can get access to Cleura’s services, or purchase application hosting relying on Cleura’s services, from a partner of Cleura. In such a case, the organisation will have an agreement directly with the partner. The organisation will typically not have an agreement directly with Cleura.
The partner will be responsible for delivering services to the customer, while the partner relies on Cleura as a subcontractor.
The agreement between the partner and the customer will explain which terms apply.
Cleura’s sub-processors are listed on the cloud regions and sub-processors page. Cleura’s processing of personal data as a controller is described in Cleura’s privacy notice.
Terms - PreviousIn service casesNext - TermsInsights
CONTENTS
We only use strictly necessary and functional cookies, and cookieless analytics.
1. One necessary cookie, spu_closing_9226, to know if you have recently closed a popup like this one. That’s so we don’t show it to you again during your current visit.
2. Matomo and Plausible to measure website visits and the effectiveness of our website, without using cookies.
×
Subscribe
×