Terms of service

Version 2026-11-10.a7056505

Last updated: 10 November 2026

1. About these terms

1.1 Clusterz is run by Zer0Paper OÜ, registry code 16797271 in the Estonian commercial register, Ahtri tn 12, 15551 Tallinn, Estonia. Our email address is contact@clusterz.eu. In these terms, "we" and "us" mean Zer0Paper OÜ, and "you" means the business or organisation that uses Clusterz.

1.2 These terms are our contract with you. Three more documents form part of it:

• the acceptable use policy, which sets out what you must not do with Clusterz and how anyone can report illegal content to us;
• the data processing agreement, which covers the personal data in your apps that we process for you;
• the subprocessors page, which lists the companies that help us process that data.

1.3 If the data processing agreement and these terms differ about personal data, the data processing agreement applies.

1.4 Our privacy policy explains how we use personal data about you and the members of your team.

1.5 Clusterz is for businesses and organisations only. When you sign up, you confirm that you act for a business or organisation and may accept these terms for it.

1.6 Every page where you sign up links these terms, and section 1.2 links the documents that form part of them, so that you can read and save them before you first sign in. You accept them when you tick the box on that page and continue, or when you tick it and press Accept in the dashboard. We record which version you accepted, when, and which of the two you used.

2. The service

2.1 Clusterz runs software for you on our servers. With it you can:

• install a bundle, which is a set of apps chosen for one kind of organisation;
• install a single app;
• build and run apps from your own code, kept in a repository at GitHub, GitLab or Bitbucket.

2.2 The apps we offer, alone or in bundles, are open-source software made by others. Each has its own licence, such as the GNU General Public License, the GNU Affero General Public License, the Apache License or the MIT License. Their licences apply to your use of them. Each app works as its maker designed it, as section 5 of the subprocessors page explains.

2.3 Clusterz gives you working systems. It does not give you advice or approvals. We do not:

• obtain a licence or approval your organisation needs, such as a banking licence;
• check that reports from the apps meet the format a regulator requires;
• move records in from your old systems;
• train your staff;
• give medical, legal, financial or regulatory advice.

2.4 Your apps run on our servers, so the people who use them need an internet connection.

2.5 status.clusterz.eu shows whether Clusterz is working, and the dashboard shows the uptime we measured for the apps you installed from us. These figures report past performance. They are not a service level commitment.

2.6 Support is by email to contact@clusterz.eu, through our help form, and through the Clusterz assistant, an AI system in the dashboard and on our website that can send your request on to us. A person answers what reaches us. If your team has a bundle, we reply within one working day, Central European time. A reply is not a fix. Please keep data from your apps out of all three. The assistant gives general help with Clusterz and no advice of the kinds in section 2.3. If it differs from these terms, these terms apply. We set how much it can be used, and we may change that or turn it off.

2.7 If we stop offering a bundle, a team that already has it keeps it, and keeps paying for it, until the team deletes the bundle's apps.

3. Your account and your team

3.1 You sign in with an account you hold at Google, Apple, GitHub, GitLab or Bitbucket, as our sign-in page offers. Clusterz keeps no password for you, so keep that account safe.

3.2 The first time you sign in, we create your account and a team, and make you the team's owner.

3.3 Each member of a team has one role:

• A viewer can read the team's logs, metrics, billing and list of members.
• A developer can also create, build, deploy and roll back apps, and change their settings.
• An admin can also add credit, choose the plan, install bundles, delete apps, restore backups, manage domains, invite and remove members, change their roles, and read the team's audit log.
• The owner can also reveal or reset the admin password of an app we set up. We record each reveal and reset.

3.4 A team has one owner: the person who created it. To change the owner, the owner writes to contact@clusterz.eu. If the owner has left or cannot act, your organisation can write to us with proof that it speaks for the team, such as a registry extract or a signed letter. We then change the owner or delete the team, as it asks.

3.5 Owners and admins invite people by giving them a link. A link works for 7 days, and only for the verified email address it was made for. If that person already has an account, we add them to the team as pending, with the role you chose.

3.6 You are responsible for what the members of your team do in Clusterz, and for choosing who joins it.

4. The free trial

4.1 The first bundle your team installs comes with a free trial of 14 days, counted from the install. You need no card and no credit to start it.

4.2 Each verified email address, each account and each team can have one free trial. An account needs a verified email address to start one. Plans have no free trial. A trial whose bundle never ran, and which you deleted, does not count.

4.3 Before you install a bundle, the dashboard shows its price and the date the trial ends. We install only on the terms it showed you. If they changed in the meantime, the install stops and the dashboard shows you the new terms.

4.4 When the trial ends, what happens depends on whether your team has paid us by then, by adding credit or by bank transfer. Credit we give you is not a payment.

