If you believe that I have some how collected Personally Identifiable Information (Pii) about you and wish it to be removed, I am more than happy to please contact me at @lyndonjonmartin on Twitter.
If your Pii e.g. name, social handle e.t.c is found within a blog post on my personal blog, you will know that I have asked you personally to use your name, social post within my personal blog prior to its publication.
I do not make use of the built-in WordPress registration database feature e.g I do not allow anyone to register its DISABLED and therefor I do not process social handles, email address, mobile/telephone numbers e.t.c within the WordPress database that powers my personal blog. I disabled the WordPress registration database externally on day one when/how I started this personal blog so it only contains my own personal details to login write (draft) and post my blog articles.
This is a personal blog that does not generate any revenue e.g gain from economic activity (Its AD free) and its purely funded by Lyndon-Jon Martin personally on a monthly basis, since I started it with its core mission to provide knowledge to the world in a text based format freely in a clear and concise manner as best I can without all those annoying ads, widgets that slow down the loading of the web page.
In terms of media I utilise my own personal social handles where right vs. relevant to embedded content e.g videos, images e.t.c to help the readers of my blog posts better understand what I am aiming to articulate. Where I have included another individuals social post I have requested there personal consent to do so and its there personal choice to remove “embedded location data (EXIF GPS)” from content within there social posts.
This personal blog does make use of analytics*, which is utilised to better understand the following:
– Does this personal blog actually have an impact within the globally Workspace or EUC industry (e.g community knowledge sharing) otherwise I may as well not write any articles and close down this personal blog
– How busy is this personal blog by number of unique visitor including geographic e.g country
– What are the most popular blog articles so that I can focus on writing follow-up articles or amending existing articles with fresh content where right vs. relevant
– Any analytical data is collected, processed by WordPress plug-ins* and no automated profiling is used
We do not knowingly collect personally identifiable information from children or anyone under the age of 18. If you are a parent or guardian and you are aware that your Children has provided us with Personal Data, please contact us.
I don’t make use of the following:
– WordPress database to store Pii e.g registration database for users expect for myself for publication and administration purposes.
– Cookies (as I’m a web developer I personal DISLIKE them and always have its messy and mostly likely why the EU pushed for Pii compliance laws) only if WordPress uses them to improve the UX if they store Pii it should be on your computing device so delete your internet browsing history and they will be removed.
– Comments are disabled on my blog so no Pii anything that manages to get through the security filters in-place I delete
WordPress database which can be used to store Pii e.g registration database for users expect for myself for publication and administration purposes.
I personal DISLIKE them and always have its messy and mostly likely why the EU pushed for Pii compliance laws) only if WordPress uses them to improve the UX if they store Pii it should be on your computing device so delete your internet browsing history and they will be removed.
Web Forms & Comments
Comments are disabled on http://axendatacentre.com/blog/ so no Pii is collected in this way anything that manages to get through the security filters in-place is deleted.
The following named plug-ins listed below was accurate as of 24/06/2018.
– Centrora Security Badge
– Centrora Security
– WordPress Importer
– Simple Backup
– Duo Two-Factor Authentication
– Complete Central Backup
– WordPress.com Stats
– W3 Total Cache
– WassUp Real Time Analytics
– WP Database Cleaner
Process & Procedure: Right to be forgotten
1. I will respond within 30 business days of receiving and having viewed your inital request. Why? I maybe on holiday or in a country with no access to the internet.
2. Contact me directly via my Twitter handle at https://twitter.com/lyndonjonmartin/ by requesting me to follow you and Direct Mailing (DM) me.
3. I will then provide you with an email address to provide your request in writing or if you prefer in my Twitter inbox (DM) its your choice.
4. I will work with you to establish any Pii and have it removed, within an agreed time frame that we agree upon and if required I may have to pass a Pii removal request to a 3rd party e.g WordPress Plug-In you will be notified about this and again I will work with you.
5. Once your Pii is deleted/removed we will need to agree if we delete all related communication(s) in any/all digital footprints again this is your choice.
Process & Procedure: Data, Secuirty Breach Prevention
1. Any breaches e.g untrusted including unknown access to the WordPress administrative area or the private key to the certificate that protects the administrative area will be published under the “Data Breach Report”
2. WordPress is consistently on a regular basis including any/all plug-ins and template to ensure that http://axendatacentre.com/blog/ is running the latest stable version as recommended by WordPress or https://wordpress.org.
3. WordPress settings have been optimised to harden this personal blog as best as possible and are reviewed on a 3 month cadence.
4. WordPress Administrative login access only utilises HTTPS connections to avoid any untrusted access to the Administrator area of the blog. The certificate expires and is renewed every 12 months and if the private key is found to be breached it will be re-generated along and a new certificate bound to HTTPS interface.
Process & Procedure: Data, Security Breach Report
The following outlines an example of how http://axendatacentre.com/blog/ will report any data, security breaches.
Date + Time: 25 May 2018 00:01
Breach Type: Private Key
Overview: The private key for the certificate that protects the WordPress administrative area was access by a trusted but 3rd party.
Resolution: We have revoked the existing private key and public signed certificate and re-issued both and unbound and bound the new certificate to the HTTPS interface.
Data, security breaches will be published as blog articles for clear transparency to readers of the http://axendatacentre.com/blog/ blog.