How SchoolConnect protects school data

Staff, teacher, parent, and finance accounts authenticate with bcrypt-hashed passwords—credentials are never stored in plain text.

Authenticated sessions and role-based permissions control access to student records, billing ledgers, gradebooks, and uploaded materials.

Production deployments are intended to run over HTTPS/TLS. Laravel's AES-256-CBC cipher is available for application-level encryption where sensitive values require it.

Super Admin accounts can be required to enable two-factor authentication before accessing platform controls.

Platform practices are designed to support K-12 schools operating under the Philippine Data Privacy Act of 2012.

Schools retain ownership of their institutional data. SchoolConnect provides scoped workspaces—not a shared directory across institutions.

Platform-level actions—such as subscription changes, impersonation, and payment proof review—can be recorded in audit logs for operator review.

Each registered school is an independent tenant. Academic, billing, and messaging data are scoped to that school throughout the application.

Data from one school is not visible to another. Additional campuses register as separate schools—not shared branches under one organization account.

Within a school, teachers are further scoped to assigned classes for uploads and roster-sensitive workflows.

Classroom activity photos are published to linked parents only and are automatically removed after 30 days.

Learning materials and payment proofs are stored in school-scoped paths and served through authenticated download flows—not open public directories.

Material visibility can be limited to the whole school, faculty only, or a specific class—depending on how staff publish the file.