anchor.diff:      <p>Because communication is personal and individualized, many communicators add buttons
       representing personal information, such as family members, medical details, addresses, 
       etc. The system does not prevent this type of information from being added, but it is
  -    not required. <b>Support teams should talk with communicators before adding potentially
  -    sensitive information to their boards, as this information could technically be discovered
  +    not required. Such user-generated data will be encrypted, but is still available once
  +    logged in. <b>Support teams should talk with communicators before adding potentially
  +    sensitive information to their boards, and should remember that this information could 
  +    technically be discovered
       by anyone with physical access to the communicator's device.</b></p>
       
       <h4>Logs, Reports and Tracking</h4>
  
positive.code:     a communicator's boards. All supervisors have access to a communicator's full vocabulary
      set and any logs that have been recorded. As such, <b>we encourage support teams to 
      check with communicators before adding anyone as a supervisor to their account on their
      behalf.</b>.</p>
      
      <p>CoughDrop has a built-in logging and reporting mechanism that can provide valuable insights
      and summaries of communication usage and progress over time. Data can be a powerful
  
negative.code:     accounts from being set to public.</b> The 
      user name tied to each account is not encrypted, and without authorization another
      CoughDrop user can check on the existence of a specific user name, but will not be 
      able to retrieve any additional non-public information about that user name. This is another 
      reason why we encourage teams to use anonymized user names when creating accounts
      for their communicators.
      
      <p>All CoughDrop employees with potential access to personal data are trained on user 
  