Legal
Terms of service
These terms describe the agreement for using Rydya as the product actually exists today. They contain no invented pricing and no service level we cannot honour. This is a working draft pending review by qualified legal counsel, it is not legal advice, and the contracting entity and governing law are matters for a written agreement rather than this page.
- Executive and finance
- Quality and compliance
- Hospital operations
What is in these terms of service
Definition
These terms
These terms set out the basis on which an organisation and its invited users may use Rydya: what each side is responsible for, who owns what, what we currently promise about availability and support, and the limits of those promises while the product is early.
They are written to describe the product as it is, not as it might be. Where Rydya does not yet offer something a mature vendor would, these terms say so rather than papering over it, because a term you cannot rely on is worse than an absence you were told about.
The commercial relationship, including price, packaging and the specific legal entity you contract with, is agreed in a written order or agreement. This page is the general framework, and where that written agreement and this page differ, the written agreement governs.
Accounts and acceptable use
Accounts are created by invitation, secured by the person who holds them, and used lawfully for managing your own equipment operations.
Accounts are by invitation
There is no public sign-up. Your administrators invite the people who need access and assign their scope. You are responsible for who you invite and for removing access when someone leaves.
Keep your credentials safe
Each user is responsible for keeping their sign-in credentials and multi-factor device secure, and for activity under their account. Tell us promptly if you believe an account has been compromised.
Use it lawfully and as intended
Use Rydya to manage your own organisation's equipment operations. Do not use it to break the law, to infringe others' rights, to probe or disrupt the service, or to upload content you have no right to upload.
You are responsible for your content
The equipment records, files and figures you enter are yours and your responsibility. Rydya does not review them, and uploaded files are not scanned for malware today, so treat what you upload accordingly.
Who owns what
Your data stays yours. The software, and everything we build into it, stays ours. Neither side takes the other's by using the service.
Your operational data, the equipment records, evidence and figures your team enters, belongs to your organisation. Using Rydya does not transfer ownership of it to us. We process it to provide the service, as described in the privacy policy and the data processing terms, and for no undisclosed purpose.
Rydya, including the software, its design, and the platform behind it, belongs to us and our licensors. These terms grant your organisation the right to use the service for its own operations while your agreement is in effect; they do not grant ownership of the software or any right to copy, resell or reverse engineer it.
If you send us feedback or suggestions, we may use them to improve the product without obligation to you. That is the only thing resembling a licence you grant us over your own words, and it exists so that acting on a good idea does not create a dispute about who owned it.
Subscriptions, availability and support, stated honestly
Commercial terms are agreed in writing. We do not publish a price here, and we do not commit to a service level we have not proven.
Subscriptions and any fees are set out in the written order or agreement for your organisation, not on this page. There is deliberately no pricing here to quote or misquote. Nothing in this draft should be read as an offer at a particular price.
On availability, we are honest rather than aspirational. We do not commit to a formal service level agreement today, and we publish no recovery objectives we have not measured, because an unmeasured objective is a number without a commitment behind it. Our backup and restore procedure is documented but has not yet been drilled, which is stated in full on the backups and recovery page. The service is provided on a reasonable-effort basis while it matures.
Support today is by email to one monitored address rather than a tiered support desk with promised response times we cannot yet stand behind. As the product and the organisation behind it mature, these commitments will become firmer and will move into your written agreement.
Service limitations you should know before you rely on us
The same gaps the trust pages publish, restated here so they are part of the agreement rather than a surprise.
No enterprise single sign-on yet
There is no SAML, OIDC login or SCIM provisioning. Authentication is email and password with multi-factor and step-up. If your identity team requires enterprise single sign-on, that is a genuine gap today.
Uploaded files are not scanned
Files uploaded as evidence are not scanned for malware. Downloads are permission-checked and audited, which addresses a different risk and is not a substitute for scanning.
No committed hosting region or certifications
Hosting region and data residency are not yet committed, and we hold no SOC 2, ISO 27001 or independent penetration test. If your procurement requires any of these today, or an equivalent in your market, we do not meet that bar.
The audit trail is deliberately immutable
Because the audit trail cannot be edited or deleted, some records genuinely cannot be removed on request without breaking the property that makes them trustworthy. We will tell you where this applies.
Warranty and liability
The service is provided as it is. The precise warranty disclaimer and liability limits are for the written agreement and legal review, and this draft does not invent them.
The service is provided on an as-is and as-available basis while it is early. To the extent the law allows, we do not give implied warranties such as fitness for a particular purpose or uninterrupted operation, precisely because we are being candid on this page about what is not yet proven. What Rydya genuinely enforces, such as tenant isolation and the safety and quarantine gates, it enforces at the server and the database rather than by promise, and those enforcement properties are described on the trust pages.
The limitation of our liability, and any exclusions, are matters that belong in your written agreement and must be set by qualified counsel for your jurisdiction. This draft does not state a figure or a formula, because a liability cap written by people unqualified to write it would be worse than none. Nothing in these draft terms is intended to exclude a liability that cannot lawfully be excluded.
Why these terms are a draft, how they change, and how the agreement ends
They are a draft because the commercial and legal specifics need counsel and a written agreement. Either side can end the arrangement, and we will give notice of material changes.
These terms are a working draft for the same reason our other legal pages are: the specifics, the contracting entity, the governing law, the liability position and the commercial terms, need qualified counsel and a signed agreement rather than a marketing page. Publishing the framework now, honestly, lets you evaluate us without waiting for the paperwork to catch up.
We may update these terms as the product and the agreement mature. Where a change materially affects your rights, we will update this page and its date and, for customers under a written agreement, give notice through that agreement. Continued use after a change means acceptance of the updated terms, except where your written agreement says otherwise.
Your organisation can stop using the service, and we can suspend or end access where these terms are seriously breached or where required to protect the service or other customers. On termination, we will make your operational data available for export for a reasonable period, subject to the retention and deletion realities described in the privacy policy, including the parts of the audit trail that are immutable by design.
This is a working draft, and what still needs counsel
This is a working draft and must be reviewed by qualified legal counsel before it is relied upon or executed. The contracting legal entity, the governing law and jurisdiction, the precise warranty disclaimer and the limitation of liability are deliberately not fixed here, because they depend on decisions and legal advice we have not yet completed. Nothing on this page is legal advice, and where a signed agreement exists it governs over this page.
Questions
How much does Rydya cost?
This page does not state a price, and that is deliberate. Commercial terms, including price and packaging, are agreed in a written order or agreement for your organisation rather than published here, so there is no figure on this page to quote or misquote. Ask us and we will discuss what fits your situation.
Do you offer a service level agreement or uptime guarantee?
Not today. We do not commit to a formal service level agreement and we publish no recovery objectives we have not measured, because an unproven number is a wish rather than a commitment. The service is provided on a reasonable-effort basis while it matures, and our backup and restore procedure is documented but has not yet been drilled, which we state in full on the trust pages.
Who owns the data we put into Rydya?
Your organisation does. Using the service does not transfer ownership of your equipment records, evidence or figures to us; we process them to provide the service as described in the privacy policy and data processing terms. The software and platform remain ours, and these terms grant you the right to use them rather than to own them.
Can we get our data out if we leave?
Yes. The product exports operational data in common formats, and on termination we will make your data available for export for a reasonable period. Some entries that form part of the immutable, append-only audit trail cannot be altered or removed without breaking the property that makes them trustworthy, and we will tell you where that applies.
Keep reading
Privacy policy
What data we hold and process, and the rights you have over it.
Data processing addendum
The processor terms that sit alongside these, drafted for review.
Cookie policy
What the product stores in your browser, and why it is not tracking.
Security
The service limitations above, described at the level a reviewer can test.
Backups and recovery
Why there is no recovery objective quoted in these terms.
See it on your equipment
Live in an afternoon, useful the same week. A person replies, usually within one working day.
Contact us