We’ve made a range of new improvements to The HiVE, including updates to subscriber list permissions, results data and privacy improvements. These updates are part of good housekeeping around privacy and ensuring data collected is consistent across tools.

person on laptop

IP address masking

IP addresses are captured by The HiVE when a user submits their feedback and are displayed in the Results section of reporting and in the data exported from the system. To provide further protection of personal information in The HiVE, IP addresses will now be obscured or masked in the results data.

A hashing algorithm (specifically adler32 and crc32b in combination with a salt) will now be applied to mask the actual value of all IP addresses displayed in the HiVE.

This will result in a new 16 digit number for all IP addresses displayed in the feedback data. For example, a ‘raw’ IP address of 192.168.1.1 will be converted to a new value of ‘062c02153610a686’.

The change will allow IP addresses to be de-identified to protect privacy, while still allowing you to recognise patterns such as contributions coming from the same device. It should also be noted that the IP address will still be retained in its raw form within the database.

Unique contribution IDs

Each time a participant makes a contribution to the platform, that contribution is assigned a unique identification number for reference. Currently, the ID number given to a contribution is unique to each of the feedback tool types, but not unique with the system.

To ensure a more robust contribution management system, unique ID numbers for all contributions in the system will be assigned. This change will result in existing contribution ID numbers from all previous contributions being reassigned a new unique ID number.

Member status data

The ‘Member Status’ data displayed in the feedback results has been updated to address inconsistencies between the way values were expressed across each of the feedback tools.

The new values will be as follows:

  • Active - Participant is an active Member
  • Inactive - Participant is Member, but their account has been deactivated
  • Empty - Participant is a non-Member

Member IP Address removal

The Member IP Address field has been removed from the export of the feedback results data as it is unnecessary for analysis.

Username and email data

A new ‘Member Username’ and ‘Member Email’ field has been added to the results data to make it clearer as to whether data has been collected through the feedback activity (via the member attributes system) or the user registration process. Previously, this information was shown in the same field in some cases, causing confusion as to how this data was captured.

Additionally, if the Username and Email fields are not enabled through the member attribute system of a specific feedback tool, these fields will not appear in the feedback results.

Results data reorganisation

To provide a more logical grouping of data in the feedback results data, data fields have been reordered to make a clearer distinction between data collected from the activity itself and data collected through the user registration process.

The new order of the fields in the feedback results data table will be:

  • Contribution ID
  • Date Submitted
  • Screen Name (if collected)
  • Email (if collected)
  • Member Username
  • Member Email
  • Contribution data (different per tool)
  • Additional member attribute questions
  • IP Address
  • Moderation Status (if applicable)

The new order of the fields in the feedback results export will be:

  • Contribution ID
  • Data Submitted
  • Screen Name (if collected)
  • Email (if collected)
  • Contribution data (different per tool)
  • Additional member attribute questions
  • IP Address
  • Moderation Status (if applicable)
  • Member Status
  • Member ID
  • Member Username
  • Member Email
  • Member Postcode
  • Member Gender
  • Member Age Group

Subscriber list permissions

The Subscribe block can be used to contact or connect with the community to keep them informed of a project or update them on future opportunities to participate.

Currently, any Site Users can view all internal lists created through the Subscribe block within the system potentially giving them access to the personal information (such as first name and last name) of participants who are not related to their projects.

To better protect the privacy of subscriber data, new permissions will be applied to ensure subscriber lists can only be accessed in the Dashboard by Site Users associated with the project. Additionally, when a Site User adds a new Subscribe block to a page, they will only be able to select a subscriber list belonging to projects they have been given access to.