Ordnary Web Services

Ordnary Web Services is our cloud infrastructure: compute, storage, networking, and managed databases you can run your own applications and workloads on. This page explains what Ordnary Web Services is, how we process your data when you use it, and the terms that apply. It supplements the Terms of Service, the Acceptable Use Policy, and the Billing & Refund Policy; for business customers, the Data Processing Addendum also applies.

What Ordnary Web Services is

Ordnary Web Services includes compute (virtual machines and bare-metal servers), load balancers, object storage, storage volumes, managed databases and caching, an edge network for content and edge functions, certificate management, and identity and access management. You choose which components you use and how you configure them.

What data we process

In delivering Ordnary Web Services, we process two kinds of data.

Account data: who has access to your workspace, what roles they have, and what API keys and access tokens have been issued.

Customer data: the content, code, and data you place on your resources or have processed, such as files in object storage or rows in a managed database. This data remains yours; we only process it to deliver the service and as you instruct under the Data Processing Addendum.

We use account data to determine who has access to which resources, and to run your workloads as you've configured them. We don't read or use the contents of your customer data except as necessary to deliver or support the service, for example to detect abuse or to bill you.

Regions and data residency

You choose which region your compute, storage, and networking run in. That choice is an explicit setting you control, not a location we infer about you; see our Location Data page for more on that distinction. We host Ordnary Web Services primarily in the European Union.

Your workloads and responsibility

You're responsible for the resources you provision, the software and content you run, your configurations, and your end users. You must:

• secure your instances, keys, secrets, and storage;
• keep your software patched and configured safely;
• comply with the Acceptable Use Policy and the acceptable-use requirements of our underlying infrastructure providers; and
• not use Ordnary Web Services to harm or attack others, host malware, run abusive proxies, send unlawful bulk communications, or conduct prohibited cryptomining.

Workspaces, isolation, and access

Ordnary Web Services uses multi-tenant workspaces with role-based access and member management. You're responsible for managing your members, roles, API keys, and access tokens, and for promptly revoking access when it's no longer needed.

Backups and deletion

Backups are your own responsibility, unless a managed product explicitly includes them. Where automated backups are offered, you remain responsible for verifying and exporting critical data.

On termination or deletion of resources, data may be irreversibly destroyed. Export anything you need before deleting resources or closing your account. We may retain limited records as required by law.

Availability, maintenance, and SLAs

We aim for high availability, but unless a separate written SLA applies, Cloud Services are provided without an uptime commitment. We may perform planned and emergency maintenance and will give reasonable advance notice for planned maintenance where practicable. Any service credits are governed solely by a separate SLA, if you have one.

Capacity, limits, and fair use

We may set quotas, resource limits, and fair-use thresholds to protect the platform. We may decline, throttle, or suspend resource-intensive or abusive workloads. Some capacity depends on third-party provider availability and is not guaranteed.

Security

We secure the underlying platform with encryption, access controls, network security, logging, and monitoring. Security of Ordnary Web Services is a shared responsibility: we secure the platform, you secure your workloads, data, configurations, and access. See our Security Policy for the full overview.

Subprocessors

Parts of Ordnary Web Services run on third-party infrastructure, such as hosting providers. These parties are bound by obligations no less protective than our own. See our Subprocessors page for the full list.

Billing

Ordnary Web Services is billed based on the resources you provision and consume, as described in your plan and the Billing & Refund Policy. Running resources accrue charges until you delete them, even if unused. You're responsible for monitoring and controlling your own spend.

Suspension and termination

We may suspend or terminate Ordnary Web Services for non-payment, abuse, security risk, legal requirement, or breach of these terms. We may suspend specific resources to protect the platform. Where practicable, we'll notify you. On suspension for non-payment, running resources may be stopped and, after a grace period, deleted.

Third-party infrastructure

Parts of Ordnary Web Services rely on third-party infrastructure. Their outages, policy changes, or restrictions may affect Ordnary Web Services, and their terms may apply to the relevant components. We're not liable for losses outside our reasonable control.

Changes

We may update this page and the terms described here as Ordnary Web Services evolves. We'll communicate material changes as described in the Terms of Service.

Contact

Ordnary Web Services questions: support@ordnary.com. Security: security@ordnary.com.

For urgent requests, call +31 85 401 3197.