AUP

##Acceptable Use Policy (AUP) Version 1.1 · Effective Date: 12 August 2026 Operated by myfxvps.co (in this policy, “myfxvps”, “we”, “us”).

This policy sets out what you may and may not do with a server hosted by FxSVPS. It forms part of our Terms of Service, and it applies to you, to anyone you give access to, and to anything running on your server, including scripts, expert advisors and automated tools, whether you started them or not.

Report abuse to help@myfxvps.co

*Why this policy exists: Our servers share physical hardware, network capacity and, on NAT plans, public IP addresses. What one customer does affects everyone else on that node. A single spam run gets a shared IP listed on blocklists, and every customer behind that IP loses mail delivery. One outbound attack gets an entire range null-routed by the upstream provider. One copyright complaint puts the whole node at risk with the datacentre. That is the reason this policy is strict about a small number of things, and reasonable about everything else.*

##1. What you are responsible for## Everything that happens under your account. If your credentials are stolen, or an expert advisor you installed does something you did not expect, or a person you gave access to misuses the server, it is still your account and your responsibility. Keeping the server secure. Strong and unique passwords, current patches, and no default credentials. Most compromised servers we see were running an unpatched service or a reused password. Your own data. Unless you have bought a backup add-on from us, keep your own backups. We do not guarantee recovery of data from a suspended, terminated or failed server. Content being lawful where the hardware sits. Our nodes are in several countries. What is permitted in your country is not the test; what is permitted where your server physically runs is.

##2. Prohibited immediately, with no warning## These result in immediate suspension without prior notice. Where the law requires it, we report to the relevant authority. No refund is given.

Child sexual abuse material. Zero tolerance, reported without exception. Attacks on other networks. Denial of service, amplification or reflection attacks, port scanning, packet flooding, brute-force or credential-stuffing attacks, exploitation attempts, or operating command-and-control infrastructure for a botnet. This applies whether the target is a stranger, a competitor or your own broker. Malware operations. Distributing, hosting or controlling ransomware, trojans, keyloggers, stealers or exploit kits. Fraud infrastructure. Carding tools, stolen credential databases, card checkers, phishing pages, fake login portals, or any part of a payment fraud operation. Traffic to or from our platform obtained by fraud. Ordering with a stolen card or a stolen account. Content that is illegal where the server is located, including material that infringes copyright at scale, and anything a datacentre or upstream provider is legally required to remove. Cryptocurrency mining of any kind. Mining, hosted mining pools, mining proxies, browser-based mining and idle-time mining are all prohibited on every FxSVPS plan, without exception. Our plans are built and priced for low-latency trading workloads, not for sustained maximum CPU. There is no plan on which mining is permitted, and asking support will not change the answer. Unsolicited bulk email. Sending it, relaying it, or hosting any component of an operation that sends it, including landing pages, list servers, tracking pixels and unsubscribe handlers, even where the sending itself happens on another provider's network. Purchased and scraped lists count as unsolicited regardless of what the seller told you. Outbound port 25 is closed on all plans and we do not open it. If you need to send mail from an application, use an authenticated third-party relay such as a transactional email provider over ports 587 or 465. That is permitted; bulk sending is not, whichever port it leaves by.

##3. Prohibited, with notice where we reasonably can## For these we normally contact you first and give you a defined period to correct the problem, unless the impact on other customers is immediate.

Open relays and open proxies. Any service that lets an unauthenticated third party send traffic through your server. Reselling access to third parties as a proxy or VPN. You may run a VPN for yourself, your business or your own staff. You may not sell, share or publicly distribute access to a proxy or VPN endpoint running on our network. Public file distribution and torrenting, including seeding, public file lockers and warez distribution. Media transcoding farms and public streaming servers. Mass automated scraping that places an unreasonable load on a third party's systems or ignores their published access rules. Nested virtualisation and sub-hosting. You may not run your own hypervisor to resell virtual machines from your VPS, unless you are on our reseller programme and have agreed the Reseller Agreement. Anything that misrepresents the origin of traffic, including IP spoofing, forged mail headers and forged packet headers. Exceeding the terminal limit on your plan, as set out in section 4.

##4. Terminal limits on Windows plans## Every Windows plan includes a maximum number of trading terminals you may run at the same time. The limit for your plan is shown on the plan's page at the time you order and on your service details in the client area. That page is the authoritative figure; this policy explains how the limit works rather than restating the numbers.

