Skip to content
Deploy

Legal

Services Addendum

This addendum covers the work our team does inside a server for you: hardening Remote Desktop, moving a server, fixing a listed Remote Desktop fault, admin time and Care. It adds to the Terms of Service; it does not replace them.

Last updated:

RyzenRDP is a brand of Rackvolt Cloud Solutions Pvt Ltd, a private limited company incorporated in India.

About this addendum

This Services Addendum applies when you order or use one of the services below from Rackvolt Cloud Solutions Pvt Ltd, a private limited company incorporated in India ("we", "us"). It forms part of the Terms of Service ("Terms"). Where this addendum and the Terms differ about a service, this addendum applies to that service. Words such as "server", "console" and "account" mean what they mean in the Terms.

  • A service is work our team does inside a server for you, as listed under The services.
  • A job is one order of a service, from the ticket we open for it to sign-off.
  • Hand-over is the ticket message in which we tell you that a job is done and what we changed.
  • Sign-off is your confirmation in the ticket that a job is complete (see Hand-over and sign-off).
  • A server elsewhere is a server that is not a RyzenRDP server, for example one you rent from another provider.

The services

Each service page shows the price, what the service includes and what stays yours. The price on your invoice is the price that applies.

  • RDP Security Check (free). A script you run yourself on your own Windows server. It reads settings and writes a graded report on that server. It changes nothing, and nothing is sent to us unless you send us the report.
  • Hardened Start (one-off add-on for a new RyzenRDP Windows server). Basic Remote Desktop hardening of a new server: Network Level Authentication on, TLS and high encryption for Remote Desktop, an account lockout policy, SMBv1 off, Microsoft Defender checked, the Windows firewall checked and turned on if it is off (if programs of yours already listen, we ask you first), and audit logging on, with a short report. The Remote Desktop port stays as it is.
  • RDP Lockdown Standard (one-off, for one server running Windows Server 2019, 2022 or 2025, at RyzenRDP or elsewhere). Network Level Authentication, TLS and high encryption for Remote Desktop, an account lockout policy, a review of local administrator accounts, Remote Desktop limited to the IP addresses you list if you ask for it, SMBv1 off, and Defender, firewall and audit settings checked, with a before-and-after report of every setting we changed. While your address list is active, we pause the Remote Desktop auto-repair task that comes with our Windows Server image, because it would reopen Remote Desktop to every address; it is turned back on when the Lockdown is undone.
  • RDP Lockdown Plus (one-off). Standard, plus two-step sign-in for Remote Desktop through an account you hold with a multi-factor authentication provider of your choice. Plus does not include a Remote Desktop Gateway.
  • Server move (one-off). We copy your data and applications from your current server to a RyzenRDP server. With a yearly plan you can have an assisted move at no charge: our guide and our pre-flight script, while you copy the data yourself; you then run our check script on the new server and we compare its report with the one from the old server. Each done-for-you tier has the limits shown on the service page, such as the amount of data or the number of applications; a larger job is quoted before we start.
  • RDP Rescue (per listed fault, RyzenRDP servers only). We fix one fault from the list on the RDP Rescue page at the time you ask, for example a Remote Desktop lockout after a firewall change or a CredSSP error. You pay after it works (see Fees and payment). A fault on our side is fixed free and is not an RDP Rescue job.
  • Admin time (prepaid, RyzenRDP servers only). Work inside your server that is not on the RDP Rescue list, such as installing software you are licensed to use, in prepaid blocks.
  • Care (monthly add-on on a RyzenRDP server). Operating system updates in a window you choose, holding back updates known to break Remote Desktop, a check after the restart, one restart of a service you name, and a monthly report. On Windows, Care also includes the admin time shown on the service page each month. See Care.

No service includes backups, snapshots or checkpoints of your server, a Remote Desktop Gateway, licences of any kind, support for your own applications, or a promised time for a reply or for completing the work.

Who may order, and your authority

  • Only the account holder, or a person the account holder has named to us in a ticket, can order a service, give consent or sign off. For servers ordered through the reseller program, that is the reseller: we do not take instructions about those servers from the reseller's own customers.
  • By ordering a service you confirm that you own the server or are authorised to control it, and that you may let us work on it. For a server elsewhere you also confirm that your agreement with that provider allows this, and that you can reach the server through that provider's own console if Remote Desktop stops answering.
  • For a server elsewhere we ask you to prove control before we start, for example by running our script on the server so that it shows a one-time code we give you in the ticket. We do not start until this is done.
  • We start a job only after you have agreed in the ticket to the consent text for that job. The consent, and every session of work on your server, stays on record in the ticket.
  • We may ask for more information before we start, for example how each application you want moved is licensed.