• If it has never paid, we charge nothing and you owe nothing. Every app of your team stops 72 hours after the trial ends, and section 7.4 applies. The bundle's first month starts on the day your team first pays. We charge that month in full that day, and your apps start again by themselves, except any you stopped yourself. If you had stopped every app yourself, section 5.6 applies instead, and we charge the month when an app starts again. If your payment does not cover that month, section 7 applies from then.
• If it has paid, we charge the bundle's first month to your team's credit when the trial ends, even if the credit does not cover it. Section 7 says what happens then. We charge it only once every app of the bundle is running. To avoid that charge, delete the bundle's apps before the trial ends.

5. Credit, prices and payment

5.1 Your team pays in advance with credit. Prices and credit are in euros. Where we charge a card in another currency, we show that amount before you pay. Bundle prices are in the pricing section of our website. Plan fees and usage rates are in the dashboard, which shows the price before you buy.

5.2 Owners and admins add credit in the dashboard through Revolut, within the limits shown when they pay. Your card details go to Revolut, not to us. The credit reaches your team once Revolut confirms the payment.

5.3 Credit belongs to the team, not to the person who added it. It cannot be moved to another team or paid out. If you choose to leave, unused credit is not refunded, including when a team is deleted at your request. We refund it in these cases:

• we end the contract for a reason other than your breach, or stop a service you were paying for;
• you leave before a change to a price, these terms, the data processing agreement or our subprocessors applies, because you do not accept the change;
• you leave because we broke these terms;
• the law requires a refund in any other case.

5.4 Bundles. A bundle has one monthly price, which covers your team and all the bundle's apps. Each month starts when the trial ends, or at the install if there was no trial. If your team had never paid when the trial ended, its months start instead on the day it first pays, as section 4.4 says. We charge each month once, at its start, at the price that applies then. Without a trial, we set the first month's price aside from your credit at the install, and the install is refused if your credit does not cover it. It pays the first month once every app of the bundle is running. If the bundle does not install, we put it back in your credit and tell you by email. If the bundle starts working later, we charge its first month that day, and its months start then. Apps of a bundle that did not finish installing stop after 72 hours, and their data stays. A bundle with no apps left is not charged. When you delete a bundle's last app, the whole days left of the month you paid for go back to your credit.

5.5 Plans. A plan gives your team an allowance of memory, processing power and apps for a monthly fee. Apps that came with a bundle do not count against it.

• When you choose a plan, or move to a bigger one, we charge the full monthly fee at once and a new month starts. We do not credit the unused part of the old plan. The change is refused if your credit does not cover the fee.
• A move to a smaller plan takes effect at the end of the current month.
• Each month renews by itself and is charged even if your credit does not cover it.
• Use above the allowance is charged for each hour of memory and processing power used, at the rates the dashboard shows, and taken from your credit each day.

5.6 Billing is held while every app of your team is stopped, by you or under section 4.4 or 7.3. No plan fee, no bundle month and no add-on is charged while it is held. A bundle or add-on month that falls due in that time is charged when an app starts again, and a month that is held from start to end is not charged. Use on the day the apps stop may still be charged. Charges already made are not refunded, except as section 5.4 says. A team that has never paid is charged nothing after its trial ends until it first pays, as section 4.4 says.

5.7 We do not charge VAT, because Zer0Paper OÜ is not registered for it. A business customer in another EU country may have to account for VAT on these services itself. The dashboard's billing page shows your team's credit and its history. We issue an invoice for each payment of credit, and for any balance below zero under section 7.6. When a payment pays off an invoice, that invoice covers that part of the payment, and we confirm it by email. An invoice shows a number, the date, our name, registry code and address, your legal name and address, any VAT number you give us, what you bought and the amount in euros. An Estonian company registered as an e-invoice recipient can ask us for an e-invoice. We keep our record of each payment for at least 7 years after the end of the financial year, as the Estonian Accounting Act requires.

5.8 Add-ons. An add-on has a monthly price, shown before you buy. We charge it when you buy it and each month on that day, to your team's credit. You can remove it at any time. It stays on until the end of the month you paid for, and we do not refund the rest of that month. Stopping an app does not stop its add-ons.

6. Price changes

6.1 We email the owners and admins of your team at least 30 days before a new price applies to it. The new price applies from your team's first charge after those 30 days.

6.2 If you do not accept a new price, you can leave before it applies, as section 14 describes, and we refund your unused credit as section 5.3 says.

6.3 An install always happens at the price the dashboard showed you when you confirmed it.

7. When your credit runs out

7.1 We charge fees when they fall due, even if your credit does not cover them, so your credit can fall below zero. A team that has never paid is charged nothing after its trial ends until it first pays, as section 4.4 says. The dashboard warns your team when credit runs low and when it runs out.

