In order to provide my visitors with a more pertinent (i.e. legible) overview of the evolution of my web statistics since the enactment of the GDPR on 2018-05-25 (1), which occurred at the same time as my request for clarification of declarative situation reached its litigation phase, I enriched the present website with a Statfolio section (2), which - though password-protected - will remain accessible in demo mode until the launch of my CMS-focused production phase (hence the background image of the login page, which suggests a future "VPN+" solution entirely dedicated to the master-securement of my global web construction site [3]).

The time has come to reconsider the problem solving cycle from the perspective of the web statistics available for the period of reference 2013-2018 (my publication phase 2/3), on the grounds of the raw statistics logged by OVH’s web servers for interpretation by the Urchin-v6-enabled analytics tool included in the provider’s shared web hosting plans. Let us start with a brief historical introduction, for the sake of gaining a better insight into the underlying issues (1, 2):

How to preserve data integrity at each new step of the value chain without compromising the web content production process in part or in whole? Did you ever wonder why our systems are still failing us, despite the many dedicated users who actively participate in the internet’s countless support forums (1)? This GDPR-focused audit closure report frames the answer to such questions, from the perspective of the meta-convergence of workflows and feeds (2). Let us start with the usual flowchart matrix.