Terms of service

Cahaves Cloud is provided by PT Cahaves Technology International, a company in Bandung, Indonesia (“Cahaves”, “we”). These terms are between us and whoever holds the Cloud account (“you”). If you use Cloud for a company or another entity, through your account or one of its organizations, you accept these terms for it as well as for yourself, and you confirm you may do so.

You accept these terms when you sign in to Cloud for the first time, and each time you use it after that. You must be old enough to enter a binding contract where you live, and in any case at least 18.

The privacy policy and the refund policy are part of this agreement.

Cloud builds, deploys and runs your applications, databases and multi-container stacks on servers we operate, so you do not provision or maintain one yourself. Around that it provides persistent volumes, scheduled backups of databases and volumes, custom domains with their certificates, logs and resource figures for each service, and a shell into your services.

A service runs in one of two pools. In the shared pool it shares a server with other customers' services, each held to the CPU and memory of its size. In the dedicated pool the server runs only your services.

Cloud is young and under active development. We add, change and remove features as it grows. When a change removes something you rely on, we tell you by email before it happens.

You sign in to Cloud with GitHub or Google, through a Cahaves account that your first sign-in creates. An account is one person: keep the GitHub or Google account you sign in with secure, and tell us at support@cahaves.com, external link if you think someone else has used yours. You are responsible for what is done through your account.

Your account holds one or more organizations. Each organization has its own projects and services and its own bill: its way to pay, its monthly limit and its statements. Your sign-in, SSH keys, git connections, notification channels and backup storage belong to your account, and you use them in every organization. Whatever is done in any of your organizations is done through your account.

Keep your email address current. Cloud sends notices about a monthly limit, a payment that did not go through, a month waiting for a card and a suspension to that address, naming the organization a notice is about, and those notices cannot be turned off, because they are how we reach you about what you owe and about anything of yours that is about to stop.

One person, one account. Opening more accounts to use the free allowance more than once is a breach of these terms. Organizations do not add to it: the free allowance is your account's, counted once across all its organizations.

Cloud is paid for after you use it, once a month, in US dollars, and each organization is billed on its own. Once an hour Cloud counts what is running. An application or a stack is charged the hourly rate for its size and pool, for each container it runs, and a database is charged for the data it holds, at the rate per GB for its size and pool. A stopped service is not charged. The rates in force are on the pricing section of this site and in the console.

Your account's first nano application in the shared pool runs free, and its first nano database holds an amount of data free, which the console states. Each is counted once across all your organizations: the oldest nano application and the oldest nano database you run, in whichever organization each is, are the free ones. Running only those, within the free database's free data, needs no way to pay.

On the 1st of each month, Cloud adds up the month before for each organization, counted in UTC, and charges it, with tax added where it applies. Each organization's statement for each month is in the console under that organization's Billing, showing that month, its total and where it stands, and a way to pay it while a payment is due. Once the month is charged or invoiced, the statement has its document, which lists a line for each service and rate. We give the lines of any month on request.

Anything past the free allowance needs a card in the organization it runs in, unless we agreed to bill that organization by invoice. You add a card to an organization in the console, in a form Paddle provides, and Paddle keeps it. Cahaves never sees or stores your card number. Paddle holds each organization's card in a subscription of its own that costs $0 a month, and cancelling that subscription removes the card from that organization.

Each organization's total for a month is a separate charge to its card, which Paddle makes as merchant of record: Paddle is the seller of that charge, works out and collects any tax, and sends the receipt and its invoice.

If we agree to bill an organization by invoice instead, we send one for each of its months, made out with the billing details you give for that organization, in US dollars or in rupiah. The invoice says what it covers and when it is due. You pay it through the link it carries, which is Paddle for an invoice in US dollars and SingaPay for one in rupiah. An invoice in rupiah converts each line at the exchange rate we set and prints that rate and the date it was set.

A month whose total is too small to charge on its own is not charged that month. It is carried into that organization's next statement as a line of its own. So are hours Cloud records late, after their month's statement has closed.

We can change rates. A new rate applies only to hours after it takes effect; an hour already charged keeps the price it was charged at. Cloud keeps a record of every hour it charges, and cannot edit or delete one once it is written.

Refunds are covered by the refund policy.

Every organization has a monthly limit of its own, in US dollars. A new organization's limit is $20, and we can raise it when you ask at support@cahaves.com, external link.

Cloud works out what an organization's month will come to if everything running in it now keeps running to its end, and refuses new paid work in that organization that would take that past its limit: creating, deploying, starting, restoring or resizing a paid service, opening a paid database's public access, or choosing its settings before its first start. When what an organization has run in the month reaches its limit, Cloud stops that organization's paid services, and starts them again when we raise the limit or the next month begins. Your free application and free database are never stopped. Because Cloud counts once an hour, a month can end a little above the limit.

If a month's card charge does not go through, Cloud emails you, and the console lets you pay it again with the same card or another. An invoice not paid by its due date is overdue. If an organization's month closes while it has no card, the month waits and is charged once you add one to it.

