Terms, Policies & Agreements
These terms & policies explain our legal relationship with you.
General Data Protection Regulation (GDPR)
The General Data Protection Regulation, known as GDPR, went into effect on May 25, 2018. It is the most sweeping legislation in the last two decades focused on data security and privacy, and significantly updates, extends, and harmonises data protection legislation across the EU/EEA.
To read more about GDPR, please click here.
ManageBac has been committed to data privacy for over 10 years and welcomes the new regulation. ManageBac has been GDPR compliant since May 2018.
1. Who is subject to GDPR?
1.1 Individuals, organisations and companies that control or process personal data are subject to GDPR. In broad terms, there are three different actors:
(i) Data subjects (students, families, school employees)
(ii) Data controllers (the school)
(iii) Data processors (systems like ManageBac)
1.2 As a data processor, we do not decide the purpose or lawfulness of the data we process and store. We are trustees acting on our customers’ behalf. As data controllers, schools remain ultimately responsible for documenting and deciding how data enters our systems.
1.3 GDPR regulations do impose new and stricter regulations on processors. We will fully comply with these requirements for all of our services, including ManageBac, and Integration partners.
2. How is GDPR different from previous data protection laws?
Key areas of difference center on increased accountability for companies, greater access to personal data for individuals, and higher penalties for non-compliance.
2.1 GDPR explicitly lays out key rights of data subjects:
(i) right to be informed
(ii) right of rectification
(iii) right of erasure
(iv) right to restrict processing
(v) right of data portability
(vi) right to object
(vii) right of access
2.2 These rights form the framework for interactions between the data subject, controller, and processor. While the controller (school) remains responsible for respecting these rights, the processor (us) may assist in accomplishing these tasks.
2.3 The penalties for non-compliance are not insubstantial. A school found in violation of GDPR may be assessed fines worth up to 4% of total annual revenue.
2.4 The Information Commissioner’s Office (ICO) is responsible for enforcing GDPR and has a broad range of powers to do so.
3. What kind of data is covered, and what information are schools allowed to collect?
3.1 All personal data concerning an individual (data subject) is included under GDPR.
3.2 Specifically, personal data that allows an individual to be identified — for example name, address, phone number, photo, etc. — is included under GDPR.
3.3 Even if personal data has been encrypted, pseudonymised, or anonymized, it may still fall under the scope of GDPR if the data can still be used to identify a specific individual.
3.4 Examples of personal data that our schools collect and store includes:
(iii) E-mail Addresses
(iv) Phone Numbers
(v) ID Numbers (passport, national ID, SSN)
3.5 GDPR specifies six lawful bases for collecting personal data:
(ii) Written contract
(iii) Legal obligation
(iv) Vital interests
(v) Public tasks
(vi) Legitimate interests
3.6 For most schools, the legal basis for data collection relates to either legal obligations as learning institutions, or to legitimate interests.
3.7 Most of the bases require that the data processing is necessary, i.e. if you can reasonably achieve the same results and purpose without processing data, then you do not have a lawful basis.
4. Is ManageBac GDPR-compliant?
4.1 Yes. ManageBac has been designed from the start with personal data protection in mind, and we pride ourselves on offering schools, students, and parents the highest level of security.
4.2 We have spent the lead up to May 2018 analysing the new requirements and making changes in our services and internal workflows.
4.3 As a part of our commitment to GDPR, ManageBac will:
(i) Ensure organisational and technical security for all services.
(ii) Assist with documentation to demonstrate compliance and keep users informed.
(iii) Provide contract addendum that comply with GDPR requirements for Data Processing Agreements (DPA)
(iv) Offer support when your users exercise their data subject rights.
5. How does my school become GDPR-compliant?
5.1 We cannot directly advise our schools on GDPR compliance, aside from recommending that you seek legal advice as soon as possible, and appoint a team to begin reviewing your current data processing practices.
5.2 Most of our schools in Europe will be required to appoint a Data Protection Officer (DPO), who oversees your compliance requirements and reports directly to senior management.
5.3 GDPR requires you to explicitly record and evaluate how personal data is processed and used. At a minimum, you will need to fully review user data end-to-end, justify why you hold it (using one of the legal bases), for how long you will retain it, and conduct a security review. The purpose of every data point you hold must be defined.
5.4 When adopting new technology platforms that involve personal data, you will need to perform a Data Protection Impact Assessment (DPIA). You are expected to monitor and ensure that the systems you use are GDPR compliant.
5.5 Individual rights have been strengthened under GDPR, we strongly recommend making your users aware of their rights, and establishing clear procedures for responding when users exercise those rights.
6. I have heard that ManageBac is not secure enough under GDPR! Is this true?
6.1 GDPR does not specify precise security requirements for cloud-based services.
6.2 As a data processor, we have a shared responsibility with our schools (controllers) to provide appropriate organisational and technical security, and be able to demonstrate it.
6.3 GDPR strengthens the liabilities and penalties for companies that are unable to demonstrate those security protocols.
6.4 For over a decade, ManageBac has successfully protected data from millions of users. We continue to invest in organisational security, network and infrastructure security, and application security to ensure we can offer world-class security beyond standard requirements. We regularly allow third parties to audit our security measures, and we invite customers to perform their own audits.
6.5 We are careful not to provide explicit detail about our security measures but our standard protocols include:
(i) Application security: traffic encryption, strongly hashed passwords, safeguards against vulnerabilities such as cross site scripting, SQL injections, phishing and others.
(ii) Network security: firewalls and systems to detect suspicious behaviour, stop malicious attempts to gain access, or compromise the resilience of the service (e.g. DDOS attacks).
(iii) Organisational security: access policies, audit logs and confidentiality agreements.
(iv) Physical security: preventing unauthorized access to infrastructure processing personal data.
(v) Procedural security: IT management processes to minimize the risk of human errors, or testing regimes to identify software weaknesses before releasing new features to our cloud services, or policies to ensure data is only processed on instruction from our customers.
7. How does ManageBac obtain personal data about users, and how is it used?
7.1 User data is submitted to our platforms in three ways:
(i) directly by the users
(ii) by representatives authorised by the users (e.g. the school technology director obtains data and then uploads it to our platform)
(iii) via an integration with a third-party system
7.2 Data typically enters our systems via “student information systems” independently maintained and controlled by our customer schools.
7.3 We import data from third-party systems only under direct instruction from our customers.
7.4 We use personal data under our protection only when we receive direct instructions from the customer.
7.5 The data stored on our systems belongs directly to our customers, and only a handful of ManageBac staff have access to personal data under strict confidentiality and security.
7.6 We process personal data independently only if it is vital to the integrity or security of the service, or to analyze or evaluate the quality of the service provided.
8. Can any of our users request data deletion under the “right to be forgotten”?
8.1 Likely not. A data deletion request is valid only if the lawful basis of the processing is Consent (see above), or if the original purpose is no longer valid.
8.2 We strongly recommend that our schools implement clear processes for evaluating these kinds of requests.
8.3 Our Data Protection Officer can also assist with advice in difficult cases. If a data subject is granted the right to be deleted, ManageBac will, either through our software or our support services, help execute these rights and confirm the deletion.
9. When does ManageBac delete personal data?
9.1 ManageBac deletes personal data when instructed by our customers, or if the contract between us and the customer is terminated.
9.2 The procedures around deleting customer data upon termination of service should be provided in writing or in a Data Processor Agreement.
9.3 An instruction to delete a user in our services can either be manually performed in the platform by a customer representative or upon request to our support team.
9.4 When users are deleted in our systems, there are safeguards in place to prevent errors leading to an irreplaceable loss of data. In many cases customers will have to manually confirm the deletion of customer data, including personal data.
9.5 Are we required to provide the personal data that we store on a user when requested?
To a limited degree, yes. Your users have strong rights to transparency, information, and data access. Any data subject can request a copy of all personal data stored, provided that it does not adversely impact other users, or if the data is not already directly available.
Please note this is not an absolute right. There are other laws in place that require you to protect the data subject and others from accessing certain kinds of information. Again, we strongly recommend that you implement a clear process for evaluating this kind of request, and our Data Protection Officer can assist in difficult cases. If you grant a data subject the right of access, we will, either through our software or our support services, help execute these rights.
9.6 Our systems were built for transparency across all stakeholder groups, so the majority of data stored about a user is directly accessible via the individual user profile.
10. Can a user contact ManageBac directly (e.g. student, parent, teacher) to exercise his rights under GDPR?
10.1 No. Under GDPR, the data subject (user) rights are between him and the controller (our customers).
10.2 Any data subject requests from end users to ManageBac will be handed over to the customer. 10.3 ManageBac will cooperate in good faith with customers to ensure they can exercise the rights of the data subjects in a prompt manner.
11. Does ManageBac send data to third parties?
11.1 No, unless we receive instruction / confirmation from our customers or have a legal obligation to do so.
11.2 Schools often request that we integrate with a third-party tool or service, or set up this integration directly themselves using our publicly available APIs.
11.3 We take steps to prevent customers from sending data to 3rd parties without complying with data protection regulations.
11.4 It is important that our customers themselves implement safeguards to ensure that data transfer occurs in adherence with regulation.
12. Will ManageBac notify users if a data breach has occurred?
12.1 Depending on the nature of the data breach, our customers might be required to promptly notify both the users affected and the supervising authorities.
12.2 ManageBac is required to notify its customers when becoming aware of a data breach, and to help them in fulfilling obligations in notifying users.
13. Can I require a cloud service provider, like ManageBac, to only host personal data in my country?
13.1 One of the GDPR’s primary objectives is the free flow of personal data inside the European Economic Area (EEA), under one common regulation.
13.2 In most cases, restricting vendors in processing data across the EEA would not be permitted under GDPR.
14. Does ManageBac process data outside the EEA? Is it allowed to process data outside the EEA?
14.1 GDPR does not forbid personal data to flow outside the EEA, but expects that any data processing outside the EEA is done following the same principles.
14.2 Controllers or processors that process data outside the EEA must provide detailed information about the nature of the processing. In some cases, they must also allow customers or users to object to the processing.
14.3 The European Commission has recognized Canada as a jurisdiction with ‘adequate’ data protection. To learn more, click here.
15. Does GDPR impact customers outside the EU?
15.1 Not legally. The EU, obviously, has no legislative power over other jurisdictions.
15.2 GDPR does not offer any rights or freedoms to data subjects located outside the EU, and does not put obligations on non-EU customers that do not process data on EU/EEA data subjects.
15.3 ManageBac offers, for the most part, the same services and same level of security to all our customers. In other words, no matter where your school is located, you will benefit from our approach to security of personal data under GDPR.
16. Who do I contact with further questions?
16.1 For general questions related to ManageBac you can always contact our support team at [email protected].
16.2 For contractual or commercial questions, please contact your Account Manager or [email protected].
16.3 For specific GDPR-related questions from our customers, please contact our Data Protection Officer. In addition to monitoring our own compliance and providing advice and training to our own staff, our DPO will be available to our customers and their DPOs to discuss data privacy issues. They can be reached at [email protected]. Please note that any communication with our DPO must be in English.