<commit_before><div class="row">
  <div class="col-sm-8 col-sm-offset-2">
    <h2>Respecting User Privacy</h2>
    <p>Updated: Oct 10, 2017</p>
    
    <p>CoughDrop is a powerful, flexible communication app and system that enables communicators 
    and the teams around them to develop a personalized language learning strategy and
    to communicate effectively. Because CoughDrop is used in medical and educational settings for
    adults and minors, we are sensitive to state and federal regulations like FERPA,
    HIPAA, COPPA, etc. and work hard to track policies related to those regulations.
    Compliance with privacy and security regulations requires collaboration
    between CoughDrop and the institutions that use our software. As such, we have 
    compiled this set of assurances and best practices to prevent exposing personal information
    to anyone who shouldn't have access to it.</p>
    
    <p>CoughDrop uses the cloud to back up, synchronize, and report on
    a communicator's vocabulary and activities. Because of the potentially sensitive nature
    of the information related to an individual's communication, we take user privacy very
    seriously. Below are some of our protection strategies, and best practices that you can
    follow to ensure the privacy and rights of the communicator are respected. The 
    information is provided to help organizations in their decision-making and
    training processes, and should be considered supplementary information, as it may
    change over time.</p>
    
    <h4>General Access</h4>
    <p>By default CoughDrop doesn't collect personal or academic information about our users.
    Access to CoughDrop is login-based, and every user must have a user name, email address,
    and password. However, the email address can be reused or even be invalid if needed.
    <b>We encourage therapy and educational teams who create logins on behalf of their
    users to use anonymized user names</b>, and many programs already have anonymized identifiers
    in place for the users they work with.</p>
    
    <h4>User-Generated Data</h4>
    <p>The CoughDrop application communicates with remote servers to download and update
    user-generated information such as board content, logs, etc. This communication is always
    done over a secure, encrypted (SSL) channel. In addition, user-generated 
    content such as buttons, email address, profile information
    and log data is encrypted before being stored to prevent unauthorized access. Within
    the system users can specify that their account is "public", in which case basic 
    user-entered information like summary, public boards, etc. will be available to
    any CoughDrop users, but this is an opt-in behavior. <b>We discourage communicator
    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 
    privacy best practices
    and are instructed to only access information needed for supporting communicators and
    teams. Within the app, access to user information is based on strict access controls,
    and any access to a communicator's information must be authorized by the communicator
    account. The only exception to this is if an organization creates communicator accounts
    and assigns them to communicators, in which case <b>we encourage organizations to make
    sure communicators are aware of and comfortable with the organization's access to their 
    information</b> before proceeding.</p>
    
    <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. 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>
    <p>In addition, communicators can add "supervisors" to their account. Supervisors are 
    additional logins that are tied to a different user, possibly a therapist, parent, teacher,
    grandparent, aide, etc. Supervisors can be added as read-only or with permission to edit
    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>
    <commit_msg>note on file uploads not encrypted at rest<commit_after><div class="row">
  <div class="col-sm-8 col-sm-offset-2">
    <h2>Respecting User Privacy</h2>
    <p>Updated: Dec 11, 2017</p>
    
    <p>CoughDrop is a powerful, flexible communication app and system that enables communicators 
    and the teams around them to develop a personalized language learning strategy and
    to communicate effectively. Because CoughDrop is used in medical and educational settings for
    adults and minors, we are sensitive to state and federal regulations like FERPA,
    HIPAA, COPPA, etc. and work hard to track policies related to those regulations.
    Compliance with privacy and security regulations requires collaboration
    between CoughDrop and the institutions that use our software. As such, we have 
    compiled this set of assurances and best practices to prevent exposing personal information
    to anyone who shouldn't have access to it.</p>
    
    <p>CoughDrop uses the cloud to back up, synchronize, and report on
    a communicator's vocabulary and activities. Because of the potentially sensitive nature
    of the information related to an individual's communication, we take user privacy very
    seriously. Below are some of our protection strategies, and best practices that you can
    follow to ensure the privacy and rights of the communicator are respected. The 
    information is provided to help organizations in their decision-making and
    training processes, and should be considered supplementary information, as it may
    change over time.</p>
    
    <h4>General Access</h4>
    <p>By default CoughDrop doesn't collect personal or academic information about our users.
    Access to CoughDrop is login-based, and every user must have a user name, email address,
    and password. However, the email address can be reused or even be invalid if needed.
    <b>We encourage therapy and educational teams who create logins on behalf of their
    users to use anonymized user names</b>, and many programs already have anonymized identifiers
    in place for the users they work with.</p>
    
    <h4>User-Generated Data</h4>
    <p>The CoughDrop application communicates with remote servers to download and update
    user-generated information such as board content, logs, etc. This communication is always
    done over a secure, encrypted (SSL) channel. In addition, user-generated 
    content such as buttons, email address, profile information
    and log data is encrypted before being stored to prevent unauthorized access. Within
    the system users can specify that their account is "public", in which case basic 
    user-entered information like summary, public boards, etc. will be available to
    any CoughDrop users, but this is an opt-in behavior. <b>We discourage communicator
    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 
    privacy best practices
    and are instructed to only access information needed for supporting communicators and
    teams. Within the app, access to user information is based on strict access controls,
    and any access to a communicator's information must be authorized by the communicator
    account. The only exception to this is if an organization creates communicator accounts
    and assigns them to communicators, in which case <b>we encourage organizations to make
    sure communicators are aware of and comfortable with the organization's access to their 
    information</b> before proceeding.</p>
    
    <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. 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>
    
    <p>It is important to note that user-uploaded files including images (including photographs),
    audio records and videos uploaded to the CoughDrop system
    are encrypted in transit via SSL, but are not encrypted at rest, and <b>we 
    recommend only uploaded anonymized images and
    videos that do not disclose private information</b>.</p>
    
    <h4>Logs, Reports and Tracking</h4>
    <p>In addition, communicators can add "supervisors" to their account. Supervisors are 
    additional logins that are tied to a different user, possibly a therapist, parent, teacher,
    grandparent, aide, etc. Supervisors can be added as read-only or with permission to edit
    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>
    
{'fraction_non_alphanumeric': 0.040177334441673596, 'fraction_numerical': 0.0029555740278932297, 'mean_word_length': 3.7784642541924094, 'pattern_counts': {'":': 0, '<': 77, '<?xml version=': 0, '>': 77, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1074497', 'n_tokens_mistral': 2557, 'n_tokens_neox': 2428, 'n_words': 1469}