Last reviewed: 21 October 2026.
Security work starts with a clear scope, authorised access and an understanding of the information involved. This page explains how to raise security and data protection questions with Proxar Limited through managed-service-provider.co.uk.
Keep confidential material out of general enquiries
A first enquiry usually needs a description of the problem and a way to contact you. Please do not send passwords, private keys, authentication codes, complete configuration exports or sensitive customer records through the public contact form.
The form sends a message through our email system. HTTPS protects the browser connection; it does not turn the resulting email into an end-to-end encrypted file-transfer service. Where we need confidential diagrams, captures, records or configuration files, agree the transfer method, recipients and handling arrangements first.
Website and customer information
Proxar is responsible as controller for the website and business-enquiry processing described in our Privacy Policy. When we handle personal information on a customer’s documented instructions, the relevant controller and processor responsibilities must be addressed in the service and data-processing agreement.
Those arrangements need to cover the work, information, permitted use, security, assistance with rights and incidents, relevant suppliers, retention and return or deletion. This public page does not replace an Article 28 contract, service-level agreement or a customer’s own privacy notice.
Access, changes and assurance
Agree the systems in scope, who can authorise work and what access is needed. Changes should have suitable approval, verification and recovery arrangements. Support hours, response commitments and incident reporting routes belong in the agreed service documents.
Our website uses HTTPS and Cloudflare delivery and protection services. These controls help protect the site but do not eliminate every risk. Customer assurance may require more detailed evidence; tell us what your review needs and the proposed service. Confidential material may require a non-disclosure agreement.
Partner status, technical assessments and security tools do not themselves certify a customer’s GDPR compliance. Certificate scope and current validity also matter; see Accreditations.
Report a suspected website vulnerability
Email admin@proxar.co.uk with the affected address, when you noticed the issue and a concise description. Avoid sending other people’s data or sensitive attachments in the first message. We can agree a suitable route for necessary evidence.
If you encounter personal or confidential information unexpectedly, stop accessing it and describe the issue without collecting or circulating further copies. This reporting route does not authorise intrusive testing, exploitation, social engineering, denial-of-service activity or access to customer systems. Any testing permission must be agreed separately in writing.
We will assess reports and determine the next steps. Existing customers should use their agreed support and escalation route for operational incidents; the public website is not an emergency service or a replacement for contractual incident notification.
Privacy concerns
Use our data protection complaints procedure if you are concerned about how we used your personal information. The Privacy Policy explains your rights and contact options.