How we access your server

  • We never ask for the password of your own account. For a job, we ask you to create a temporary account for our team, or we create one with your agreement, and we remove it at hand-over. For Care, a named account for our team stays on the server while Care is active and is removed when Care ends.
  • On a RyzenRDP server we may also use our out-of-band screen access to the server, which does not depend on Remote Desktop, to put things right if Remote Desktop stops answering during a job.
  • We record each session of work on the ticket: when it started, when it ended and what we did.
  • You can withdraw our access at any time by removing our account or by telling us in the ticket. If you do so before hand-over, we stop, and the job ends as described under When we decline or stop a job.
  • Where a job needs a password, key or code for another service, such as your multi-factor authentication provider, you enter it yourself where you can. If you give one to us, please put it in the ticket in a message of its own: we use it only for that job, we remove that message from the ticket once we have used it, and we ask you to change it after hand-over. The same applies to the password of the temporary account you create for us.
  • We do not sign in to your accounts with other services, such as your multi-factor authentication provider, another hosting provider's control panel, your email or your software vendors' accounts.

Our role and the standard of our work

  • When we work on your server we act as your agent, on your instructions and on your behalf. You remain the operator of the server and responsible for what runs on it, as the Terms and the Acceptable Use Policy say.
  • We do the work with reasonable skill and care, using our own scripts and written procedures, and only tools whose terms allow their use in a paid service.
  • We do not promise a particular outcome. RDP Lockdown and Hardened Start reduce the risk of brute-force sign-ins; they cannot make a server immune to attack. Care reduces the chance that an update breaks Remote Desktop; it cannot prevent every fault. After hand-over, the security of your server and of the accounts on it stays your responsibility.
  • We do not support, debug or update your own applications, except in admin time you have prepaid.

Licences stay yours

  • Licences for the software on your server are yours: for applications, for Remote Desktop user access, for databases, for office software and for any other third-party product. We do not sell, supply, transfer or activate licences, and we do not supply product keys or activation tools. Where software asks for a product key or for activation, you enter the key and activate it yourself. As the Terms say, the Windows Server licence is not included in the plan price. Windows Server is installed for you but not activated: you license and activate it yourself.
  • We never work around a licence check, for example by resetting the Remote Desktop licensing grace period. Where a fault comes from a missing licence, the fixes we offer stay within your licences: returning the server to the two administrative Remote Desktop sessions that Windows Server allows without RDS CALs, or connecting it to a licence server that holds your own valid licences.
  • Before a server move we ask how each application is licensed. Many licences cannot be used on a hosted server whose hardware is shared with other customers' servers; for most Microsoft software, only subscription licences or licences with active Software Assurance can. We do not install software whose licence, as you describe it to us, does not allow its use on our servers.
  • Remote Desktop user licences for older versions of Windows Server do not work with Windows Server 2025. If more than two people need to use Remote Desktop at the same time on the new server, you need your own licences for that version that may be used on a hosted server; otherwise we set the new server up for the two administrative sessions.
  • After a move, re-activating your applications with their vendors is your task, and so is licensing and activating Windows Server on the new server. The Windows licence of a server elsewhere does not move with your data.

Your data

  • We take no backups, snapshots or checkpoints of your server under any service. Keep your own copy of anything you need before a job starts, as the Terms of Service already ask.
  • Server moves: copy, never delete. We copy your data to the new server. We do not delete, change or switch off anything on your old server. On it we add only our temporary account, a working folder that we name in the ticket and, for a Windows server, a temporary firewall rule that lets only the new server connect for the copy; we remove all three at sign-off. The old server keeps running until you sign off. Cancelling the old server is your decision, after sign-off. If the old server is a RyzenRDP server, it stays on its normal billing until you cancel it.
  • Data is copied directly from server to server. We do not keep copies on our own computers. Any working copy we make on either server is listed in the hand-over and removed at sign-off with your agreement.
  • On a Windows server, our scripts keep a record of the changes they made and their logs in the folder C:\ProgramData\RyzenRDP, so that a change can be undone later. The hand-over names it. It stays on your server, never with us; ask us in the ticket to delete it, or delete the folder yourself once you no longer need to undo a change.
  • Our team looks only at what a job needs, never uses your data for any other purpose, and is bound by confidentiality obligations.
  • When a job involves personal data on your server, such as user names and IP addresses in event logs, user profiles or files, we process it on your behalf under the Data Processing Addendum.
  • If we find signs that your server has been compromised, we stop the job and tell you. We may have to report the incident where Indian law requires it. Investigating a compromise is not part of any service.

Care: standing consent and your patch window

When you add Care, you agree in the ticket to a standing consent. From then on, without asking you each time, we may sign in to the server with the Care account to do the following, and only this:

  • set the server's automatic updates to wait for your patch window (we put the setting back when Care ends);
  • install operating system updates in the patch window you chose, except updates we hold back because they are known to break Remote Desktop and updates you asked us to skip (on Windows, a held update is hidden in Windows Update until we release it or Care ends, so it cannot install on its own);
  • restart the server when updates need it, check afterwards on the server that Remote Desktop (SSH on Linux) answers, and restart the one service you named, once, if it is not running; on Linux, if an update is interrupted, finish it and start the SSH service again if the update left it stopped;
  • read the result of each window and, if the server did not come back after the updates, sign in through our out-of-band screen access and uninstall the update that caused it, even after the patch window has ended;
  • prepare the monthly report, and use admin time you ask for in a ticket.

