Privacy policy

We collect nothing about you as a visitor. When you look up a postcode, we show certificate data from the government register — and that data includes addresses, so we look after it carefully.

Last updated 25/09/2026

Who is responsible

EPC Checker (epcchecker.uk) is responsible for the data described on this page. For anything about your data, email privacy@epcchecker.uk.

If you are visiting this site

  • No accounts, no sign-up and no forms.
  • No cookies, no analytics and no tracking. See cookies.
  • Every calculator runs in your browser. What you type into the rating, upgrade cost, landlord 2030, expiry or ECO4 tools never leaves your device, and the calendar reminder file is created on your device too.

When you look up a postcode

The postcode is sent to our server, which asks the Energy Certificate Data API run by the Ministry of Housing, Communities and Local Government (MHCLG) for the certificates held for it. Our own code does not record the postcode.

Two things do happen, and you should know about them:

  • Hosting logs. Our hosting provider, Vercel, keeps short-lived technical logs of requests to run and secure the service. These include the address of the page requested — which contains the postcode — and your IP address.
  • Abuse protection. To stop the lookup being scraped, we count lookups per IP address, in memory, for one minute at a time. The count is not written anywhere.

If you live in or own a property with a certificate

Energy Performance Certificates for England & Wales are held on a public register. Because a certificate is tied to an address, the data on it counts as personal data about the people who live there, and we are responsible for how we show it.

What we show

Only when someone searches for your postcode: the address, the energy rating and score, the potential rating, the floor area, the property type and the date the certificate was lodged. The certificate holds much more; the rest never leaves our server.

Why, and on what basis

To help people understand how energy efficient a property is and what it would take to improve it — for buyers, tenants, landlords and occupiers. This is one of the purposes for which Ordnance Survey and Royal Mail allow the address data to be used.

Our lawful basis is legitimate interests (Article 6(1)(f) of the UK GDPR): making information that is already public on the government register easier to find and understand. We have weighed that against your privacy, which is why we:

  • show a certificate only when someone searches for its postcode;
  • never publish a page about an individual address;
  • keep every results page out of search engines;
  • never build lists of addresses, sell data, or use it for marketing;
  • never combine it with any other data about you.

Our area pages, when they exist, show statistics for whole postcode districts only — never an address.

How long we keep it

We do not store certificate data. Responses are cached for no more than 25 hours to reduce the load on the register, and then discarded.

Who else handles it

  • MHCLG, which runs the register and the API we query.
  • Vercel, which hosts the site. Our server functions run in London; the provider’s network may hold short-lived cached copies elsewhere.
  • Supabase, if the lookup cache is switched on, to hold cached responses for up to 24 hours.

Your rights

  • Object. Ask us to stop showing the certificate for your address and we will. It stays on the government register, which we do not control, but it will no longer appear on this site.
  • Access. Ask what we hold. For certificate data the honest answer is usually nothing, because we do not store it.
  • Correction. We cannot change a certificate. It can only be corrected by the accredited assessor who lodged it, or replaced by a new assessment. We can stop showing it while that happens.

Email privacy@epcchecker.uk with the address or the certificate number.

If you are unhappy with how we have handled your data, you can complain to the Information Commissioner’s Office at ico.org.uk.

Changes to this policy

If what we do with data changes, this page changes first, with a new date at the top.