Back to Edvia
Terms and Conditions

Edvia Privacy Policy

How Edvia handles information for learners of all ages, families, educators, and schools.

Effective date and version: 2026-08-25

This Privacy Policy applies to the Edvia website, learning portal, virtual campuses, mobile experiences, and related support services. It should be read with the Terms and Conditions and any privacy notice supplied by the school or organisation that manages your account.

1. Information we collect

  • Account and identity details, such as name, contact details, date of birth, school, role, language, and login information.
  • Parent, guardian, and school-authorisation details when needed to create or supervise a learner account.
  • Learning records, including enrolments, recommendations, answers, assignments, assessments, attendance, progress, certificates, educator feedback, and support history.
  • Campus, event, chat, attachment, house, avatar, virtual-item, and other activity created through interactive features.
  • Transaction and entitlement records for subscriptions, tokens, and virtual items. Payment providers process payment-card details under their own privacy terms.
  • Technical and security data, such as device, browser, IP address, timestamps, cookies, session identifiers, diagnostics, and suspected misuse.

2. Where information comes from

Information may come from the user, a parent or guardian, an authorised school or educator, activity generated while using Edvia, connected services selected by the user or school, and security or support investigations.

3. Why we use information

  • Create accounts, authenticate users, provide learning content, and operate role-based access.
  • Recommend courses, administer surveys and assessments, record learning evidence, and report progress.
  • Operate live events, campuses, rooms, chats, houses, rewards, and other collaborative features.
  • Provide safeguarding, moderation, fraud prevention, security, technical support, and service communications.
  • Meet school agreements and legal duties, enforce the Terms, resolve disputes, and improve service reliability and accessibility.

4. Responsibility and legal basis

Depending on how an account is provided, Edvia may determine why information is processed, or may process school-managed information for the responsible school or organisation. The school may therefore be the first contact for a school-managed learner record.

The legal basis depends on applicable law and may include performing a contract, providing an education service requested by a school, legitimate interests in operating and securing the platform, compliance with law, protection of users, and consent where consent is required. Consent may be withdrawn for future processing, but this does not make earlier lawful processing invalid.

5. When information is shared

Edvia does not sell or rent personal information. Information may be shared only as needed with the responsible school and its authorised staff; vendors that host, secure, communicate, analyse, support, or process approved payments for the service; another user when a collaborative feature intentionally requires it; professional advisers; a successor to the service; or public authorities when lawfully required.

Service providers must use information only for the contracted purpose and protect it appropriately. Public profiles, chats, attachments, houses, and events can reveal information to participants, so users should share only what is appropriate for that learning space.

6. Learners of all ages

Edvia is designed for learners of all ages, including children. A learner below the age at which they can independently agree to data processing under applicable law must use Edvia with approval from a parent, legal guardian, or authorised school as applicable. Schools that create or authorise accounts are responsible for required family notices, permissions, and supervision.

Parents and guardians may ask the responsible school or Edvia support to review, correct, restrict, export, or delete a child’s information where applicable. Edvia may verify the requester’s identity and authority before acting. If Edvia learns that a child account lacks required authorisation, it may restrict the account while appropriate authorisation or deletion is arranged.

7. Retention

Information is retained only as long as reasonably needed for the service, the school agreement, learning continuity, safeguarding, security, fraud prevention, legal compliance, or disputes. Retention periods vary by record type and school instructions. Data may then be deleted, anonymised, or retained in a restricted archive where law requires it.

8. Security

Edvia uses administrative, technical, and organisational measures intended to protect information, including authentication, role-based access, logging, and controlled storage. No online service can guarantee absolute security. Users should protect credentials and promptly report suspected unauthorised access through the in-platform support channel or their school administrator.

9. Privacy rights and choices

Depending on location and the responsible organisation, a person may have rights to access, correct, export, delete, restrict, or object to processing; withdraw consent; and complain to a data-protection authority. Requests may be made through the responsible school or the in-platform support channel. Identity and authority may be verified, and lawful exceptions may apply.

10. Cookies, third-party resources, and international processing

Edvia may use essential cookies and similar technology for sessions, security, language, preferences, and service operation. Course links and embedded resources may be operated by third parties whose terms and privacy policies apply independently. Service providers may process information in other countries subject to contractual and legal safeguards required by applicable law.

11. Changes and contact

Material policy changes will be posted with a new version date and, where appropriate, notified through Edvia or the responsible school. Questions, privacy requests, and concerns may be submitted through the in-platform support channel. School-managed users may also contact their school administrator.