Beyond European Hosting: Five Checks for Choosing Institutional Video Conferencing

20.11.2026
European schools and public institutions need more than a European server address to assess a video conferencing platform. This guide helps IT managers, data protection officers, and procurement teams evaluate data flows, contractual safeguards, security evidence, recording controls, collaboration tools, and peak connection capacity. Using bbbserver.com’s BigBlueButton-based offering as a practical reference, it outlines how to make a procurement decision grounded in verified commitments and tested capabilities.

For European schools and public institutions, procuring a video conferencing platform requires more than comparing features and subscription fees. IT managers and data protection officers must establish where personal data goes, who can access it, and whether the service supports the institution’s legal and operational obligations.

European hosting is a valuable starting point, but server location alone does not establish GDPR compliance. A service may host meetings in Europe while relying on support teams, subprocessors, or ancillary services elsewhere. Meeting content is also only one part of the picture: account details, usage logs, recordings, and support requests may follow different processing paths.

Ask prospective suppliers to provide a documented data-flow overview covering:

  • Hosting locations: Identify the countries used for live meeting infrastructure, recordings, backups, and disaster recovery.
  • Subprocessors: Request a current list of providers involved in hosting, support, analytics, and other processing activities, including their locations.
  • Remote access: Establish whether personnel outside the European Economic Area can access personal data and under what conditions.
  • International transfers: Where applicable, examine the transfer mechanism and any necessary assessments and supplementary safeguards.
  • Service telemetry: Determine what diagnostic information is collected, why it is needed, and how long it is retained.

bbbserver.com describes its infrastructure as European-hosted, making it relevant to institutions seeking a privacy-focused alternative. Procurement teams should nevertheless confirm the exact locations and processing arrangements in the contractual documentation. “Europe” and “the European Economic Area” are not interchangeable terms.

The institution must also identify an appropriate lawful basis for its own processing. This is particularly important in educational settings, where participation may be required and consent may therefore be inappropriate as a default basis.

2. Examine the Data Processing Agreement and Security Evidence

A supplier’s privacy statements should be supported by enforceable commitments. Where the provider acts as a processor, the institution should obtain and review an Article 28 GDPR data processing agreement before deployment.

The agreement should clearly describe the subject matter and duration of processing, its nature and purpose, the categories of personal data, and the groups of people affected. For schools, these groups may include pupils, parents, teachers, and external specialists; for public institutions, they may include employees and members of the public.

The procurement checklist should cover:

  • Processing only on documented instructions, with appropriate confidentiality commitments.
  • Technical and organisational security measures proportionate to the risks.
  • Subprocessor authorisation arrangements and notification of changes.
  • Assistance with data subject requests, security incidents, and data protection impact assessments.
  • Notification of personal data breaches without undue delay, supported by practical escalation procedures.
  • Return or deletion of personal data when the service ends, subject to applicable legal requirements.
  • Access to information needed to demonstrate compliance and appropriate audit arrangements.

Assess whether a data protection impact assessment is required, particularly where proposed uses involve vulnerable individuals, systematic monitoring, or other processing likely to create high risks.

Security certification deserves equally careful scrutiny. bbbserver.com states that its data centres hold ISO 27001 certification. This is relevant evidence, but a certified data centre does not automatically mean that the conferencing application or the supplier’s entire operation is certified.

Request the current certificate and scope statement. Check the certified legal entity, covered locations and services, validity period, and certification body. Establish whether application development, operational administration, customer support, and incident management fall within the scope or require separate evidence.

ISO 27001 concerns an information security management system within a defined scope. It is neither a guarantee against breaches nor a substitute for GDPR assessment.

3. Set Rules for Recordings, Access, and Meeting Participation

Privacy protection depends on configuration and daily practice as much as procurement documentation. A suitable platform must support the institution’s rules without placing unreasonable demands on teachers or administrative staff.

Start with recording governance. Recordings can capture voices, faces, names, chat messages, shared screens, and sensitive discussions. Their educational or administrative value should be weighed against the additional privacy risks.

