EduConnect Policies & Legal

Security and Data Protection Policy

1. Implemented application controls

EduConnect implements authentication, role-based authorisation, tenant-aware data handling, CSRF protection, audit logging for selected sensitive actions, controlled document-download checks and payment reference verification workflows. Production settings enable secure cookies, HTTPS redirect and related browser protections when deployed with the required production configuration. These measures reduce risk but do not guarantee absolute security or a certification.

2. Data and document handling

Access to institutional records is intended to be scoped by role and tenant. Uploaded documents and payment-related records are handled through application permissions; users must upload only authorised, lawful content. Secrets such as payment keys are configured outside the repository and should never be posted in messages, documents or support requests.

3. Monitoring, vulnerabilities and backups

The service records selected audit and operational events. KizTech should assess, prioritise and remediate reported vulnerabilities using a risk-based process. Backup, recovery, hosting monitoring and deployment arrangements depend on the environment and are not represented here as a guaranteed recovery objective, retention period or independently certified control unless verified in a written agreement.

4. AI and incident safeguards

AI assistance is role-scoped and should not replace human review of consequential decisions. Users must avoid submitting unnecessary sensitive information and must validate AI outputs. Suspected compromise, unauthorised disclosure or security vulnerability should be reported promptly to the institution and kiztech01@gmail.com. KizTech will investigate and coordinate incident communication as required by law or contract.

5. Institutional responsibilities

Institutions must assign roles carefully, remove access when it is no longer needed, train authorised users, protect local devices and processes, and maintain their own academic, records-management and incident procedures. Recommended improvements should be assessed against the institution's environment; they are not claims that every control is already implemented.