Body: <p>Under templates_c, a lot of .php files are being created that contain things like the following:</p>
  
  <pre><code>&lt;?php /* Smarty version 2.6.30, created on 2018-04-27 00:20:41
           compiled from string:REDACTED */ ?&gt;
  &lt;?php require_once(SMARTY_CORE_DIR . 'core.load_plugins.php');
  smarty_core_load_plugins(array('plugins' =&gt; array(array('block', 'crmScope', 'string:REDACTED', 1, false),)), $this); ?&gt;
  &lt;?php $this-&gt;_tag_stack[] = array('crmScope', array('extensionKey' =&gt; "")); $_block_repeat=true;smarty_block_crmScope($this-&gt;_tag_stack[count($this-&gt;_tag_stack)-1][1], null, $this, $_block_repeat);while ($_block_repeat) { ob_start(); ?&gt;string:REDACTED&lt;?php $_block_content = ob_get_contents(); ob_end_clean(); $_block_repeat=false;echo smarty_block_crmScope($this-&gt;_tag_stack[count($this-&gt;_tag_stack)-1][1], $_block_content, $this, $_block_repeat); }  array_pop($this-&gt;_tag_stack); ?&gt;
  &lt;br/&gt;
  </code></pre>
  
  <p>The problem is that the file names contain the names of contacts. Under GDPR, these need to be deleted.</p>
  
  <p>Can we change the name to be the ID instead?</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-04-27T10:06:54.943Z
Comments.Text: a) What part of GDPR implies this? b) You can delete everything under templates_c and it will be rebuilt as needed
Comments.UserDisplayName: Aidan
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-04-27T17:17:56.230Z
Comments.Text: Right to erasure. If someone requests that we delete all data we hold on them, for there to be a thing on our system, cached or otherwise, that contains their name, could be portrayed as not fully respecting that right.
Comments.UserDisplayName: JohnFF
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-04-30T20:51:01.537Z
Comments.Text: Hi John - aren't these temporary files which are removed when you clear caches?
Comments.UserDisplayName: Parvez Saleh
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2018-05-01T13:19:26.067Z
Comments.Text: Yes. But I still don't see how more privacy is ever a bad thing. Also, I can imagine instances where these may be around longer than necessary: backups, clones, misconfigured server not being able to delete them, so on.
Comments.UserDisplayName: JohnFF
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-10T17:56:58.427Z
Comments.Text: @JohnFF someone's name alone is not personal data within the scope of the GDPR if the information contained in a cached template is enough to identify the individual it would be within scope for GDPR and the Right to Erasure but that seems unlikely.
Comments.UserDisplayName: HomoTechsual
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-22T11:09:14.473Z
Comments.Text: @JohnFF how would changing the name to the ID being different? Both could be traced back to a person.
Comments.UserDisplayName: Jaap Jansma - CiviCooP
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2018-05-23T11:34:21.157Z
Comments.Text: Hi Jaap, 
  
  Because you can redact / pseudonymise the name and then you aren't left with it elsewhere.
Comments.UserDisplayName: JohnFF
Tags: <cache>
Title: GDPR: How to stop smarty cache entries containing contact name being created?
ThreadText: # GDPR: How to stop smarty cache entries containing contact name being created?
  
  (Asked by: username_0 on 2018-04-26)
  
  Under templates_c, a lot of .php files are being created that contain things like the following:
  
   array(array('block', 'crmScope', 'string:REDACTED', 1, false),)), $this); ?>
  _tag_stack[] = array('crmScope', array('extensionKey' => "")); $_block_repeat=true;smarty_block_crmScope($this->_tag_stack[count($this->_tag_stack)-1][1], null, $this, $_block_repeat);while ($_block_repeat) { ob_start(); ?>string:REDACTED_tag_stack[count($this->_tag_stack)-1][1], $_block_content, $this, $_block_repeat); }  array_pop($this->_tag_stack); ?>
  
  
  The problem is that the file names contain the names of contacts. Under GDPR, these need to be deleted.
  Can we change the name to be the ID instead?
  
  **Tags:** cache
  
  > **Comments:**
  > **username_1**: a) What part of GDPR implies this? b) You can delete everything under templates_c and it will be rebuilt as needed  
  > **username_0**: Right to erasure. If someone requests that we delete all data we hold on them, for there to be a thing on our system, cached or otherwise, that contains their name, could be portrayed as not fully respecting that right.  
  > **username_2**: Hi John - aren't these temporary files which are removed when you clear caches?  
  > **username_0**: Yes. But I still don't see how more privacy is ever a bad thing. Also, I can imagine instances where these may be around longer than necessary: backups, clones, misconfigured server not being able to delete them, so on.  
  > **username_3**: @username_0 someone's name alone is not personal data within the scope of the GDPR if the information contained in a cached template is enough to identify the individual it would be within scope for GDPR and the Right to Erasure but that seems unlikely.  
  > **username_4**: @username_0 how would changing the name to the ID being different? Both could be traced back to a person.  
  > **username_0**: Hi Jaap,   Because you can redact / pseudonymise the name and then you aren't left with it elsewhere.  
  
  ---
  
  ## 0 answers
  
  