Terms of service
Updated
Draft. These terms were written by the team that operates the service, not by a lawyer, and have not been reviewed by one. They describe honestly how we intend to work. Before they bind anyone they need review in the jurisdiction where the contract is signed.
1. Who we are
RX Team builds and operates infrastructure — private clouds, storage, the edge, mail, private networking and the server side of applications — on infrastructure the client owns or rents. We do not resell hosting and we do not take custody of client funds. Servers and provider accounts are in the client’s name; the client pays the provider for them directly, and that cost is not part of the price of our work.
2. What is being bought
Work is bought as one of the packages published on this site, or as a scope agreed in writing before it starts. Each engagement names its deliverables, its price and its timeline. Anything not named is not included.
The audit is a fixed-price deliverable: a written report. It does not include implementing what the report recommends.
3. Access
The client provides access to the systems in scope and to DNS control for the domains in scope. We ask for the narrowest access that lets the work happen. Edge, mail and network work needs no application source code or database contents. Application and storage work — speeding up and hardening an application, migrating data — does need access to code, the database or the data; its extent and duration are named in writing before the work starts, and client data is not copied outside the client’s infrastructure without the client’s written consent. Credentials are held only for the duration of the engagement and revoked at its end by the client; we will confirm in writing when we no longer need them.
4. What we will not do
We do not operate infrastructure used for the activities listed in the acceptable use policy. We will decline or stop work on discovering such use, and section 8 applies.
5. Payment
The audit and any one-off work is paid before delivery. Retainers are invoiced monthly in advance. Payment is accepted in cryptocurrency, or by invoice where documents are required.
Prices on the English site are in US dollars, on the Russian site in roubles. The currency of a given engagement is fixed in writing together with its price.
Published prices are indicative. The price for a specific engagement is fixed in writing before work starts and does not change during it. If the scope changes, the change and its price are agreed in writing first.
6. What we promise
We promise the work described, done competently, within the agreed timeline, and an honest account of what we found and what we changed.
We do not promise that the systems we operate will never fail. Nobody can. What a retainer buys is a defined response when they do, not the absence of failure.
Where an engagement carries an availability or response commitment, that commitment is written into that engagement and states its own measurement and its own remedy. Absent such a clause in writing, none is implied.
7. Liability
Our liability for an engagement is limited to the fees paid for it. We are not liable for indirect or consequential loss, including lost revenue or lost data, except where the law does not permit that limit.
8. Ending the agreement
Either side may end a retainer with thirty days’ written notice. We may suspend or end an engagement immediately on acceptable-use grounds, on non-payment after written notice, or where continuing would require us to act unlawfully.
On termination we hand over configuration, documentation and access in a usable state. We do not hold client infrastructure hostage to a billing dispute.
9. Confidentiality
What we learn about a client’s systems stays between us. We do not name clients publicly without written permission, and nothing we publish describes a client’s topology, addresses or hostnames.
10. Changes to these terms
The version in force is the one in effect when an engagement is agreed. Changes published here do not apply retroactively to work already agreed.