7.2 While your credit is below zero, or at zero outside a bundle's free trial, your team cannot start new deploys.

7.3 If your credit stays below zero, every app of your team stops 72 hours after we first find it below zero. The dashboard shows the date.

7.4 Your apps and their data stay until your team is deleted. We do not delete them because your credit ran out or your trial ended. The team's owner, or your organisation under section 3.4, can ask us to delete the team, as section 14.4 describes.

7.5 When your balance is no longer below zero, whether you added credit or paid by bank transfer, your apps start again by themselves. Apps you stopped yourself stay stopped. Apps stopped under section 4.4 start again when your team first pays, as that section says. Credit we give you does not start them.

7.6 A balance below zero is money your team owes us. We send an invoice for it, payable within 14 days. You can pay it by adding credit, which pays it off first, or by bank transfer. If your team is deleted, that amount stays due.

8. Where your systems run and your data is kept

8.1 Your apps, their data and our own account database run on servers of Hetzner Online GmbH, in its data centres in Germany.

8.2 Backups of your apps' databases, the images of your apps and our logs are kept in Hetzner's object storage in Falkenstein, Germany. So are the files of an app we offer that keeps them there, which today is Nextcloud, and each night we copy those files to Hetzner's object storage in Nuremberg, Germany. The keys that encrypt your apps' backups are protected by Google Cloud's key service in Frankfurt, Germany. Google handles those keys when it wraps and unwraps them. It never receives the backups.

8.3 Some data goes to other companies, some of them outside the European Union. For example, the web addresses of your apps go to Let's Encrypt in the United States, which issues their security certificates. The subprocessors page lists the companies we use, what each receives and where. Section 5 of that page covers the apps we offer.

8.4 Your apps, their data, their backups and our account database are in Germany, and subject to German and European Union law. We are subject to Estonian and European Union law. The key service that protects your apps' backup keys runs in Germany and is provided by Google Cloud EMEA Limited, an Irish company.

8.5 We give your data to a public authority only when European Union law, or the law of an EU member state, requires it. An order from an authority outside the EU counts only where Article 48 of the GDPR allows for personal data, and Article 32 of the EU Data Act allows for other data. We tell you before we answer, unless the law forbids it. If we report a suspected threat to life or safety, as section 10 of the acceptable use policy describes, the report may include data from your app, and we tell you afterwards unless the law forbids it.

9. Backups

9.1 For each running app you installed from us that has a database, we back up that database. Each app's backups are encrypted with a key of its own before they leave our servers.

9.2 A PostgreSQL database sends its latest changes to its backup at least every 60 seconds, and we take a full copy of it each night. The dashboard lets you restore it to any minute from 2 minutes ago back to the start of its backup period, or back to its last restore if that is later.

9.3 A MariaDB database is copied in full each night. The dashboard lets you restore it to one of those nightly copies.

9.4 While an app runs, we keep every copy for 7 days, then one copy a week until the end of the backup period. We also keep the newest copy, and the copy that a restore to the start of the period needs.

9.5 Every app includes the backup period shown on its page. You can buy a longer one there. When a longer period ends, copies older than the included period go on that night's run.

9.6 Owners and admins can ask for a restore in the dashboard. The app is stopped while it is restored, and each restore ends by taking a fresh full copy.

9.7 Backups reduce the risk of losing data, and they do not remove it. You remain responsible for keeping your own copies of anything you cannot afford to lose, including your code, your files and any data our backups do not cover.

10. When our staff may access your systems and data

10.1 Our staff open your apps or read the data in them only:

• when you ask us to, for example in a support request;
• when we need to, to keep Clusterz running and secure, or to deal with a report of illegal content or a breach of the acceptable use policy;
• when European Union law, or the law of an EU member state, requires it.

10.2 Our staff tools show which teams, members and apps exist, and record the changes staff make with them. They do not show the data inside your apps.

10.3 Everyone we allow to process your data is bound to keep it confidential.

11. Your content and personal data

11.1 What you put on Clusterz stays yours: your code, your apps' data and your settings. You allow us to store, copy, run and back it up only as far as we need to provide Clusterz to you.

11.2 When your apps hold personal data, you decide how it is used, and we process it for you under the data processing agreement. You are responsible for having a lawful basis for that data, including any health data.

11.3 The web address of each app contains its slug and your team's slug. A new team takes its name from the person who signs up, and its slug is random until you change it. Owners and admins can change both in the team's settings, and an old address keeps working for 30 days.

11.4 These addresses, and any domain of your own that you connect, go to Let's Encrypt and appear in public logs of security certificates, as every public certificate does. Choose slugs that hold no personal or secret information before you install an app.

