Info Section - On Updating Policy's (#34)

This extra info is in regards to Issue: #32

partials/_overall_info.htm

@@ -98,12 +98,14 @@ <h2>Table of Contents:</h2>
       <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr62">Dismiss</a></li>
       <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr63">Show</a></li>
       <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr64">Our Plugins Banner as per the Requirements</a></li>
+      <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr65">How to pass the Law when adding new scripts, modules or cookies to the backend list</a></li>
+      <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr66">Updating a Privacy Policy, Cookie Policy etc.</a></li>
 	</ul>
-  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr65">Website Checklist for GDPR and ePrivacy</a></li>
-  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr66">Phase 1: Need to understand</a></li>
-  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr67">Phase 2: Assess Risk</a></li>
-  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr68">Phase 3: Mitigate Risk - Implement</a></li>
-  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr69">Phase 4: Demonstrate</a></li>             
+  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr67">Website Checklist for GDPR and ePrivacy</a></li>
+  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr68">Phase 1: Need to understand</a></li>
+  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr69">Phase 2: Assess Risk</a></li>
+  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr70">Phase 3: Mitigate Risk - Implement</a></li>
+  <li><a role="link" href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr71">Phase 4: Demonstrate</a></li>             
 </ol>
 
 
@@ -770,11 +772,43 @@ <h3 id="gdpr64">Our Plugins Banner as per the Requirements</h3>
 <figure><p><img role="img" style="max-width: 947px;" src="../../../../../../plugins/offline/gdpr/assets/images/gdpr-eprivacy-2.png" alt="cookie banner" width="947" height="165"></p></figure>
 
 
-<h2 id="gdpr65">Website Checklist for GDPR and ePrivacy</h2>
+<h3 id="gdpr65">How to pass the Law when adding new scripts, modules or cookies to the backend list</h3>
+
+<p>When adding New Scripts, Modules or New Cookies to your Admin Control Panel Back-end.</p>
+
+<blockquote><p>You do NOT need to re-show the Banner to Users again who have already given consent previously!</p></blockquote>
+
+<p>We recommend creating a link in the footer linking directly to the &quot;<strong>Advanced Settings</strong>&quot; webpage - as described in the above Section Titled <a href="<?= Backend::url('offline/gdpr/info/overallinfo') ?>#gdpr63">Show</a>.</p>
+
+<p>The Reason for NOT re-showing the Banner would be because it's very annoying to the User-Experience and not necessary with regards to ePrivacy and GDPR Laws! Also the user process flow would be like this: A User would not edit the &quot;New Options&quot; in the Banner! They would edit the &quot;New Options&quot; from the chosen &quot;<strong>Advanced Settings</strong>&quot; webpage options. Therefore there is no point in re-showing the Banner for a second time after the initial consent has been given! To fully pass the Law just create a permanent link in the footer linking directly to the &quot;<strong>Advanced Settings</strong>&quot; options webpage.</p>
+
+
+<h3 id="gdpr66">Updating a Privacy Policy, Cookie Policy etc.</h3>
+
+<p>When adding new scripts, modules or cookies to the back-end you will be changing the Privacy Policy or Cookie Policy etc. You will need to do an extra thing to pass the Law.</p>
+
+<blockquote><p>To keep User's informed to any updates or changes made to your Policies you should either Date them and/or also have them archived.</p></blockquote>
+
+
+<h4>Archived Example:</h4>
+
+<p>Below is an example of Archiving all the Policies:</p>
+
+<figure><p><img role="img" style="max-width: 806px" src="../../../../../../plugins/offline/gdpr/assets/images/archived.png" alt="Archived Example" width="806" height="518"></p></figure>
+
+
+<h4>Dated Policy Update Example:</h4>
+
+<p>Below is an example of Dated Policy Update:</p>
+
+<figure><p><img role="img" style="max-width: 423px" src="../../../../../../plugins/offline/gdpr/assets/images/updated.png" alt="Dated Policy Update" width="423" height="137"></p></figure>
+
+
+<h2 id="gdpr67">Website Checklist for GDPR and ePrivacy</h2>
 
 <p>Below is a Checklist for OctoberCMS Users and Developers to Follow:</p>
 
-<h3 id="gdpr66">Phase 1: Need to understand</h3>
+<h3 id="gdpr68">Phase 1: Need to understand</h3>
 
 <ul>
   <li><p>What personal data and sensitive data we collect/hold?</p></li>
@@ -790,7 +824,7 @@ <h3 id="gdpr66">Phase 1: Need to understand</h3>
 </ul>
 
 
-<h3 id="gdpr67">Phase 2: Assess Risk</h3>
+<h3 id="gdpr69">Phase 2: Assess Risk</h3>
 
 <ul>
   <li><p>How much is personal data?</p></li>
@@ -805,7 +839,7 @@ <h3 id="gdpr67">Phase 2: Assess Risk</h3>
 </ul>
 
 
-<h3 id="gdpr68">Phase 3: Mitigate Risk - Implement</h3>
+<h3 id="gdpr70">Phase 3: Mitigate Risk - Implement</h3>
 
 <h4>Data Breach</h4>
 
@@ -915,7 +949,7 @@ <h4>Change Management</h4>
 </ul>
 
 
-<h3 id="gdpr69">Phase 4: Demonstrate</h3>
+<h3 id="gdpr71">Phase 4: Demonstrate</h3>
 
 <ul>
   <li><p>Can we demonstrate:</p></li>