- 4.53.690 (20/06/18)
- 4.52.680 (03/05/18)
- 4.51.670 (26/02/18)
- 4.49.650 (08/05/17)
- 4.48.640 (09/02/17)
- 4.47.630 (21/09/16)
- 4.46.620 (01/06/16)
- 4.45.610 (27/04/16)
- 4.44.600 (29/01/16)
- 4.43.590 (23/09/15)
- 4.42.580 (23/04/15)
- 4.40.560 (14/01/15)
- 4.39.550 (07/10/14)
- 4.39.540 (15/07/14)
- 4.39.530 (23/05/14)
- 4.39.520 (16/04/14)
Release notes 4.53.690
- IMPORTANT New fields added in order to adapt the software to the new Data Protection regulation (specifically, the EU's 2016/679 General Data Protection Regulation, also known as "GDPR"). These fields can be found in aGora's students, customers, staff and enquiries. We'll proceed to explain the new fields and their function:
Legal bases. This new field specifies the legal base that sets the boundaries the center must adhere to when dealing with the personal private data of the item. It is a dropdown menu with fixed values, which are as follows:
· Not applicable
· Legitimate interest
· Legal obligation
· Vital interest
· Public interest
Bear in mind that, in cases in which the Legal bases is set to Consent (showing the explicit consent given by the person the personal data belongs to), if the specified person has NOT accepted the privacy conditions (a field we explain later) should NOT have their personal data stored in the software.
Conditions-obtaining process' state. This field states, for persons which Legal bases field is Consent, the status of their acceptance of your company's privacy policies. Bear in mind these policies must be made known to the person which data will be stored in the software, and the process by which the policies are communicated and acceptance (or lack thereof) of said policies by the affected person is NOT automated by aGora in any way: the company must take the necessary steps to communicate the policies, receive the person's answer and transfer the result to aGora. There are three possible values to the field, each representing the different possible states of the person's acceptance of the privacy policies:
· Pending: The company has not contacted the person to ask for acceptance of its privacy policies.
· Sent: A petition for acceptance of the company's privacy policies has been sent to the person, but the person has not yet answered (neither yes nor no).
· Obtained: The person has answered the petition for acceptance of the company's privacy policies. Bear in mind that this only states that the person has answered the petition, NOT if the person has agreed/disagreed to the privacy policies (this will be covered in another field).
- NEW FEATURE Accept the privacy conditions. This field states if the person has agreed or not to the company's privacy policies. Please bear in mind that, if the person has NOT agreed, your company should not keep their personal data stored in our software, and should be eliminated. There are procedures in place to help you delete the personal data of a person even if said person is currently linked to other items in our software. We'll explain those procedures later.
The existing checkbox in aGora which allowed the person to state that he/she did not want to receive e-mails from your company has been changed for 4 new checkboxes, each one stating the willingness of the person to be contacted by your company in one of several means of communication (the checkboxes now state an explicit consent, rather than an explicit denial). The new checkboxes are:
· Allow to receive commercial e-mails: the person accepts that your company sends him/her e-mails with commercial purposes.
· Allow to be sent commercial text messages: the person accepts that your company sends him/her text messages (SMS, Whatsapp, Telegram or any other messaging app) with commercial purposes.
· Allow to receive commercial phone calls: the person accepts that your company calls him/her via telephone with commercial purposes.
· Allow to receive commercial information through social networks: the person accepts that your company sends him/her commercial information via several social networks (Twitter, Facebook, Instagram, etc.).
- NEW FEATURE Automated process to delete personal data. In order to help the company efficiently clean the personal data they cannot legally keep anymore, either by express petition of the related person or because of a legal obligation (for example, if the services the data was provided for are no longer active), we've implemented a new function to help delete said personal data, either on a person by person basis or for several persons at once (you will choose which persons have their data deleted). That function won't be triggered automatically, you must decide when to run the process. We also implement a different process that will delete all personal data of students/customers no longer linked to an active contract and for whom a specific time period has passed since their last contract ended. Finally, another different process will allow you to delete the personal data of students/customers who've never had an active contract in aGora (that's to say, they were created as potential students/customers, but never really purchased any of your services) for whom a specific period of time has passed since they were created in aGora.
- NEW FEATURE Automated processes to edit/import privacy data to aGora. A batch process has been added in order to make it easier for you to manage the acceptance of your privacy policies and the permissions for different methods of contact, which will allow you to import an Excel file storing the new information so it changes the existing persons' information in aGora. Another similar process will allow you to select one or several persons at once and set a specific field to a new value to all of them at once, without the need for an Excel file.