Your patch window and your choices:

  • You choose a recurring monthly window when Care starts, for example the second Saturday of the month at 02:00 in your time zone, and you can change it in a ticket. A change applies from the next window.
  • You can skip a month, or ask us to skip a particular update, by telling us in the ticket before the window starts. You withdraw the standing consent by cancelling Care.
  • Outside the patch window, only the automatic restart of your named service after the updates is promised. Our team reads each window's result and works on any problem it finds in the order tickets arrive; we do not promise a time.
  • Each month we install the new updates on staff servers first. A window that falls before that step is done for the month gets only the updates released earlier.
  • Care does not include backups, snapshots or checkpoints, updates of your own applications, support for your applications, or monitoring outside the patch window.
  • On Windows, the admin time included in Care is for that month; unused time does not carry over.
  • Care is billed monthly. You can cancel it at any time with a ticket in the console; it runs until the end of the month you paid for. When Care ends, we remove the Care account, our scheduled task and our Care files from the server.
  • We install nothing until you have agreed to the standing consent and chosen your window. If we still do not have them 30 days after you add Care, we remind you in the ticket, and you can cancel Care with a ticket in the console.

Hand-over and sign-off

  • At the end of a job we send a hand-over in the ticket: what we changed, how to undo it, what you need to do next (for example change any password you shared with us), and confirmation that our temporary access has been removed.
  • After RDP Lockdown and RDP Rescue we ask you to confirm that you can still sign in. After RDP Lockdown we ask again about 24 hours after hand-over.
  • You sign off by confirming in the ticket. If you do not reply within 14 days of the hand-over, the job counts as signed off.
  • If something we did does not work as the hand-over describes and you tell us within 7 days of the hand-over, we put it right at no charge. This covers our own work only, not changes made after hand-over by you or by others.

Fees and payment

  • Prices are in US dollars, as shown on the service page and on your invoice. Any tax that applies is shown on the invoice.
  • Hardened Start, RDP Lockdown, done-for-you server moves and admin time are paid in advance. For a done-for-you move we confirm the tier from your pre-flight report before we start. If the job is larger than the tier you ordered, we quote the difference, and you can accept the quote or have your payment refunded.
  • RDP Rescue: no fix, no invoice. We invoice a listed fix only once you confirm that you can sign in. If we cannot fix it, there is no invoice. A fault on our side is never charged.
  • Care is billed monthly, as an add-on to the server.
  • Refunds for services follow the services section of the Refund and Cancellation Policy.
  • If you think a service invoice is wrong, please open a ticket so that we can look at it with you.

When we decline or stop a job

We may decline a job, or stop one before hand-over, if:

  • you cannot prove control of a server elsewhere, or cannot reach it through your provider's console;
  • the work would break the law, these terms, the Acceptable Use Policy or a licence;
  • the job needs something we do not offer, such as a backup, a Remote Desktop Gateway, a licence or a way around a licence check;
  • the job is larger than the tier you ordered and you do not accept the quote;
  • the server shows signs of compromise;
  • carrying on would put your data, our network or other customers at risk; or
  • the person asking is not the account holder or a person the account holder has named.

If we decline or stop a job for a reason that is not a breach of these terms on your part, you pay nothing for it, and anything you paid for it is refunded. We tell you the reason where we can.

If a one-off job paid in advance cannot start because we are still waiting for your consent, access or pre-flight report 30 days after the order, we close the job and tell you in the ticket. Within 12 months of the order you can ask us to reopen it, or to refund the payment. Care is covered under Care.

Timing

  • We do not promise a time for a reply or for completing a job. Jobs are worked in the order in which they are ready to start.
  • Server moves are booked into weekly slots, which are limited in busy periods such as December and January. We confirm your slot in the ticket; a slot is the date we plan to start, not a completion date.
  • For RDP Lockdown Plus we agree a time with you for setting up two-step sign-in, because you need to be available to approve it.

Liability for services

  • Our total liability for all claims about a job is limited to the fee you paid for that job. For Care it is limited to the Care fees you paid in the three months before the event that gave rise to the claim. To the extent the law allows, a free service or tool carries no liability.
  • We are not liable for the loss of data of which you did not keep a copy, for faults in your own software or in third-party software and services (including your multi-factor authentication provider and any other hosting provider), for the consequences of licences you hold or lack, or for anything done on the server after hand-over.
  • The rest of the Liability section of the Terms, including the exclusion of indirect loss, also applies to services. Nothing in this addendum limits liability that cannot be limited by law, or your rights as a consumer under the law that applies to you.

Free tools

  • Our free scripts, such as the RDP Security Check and the pre-flight script for server moves, are provided as they are, without warranty. They read settings and write a report on the server where you run them. They send nothing to us; you decide whether to send us the report.
  • Run them only on servers you control.

Changes and contact

We may change a service or this addendum in the way the Terms describe for changes to the Terms. A change does not apply to a job that has already started, or to a month of Care you have already paid for. Questions about this addendum: [email protected], or a ticket in the console.