How we secure this website, the partner portal and the data you share with us, and where we stand on the regulations that govern our products — and how that maps to recognized security standards.
Last updated: 2 November 2026
Vision Telematics designs security in rather than bolting it on. This page describes the controls protecting our website and partner portal, plainly and honestly: where we align with a recognized standard we say aligned — we do not claim certifications we don’t hold.
Found a vulnerability? We want to hear about it. Our full coordinated vulnerability disclosure policy sets out scope, timescales and the assurances we give researchers. Email info@visiontelematics.com and we’ll acknowledge within three working days — machine-readable details are published at /.well-known/security.txt. Please avoid accessing other people’s data or disrupting the service while researching.
An honest summary: aligned means our technical controls follow the standard’s requirements at website scope — it does not mean certified.
| Standard | Our position |
|---|---|
| Cyber Essentials | Technical controls in place; certification is on our roadmap. |
| UK GDPR / PECR | Designed to comply: ICO-registered data controller (ZC201837), minimal data, consent where required, published policies. |
| NIST CSF 2.0 | Aligned: strong protection and recovery controls; detection and response processes are being formalized. |
| CIS Controls v8.1 | Core safeguards implemented: secure configuration, multi-factor authentication, access management, data recovery and a vulnerability-disclosure channel. |
| ISO 27001 / ISO 27701 | Practices informed by both; not certified. Personal-data handling follows ISO 27701 principles. |
| EU Cyber Resilience Act | Preparing. Applies to our products; main obligations from 11 December 2027. Vulnerability reporting duties began 11 September 2026. What we have done. |
| EU AI Act | Preparing. We use AI for safety detection, not emotion inference or biometric identification. High-risk obligations from 2 December 2027. Where we stand. |
| EU Data Act | Preparing. Applies since 12 September 2025; your right to access and move your product data is live today. How to use it. |
| NIS2 / DORA / HITRUST / FedRAMP | Not in scope for our activities; we support customers’ own supply-chain security duties under these regimes. |
Three EU regulations now govern the products we supply, rather than this website. We place hardware and software on the EU market under our own brand, which makes us the responsible party under each of them. The tables below are our honest self-assessment against the obligations that matter. They are not a claim of compliance, and they are not a legal opinion. Where we have not done something yet, they say so.
The operational routes these obligations create — reporting a vulnerability, requesting an SBOM, getting your data out — all live on our Product Compliance page.
The CRA sets cybersecurity requirements for products with digital elements sold in the EU. Aftermarket devices fitted to vehicles are in scope even though type-approved vehicles themselves are not. Our products fall in the default class, which means we can self-assess rather than use a notified body. Obligations run from 11 September 2026 for reporting, and from 11 December 2027 for everything else.
| Obligation | Where we stand |
|---|---|
| Coordinated vulnerability disclosure policy | Done. Published, with scope, timescales and researcher assurances. |
| Single point of contact for security | Done. We publish a security contact and a machine-readable security.txt file. |
| Publishing advisories for fixed vulnerabilities | Process established. None published to date. |
| Software bill of materials | On request. For products we supply. Machine-readable SBOMs for every line are in progress with our manufacturing partners. |
| Reporting exploited vulnerabilities within 24 hours | Not yet in place. This duty began on 11 September 2026 and we are standing up the reporting route. We are saying so rather than implying otherwise. |
| Declared support period with an end date at purchase | In progress. The floor is five years. We are confirming the period per product family and will publish the dates. |
| Technical documentation, risk assessment, CE marking | Not started. Required by 11 December 2027. |
| Free security updates through the support period | Partly. Remote updates ship today and are always free; the formal commitment follows the support-period work. |
The AI Act regulates AI by risk. Putting our brand on an AI system makes us its provider. The prohibitions have applied since 2 February 2025, transparency duties since 2 August 2026, and obligations for high-risk systems apply from 2 December 2027.
| Obligation | Where we stand |
|---|---|
| No prohibited practices | Met. Nothing we supply infers emotions, recognizes faces, identifies people biometrically or scores people socially. |
| Fatigue detection and the workplace emotion ban | Outside the prohibition. Fatigue is a physical state, not an emotion, and the Act names driver fatigue detection for accident prevention as an example of what it does not cover. We hold suppliers to that boundary. |
| Transparency to people interacting with AI | Assessed as not engaged. Our systems are not conversational, and are neither emotion-recognition nor biometric-categorization systems. |
| Driver-behavior scoring | Likely high-risk. That is our reading where it monitors and evaluates employees. We are treating it as high-risk and seeking a qualified opinion rather than assuming the lighter answer. |
| High-risk provider duties: risk management, data governance, logging, human oversight, conformity assessment | Not started. Required by 2 December 2027. |
| AI literacy of our people | Not yet in place. This duty began on 2 February 2025 and is the first gap we are closing. |
The Data Act gives users of connected products the right to the data those products generate. It has applied since 12 September 2025, and since 12 September 2026 new products must be designed so that data is accessible by default. This one is live now, and it is your right rather than our obligation to be gracious about.
| Obligation | Where we stand |
|---|---|
| Your right to access the data your devices generate | Available on request. Free, in a structured machine-readable format. Ask us or your account manager. |
| Your right to send that data to someone else | Available on request. That includes sending it to another supplier. |
| Not using your product data to compete with you | We do not. And we have said so in writing. |
| Self-service access built into the product | Not yet. Access is handled as a request today; building it into the platform is the right answer and is planned. |
| Telling you before purchase what data a product generates | Not yet consistently. We are adding it to product documentation. |
| Fair contract terms | Under review. We are checking our terms against the list of terms that cannot be imposed on smaller businesses. |
Third-party services that may process data when you use this site:
| Service | Purpose |
|---|---|
| Amazon Web Services (London) | Hosting |
| Twilio SendGrid | Transactional email — enquiries and sign-in codes |
| Twilio | WhatsApp sign-in codes |
| Cloudflare Turnstile | Bot protection on forms |
| Google Fonts | Typeface delivery |
| postcodes.io | UK postcode lookup on order forms |
Email info@visiontelematics.com or call 0800 020 9339 — we’re happy to complete security questionnaires for customers and prospective partners.