How EdixPark protects school information

EdixPark is a school management platform. We provide the software, hosting environment, infrastructure, and support that help schools run academic, administrative, reporting, and financial workflows in one place.

Each school uses its own workspace inside the platform. The school decides what records to enter, which users should have access, and how those records should be used in line with the school's own responsibilities.

This page explains EdixPark's platform privacy responsibilities in plain language. It is meant to support understanding and internal review. It is not legal advice.

• Schools control the records they create and manage in their own workspace.
• EdixPark provides platform infrastructure, service operations, and support.
• Privacy decisions inside a school workspace should also reflect the school's own policies and legal obligations.

The information stored in EdixPark depends on the features a school chooses to use and the records that authorized users enter into the school workspace.

That may include day-to-day school records, account details, and support communications needed to operate the service.

• School profile details such as school name, contact details, billing contacts, and workspace setup information.
• User account details such as names, email addresses, login records, and role assignments created or managed by the school.
• Operational school records such as students, attendance, assessment records, fees, payments, reports, and internal notes where those features are used.
• Support, onboarding, and training messages sent to EdixPark by schools or authorized users.

EdixPark may process account, usage, support, and workspace information so the platform works as expected for each school.

That includes the operational work needed to keep a school workspace available, apply access rules, respond to technical issues, and maintain subscription or billing processes.

• To create, maintain, and host each school workspace.
• To sign users in, apply permissions, and support role-based access.
• To troubleshoot issues, monitor reliability, and improve product performance.
• To provide onboarding, support, service communications, and training assistance.
• To process subscription, invoicing, payment, and account administration tasks.
• To investigate misuse, protect accounts, and help keep the platform secure.

EdixPark does not take ownership of a school's institutional records simply because they are stored in the platform.

Schools are responsible for the accuracy, quality, permissions, and lawful use of the information they enter, upload, or manage in their own workspace.

Schools should make sure they have an appropriate basis to collect, manage, and use information relating to their staff, parents, students, or other users.

• School administrators decide which staff or users should have access.
• Schools are responsible for keeping their records accurate and up to date.
• Schools are responsible for making sure information is collected and used appropriately inside their own operations.

EdixPark is built so each school works inside a separate platform workspace. One school should not be able to access another school's records through normal platform use.

Inside a school workspace, access is role-based. Permissions may differ between administrators, finance staff, teachers, or other users depending on the setup chosen by the school.

• Each workspace is intended to operate separately from other schools on the platform.
• Role-based access helps limit what each authorized user can view or manage.
• Unexpected or unauthorized cross-workspace access would be treated as a serious platform security concern.

EdixPark does not sell school data. We do not make one school's records available to another school.

In limited situations, information may be shared with service providers or support tools used to operate the platform, or where sharing is needed to investigate issues, meet lawful obligations, or carry out authorized platform processes.

• With infrastructure, hosting, communication, or support providers that help operate the service.
• With payment or billing providers where needed to handle subscriptions or transaction records.
• With authorized school or platform contacts when support, account verification, or troubleshooting requires it.
• Where required for legal compliance, lawful requests, fraud prevention, security response, or protection of the platform and its users.

Information may be retained for as long as a school workspace remains active, or for longer where retention is needed for support, security, billing records, dispute handling, or legal obligations.

Requests about school records are usually managed first by the school that controls the workspace. Where applicable, schools can contact EdixPark for support with exports, corrections, closure requests, or deletion steps.

• Schools remain the primary point of control for records inside their own workspace.
• Some operational, security, or billing records may need to be retained for a reasonable period even after service changes.
• Deletion or closure support may depend on account status, legal obligations, and technical or service requirements.

EdixPark works to protect the platform through account controls, operational monitoring, access management, and service maintenance. We also respond to technical issues, misuse, and suspected security problems when identified.

Schools and users also play an important role by protecting login credentials, reviewing permissions, and reporting suspicious activity promptly.

• Use strong passwords and keep login details confidential.
• Limit account access to authorized users only.
• Review user roles and remove unnecessary access when staff responsibilities change.
• Contact EdixPark promptly if you believe an account or workspace has been compromised.

If a school uses paid services, EdixPark may process billing contacts, invoices, payment status, subscription activity, and related support records.

Payment processing may involve trusted payment or financial service providers where needed to complete transactions or manage payment records.

• Billing records help manage subscriptions and account status.
• Payment details may be handled through approved payment providers rather than stored directly by EdixPark in every case.
• Financial records may also be retained where needed for reconciliation, support, audits, disputes, or legal requirements.

EdixPark may host records relating to students, parents, guardians, staff, or other school users where a school chooses to use the platform that way.

Because the school controls what information is entered into its workspace, the school remains responsible for making sure those records are handled appropriately and lawfully within its own operations.

• Schools should review what information is necessary before entering it into the platform.
• Parents, staff, and school users may need to contact the relevant school first for record-specific questions or corrections.
• EdixPark can support the school on platform questions, workspace management, and technical account issues.

EdixPark may revise this Privacy Policy to reflect platform changes, support practices, billing changes, security improvements, or clearer explanations of how the service works.

When this page changes, we will update the date at the top of the page so schools and users can see when it was last refreshed.

If you are a school owner, administrator, staff member, parent, or user with a privacy-related question about the EdixPark platform, contact us and we will guide you to the right next step.

Where the question relates to records inside a particular school workspace, the school may remain the first point of decision-making, but EdixPark can still support with platform-level help where applicable.

• Contact the relevant school first for record-specific requests managed directly by that school.
• Contact EdixPark for platform privacy questions, workspace support, export guidance, account closure, or technical follow-up.