Security for structured school operations

Security approach

EdixPark is built for schools that need a safe and reliable platform.

Our job is to protect the system so each school can use its own private space with confidence.

Tenant separation and data isolation

EdixPark is a multi-tenant system. Each school works inside its own isolated school workspace.

In simple terms: each school's data is kept separate and cannot be accessed by others.

• School records are tied to the correct school workspace.
• All school data stays within school boundaries.
• Unexpected cross-school access is treated as a serious security issue.

Authentication and access control

Users access EdixPark through authenticated accounts and role-based permissions.

After login, users can only work with the school workspace and modules they are allowed to use.

This means only people your school allows can access your school system.

• Access is limited by user role and school workspace.
• School administrators control who gets access.
• Administrators decide what each user can do.
• School data is visible only to users whose role requires it.
• Administrators should remove access when it is no longer needed.

Operational safeguards

We maintain the platform carefully so it stays stable and safe to use.

This includes updates, monitoring, troubleshooting, and routine maintenance.

• Controlled access around sensitive parts of the platform.
• Controlled system updates as the product evolves.
• Monitoring and troubleshooting to support stability.
• Maintenance practices that support platform health.
• Backup and recovery practices that support service continuity.

Monitoring, logging, and abuse prevention

We may review platform events when needed to detect misuse, investigate suspicious behavior, troubleshoot problems, or protect reliability.

This supports security and platform health. It does not give EdixPark access to a school's private data.

Shared responsibility with schools

Good security depends on both EdixPark and the school.

EdixPark protects the platform. Schools manage how their people use it.

• EdixPark protects the application, tenant boundaries, login flow, and core platform operations.
• EdixPark maintains the system, not the school's internal data.
• Schools manage users and decide who should have access.
• Schools should protect login details and remove former users.
• Schools should train staff to handle school data carefully.

Incident response and responsible reporting

EdixPark monitors for issues that may affect service stability or security.

If we identify a serious issue, we will investigate, take appropriate action, and communicate with affected schools when needed.

If you believe you found a vulnerability, contact EdixPark with a clear description. Please do not access, change, delete, or expose data that does not belong to you.