Privacy-Conscious Video Conferencing: Five Checks for European Schools and Public Institutions

10.11.2026
European hosting alone does not establish GDPR compliance. This practical guide helps school leaders, public-sector procurement teams, IT administrators, and data protection officers assess five essential areas: data hosting and access, contractual safeguards, recording and retention, collaboration tools, and ongoing governance. Using bbbserver.com’s BigBlueButton-based offering as an example, it explains what institutions should verify before adopting a conferencing service to help protect pupils, staff, and citizens.

For European schools and public institutions, choosing a video conferencing platform requires more than comparing picture quality and subscription fees. Meetings may involve children’s personal data, confidential administrative discussions, or sensitive information about pupils and citizens. Privacy requirements should therefore be assessed before a platform becomes part of everyday operations.

European hosting is a useful starting point. bbbserver.com, for example, describes its BigBlueButton-based offering as using European servers and ISO 27001-certified data centers. These are relevant selection criteria, but neither European hosting nor certification alone establishes GDPR compliance.

When reviewing a provider, ask:

  • Where is each category of data stored and processed? Check live meeting data, recordings, chat messages, account information, logs, and backups.
  • Does “Europe” mean the EU or European Economic Area? Some European countries are outside the EU/EEA, so the precise location matters.
  • Who can access the data? Ask about administrators, support personnel, subcontractors, and remote access from outside the EU/EEA.
  • Are international transfers involved? If so, request information about the applicable transfer mechanism and any necessary supplementary safeguards.

ISO 27001 certification provides evidence that an information security management system has been independently assessed within a defined scope. However, a data center’s certification does not necessarily cover the conferencing provider’s application, support processes, or entire service.

Request the certificate, its scope, and its validity dates. Also ask about encryption, access controls, security updates, incident response, and backup protection. Do not assume that an encrypted connection means end-to-end encryption; ask the provider to explain its security model, particularly for recordings and server-side processing.

2. Review the Data Processing Agreement and Legal Basis

A platform can support compliant use, but the institution remains responsible for how and why it processes personal data. GDPR compliance depends on the contractual arrangements, technical configuration, and day-to-day practices—not simply the location of the servers.

Where the provider acts as a processor, the school or public institution should have an appropriate data processing agreement under Article 28 GDPR. Review this agreement before staff begin using the service.

The agreement should clearly address:

  • The purpose, duration, and scope of processing.
  • The types of personal data and categories of people concerned.
  • Processing on the institution’s documented instructions.
  • Confidentiality and appropriate security measures.
  • Subprocessor arrangements and notification of changes.
  • Assistance with data subject requests and personal data breaches.
  • Deletion or return of data when the service ends.
  • Information and audit arrangements needed to demonstrate compliance.

Ask for a current subprocessor list and check whether it matches the provider’s explanation of hosting, support, and additional services. Optional live streaming, for example, may introduce another platform with separate data flows and contractual requirements.

The institution must also identify an appropriate legal basis for each purpose. Depending on applicable law, a school or public authority may rely on a public task or legal obligation for certain activities. Consent should not automatically be selected, especially where pupils, parents, or employees may feel unable to refuse freely.

Consult your data protection officer and relevant national or regional education guidance. Assess whether a data protection impact assessment is required, particularly if the proposed use is likely to create a high risk to individuals. Provide accessible privacy information explaining what is collected, why, who receives it, and how long it is retained.

3. Set Clear Rules for Recording, Consent, and Retention

Recording changes the privacy implications of a meeting. A live discussion is temporary; a recording creates a persistent record that may capture faces, voices, names, presentations, and personal disclosures.

For schools and public institutions, recording should be a deliberate decision rather than an automatic default.

Before enabling it, establish:

  • A defined purpose: Explain why a recording is necessary and whether a less intrusive alternative would suffice.
  • An appropriate legal basis: Assess recording separately rather than assuming that permission to hold a meeting also covers recording it.
  • Clear advance notice: Tell participants what will be recorded, who may access it, and when it will be deleted.
  • Restricted access: Limit viewing and downloading to the intended audience.
  • A retention period: Set a justified deletion deadline and assign responsibility for enforcing it.

If consent is the chosen legal basis, it must be freely given, specific, informed, and unambiguous. Participants should be able to refuse or withdraw consent without inappropriate disadvantage. In educational settings, children’s rights, applicable national rules, and any relevant parental involvement require particular care. A recording notification or participation in a meeting is not, by itself, valid consent.

Using bbbserver.com’s recording capabilities as an example, institutions should verify what administrators can actually control. Can recording be disabled for particular rooms? Can access be restricted? Is automated deletion available, or will staff need a documented manual process?

Apply retention rules beyond recordings. Chat histories, attendance information, uploaded presentations, and service logs may also contain personal data. Confirm how deletion affects backups and whether downloaded copies remain outside the platform’s control.

4. Evaluate Collaboration Tools Through a Privacy Lens

Privacy-conscious procurement should still support effective teaching and public service delivery. A tool that is difficult to use may encourage staff to adopt unapproved alternatives.

bbbserver.com’s BigBlueButton-based offering illustrates how conferencing can combine practical features such as breakout rooms, screen sharing, and a collaborative whiteboard. The key is to evaluate these functions alongside their administrative controls.

Breakout rooms: Check how participants are assigned, what moderation options are available, and how staff can supervise activities appropriately. Establish rules against discussing sensitive individual cases in unsuitable group settings.

Screen sharing: Train staff to share a specific application window where possible, close unrelated documents, and disable notifications. A secure platform cannot prevent an accidental disclosure of pupil records or internal correspondence displayed on screen.

Whiteboards and presentations: Avoid unnecessary personal information in collaborative materials. Confirm whether content persists after the meeting and how exported or downloaded files should be handled.

Meeting access: Verify available controls for invitations, participant entry, moderator permissions, and removal of unwanted attendees. Use the controls appropriate to the meeting’s sensitivity and avoid publishing links intended for restricted groups.

Live streaming: Treat broadcasting as a separate use case from a closed conference. Check the destination platform, audience, participant notices, and legal basis before enabling it.

Device compatibility also matters. Test access from the PCs, Macs, tablets, and smartphones that staff and participants actually use. Include accessibility in the assessment so that privacy safeguards do not create unnecessary barriers to participation.

5. Test the Service and Establish Ongoing Governance

Before committing to a subscription, run a limited pilot using non-sensitive content. Include teaching or administrative staff, IT personnel, and the data protection officer in the evaluation.

For a service such as bbbserver.com, whose described subscription model is based on simultaneous connections rather than the number of conferences, assess peak demand. Several classes or departmental meetings running at the same time may require more capacity than the total number of scheduled sessions suggests.

A final procurement checklist should confirm that:

  • Hosting locations, access arrangements, and subprocessors are documented.
  • Security evidence has been reviewed within its actual scope.
  • The data processing agreement is suitable for the institution’s use.
  • Legal bases, privacy notices, and any necessary impact assessment are in place.
  • Recording and retention rules can be implemented reliably.
  • Collaboration tools, accessibility, and concurrent capacity have been tested.
  • Staff know how to configure meetings and report incidents.

Assign an owner for periodic reviews, including changes to subprocessors, service features, and institutional needs.

The objective is not simply to choose a platform advertised as privacy-focused. It is to establish a conferencing service whose contracts, configuration, and everyday use support the institution’s obligations. European hosting and certified data centers are valuable foundations; responsible governance turns those foundations into practical protection for pupils, staff, and citizens.