Before enabling recordings, establish:

  • Purpose and authority: Define which meetings may be recorded, why recording is necessary, and who can authorise it.
  • Participant information: Explain the purpose, lawful basis, access arrangements, and retention period before recording begins.
  • Access restrictions: Limit playback and downloads to authorised users rather than relying solely on an unlisted link.
  • Retention and deletion: Specify retention periods by use case and verify whether automatic expiry is available.
  • Backup treatment: Clarify when deleted recordings disappear from backups and how restoration avoids unintended reintroduction.
  • Disclosure and export: Establish procedures for lawful requests, controlled sharing, and contract termination.

Do not assume the advertised availability of recording includes automated retention controls or detailed access logging. Ask for a demonstration of the precise workflow.

For live meetings, assess authentication, moderator permissions, guest access, room-entry controls, and the ability to restrict screen sharing or remove disruptive participants. Verify whether administrative accounts support multi-factor authentication and whether institutional sign-on is available if required.

Also ask how meeting traffic and stored data are encrypted. Transport encryption should not be confused with end-to-end encryption; require an explanation of who can technically access content, particularly when recording or streaming is enabled.

Define separate configurations for classroom teaching, confidential internal meetings, and public events. A livestream intended for broad distribution should not inherit the same settings as a pupil support session.

4. Test Collaboration Tools Against Real Institutional Workflows

A privacy-first platform must still enable effective teaching and public service delivery. Otherwise, staff may adopt unapproved alternatives, undermining the controls procurement teams have established.

bbbserver.com is based on the open-source BigBlueButton platform and offers collaboration capabilities including whiteboards, breakout rooms, and screen sharing, alongside meeting scheduling, session recordings, and live streaming options. These can support different institutional activities:

  • Teaching: Whiteboards and breakout rooms can facilitate guided exercises and small-group learning.
  • Administration: Scheduled conferences and screen sharing can support staff coordination, training, and document review.
  • Public communication: Live streaming may support events intended for wider audiences, provided publication and platform arrangements have been assessed.
  • Asynchronous access: Recordings can support later review where a justified recording policy is in place.

Open-source foundations offer opportunities for transparency, but they do not by themselves establish the security of a hosted service. Ask how the provider handles updates, vulnerability remediation, and changes to its deployed software.

Run a pilot with representative teachers, administrators, and participants. Test supported browsers and devices, including PCs, Macs, tablets, and smartphones. Assess accessibility, keyboard navigation, assistive technology compatibility, and performance on constrained networks.

For streaming, establish whether an external destination introduces additional recipients, subprocessors, or international transfers. Treat each enabled integration as part of the assessment rather than assuming it inherits the core service’s privacy properties.

5. Plan Capacity and Make Approval Evidence-Based

bbbserver.com’s subscription model is based on simultaneous connections rather than the number of conferences. This allows institutions to organise multiple sessions within a purchased connection capacity and can support predictable budgeting across departments.

The key planning metric is peak concurrent demand, not total enrolment or the number of meetings scheduled during a month. For example, six simultaneous classes with 25 pupils and one teacher each would require 156 connections, assuming each participant uses one connection. Additional staff meetings, support personnel, or duplicate device connections would increase that demand.

Before selecting a plan, confirm:

  • How connections are counted, including moderators and participants joining from multiple devices.
  • Whether there are separate per-room limits or recommendations.
  • What happens when the contracted capacity is reached.
  • Whether temporary increases are available for predictable peaks.
  • Whether recordings, storage, streaming, and support carry separate limits or charges.
  • What service availability, incident response, and support commitments apply.

Build headroom around timetable overlaps, examination periods, staff training, and large events. A simultaneous-connection model can reduce the need to budget by individual licence, but predictability depends on understanding both usage patterns and contractual limits.

Complete procurement with an evidence-based approval record. Document the verified hosting arrangements, accepted data processing agreement, security evidence, recording policy, access-control settings, pilot findings, and capacity assumptions. Record unresolved issues and assign responsibility for reviewing them.

bbbserver.com’s European-hosted, BigBlueButton-based offering may align well with these requirements. The final decision should rest on confirmed contractual commitments and tested capabilities—not hosting geography or certification labels alone.