While an organization's charge has failed, its invoice is overdue, its closed month waits for a card, or it runs paid services with no card and no invoice billing, Cloud refuses new paid work in that organization, as it does past its limit, and emails you the date its paid services will stop. If it has not paid, or added a card, by that date, Cloud stops that organization's paid services. Your free application and free database keep running, your other organizations are not affected, and you can still sign in, stop or delete services, and pay. Once it has paid, or has a card, Cloud starts again what it stopped, and paid work in that organization is accepted again.

If an organization's paid services stay stopped this way, Cloud archives them on a date it emails you when they stop, at least 7 days later, and emails you again 7 days and 1 day before. Archiving takes a final backup of each service's data that Cloud can back up, a database's dump or the volumes an application uses, into Cahaves' backup storage, and then deletes the service, its volumes and its domains. A Redis database, a compose stack, an application with no volume and a service that never ran are deleted with no final backup. You can download the final backups from the console until a date Cloud emails you when it archives, at least 7 days later, and then Cloud deletes them. Paying what is owed, or adding the missing card, before the archive date keeps everything as it was. A stop for the monthly limit is never archived, and neither are your free application and free database.

A payment that stays unpaid is a reason we may suspend the account, as the section “When we suspend or close an account” describes.

Your code, images, configuration, databases, files and the data your applications hold (“your content”) remain yours. You give us permission to store, copy, build, run, back up and transmit your content only as far as that is needed to provide Cloud to you, and for no other purpose.

We access your services and data only to run Cloud, to help you when you ask, to keep the platform and other customers safe, or when the law requires it. The privacy policy says what our staff can see, how a support session on your account is shown to you and recorded, and how we handle personal data inside your content.

You are responsible for your content and for having the right to run it, including the licences of the software you deploy and any personal data about others it processes.

You may not use Cloud to:

• host or send anything that is illegal where you or we are;

• distribute malware, run phishing, or host material that sexually exploits children;

• send unsolicited bulk email or messages;

• attack, scan or break into systems you are not authorised to test, including other customers' services;

• break out of your services' limits, reach another customer's services or data, or interfere with the servers Cloud runs on;

• avoid or tamper with Cloud's metering and billing;

• mine cryptocurrency;

• infringe someone else's copyright, trademark or other rights.

If you find a security weakness in Cloud, report it to support@cahaves.com, external link rather than testing it further.

We can suspend an account that breaks these terms, that leaves a payment unpaid after we have asked for it, or that we reasonably believe puts the platform, other customers or anyone else at risk. A suspension stops the services of every organization in the account and refuses new ones, deployments and backups. It deletes nothing. For serious or repeated breaches we can close the account, which also stops it signing in.

Every suspension and closure is recorded with its reason, and we tell you that reason, unless the law or an investigation stops us. Where the problem can be fixed, we give you the chance to fix it first, unless the harm is immediate.

What you owe, and what is refunded, when we suspend or close an account is in the refund policy.

You can stop or delete any service at any time, and a deleted or stopped service stops being charged from the next hourly count. The hours it ran before that are charged on the next statement. Apart from archiving, described under “When a payment does not arrive”, Cloud deletes nothing of yours as a side effect: a service's domains and volumes are removed first, by you, before the service can be deleted, and deleting a stack does not delete its volumes.

Cloud has no button that closes an account yet. To close yours, email support@cahaves.com, external link from the address you sign in with. We stop and remove your services, charge the hours they ran in that month on the 1st as usual, and delete your data as the privacy policy describes. Copy anything you want to keep before you ask.

We work to keep Cloud running and your data intact, but we do not promise any level of availability, and Cloud has no service level agreement. Servers fail, networks fail, and we sometimes take parts of Cloud down to maintain them.

Cloud's volume backups are a tool you use, not a guarantee we give. Keep your own copy of any data you cannot afford to lose, somewhere other than Cloud.

Cloud is provided as it is and as it is available. To the extent the law allows, we give no warranty that it will be uninterrupted, free of errors, or fit for a particular purpose.

To the extent the law allows, we are not liable for lost profits, lost revenue, lost data or any indirect or consequential loss, and our total liability to you for anything arising from Cloud is limited to what you paid us for Cloud in the 12 months before the event that caused the claim.

None of this limits a liability that the law does not allow to be limited, or a right you have as a consumer.

We may change these terms. The date at the top of this page says when they last changed. When a change affects your rights or what you pay, we email you at least 14 days before it takes effect. If you keep using Cloud after that, you accept the new terms; if you do not accept them, you can leave Cloud as described above.

These terms are governed by the laws of the Republic of Indonesia. If a dispute arises, write to us first and we will try to settle it together. A dispute we cannot settle within 30 days goes to the courts of Indonesia, without taking away a right you may have to bring a claim where you live as a consumer.

PT Cahaves Technology International, Bandung, Indonesia. Email support@cahaves.com, external link. A person reads every message.