Ned Tools is designed around data minimization. Administrators should be able to understand what stays inside Moodle, what an enabled feature sends to Ned Cloud, and what may be sent to a third-party service.
Plugin configuration, course operations, and school data should remain within the school's Moodle environment whenever a feature does not require an external service. Ned Tools is designed to avoid moving data outside Moodle merely to perform local Moodle workflows.
Ned Cloud supports approved operational services such as site identity, licensing and entitlement responses, covered-usage support, private-distribution authorization, and trusted release metadata. Requests should be limited to the information required for the specific operation.
Installing or updating a plugin should not require transmitting student content, profile values, assessment content, or other unrelated personal information to Ned Cloud.
Ned Tools separates covered-usage and operational information from student content. Covered student or course capacity is coordinated centrally through Ned Hub; individual plugins should not invent separate over-capacity rules or transmit unrelated content to enforce licensing.
Some current or future features may use an external service, including a third-party AI provider. When a feature requires external processing, its product documentation should identify that dependency and the relevant data flow. External transmission should be minimized and should occur only for the enabled feature that requires it.
Ned Tools does not treat a general privacy statement as permission to send school data to an external AI service. The applicable feature and school configuration determine whether an external service is used.
Different plugins perform different jobs and may have different permissions or data flows. Maintained plugin documentation should describe the plugin's permissions, local processing, external data sharing, licensing behavior, and relevant troubleshooting information.
Ned Tools does not claim certifications, legal compliance, data residency, privacy-law approval, regulatory approval, or specific retention guarantees unless those claims are explicitly established and documented. Schools should evaluate the product against their own policies, contractual requirements, and applicable law.
Schools control their Moodle environment, enabled features, user permissions, and applicable institutional policies. Before enabling a feature that uses an external service, administrators should review the feature's documentation and determine whether the data flow is appropriate for their environment.
The catalogue links to maintained manuals as product documentation becomes available.