Security
Eduly builds software for schools. Security and data stewardship are part of how we design the platform and operate this marketing site.
This page summarises practices at a high level. It is not a certification, audit report, or customer security questionnaire response. Schools evaluating the product should request current documentation through their sales or success contact.
Last updated: 20 August 2026.
Product security (overview)
The Eduly platform is designed with tenant isolation so school data is scoped to the correct organisation.
Access to product features is controlled through role-based permissions. Sensitive fields may be encrypted at rest where the product architecture requires it.
We use industry-standard transport encryption (TLS) for data in transit on supported endpoints.
Infrastructure and operations
We host on reputable cloud providers and apply least-privilege access for operational staff.
We monitor for abuse and maintain processes to investigate and respond to security incidents affecting systems we operate.
This marketing website
The public website is separated from school production tenant data. Forms and analytics follow the Privacy Policy and Cookie Policy.
Optional analytics tags load only according to your cookie consent choice.
Responsible disclosure
If you believe you have found a security vulnerability in Eduly systems, please report it responsibly via /contact with enough detail for us to reproduce the issue. Do not access data that is not yours or disrupt service while testing.
We aim to acknowledge good-faith reports and prioritise remediation based on severity.
Customer due diligence
Enterprise and school buyers may receive additional security documentation under NDA as part of procurement. Contact us through /contact or your Eduly representative.