Verification Service Privacy Notice

Last updated: 28 September 2026

Notice version: 2026-09-28

1. Who we are

This notice covers the badge verification service at verify.mywebaccess.co.uk, and visits to legal.mywebaccess.co.uk, where this notice and our other legal documents are published. MyWeb Access is an accessibility audit service operated by MyVision Oxfordshire Ltd, a charity registered in England and Wales (charity number 1140556) and a company limited by guarantee (company number 07465300), which is the data controller for the processing described here.

Registered office: MyVision Oxfordshire, Bradbury Lodge, Gordon Woodward Way, Oxford, OX1 4XL. We are registered with the Information Commissioner’s Office under reference Z2824840.

You can contact us about anything in this notice at support@mywebaccess.co.uk, or by post at the address above.

2. Cookies and your device

Our own pages store nothing on your device and read nothing from it: no local storage, no analytics, and no third-party scripts, images or fonts. Our network provider, Cloudflare, runs a short automated security check in your browser, which sends Cloudflare information about your browser, to protect the service from abuse. It normally sets one cookie, cf_clearance, which records the result of the check, applies to mywebaccess.co.uk and its subdomains, and lasts up to a year. If Cloudflare decides a visit needs a closer look it may show a check page and set further security cookies. We do not use it for anything else. Cloudflare also uses information about traffic on its network to run, secure and improve its services, under its own terms and privacy policy.

3. What we process when you visit

Our hosting and network providers record ordinary server logs: your IP address, the page you requested, the time, and your browser’s user-agent string. We use these only to keep the service running and secure, and we keep no copies. Railway keeps its request logs as a separate controller, for as long as its own privacy policy allows. Cloudflare keeps traffic records for as long as it needs them to run and secure its network; its privacy policy sets no fixed period. Our lawful basis is legitimate interests (Article 6(1)(f)) — operating and protecting a service we publish.

If you arrive by clicking a badge, your browser usually tells the service which website you came from (normally just the site’s address, not the page), unless that website or your browser is set not to. It reaches our providers with the rest of the request. We do not keep it or use it for anything else.

The badge check happens in your browser, not on our servers. If your browser passed on the site you came from, the page compares it with the site the badge was issued for and shows the result; if not, it shows nothing. The result is not sent back to us, stored or combined with anything.

If you email us at support@mywebaccess.co.uk, we process what you send in order to answer you, under legitimate interests. Messages pass through Cloudflare’s email routing and are delivered to a Microsoft 365 mailbox operated by MyVision. We keep routine messages for 12 months after the last message in the conversation. A message that becomes part of a client engagement, a complaint or a rights request is kept with that record, for as long as that record is kept.

4. What we publish about audited organisations

No verification record has been published yet. This section describes what a record will contain and how it will be handled, and none will be published until the safeguards it describes are in place.

A verification record is public. It states the organisation whose website was audited, the website or section audited, the WCAG version and level, the date of the audit, the date its re-audit falls due, and whether that date has passed. Publishing the record will be a condition of having a badge: a client who does not want a public record can still have the audit and its report, but not the badge.

For most audited organisations this is information about an organisation and not personal data, and data protection law does not apply to it. Where the audited organisation is a sole trader or is identified by an individual’s name, or the website’s address is itself a person’s name, it is personal data and the rest of this section applies.

Our lawful basis is legitimate interests (Article 6(1)(f)), both while a record is current and after its re-audit date has passed. The interest is the integrity of a public verification scheme: a badge displayed on a website must resolve to a truthful record, or the badge means nothing to the person checking it. A record that disappeared when a client stopped being a customer would leave that badge asserting something no one could check — which is the harm the scheme exists to prevent. We are still writing our assessment of that interest against your rights, and no verification record will be published until it has been adopted.

A record’s details stay public for a fixed period after its re-audit due date. That period will be set, and stated here, before any record is published. After it we remove the details. The record’s address keeps working, but shows only a short statement that there is no current verification record there. It names nobody and gives no dates or reasons, and this step will exist before any record is published. The address may still be linked from sites where the badge remains, and the badge itself shows the website’s address. Before any record is published we will also set, and state here, what we keep internally once a record’s details are removed, for how long, and how earlier versions of a record are handled. We do not simply delete the page, because a badge already displayed on a website cannot be recalled by us, and a badge that suddenly resolves to nothing reads as a forgery rather than as an expiry.

You can object to this processing at any time, or ask for the record to be erased, by writing to the address in section 1. We will respond within one month, and we will stop unless we can demonstrate compelling legitimate grounds that override your rights. Where we do stop, we take the record down. Before any record is published, we will make sure that a record taken down still resolves to a short statement that names nobody, so that a badge already on a website does not break. One limit is worth stating plainly. A record that has been public may have been saved by a search engine, a web archive or the reader, and we cannot recall copies we never held — where you ask for erasure we take reasonable steps to tell those we can identify, which is what Article 17(2) requires of us and is not the same as a guarantee.

5. Who else is involved

The service is hosted by Railway Corporation and delivered through Cloudflare, Inc.; between them they handle the requests and server logs described in section 3. Railway also uses request logs for its own security and service operation, under its own privacy policy. Email to us passes through Cloudflare’s email routing to a Microsoft 365 mailbox operated by MyVision (section 3). Verification records will be built and stored using source-code hosting provided by GitHub, Inc., from which Railway builds the service; before any record is published we will state here where records are kept and for how long any earlier versions and build logs are kept. Apart from these providers, the public record described in section 4, and anyone we are required by law to tell, we do not share personal data with anyone, and we never sell it. There is no advertising or analytics on the service.

Processing outside the UK. Railway, Cloudflare and GitHub are United States companies, so using them involves transferring personal data to the United States, wherever their servers are. Those transfers rely on the UK’s adequacy regulations for the United States (the UK Extension to the EU-US Data Privacy Framework), under which each of them is currently certified. You can ask us for details at the address in section 1.

6. Your rights

You have the right to ask what we hold about you, to have it corrected, to have it erased, to restrict or object to how we use it, and to receive it in a portable form where that applies.

Your right to object. Where we use your personal data on the basis of legitimate interests, you can object at any time. We will stop the processing unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is needed for legal claims.

Write to support@mywebaccess.co.uk or to the postal address in section 1. We respond within one month, or tell you within that month if we need up to two more months and why.

If you want to complain about how we have handled your personal data, write to the same address or to the postal address in section 1. We will acknowledge your complaint within 30 days of receiving it and tell you the outcome. If you are not satisfied, you can complain to the Information Commissioner’s Office at ico.org.uk/make-a-complaint.

7. Changes

If this notice changes we will update the version and date at the top of this page.

Back to all legal documents