End users of the Edsby platform deserve to know how their information is stored, who owns it and how it’s being used.
Edsby is a cloud-based software service that modernizes how educators, students and parents engage with each other. It is used by national, state and provincial governments, public school districts and private school organizations. Edsby is selected by these organizations, often through a formal competitive procurement process and rigorous evaluation of many factors including privacy and security of student data. Edsby is managed by the education organization as one part of the suite of technology solutions that every education organization requires.
Education organizations pay to use Edsby, and thereby own all the data within. Each education organization controls the management of its data. This is unlike many free education software solutions on the internet which bypass the approval and management of education organizations so as to encourage adoption by teachers.
Cloud-based solutions offer lower costs, higher reliability, better security and more innovative capabilities than traditional software solutions installed and managed by local information technology staff within an education organization’s data center.
As a result of these advantages, education organizations are moving more and more of their mission-critical technology solutions to the cloud. As an example, many of these organizations have rolled out cloud-based email and storage solutions such as Microsoft 365 and Google Workspace for Education to the students and staff of their organization. When these organizations look at new technology solutions they generally request or even require that the solution be cloud-based.
Edsby uses Microsoft as its cloud services provider because Microsoft has a strong focus on serving the information technology needs of organizations around the world in a secure and reliable manner. Microsoft’s cloud platform, Azure, is used by thousands of other organizations, including governments, banks and large corporations due to its very stringent standards and requirements for information protection and data sovereignty.
Every country and region has specific regulations controlling where education-related data should physically reside, who can obtain access to information held by education organizations and under what circumstances such access may be granted. Education organizations, in turn, understandably want to ensure that their data is governed by these rules. Edsby strives to ensure the data it manages is located in and governed by the rules in the jurisdictions in which its education organization customers operate.
To meet these objectives, Edsby leverages Microsoft Azure datacenters around the world. The Microsoft Azure design enables one hundred percent of our customers’ data to be resident in a data center, or centers, within a specific country. For example, Edsby customers in Canada have their Edsby cloud servers (including all computing resources, failover systems and data storage resources including backups) in Canada. In the U.S., all Edsby customers’ systems run in U.S. Azure data centers, and all Edsby customers’ systems in Australia and New Zealand reside in Australian Azure data centers.
When an education organization chooses to use Edsby, it decides what information to provide to Edsby. Almost every education organization provides Edsby with data about its staff, students and parents so that Edsby can create accounts for those users. The education organization owns this data and strictly controls what is done with the data. Edsby uses this data to provide services to the education organization, for usage insights and for security purposes.
When Edsby users create or add information into Edsby (e.g. a teacher posting a lesson, a student submitting an essay), the user retains ownership of that information. Under Edsby’s Usage Policy agreement, the user agrees to let Edsby store and display that information in order to provide the service.
The education organization provides stewardship of all user-contributed content in their Edsby site, and Edsby manages the retention and deletion of that data at the direction of the administrators of the education organization.
Edsby never sells the data it has or collects from the education organization, as Edsby makes no claim to be the owner of the data.
Edsby does not sell Personal Information or the content provided by its users. There are certain circumstances in which Edsby may disclose, transfer or share Personal Information with a very small set of third parties, as outlined in Section 7.0 of our Services Privacy Policy. For example, Edsby may disclose data if directed to do so by the Education Organization, or in the event someone may cause or be at risk of imminent bodily harm, or if compelled to by a valid legal order.
As outlined in our privacy policies, sub-processors of data in Edsby include:
| Sub-processor | Nature and Purpose of Processing | Categories of personal data | Location of Processing | Security Measures |
| Amazon Simple Email Service | Email notifications | User email addresses, names | USA | https://aws.amazon.com/ses/ |
| Cloudflare | Content delivery network provider | Personal data contained in user account information and text or files created by customer and stored in Applicable Cloud Products | Customer traffic processed globally at the data center closest to the end user. | https://www.cloudflare.com/trust-hub/compliance-resources/ |
| DataDog | Engineering support and consulting services provider | Anonymized usage information created by customers through the use of Edsby | USA | https://www.datadoghq.com/legal/ |
| Frill | Idea management provider | User name and Edsby feature suggestion data | USA | https://frill.co/privacy-policy |
| HubSpot | Customer service and technical support | Personal data contained in product notice communications and user-initiated shared video recordings including associated comments and email messages | USA | https://legal.hubspot.com/privacy-policy |
| Microsoft Azure | Hosting provider | All Edsby data and provider of related data processing services | USA, Australia, New Zealand, Canada | https://www.microsoft.com/en-us/trust-center |
| Microsoft Azure OpenAI Service | Teacher AI assistant features | User names, assessment data, course content | USA | https://learn.microsoft.com/en-us/security/benchmark/azure/baselines/azure-openai-security-baseline |
Section 6.0 of Edsby’s Services Privacy Policy represents in detail that the company does not subject users to any advertising, contextual, personal or otherwise. There is no marketing to opt-out of, as Edsby does not send marketing messages to end users via its Edsby services. Edsby does not make offers to end users like sweepstakes or contests. And it does not sell, rent or otherwise share any personal information with any third party that does.
Edsby’s business is supported solely on the basis of usage fees paid by educational organizations with no monetization of student data whatsoever.
Edsby takes steps to ensure that an authorized user sees the information they should have access to and ensures they do not see information they should not see.
Much of the support in Edsby to do this is built directly into the Edsby software, as a function of the type of data being accessed. For example, a student can never access a teacher’s gradebook to see how other students in the class are doing. Edsby controls to prohibit this sort of access are built right into the software.
Edsby is deployed as a part of an education organization’s overall Information Technology infrastructure. As such, it integrates with other key systems of record in the organization.
These systems normally include the organization’s authentication system(s), its Human Resources (HR) system and its Student Information System (SIS), the organization’s main database. Student, staff and parent accounts in Edsby are automatically created based on the data in these systems. Each organization decides exactly what data should be supplied to Edsby from its existing systems. For basic Edsby functionality to work, it must be supplied with student names, user IDs, class enrollments and so on.
The educational organization has complete control over which information is supplied to Edsby and does so at its discretion.
For example, if an education organization decides that it doesn’t wish Edsby to store or display staff home addresses, then that information is not sent from the organization’s IT systems to Edsby. However, many organizations seek to have this information available in Edsby for school administrators. These types of decisions are made by the education organization, not by Edsby.
All Personal Information in Edsby is supplied to Edsby directly from the education organization’s existing IT systems (such as the Student Information System). This includes the information used to define user accounts such as name, unique identifier (e.g. student number or staff number), email address, home address and so on. The accuracy of the information in Edsby is a function of the accuracy within the education organization’s IT systems.
Since this information is supplied from the systems of record in the education organization, students are never asked to provide Personal Information in Edsby.
Edsby provides an additional layer of accuracy by enabling parents to review and confirm information about students the parent is responsible for. If there is inaccurate information displayed in Edsby, the parent can report it to have it updated in the education organization IT system which provided the incorrect data. For example a parent may have moved, and they wish to have the organization update their official record. The corrected information then re-syncs to Edsby.
As mentioned above, this option is never available to students, only to parents.
Edsby implements what’s known as a “role-based access control” system. This means that each user within the system is assigned a role, and each role is provided with a very specific set of capabilities that are appropriate for that specific role. There are over two hundred different capabilities in Edsby that are controlled on a per role basis, and each capability can be specified at a “no access” level, a “read access” level, or a “read/write access” level.
Examples of Edsby Roles include “Student”, “Parent/Guardian”, “Teacher”, “School Administrator”, “District Administrator”, and so on.
User roles are assigned at account creation time, and roles are rarely changed. Roles include:
In some cases, the granularity of access is not specified in specific legislation or policy, but instead is based on the policies of the specific education organization that has chosen Edsby. In areas like these, Edsby may be tailored by the education organization to implement the policy it feels is appropriate.
Edsby provides mechanisms to configure the particular access capabilities available to each role on a per-organization basis. This enables the organization to tune the level of information access that Edsby provides to match their policies. For example, some organizations opt to turn on or turn off student-to-student or even parent-to-teacher messaging in Edsby.
Edsby is intended to reflect the policies of the education organization which has chosen to use Edsby.
Edsby adopts the following among its privacy best practices to ensure that only authorized users have access to Personal Information in the Edsby Services.
Edsby maintains strict controls on who has physical access to its systems.
Each Edsby cloud instance runs in a tier one commercial Microsoft Azure cloud hosting facility that is fully SSAE 16, CSAE 316 and ISAE 3402 Type II certified. These facilities undergo in-depth independent audits of control activities, including management of the hosting and network technologies and services that are used to run Edsby. These facilities renew their certifications annually ensuring Edsby is being managed to the highest standards.
These commercial cloud hosting facilities use state-of-the-art perimeter security and access security systems to ensure only authorized personnel have access to the physical location where Edsby is run.
Controls in place at these facilities include procedures for secure data disposal. This includes both the procedures for deleting data from used data storage and procedures for destroying storage units no longer used in production.
Key operating system and database systems used by Edsby are managed by Microsoft Azure, including the notification and installation of security patches that are relevant for the Edsby software stack as they become available. Other software components used by the Edsby solution are protected by a commercial vulnerability management system that assures software integrity.
There are a number of measures taken to assure that only authorized users log in to an Edsby system and that intruders are kept out.
All data sent between the Edsby server and Edsby client (web browser, smartphone app, tablet app) is encrypted in transit via SSL (Secure Sockets Layer). This is the security protocol used by banks, online retailers and militaries to establish an encrypted link between a web server and a browser/app. This link ensures all data passed between the web server and browser/app remains private.
When stored, data is encrypted on Edsby servers with RSA 2048-bit encryption using a symmetric encryption key. Keys are stored in a secure location with identity-based access control and audit policies.
Edsby adheres to guidelines of its ISO 27001 certification and adopts policies and procedures internally to help ensure each customer organization’s information stays private to that organization.
For example, each employee and contractor within the Edsby organization who has access to customer confidential information receives training in this area, and signs an agreement that attests that they have read, understand and will abide by policies and procedures such as:
Edsby is procured and deployed by education organizations. It is often a strategic part of the organization’s overall IT strategy. The education organization defines the parameters for data retention and destruction in Edsby in terms of the number of school years’ worth of data to be held.
Amplifying on section 9.1 of Edsby’s Services Privacy Policy, an organization may choose to hold 3 years’ worth of data in Edsby, for instance, or up to our maximum retention of 7 years. This policy is established by your education organization.
In the period between school years, an archiving process is run for each organization using Edsby. Data such as classes, gradebooks, discussions, and the like from the recently completed school year are moved into a separate archive partition. From here, they can easily be accessed by appropriate staff that may wish, for example, to retrieve a lesson plan from a class taught in Edsby the previous year. Edsby can store as many archive partitions as the customer desires, up to 7 years. When an archive partition falls outside of the archiving time window specified, none of the data in that archive partition is accessible any longer.
Amplifying on section 9.2 of the Edsby Services Privacy Policy, Edsby is best characterized as a processor that manages data at the direction of the education organization, the controller. If an end user sends a request to update or delete their Personal Information, these requests are routed to the education organization for their review and potential action.
If Edsby receives a specific request from an authorized individual at the education organization to destroy specific records, Edsby complies and provides a certificate of data destruction.
Accordingly, users seeking to shut down, close or delete an Edsby user account should contact their education organization.
There are eight consumer rights of General Data Protection Regulations compliance, including:
Edsby’s Services Privacy Policy and Public Website Privacy Policy have been assessed by Common Sense Media’s privacy program for responsible student data handling practices and given a “Pass” rating and a score of 95%. No other similar product has as high a rating.
In August 2021, Edsby was certified to ISO 27001, a formal standard for Information Security. Its policies and practices are annually reviewed by a third party each year to maintain certification.