Privacy policy

This policy outlines what personal data may be collected and what may be done with it when you visit my blog.

By accessing or browsing my blog, you confirm that you have read and understood this privacy policy in its entirety. Please check back regularly to keep informed of updates to this privacy policy.

Who I am

I am Kaydee Web Ltd also known as KaydeeWeb, Kaydee Web or Kaydee Web Design.

My blog address is:

I trade as a limited company registered in England and Wales with company number: 10382600.

Registered address is: 2 Hinksey Court, Church Way, Oxford OX2 9SX.

What personal data I collect and why I collect it

During the use of my blog you may provide me with, or I may collect, some or all of the following information about yourself:

  • Your name
  • Email address
  • Postal address
  • Phone number
  • Age
  • Gender
  • IP address

Contact forms

If you submit a contact form on my blog, I will record the information you submit in the form, as well as your IP address.


This site uses cookies to improve user experience. The cookies do not contain any personal data.


I use Google Analytics to enable me to anonymously monitor user behaviour, for the purpose of improving my blog and it’s user experience. Google Analytics will set it’s own cookies to facilitate this.

You can control the information Google associates with your web activity (in Google’s words you can “opt-out of Google Analytics for Display Advertising and customize Google Display Network ads”) using the Google Ads Settings.

You can also use the Google Analytics opt-out browser add-on.


When visitors leave comments on the site I collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.

An anonymised string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: After approval of your comment, your profile picture is visible to the public in the context of your comment.

Who I share your data with

I do not share your data with anybody outside my company.

How long I retain your data

If you have simply visited my blog, only your anonymous visitor data will have been stored in my web server log files, and in my Google Analytics account. My server log files are purged after a maximum of 6 months.

If you have submitted a contact form, I will store your data for as long as there is a valid business relationship with you. Communications that are terminated will be deleted within a maximum of 12 months.

What rights you have over your data

You can request that I delete any personal data I hold about you. This does not include any data I are obliged to keep for administrative, legal, or security purposes.

To request removal of your data, please email [email protected] with your name and email address so I may identify you correctly. I will remove all of your personal data from my systems within 5 working days.

Where I send your data

Your data may be stored on my own company local file systems, cloud storage, or backup systems.

Your contact information

For any queries about this policy or any other topics, please contact me on [email protected]. I will endeavour to respond to all enquiries with 3 working days.

Additional information

How I protect your data

The blog is served over a secure connection using the HTTPS protocol (identified by the padlock icon in the address bar). This means all communication between your browser and my web server is encrypted.

I also serve the site from a fully updated and secured web server, which is located in a secure data centre.

What data breach procedures I have in place

If there is a data breach of this blog, and I can identify that your personal information has been compromised, I will inform you within 24 hours of identifying your data is involved (which may be more than 24 hours from discovering that there has been a data breach).

What third parties I receive data from

I do not receive data from any third parties.

Changes To This Policy

I  will update this policy if my procedures change. The last update to this policy was 22nd May 2018.