What counts as one terminal. One running instance of MetaTrader 4 or MetaTrader 5, or of any comparable trading platform such as cTrader or a broker's own desktop application. Each portable copy and each separate installation folder counts separately, because each one is a separate running process. Two MT4 instances and one MT5 instance is three terminals. What does not count. Trade copiers, expert advisor tools, chart utilities, scripts, Python or Node bots, browsers, and remote desktop sessions themselves are not terminals. Only the trading platforms are counted. Multiple accounts. MetaTrader runs one broker account per instance, so five accounts means five terminals and needs a plan that allows five. Why the limit exists. Each terminal holds its own memory, tick feed and chart history. The limit is how we size memory and CPU per plan so that every server on a node performs consistently. It is a capacity figure, not a licensing restriction. How we measure it. We count running trading platform processes on Windows plans as part of the resource monitoring described in section 5. We count how many are running; we do not read your charts, your account numbers, your strategies, your expert advisor code or your trade history, and we do not access the contents of your files. This monitoring is also described in our Privacy Policy. Short overruns are fine. Opening an extra terminal briefly to migrate settings, compare a chart or test a broker connection is normal. The limit is about what runs continuously, not about a single moment. What happens if you go over. We treat this as a capacity conversation, not as abuse:

We contact you by ticket, tell you what we counted and over what period, and give you 72 hours to either close the extra terminals or move to a plan that covers them. If your usage is otherwise healthy and the node has room, we may simply offer you the larger plan with the difference applied as credit. If nothing changes after 72 hours, we may throttle the server's CPU allocation to protect the other customers on the node. Suspension is a last resort and only for repeated overruns after more than one conversation, or where the overrun is degrading the node for others right now. We would much rather move you up a plan than argue about it. If you are growing and need more terminals, open a ticket and ask; the answer is nearly always yes.

##5. Resource use## Your plan includes an allocation of CPU, memory, disk and bandwidth. Short bursts above it are normal and expected; a trading terminal opening several charts at once will spike, and that is fine.

What is not fine is sustained consumption that degrades the node for other customers. Where a server sustains use well above its allocation over a prolonged period, we will contact you and ask you to reduce it, move to a larger plan, or move to a dedicated server. If it continues after that conversation, we may throttle the server.

Disk I/O. Continuous heavy writes, such as tick-by-tick logging of every symbol to disk, will be throttled. Keep logging proportionate. Memory. Running more terminals than your plan's memory supports causes swapping, which slows the whole node's storage. If you need more terminals, you need more memory. Bandwidth. Fair use applies to unmetered plans. Sustained saturation of the port is not fair use. Backups and snapshots. Where a backup add-on is included, it is for your server's own data, not as general file storage. We would rather move you to the right plan than throttle you. Ask support before you scale up, and we will tell you honestly what your plan will carry.

##6. Trading-specific points## Because most of our customers run trading platforms, these are worth stating plainly.

Permitted: expert advisors, automated strategies, trade copiers, signal services, running multiple terminals and multiple broker accounts, arbitrage strategies, and connecting to any broker you choose. What you trade and how you trade it is your business. Not permitted: attacking, flooding or attempting to gain unauthorised access to a broker's infrastructure, including credential-stuffing broker accounts you do not own, or hammering a broker's API in a way that constitutes a denial of service. Between you and your broker: whether your broker permits a given strategy is a matter for your agreement with them, not with us. We do not police your strategies and we do not report them. Equally, if your broker restricts your account, that is not a fault of the service and section 3 of our Refund Policy applies.

1. How we enforce this

Where we can, we contact you first. Our normal order is:

We get in touch by ticket and email, describing what we have seen and what needs to change. You get a defined window to fix it, usually 24 to 72 hours depending on the severity and the impact on other customers. We suspend if it is not corrected, or immediately where section 2 applies or where other customers are actively being harmed. We terminate for repeated or deliberate breaches. Suspension means the server is powered off and network access is removed. Your data is retained for 14 days from suspension, so a resolved case can be restored. After 14 days it is deleted and cannot be recovered.

Where we have suspended you and you believe we are wrong, reply on the abuse ticket and ask for a review. A second person will look at it. We would rather correct a mistake than lose a customer over one.

Termination for breach does not entitle you to a refund, under section 3 of the Refund Policy.

##8. Compromised servers## If your server is compromised and is attacking others or sending spam, we will suspend it quickly, because the harm is happening to third parties in real time. This is not a judgement about you.

Tell us as soon as you know, and we will work with you to get you back online: usually a rebuild, a restore from your backup, and a review of what let the attacker in. Customers who report their own compromises are treated as customers with a problem, not as abusers.

##9. Copyright and legal complaints## Copyright complaints go to help@myfxvps.co with enough detail to identify the material and the rights being claimed.

We pass complaints to the customer and ask for removal or a response within the window the relevant law or our datacentre requires. Repeat infringement leads to termination.

Where a court order or a binding legal demand from the jurisdiction the server sits in requires us to act, we comply, and we tell you unless we are prohibited from doing so.

##10. Reporting abuse## If a server we host is causing you a problem, write to help@myfxvps.co with the IP address, timestamps with the timezone, and log extracts if you have them. We investigate every report and we reply.

Abuse: help@myfxvps.co Support: help@myfxvps.co

##11. Changes to this policy## We may update this policy. When a new version is published, we ask you to confirm it in the client area, and we keep a record of which version you agreed to, when, and from where. You can view all of your agreements at any time under Agreements in your client area.