Privacy

Privacy Policy

Last updated 20 August 2026

In short

This website does not collect personal data about you. It sets no cookies, runs no analytics, loads nothing from anyone else's server and contains no forms.

There is one thing we cannot switch off, and we would rather name it than hide it: the servers that deliver this page log the IP address of every visitor for security purposes. That happens at our hosting provider, before anything reaches us. The rest of this policy explains that, and what happens if you write to us.

This policy covers mibeva.com only. Our products have their own privacy policies, published with the product.

Controller

The controller for the processing described here, within the meaning of the UK GDPR and Article 4 (7) of the EU GDPR, is:

Controller
MIBEVA LTD
Company number
17404533
Registered office
124-128 City Road
London EC1V 2NX
England

MIBEVA LTD has not appointed a data protection officer, as it is not required to under Article 37 of the UK GDPR. Data protection enquiries go to the address above and are handled by the director.

What this site does not do

This is a static website: a handful of HTML and CSS files served as they are written. Specifically, it does not:

  • set cookies of any kind, which is why there is no cookie banner
  • write to local storage, session storage or any other browser storage
  • run JavaScript
  • use analytics, statistics, heat-mapping or A/B testing of any kind
  • embed tracking pixels, beacons or advertising tags
  • load fonts, scripts, stylesheets, images, videos or maps from third parties — typography uses the fonts already on your device
  • contain forms, newsletter sign-ups, comments, logins or user accounts
  • profile visitors or make automated decisions about anyone, including profiling within the meaning of Article 22 of the UK GDPR
  • share, sell or transfer visitor data to advertisers or data brokers

Hosting and server logs

mibeva.com is hosted on GitHub Pages, a service of GitHub, Inc., 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA.

When your browser requests a page, that request necessarily reaches GitHub's servers and carries technical data with it, including your IP address, the time of the request, the page requested, and the user agent and referrer your browser sends. GitHub states in its documentation on GitHub Pages that a visitor's IP address is logged and stored for security purposes, whether or not the visitor is signed in to GitHub.

These logs sit with GitHub. MIBEVA LTD has no access to them, receives no reports derived from them and cannot turn the logging off. We therefore cannot identify individual visitors to this site.

The legal basis is our legitimate interest in delivering this website reliably and defending it against attack, under Article 6 (1) (f) of the UK GDPR and of the EU GDPR. Our legitimate interest is operating a website at all; the processing is limited to what is technically required to do that.

Because GitHub, Inc. is based in the United States, this processing involves a transfer of data outside the United Kingdom and the EEA. GitHub sets out the safeguards it applies, including standard contractual clauses, in its own privacy statement: GitHub General Privacy Statement. Its statement on GitHub Pages data collection is published at docs.github.com.

If you email us

The only way to contact us through this site is the admin@mibeva.com link. We deliberately use a plain email address instead of a contact form, so that no data passes through this website at all.

If you write to us, we receive whatever your message contains: your email address, your name if you give it, and the content itself. We use it to answer you and to deal with the matter you raised, and for nothing else.

Our mailbox runs on Google Workspace, a service of Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Google carries and stores the message on our behalf as our processor within the meaning of Article 28 of the UK GDPR, under the Google Workspace Data Processing Addendum, and may process it on servers outside the United Kingdom and the EEA. Google applies standard contractual clauses to those transfers. Google does not use the content of our mailbox for advertising.

The legal basis is Article 6 (1) (b) of the UK GDPR where your message concerns a contract or steps taken before entering one, and otherwise Article 6 (1) (f), our legitimate interest in answering enquiries addressed to us.

We keep correspondence for as long as it takes to deal with the matter and for any period we are required to keep business correspondence under UK company and tax law. After that it is deleted.

Links to other sites

This site links out to other websites, including getpeakfy.com. Following a link takes you to a site we do not control from a privacy point of view, and this policy stops at that point. The site you land on has its own privacy policy, which is the one that applies there. No data is passed to those sites unless you click the link yourself.

Your rights

Under the UK GDPR and the EU GDPR you have the right to:

  • ask whether we process personal data about you, and to receive a copy of it (Article 15)
  • have inaccurate data corrected (Article 16)
  • have data erased (Article 17)
  • have processing restricted (Article 18)
  • receive your data in a portable format (Article 20)
  • object to processing based on legitimate interest (Article 21)

Write to admin@mibeva.com to exercise any of these. We answer within one month. Exercising these rights costs you nothing.

In practice, unless you have written to us, we hold no personal data about you at all, and a request will get that answer.

Complaints

If you believe we have handled your data improperly, you can complain to a supervisory authority. Our lead authority is the Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire SK9 5AF, United Kingdom — ico.org.uk.

If you are in the EEA, you may instead complain to the supervisory authority in the country where you live or work.

Changes

If this website changes in a way that affects privacy — and adding anything that loads from a third party would count — this policy is updated before the change goes live, and the date at the top changes with it. There is no mailing list to notify, by design.