European schools · Data protection and procurement

Evaluate school software with data protection in view

Choosing a school platform involves student records, staff information and family communications. This page explains what to review with Skoolia before adopting the service. It is a procurement guide, not a certification or a guarantee that using a particular tool makes a school compliant.

14-day trial · No credit card required

What to review before moving school records

A data processing agreement

A Skoolia data processing agreement is available on request. Ask for the current terms and review the processing scope, responsibilities, subprocessor information and arrangements for returning or deleting data. Match the documents to the services your school plans to use.

Explore details →

Hosting and the wider processing chain

Request the current hosting locations and subprocessor details for the services your school will use. Include support, analytics, communication and AI processing in the review, as well as any transfer arrangements. Agree your data-residency requirements with the team before a migration.

School-scoped access

Skoolia uses school-scoped records and role-based permissions. During evaluation, check what administrators, teachers, parents and students can access. Confirm the audit features included in your chosen plan and agree who will review access as staff join or leave.

Explore details →

AI and communication providers

Najiba can send the data needed to answer a question to an AI provider. Do not equate school-scoped access with an absence of external processing. Review provider terms and the data involved in AI, email, payment or WhatsApp workflows before enabling those services for your school.

Explore details →

Bring these questions to your procurement review

What information will we store?

List the student, guardian and staff fields you need, and identify any sensitive information. Agree which roles require access and which information can be omitted. Use fictional records for the first trial and involve your data-protection contact before a real migration.

How will we manage the records over time?

Ask how your school will handle corrections, exports, retention and deletion requests. Confirm the capabilities and any support process in writing. Agree a migration scope and an exit process before retiring existing tools.

View details →

What evidence do we need before signing?

Request the current agreement, subprocessor list, hosting details and relevant security documentation. Clarify any requirements specific to your country or institution. Review the scope of each document rather than inferring certification from a general security statement.

View details →

European school data-protection questions

Is a data processing agreement available?

Yes. Contact Skoolia to request the current data processing agreement and discuss the services and data your school intends to use.

Does EU backend hosting mean every processing activity stays in the EU?

No. Backend location alone does not establish the location of every subprocessor or service. Review current hosting, subprocessors and transfer arrangements for your selected workflows.

Does this page certify GDPR compliance?

No. It describes evaluation questions and product controls. Your school should assess the service, contracts and its own processing practices with its data-protection contact.

Can schools outside Europe use Skoolia?

Yes. Skoolia serves schools worldwide. This guide focuses on European procurement questions while the platform continues to support English, French, Spanish and Arabic.

Evaluate Skoolia with your team

Start with fictional records or bring your requirements to a demo.