12. Acceptable use and reports

12.1 You must follow our acceptable use policy. It sets out what you must not host or do, how anyone can report illegal content, what we do about a report, and how you can ask us to review a decision.

12.2 No automated tool judges the content of your apps. Our security tools detect attacks and unusual activity automatically, and a person decides what to do with what they find. A person reads every report.

13. Suspension

13.1 We may remove or block access to content, stop an app, or suspend your team if:

• you or your apps break these terms, the acceptable use policy or the law;
• an app puts Clusterz, other customers or other people at risk;
• the law or a public authority requires it.

13.2 We act in a careful, objective and proportionate way, and choose the step that fits the problem. We delete an app only as section 14.6 allows.

13.3 When we take one of these steps, we email the owners and admins of your team to say what we did and why, as section 9 of the acceptable use policy describes.

13.4 While your team is suspended, its members cannot use the dashboard, the command-line tool or the API. Its apps keep running unless we also stop them.

13.5 Running out of credit is covered by section 7, not by this section.

14. Stopping, deleting and leaving

14.1 You can stop using Clusterz at any time. There is no notice period.

14.2 Stopping your apps. When every app of your team is stopped, billing is held, as section 5.6 describes, and your data stays.

14.3 Deleting an app. Owners and admins can delete an app. Its services stop at once, and its settings and domains are deleted. After 7 days we delete its record, with its build history, its images and the key that unlocks its backups. We erase the data it stored, any team database or bucket Clusterz set up for it, and its database backups when you ask us to at contact@clusterz.eu.

14.4 Deleting your team or your account. Email contact@clusterz.eu. The team's owner, or your organisation under section 3.4, can ask us to delete a team. We complete a deletion within one month. Deleting a team deletes its apps, the data they stored, any team database and buckets, and their backups. Copies in our log store expire within 30 days, in any backup of our own databases within 40 days, in our metrics within 90 days and in our error reports within 100 days. An account that owns a team stays until the team is deleted or has a new owner. We keep some records after a deletion, as the privacy policy explains.

14.5 Moving to another provider. If you want to move your apps and data to another provider, or to your own systems, tell us by email. Then:

• your apps keep running on these terms, charges included, for up to 30 days while you move. You can extend this once, for a period you choose. If 30 days is not technically possible, we tell you within 14 working days, with our reasons and another period of at most 7 months;
• we help you move, and tell you of any risk to the move that we know of;
• when that period ends, you have at least 30 more days to take your data;
• after that, we erase your team's data, including its backups, as section 14.4 describes, and confirm it to you.

The contract ends, and we tell you so, when the move is complete, or when you choose erasure instead of a move. We charge nothing for moving or for taking your data with you.

Your code stays in your own repository. The data you can take, which we copy for you when you ask, is:

• each app's database, as a dump in that database's own format (PostgreSQL or MariaDB);
• the files each app stored, and any team database or bucket Clusterz set up, as an archive or a dump;
• your apps' settings;
• the images built from your code;
• your team's audit log and billing history.

Each app's own export tools may offer more.

14.6 We may end the contract if you seriously or repeatedly break these terms, or if the law requires it. We tell you why by email. Unless the law or a serious risk to others prevents it, we give you at least 30 days to take your data before we delete it.

14.7 When the contract ends, section 5.3 says whether we refund unused credit.

15. Liability

15.1 Our liability to you under these terms and the data processing agreement is limited to the fees your team paid us in the 12 months before the claim arose, or €1,000, whichever is higher.

15.2 This limit does not apply to intentional breach, gross negligence, death or personal injury, or anything else the law does not let us limit.

16. Changes to these terms

16.1 We change these terms, the acceptable use policy or the data processing agreement only for a reason: a change in the law, security, features we add or withdraw, our costs, or our subprocessors. We email the owners and admins of every team at least 30 days before a change applies. The email says what changes.

16.2 If you do not accept a change, you can leave before it applies, as section 14 describes, and we refund your unused credit as section 5.3 says. If you keep using Clusterz after that, the changed terms apply to you.

16.3 If the law makes us change something sooner, we tell you as early as we can.

17. Law and disputes

17.1 Estonian law governs these terms.

17.2 Disputes go to Harju County Court in Tallinn, Estonia.

17.3 If a court finds part of these terms invalid, the rest still applies.

18. Contact

18.1 Email contact@clusterz.eu, or write to Zer0Paper OÜ, Ahtri tn 12, 15551 Tallinn, Estonia.

18.2 We send notices to you by email to the owners and admins of your team.

18.3 Authorities and users can reach us at the same address under the EU Digital Services Act, in Estonian or English, and users can also use our help form. Section 12 of the acceptable use policy gives the details.