This information gives details of the management of data security in relation to the use of Groupcall Messenger v5. Schools may wish to use this with their fair use policy.
|School hosted MIS products data extraction Show details
In the case of school-hosted MIS products the information is extracted from the school Management Information System (MIS) using Groupcall’s Xporter software. The data is securely uploaded to Groupcall Messenger v5 using industry standard SSL encryption. A unique identifier configured in Groupcall Xporter ensures that the information is linked to the correct customer account. Groupcall Xporter accesses the school MIS system using credentials that you provide and cannot access it without them.
|Cloud hosted MIS products data extraction Show details
In the case of a cloud-hosted MIS product the information is extracted from the school Management Information System (MIS) securely via a cloud-to-cloud transfer. This is initiated by Messenger v5, using industry standard SSL encryption. Groupcall Xporter is not used in this configuration; the communication is directly between Messenger v5 and your MIS provider. The credentials you provide to authenticate Messenger v5 to your MIS are stored in Messenger v5 and the information cannot be retrieved from your MIS without them. In addition, if you revoke third party access through your MIS then Messenger v5 will no longer be able to retrieve information from it.
The information from your school is held inside the Messenger v5 web platform, which is hosted in Microsoft’s Azure platform in the Europe North territory. You can find out more about the security and safety policies that affect your data in more detail in the Messenger v5 Data Security Summary document. In summary, the data in Azure is protected from exposure by multiple layers of firewalling, authentication and physical access control.
When authorised users send messages to people using Messenger v5 those messages will pass through one or more of our partner organisations, for routing and delivery. While awaiting delivery, these messages will be queued at one or more of our partner organisations. This applies to Text (SMS) messages, Voice messages and Emails. All reasonable efforts are made to protect these messages, in transit and while queuing, however the same risks apply in the case of sending your own SMS, Voice or Email messages because the same delivery network is used. Your organisation policies should provide further guidance over what is suitable to send over such mediums.
When authorised users send broadcast messages such as those to Twitter, you must enter your Twitter credentials into Messenger v5. Messenger v5 then uses industry standard integration to link into Twitter and post messages. Please note that such broadcast posts could be seen by anyone.