How EdixPark handles school information

What schools store in EdixPark

Schools and authorized users add and manage their own data inside EdixPark.

This data stays inside the school's private space in the platform.

EdixPark provides the system and infrastructure that makes this possible.

• School account and contact details.
• User accounts and role settings created by the school.
• School data entered and managed by the school.
• Messages or support requests sent directly to EdixPark.

How the platform uses this information

The platform uses this information only to make the service work for the school that added it.

This means keeping the school workspace available, applying access rules, and supporting the features the school chooses to use.

• To create and maintain each school workspace.
• To run the tools the school chooses to use.
• To sign users in, apply permissions, and protect school data.
• To respond to onboarding, support, training, and service requests.
• To troubleshoot issues and improve reliability.
• To manage subscriptions, billing communication, and service updates.

School ownership of records

Schools fully own the data they store and manage in EdixPark.

EdixPark does not claim ownership of institutional records. The platform only provides the system and infrastructure used by the school.

EdixPark does not access, view, or use institutional data outside of providing the platform infrastructure.

In simple terms: your school stays in control of its own data.

• Schools decide which users may access their workspace.
• School administrators manage roles and permissions.
• EdixPark does not decide which school staff should access internal records.
• Schools are responsible for the accuracy and proper use of the data they enter.

Multi-tenant separation and privacy boundaries

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

In simple terms: one school cannot access or view another school's data.

EdixPark does not review school records inside those isolated environments.

• User access is tied to the correct school after login.
• School data stays within that school workspace.
• Any unexpected cross-school access is treated as a security concern.

School responsibility for the data entered

Schools are responsible for the data they enter into the platform.

This includes using EdixPark in line with their own policies, internal rules, and responsibilities to their school community.

When information may be shared

We do not sell school data.

School data is not made available across schools, and EdixPark does not use institutional records outside the platform environment.

• One school's data is not shared with another school.
• School administrators control access inside their own workspace.
• If a legal or security issue arises, EdixPark may act to protect the platform or comply with lawful obligations.
• Schools can contact EdixPark for platform support without transferring ownership of their records.

Retention, export, and deletion

School data remains in the platform for as long as the service is active or as otherwise required by the school's service arrangement.

Some account, billing, or operational records may be retained where needed for support, security, disputes, operations, or legal requirements.

Schools can contact EdixPark about account closure, data export, or deletion support.

Access requests and corrections

Requests about school data are usually handled by the school that controls the workspace.

This means the school decides how access, corrections, and internal records are handled.

Schools and account owners can also contact EdixPark about platform privacy questions or account support.