Terms of Service
Last updated:
The terms governing a hosting subscription and project work: payment and renewal, grace period and suspension, data retention, availability and the limits of our liability.
These terms govern your use of Qasioun Cloud's services. By taking out a subscription, or by commissioning any project work from us, you have read and agreed to them.
Definitions
- The provider, or we: Qasioun Cloud, the operator of qasioun.cloud and of the services described on it.
- The subscriber, or you: the person or entity opening an account or commissioning work.
- The service: shared hosting and the domains, mailboxes and certificates attached to it.
- Project services: development, design, consulting, site migration and initial setup — any one-off work carried out for an agreed fee.
- The account: the cPanel account opened in your name, within the limits published for your plan.
- The term: the period paid for, monthly or yearly, from the activation date.
Scope of the service
We provide shared hosting on servers in Amsterdam. Every account has a share of CPU and memory of its own: a full CPU core and 1–2 GB of burstable memory on the Start and Business plans, and two cores and 3–4 GB on the Premium plan. The environment supports PHP, Node.js, Python and Git.
Disk, bandwidth, site count, databases and mailboxes are limited to what your plan publishes on the pricing page. Those limits are part of these terms, not an annex to them.
What the service does not include, and what we make no commitment about whatsoever: registration of domains under the Syrian national top-level domain, sub-reseller WHM accounts, or self-service restore of backups from the control panel.
We may change parts of the technical infrastructure — versions, servers, data centres — where operations or security require it. What we commit to is the service continuing at an equivalent level, not the permanence of every component in it.
Your account
- You will give accurate details when opening the account and keep them current. The email address on file is the official channel for notices, and renewal reminders are sent to it.
- You are responsible for keeping your password confidential and for all activity carried out through your account, whether you authorised it or simply did not notice it. Tell us immediately if you suspect a compromise.
- The content, applications and plugins on your account are yours and are your responsibility, including keeping them patched. A site compromised through an outdated plugin is not a fault in the service.
- Your use of the account is subject to the Acceptable Use Policy. Breaching it is sufficient grounds for suspension under the procedure set out there.
Payment and renewal
Prices are published in US dollars and paid in the Syrian pound equivalent, at a single reference rate we give you before you transfer — the rate on the day of payment. The rate you pay at is fixed at the moment of payment and holds for the whole term; it is revisited only at renewal.
An invoice is issued before the due date, and renewal happens when you settle it. We take no payment automatically and hold no payment instrument on file.
We may change plan prices, giving you 30 days' notice before the change takes effect. A new price never touches a term you have already paid for; it applies from your next renewal.
Fees or charges imposed by a third party on the payment method — a transfer commission, a wallet fee — are borne by the subscriber, and the amount due is what reaches us net.
Grace period and suspension
You have a grace period of 5 days after the due date, during which we send two reminders to your registered email. The service runs in full throughout.
At the end of the fifth day without payment, the account is suspended: the site and mail stop serving, while content and databases remain on the server untouched.
Reactivating a suspended account carries a fee of $5, added to the outstanding invoice. The fee covers manual work on the server, and is not charged where the suspension resulted from an error on our side.
We may suspend an account immediately and without a grace period where it poses a direct risk to the server or to other subscribers, or where it breaches the Acceptable Use Policy seriously. In that case we notify you of the reason as soon as the suspension is applied.
Data retention
After suspension, account data is kept for 21 days. During that window you can pay to restore the service in full, or ask us for a copy of your data.
At the end of the twenty-first day, the account, its content, its databases and its mail are permanently deleted, and we cannot guarantee that any of it can be recovered afterwards.
The backups we take are a recovery mechanism for faults affecting the server, not a personal archive for the subscriber. We commit to no particular retention period for them, and to no guarantee that the most recent copy is complete or current. Always keep your own copy of your data — this is a condition of the service, not passing advice.
Where you end the subscription yourself, the same 21-day window applies from the date it ends.
Availability and compensation
We commit to service availability of 99.9% per month, measured over the calendar month and against a complete outage of your account.
If availability falls below that in a given month, you are entitled to compensation in service days added to your term, not as a cash payment — one day for each full hour of downtime beyond the threshold. Compensation is requested through our published support channels within 30 days of the incident; it is not granted automatically.
The following do not count against availability:
- Scheduled maintenance announced at least 24 hours in advance.
- Faults on the infrastructure provider's network or in the data centre, which are outside our technical and contractual control.
- Loss of connectivity between a visitor and the server caused by their local network or their internet provider.
- Downtime caused by the subscriber: a configuration error, broken software, exceeding plan limits, or suspension for non-payment or a policy breach.
- Force majeure, including general power and telecommunications failure, war, sovereign decisions, and technical embargoes imposed by a third party.
Limitation of liability
Our total liability to you, for any claim or set of claims, is capped at the amount you actually paid for the service in the month preceding the incident. That cap covers damages of every kind.
We are not liable for indirect or consequential loss, and in particular not for lost profit, lost customers or reputation, business interruption, or the cost of rebuilding data you could have kept a copy of.
We are also not liable for:
- Faults at the infrastructure provider, the data centre, or on its network.
- Outages on the public internet or at a visitor's own provider.
- Errors by the subscriber or their staff: deleted files, misconfiguration, a leaked password, an installed plugin that was already compromised.
- The subscriber's content and the consequences of publishing it, including any third-party claim arising from it.
- Third-party services the subscriber uses through their account, even where we suggested them.
The service is provided as it stands, and we give no warranty — express or implied — of fitness for any particular purpose beyond what this document and the pricing page describe.
Nothing in this section excludes our liability for fraud or gross negligence on our part.
Development and consulting services
This section applies to development, design, consulting, site migration and initial setup. These are services separate from hosting, with their own terms below.
Ownership of the code. Ownership of code and design produced specifically for you passes to you on full payment of the agreed fee, and not before. Until then the work remains ours and is delivered under a temporary licence for the purpose of review. Excluded from that transfer are open-source components and our own reusable internal tooling; these are licensed to you perpetually and non-exclusively, to run and develop the delivered work.
Scope and revisions. Scope is agreed in writing before work starts, and the fee includes two rounds of revision within it. Any request that adds a page or a function, or changes the agreed direction, is out of scope: it is estimated and quoted separately before it is built. We will not begin out-of-scope work without your written agreement to it and to its fee.
Payment schedule. The default is 50% on scope sign-off and 50% on delivery, and it applies unless both parties agree otherwise in writing for a given project. The first instalment is non-refundable once work has started, because it covers time already committed. Files are handed over and ownership transfers once the final instalment has arrived.
Post-delivery support. For 30 days from delivery we fix, at no charge, any defect in the delivered work that does not match the agreed scope. That window does not cover new additions, changes you request after sign-off, or faults arising from someone else's edits to the code or from an update to a runtime we do not manage. After thirty days, support is by maintenance contract or hourly.
Your input is part of the schedule. Materials, access and reviews we ask for are a condition of work continuing, and a delay in providing them moves delivery back by an equivalent period without creating liability on our side.
Changes to these terms
We may amend these terms. The amended version is published on this page and the "last updated" date above it changes.
A material change — one touching price, liability, or the grounds for suspension — is notified 30 days before it takes effect, by email to the address on file. A non-material change applies from the date it is published.
Continuing to use the service after a change takes effect is acceptance of it. If you do not accept it, you may end the subscription and be refunded the unused portion of your term.
Governing law
These terms are governed by and construed under the laws of the Syrian Arab Republic, and any dispute arising from them falls to the competent courts in Damascus.
We would rather settle a disagreement amicably first. Write to us and we will answer — most of what looks like a dispute is a misunderstanding of a clause written in a way that carries two readings.
If a competent authority finds any clause of this document void or unenforceable, the remaining clauses stand, and the clause in question is read in the nearest valid sense to its intent.
Contact
For any question about these terms: info@qasioun.cloud