deploy: 6214d36

Author: aterrel

07_code_of_conduct.html

@@ -647,7 +647,6 @@ <h2>Enforcement<a class="headerlink" href="#enforcement" title="Link to this hea
 <ul class="simple">
 <li><p>Be clear on how long it will take to resolve the situation or take an action on the violation</p></li>
 <li><p>Discuss in advance with the organizing committee what the specific process will be for recording and addressing a CoC violation</p></li>
-<li><p>When recording a CoC violation, ensure that the data are stored securely and that everyone’s identities are protected. Access to the data should be limited.</p></li>
 <li><p>When possible, have a third party review the violation report (Another good way to handle the challenge of potential reports against authority figures.)</p></li>
 <li><p>Ensure the person who made the CoC violation report is aware of how it is being handled and when it has been resolved.</p></li>
 </ul>

_sources/07_code_of_conduct.md

@@ -59,7 +59,6 @@ Make sure that **everyone involved in your conference/event** is aware that the
 
 - Be clear on how long it will take to resolve the situation or take an action on the violation
 - Discuss in advance with the organizing committee what the specific process will be for recording and addressing a CoC violation
-- When recording a CoC violation, ensure that the data are stored securely and that everyone's identities are protected. Access to the data should be limited.
 - When possible, have a third party review the violation report (Another good way to handle the challenge of potential reports against authority figures.)
 - Ensure the person who made the CoC violation report is aware of how it is being handled and when it has been resolved.