AI tools are increasingly used in teaching, grading, learning support and school administration. Beyond efficiency and learning outcomes, schools also need to understand how student and school data are collected, processed, stored and protected. EDU A.I. takes schools' concerns about data privacy and information security seriously, and aims to explain clearly and transparently how we handle related data.
When teachers use AI tools, they may handle student assignments, learning content, comments or other school data.
Before adopting any AI tool, schools should therefore understand several key questions:
Understanding training use helps schools assess whether a vendor meets school-based data governance requirements.
Schools should understand the scope of collection and avoid putting personal data unrelated to teaching into AI systems.
Retention periods may differ by data type. Schools can ask vendors to explain their retention arrangements.
Understanding access controls helps schools assess internal safeguards and data leakage risks.
Schools can ask about retention, deletion or export arrangements after service ends.
Clear answers to these questions help schools improve teaching efficiency while building more responsible AI use.
When handling personal data, EDU A.I. complies with applicable requirements under Hong Kong's Personal Data (Privacy) Ordinance, and refers to relevant guidance from the Office of the Privacy Commissioner for Personal Data on artificial intelligence, data protection and responsible AI use. We also continue to review our data governance and risk management arrangements as services and technology evolve.
We want schools to understand not only what AI tools can do, but also how data is handled when those tools are used.
Below are the data privacy and security questions schools ask most often.
Different products may require different data, such as account information, teaching content provided by teachers, or other data needed to deliver the service. Our principle is to collect only what is needed to provide the relevant service, and to avoid collecting unnecessary personal data.
Not every use case requires identifiable student information. Where it does not affect service use, we recommend that teachers avoid entering unnecessary student personal data, such as ID numbers, private contact details or other information unrelated to teaching purposes.
Students' teaching content and learning data will not be used for marketing purposes unrelated to the relevant education services.
EDU A.I. clearly defines how data is handled based on each product and the AI technologies used. Where services involve third-party AI models, we also consider the relevant vendors' data processing and retention arrangements.
Some EDU A.I. services connect directly to and use third-party AI models, such as DeepSeek, Kimi and other local or overseas AI technology providers. We do not route these AI services through an intermediate agent, in order to reduce unnecessary data transfers. Before adopting third-party AI technology, we also assess the vendor's data processing and privacy arrangements, and follow data minimisation principles by sending only the data needed to provide the service and avoiding unnecessary personal data where possible.
Authorised personnel may need to access related data only when required for service operations, technical support or other legitimate needs. We limit unnecessary internal access.
EDU A.I. uses cloud technology to deliver different education services. Actual storage and processing arrangements may vary by product. If schools need further information during IT reviews or procurement, they can contact us.
We take appropriate technical and organisational measures to reduce the risk of unauthorised access, loss or misuse of data. These may include: account and access management; secure data transmission; system and cloud security measures; limiting internal data access; and regularly reviewing systems and data processing arrangements.
EDU A.I. online services use standard secure connection technologies to protect data as it moves between systems.
We keep data only for as long as needed to provide services, meet related obligations or other legitimate needs. Retention periods may differ by data type.
If a school wishes to enquire about, update or delete related data, it can contact the EDU A.I. team directly. We will follow up according to the nature of the data and applicable requirements.
After a school or user stops using the relevant service, we handle related data according to applicable retention and deletion arrangements. Schools with specific requirements can also contact us.
An AI tool's own data protection measures cannot fully replace a school's own data governance responsibilities.
When using AI tools, schools may also consider:
Enter personal data only when it is needed for the teaching or service purpose.
Clear internal guidelines help teachers use AI more consistently and safely.
Teacher awareness reduces unnecessary privacy risks in day-to-day use.
Schools should understand vendor data handling before adoption.
Depending on school policy and context, informing parents or students may be appropriate.
Clear AI use principles can help teachers adopt new tools with greater confidence while reducing unnecessary data privacy risks.
First check whether the assignment contains unnecessary personal data, and follow the school's own data and AI use policies.
Not necessarily. If the service does not need to identify students, we recommend avoiding unnecessary personal data.
EDU A.I. does not sell student data as a business model.
Some services may use third-party AI or cloud technologies. Actual arrangements depend on the product.
Yes. If needed, contact the EDU A.I. team directly.
Yes. We can provide further information to support school IT, procurement or data privacy reviews.
No. Schools should still use AI tools in line with their own data governance policies and applicable requirements.
Please contact us. We can explain further based on the actual product and use case.
Every school's IT policy, teaching workflow and data requirements are different. If you are a school leader, teacher or IT team member and want to learn more about how EDU A.I. handles data, our AI tools or school solutions, we would be glad to hear from you.
