Agreements
Terms of service
The agreement between your organisation and Rykon Technologies Inc. for using Rykloud.
- Version
- 1.0
- Effective
- 5 November 2026
- Last updated
- 5 November 2026
1.The agreement
1.1These terms of service ("Terms") are an agreement between Rykon Technologies Inc. and the Customer. They include the acceptable use policy, the data processing addendum and the service description, which form part of them. Where they conflict, the data processing addendum governs the processing of Personal Data, then these Terms, then the acceptable use policy, then the service description.
1.2You accept these Terms when you accept them in the console, which records who accepted which version and when. If you accept them for an organisation, you confirm that you are authorised to bind it. The service is provided for business use; it is not offered to consumers acting outside their trade or profession.
2.Definitions
- "Rykloud" or "the service"
- The platform provided by Rykon Technologies Inc.: the Rykon account, organisations, the console at app.rykloud.com, environments and everything Rykloud runs in them, the status page, and the websites at rykloud.com.
- "we", "us", "our"
- Rykon Technologies Inc..
- "Customer" or "you"
- The organisation that uses Rykloud, and anyone who accepts these terms on its behalf.
- "Rykon account"
- The one sign-in, at id.rykloud.com, that a person uses for Rykloud and for the Rykon products.
- "Organisation"
- The Customer as Rykloud holds it: its people and their roles (owner, admin, member), its products, environments, cloud accounts and records.
- "Environment"
- A set of cloud resources (servers, network, database, storage, and the products and services deployed in them) that Rykloud creates, runs, stops, saves and restores for an Organisation, in the cloud and region the Customer chooses.
- "Products"
- Rykon Mail and Rykon AI. Each has its own terms on its own site, which apply when you use it, in addition to these.
- "Customer Data"
- Everything the Customer or its people put into an Environment or the service, and what runs in an Environment produces: code, configuration, secrets and variables, databases, files, logs and the personal data in them.
- "Account Data"
- Information about the Customer and its people that we need to run the service: names, email addresses, organisation and roles, sign-in records, the activity record, notification choices, terms acceptances, usage and billing.
- "Personal Data", "Controller", "Processor", "Data Subject", "Processing"
- Have the meanings given in the GDPR.
- "GDPR"
- Regulation (EU) 2016/679, and where the context requires the UK GDPR and the UK Data Protection Act 2018.
3.The service
3.1Rykloud gives an Organisation one place to run its Products and its own services: it creates Environments in the cloud and region the Customer chooses, deploys what the Customer asks for into them, shows their state, logs and cost, and stops, saves and restores them.
3.2The Products are part of the same account and keep their own terms. Using Rykon Mail or Rykon AI through Rykloud means accepting that Product’s terms too.
3.3We may improve and change the service. We will not remove a material feature of a paid plan during a paid period without giving notice under the changes clause and, where you then end the service, refunding the unused part of any prepaid fees.
4.Accounts, organisations and roles
4.1People sign in with their Rykon account. You keep sign-in details secure and are responsible for everything done through your Organisation by its people. Tell us promptly at support@rykloud.com if you believe an account has been used without permission.
4.2Roles decide what each person may do: owners everything, including approving spend and adding cloud accounts; admins manage people, environments and settings; members work in the environments they are given. An owner removes people from the Organisation in the console.
5.Environments, spend and approval
5.1Nothing that costs money is created until an owner of the Organisation approves the itemised price the console shows. A change that alters the price is shown, with its new price, before it is made.
5.2An Environment with a time limit is stopped at that time and its data kept. Stopping keeps a saved copy so the Environment can be restored; destroying it removes its resources and, unless you choose to keep one, its saved copies.
5.3Each Organisation has limits on how many Environments it runs at once and how much it may commit each month. The console says when a limit stops a request; an owner can ask us to raise one.
6.Where environments run
6.1An Environment runs in one of three kinds of cloud account: Rykloud’s shared account for that cloud, an account Rykloud makes for the Organisation alone, or the Customer’s own account (AWS or Google Cloud), reached through a role or service account the Customer grants. Rykloud never asks for or stores the Customer’s cloud keys.
6.2In the Customer’s own account, the cloud provider’s bill and terms are the Customer’s, and that provider is the Customer’s own supplier rather than our subprocessor.
7.Customer Data
7.1As between the parties, Customer Data belongs to the Customer. You grant us a limited licence to host, store, copy, transmit and process Customer Data only as needed to provide, secure and support the service, and for no other purpose.
7.2For Personal Data in Customer Data, the Customer is the Controller and we are its Processor, as the data processing addendum sets out.
7.3We do not sell Customer Data, use it for advertising, or use it to train artificial intelligence models. Our staff read what is in an Environment only when you ask us to in a support request, or where the law or the security of the service requires it.
8.Plans and fees
8.1Rykloud billing is not yet switched on, and no Organisation is charged for Rykloud today. Before any charge, we will publish the price list, and an owner will approve each itemised price in the console as described above. Charges will then follow the approved prices and the time each resource ran, invoiced through our payment processor. Fees exclude taxes, which are added where the law requires.
9.Term and ending
9.1These Terms apply while your Organisation uses the service. An owner may ask us to close the Organisation at any time by writing to support@rykloud.com from an owner’s address; we confirm the request and what will be removed before acting on it.
9.2We may end the service for a serious or repeated breach of these Terms or the acceptable use policy, or, for any other reason, with 30 days’ notice and a refund of prepaid fees for the unused period.
9.3When an Organisation closes, we destroy its Environments in Rykloud’s accounts and delete their saved copies within 30 days, after giving its owners the chance to take a copy of their data. What we keep after that, and for how long, is set out in the privacy policy.
10.Availability and support
10.1What we commit to about availability, maintenance and support is in the service description. Support is by email at support@rykloud.com.
11.Changes to these Terms
11.1We will give at least 30 days’ notice by email and on this page before a price change, or a material change to these Terms, takes effect, and the console will ask you to accept the new version. If you do not accept a change, you may close your Organisation before it takes effect.
12.Warranties and disclaimers
12.1Each party confirms it has the authority to enter into these Terms. We will provide the service with reasonable skill and care. Except as stated in these Terms, and to the extent the law allows, the service is provided as is, and we make no other warranty, including of merchantability, fitness for a particular purpose, or uninterrupted operation.
12.2You are responsible for what you deploy into an Environment, for keeping your own copies of data you cannot afford to lose, and for the configuration you choose.
13.Limitation of liability
13.1Neither party is liable to the other for indirect, special or consequential loss, or for loss of profit, revenue, data or goodwill. Each party’s total liability arising out of or in connection with these Terms in any twelve month period is limited to the fees the Customer paid us for the service in that period.
13.2Nothing in these Terms limits liability for fraud, for death or personal injury caused by negligence, for the Customer’s obligation to pay fees, or any other liability that cannot be limited by law.
14.Your responsibility for your use
14.1The Customer will defend and indemnify us against third-party claims arising from what it runs in its Environments, or Customer Data it had no right to use, in breach of these Terms or the law.
15.General
15.1Neither party is responsible for failure caused by events beyond its reasonable control. Neither party may assign these Terms without the other’s consent, except to a successor of its business. If any part of these Terms is unenforceable, the rest remains in force. These Terms are the whole agreement between the parties about the service.
16.Contact
16.1Questions about these Terms, and reports of misuse: support@rykloud.com.
Change log
Version 1.0
5 November 2026First published.
