This page explains how MCI Network Services handles security and data protection. We start by agreeing what data is involved, who may see it and what work is allowed. The page describes our approach to the public. It does not publish internal settings or promise that one tool can remove every risk.
Website information and customer information
For a website enquiry, tell us what you need and how to contact you. We do not need access to your network at that stage. Keep passwords, private keys, login codes, full device exports and sensitive customer records out of the general enquiry form.
The form sends your message through the site’s email system. HTTPS protects the browser connection. It does not make the resulting email an end-to-end encrypted file-transfer service. Before sending private diagrams, captures or settings, agree how they will be sent, who may receive them and how they will be handled.
Our Privacy Policy covers data used to run this website and handle our own business contact. Work carried out on a customer’s instructions also needs the right contract and data-processing terms. The website policy does not replace those terms.
Website protection
The site uses HTTPS. Network delivery and security services also sit in front of the host. These measures help protect connections and manage abusive traffic. They cannot guarantee protection from every attack, outage or error.
We do not publish private network addresses, credentials or internal security settings here. Changes to site controls need their own tests. This policy does not prove that the live site’s cache, headers, access rules or recovery process have passed an assessment.
Access during a networking engagement
For work on your network, the scope should name the systems involved and the people who can approve changes. It should also define the access needed for the task. Access must fit the work. It should be removed or changed when that work ends or its scope changes.
A change to routing, network boundaries, identity checks or remote access can affect more than one device. The plan should cover approval, a suitable change window, tests and a way to recover. The agreed service documents set the specific commitments for access, logs, retention and security.
Evidence and compliance boundaries
Network maps, asset lists, settings reviews and change records can help a customer’s assurance process. These records do not, on their own, certify the business. They also do not prove that every part of a standard has been met.
An ISO claim must name the organisation, certificate, work and sites covered. PCI DSS duties depend on the payment environment and the roles agreed in the contract. Using Cisco or Meraki equipment does not, by itself, establish ISO certification or PCI DSS compliance.
Report a suspected website vulnerability
Send an initial report to admin@proxar.co.uk. Give the affected web address, when you saw the issue and a brief description. Include enough detail to help us reproduce the problem. Do not include credentials, other people’s personal data or a large sensitive attachment in the first email.
If you come across personal or private data by accident, stop accessing it. Tell us what you found without downloading or sharing more copies. We can agree a secure way to receive any evidence needed. This contact route does not permit scanning, exploitation, social engineering, denial-of-service tests or access to customer systems.
We will assess the report and decide the next steps. This page does not promise a bug-bounty payment, legal safe harbour or a response within a set time. Existing customers with a service incident should use the support and escalation route in their agreement. Do not rely only on a public website enquiry.
Privacy concerns and supplier assurance
Use the same email address for a data-protection concern and make its purpose clear. Our Privacy Policy explains your rights and how to complain. A security report does not replace an incident notice required by a contract. Customer-service reporting duties are set by the relevant agreement and applicable law.
For a supplier or assurance review, tell us what evidence you need and the proposed scope. Some details may require a confidentiality agreement. We will not share another customer’s settings or private audit material as proof of our experience.
Prepared on 21 October 2026; wording reviewed on 26 October 2026. Review this page when the way the website handles data, its controls or its service arrangements change.