Privacy-Conscious Video Conferencing: A Procurement Guide for European Schools and Public Institutions

12.11.2026
Selecting a video conferencing platform requires more than European hosting or assurances of GDPR compliance. This guide helps IT administrators, data protection officers, and procurement teams assess contractual safeguards, recording retention, access controls, and the scope of ISO 27001 certification. Discover how to evaluate bbbserver.com through a documented pilot that aligns teaching and institutional meetings with your organisation’s operational and data protection requirements.

For European schools and public institutions, selecting a video conferencing platform requires more than comparing meeting features and subscription prices. Online lessons and institutional meetings may involve children’s personal data, confidential discussions, attendance records, chat messages, and recordings. IT administrators and data protection officers should therefore evaluate both the service provider’s safeguards and the institution’s intended use.

The first step is to document what information the platform will process and why. Consider participant names, email addresses, IP addresses, audio and video streams, shared documents, and technical logs. Identify which information is necessary for the service and which features could create avoidable data collection.

Your assessment should establish:

  • Purpose and lawful basis: Define the purposes of online teaching or institutional meetings and identify an appropriate legal basis under the GDPR. Public task or legal obligation may apply in certain contexts, depending on applicable law. Consent should not be treated as an automatic solution, particularly where participation is not genuinely optional.
  • Roles and responsibilities: Determine when your institution acts as controller and when the provider acts as processor. Check whether the provider processes any information for its own purposes.
  • Privacy by default: Prefer settings that minimise data collection, restrict unnecessary recording, and limit participant visibility where appropriate.
  • Risk assessment: Assess whether the proposed processing is likely to create a high risk to individuals and therefore requires a data protection impact assessment. Children’s involvement and sensitive discussions deserve particular attention.

A platform can support compliant operations, but it cannot determine your institution’s lawful basis, internal policies, or appropriate use on your behalf.

2. Verify European Hosting and the Data Processing Agreement

European hosting can simplify an institution’s data protection assessment, but server location alone does not establish GDPR compliance. Compliance also depends on lawful processing, transparency, contractual safeguards, security, retention, and respect for individuals’ rights.

The description “hosted in Europe” should be examined carefully. Europe is not identical to the European Union or the European Economic Area. Moreover, a platform’s primary servers may be located in one jurisdiction while backups, support services, or subprocessors operate elsewhere.

Ask prospective providers:

  • In which countries are live meeting data, recordings, logs, and backups processed?
  • Which legal entity supplies the service, and which subprocessors are involved?
  • Can support staff or other parties outside the EEA access personal data?
  • Where applicable, what mechanisms and assessments support international transfers?
  • How are customers notified of changes to hosting arrangements or subprocessors?

bbbserver.com describes its hosted BigBlueButton offering as using servers located in Europe. For procurement purposes, request confirmation of the specific locations and the processing arrangements covered by that statement.

Where a provider processes personal data on your institution’s behalf, an Article 28-compliant data processing agreement is essential. Check that it addresses documented instructions, confidentiality, security measures, subprocessor authorisation, and assistance with data subject requests.

The agreement should also cover assistance with security incidents and data protection impact assessments, audit information, and the return or deletion of personal data when the service ends. For personal data breaches, the processor must notify the controller without undue delay; your contract should establish practical notification channels and cooperation procedures.

Treat marketing statements about GDPR compliance as a starting point for verification—not a substitute for this review.

3. Examine Recording Retention and Access Controls

Recordings can support learning and provide useful meeting records, but they also create persistent copies of information that would otherwise be temporary. A recorded lesson may capture pupils’ voices, images, questions, chat contributions, or personal circumstances. Institutional meetings can expose similarly sensitive material.

Before enabling recording, establish a clear purpose and confirm that recording is necessary and proportionate. Inform participants about what will be captured, why it is being recorded, who can access it, and how long it will remain available.

Your recording checklist should include:

  • Default settings: Can recording remain disabled unless an authorised organiser enables it?
  • Permissions: Who can start recordings, publish them, download them, or share access?
  • Retention: Can retention periods reflect different purposes rather than applying indefinite storage?
  • Deletion: How are recordings removed from active storage, and when do backup copies expire?
  • Distribution: Can access be restricted to intended recipients, and what happens to downloaded copies?

Apply the same scrutiny to chat histories, uploaded presentations, attendance information, and technical logs. If automated deletion is unavailable, establish a documented manual process with a responsible owner.

Access controls should also be tested rather than inferred from a feature list. Verify how organisers authenticate, how participant roles are assigned, and whether guests can enter without appropriate checks. Assess available controls for admitting participants, restricting screen sharing, moderating microphones, and removing unauthorised attendees.

For administrators, ask about multifactor authentication, role separation, account revocation, and security logging. For participants, balance reliable access with data minimisation: requiring every pupil or guest to create a permanent account may not always be necessary.

Where live streaming is available, assess it separately from a restricted meeting. Broadcasting changes the potential audience and the risks of further distribution. It should not become an incidental extension of an ordinary classroom session.

4. Understand What ISO 27001 Certification Actually Covers

ISO/IEC 27001 certification provides evidence that an organisation operates an information security management system within a defined scope. It is a valuable assurance signal, but it does not establish GDPR compliance or guarantee that a service is free from security risks.

The scope matters especially when certification applies to a hosting facility rather than the video conferencing provider itself.

bbbserver.com’s supplied service description states that its data centres hold ISO 27001 certification. Your institution should verify that claim and establish which facilities, entities, and activities the certificates cover. A certified data centre may provide assurance about infrastructure operations without covering the provider’s application development, customer support, or platform administration.

Request and review:

  • The certificate holder’s legal name and the current certificate.
  • The validity dates and certification body.
  • The documented scope, including relevant facilities and services.
  • The division of security responsibilities between the hosting provider and the platform operator.
  • Evidence of controls outside the certificate’s scope.

Complement this review with questions about patching, vulnerability management, incident response, backups, and recovery testing. Ask how communications and stored recordings are protected, who controls encryption keys, and which parties can access data.

Do not assume that encrypted transport means end-to-end encryption. Providers should explain the actual protection model, including any processing needed for conferencing and recording.

5. Evaluate bbbserver.com Through a Documented Pilot

bbbserver.com offers a hosted platform based on the open-source BigBlueButton software, making it a relevant option for institutions seeking European-hosted conferencing for teaching and meetings.

Its described offering combines meeting scheduling, session recordings, and live streaming options with collaborative tools such as whiteboards, breakout rooms, and screen sharing. These capabilities can support structured lessons, group exercises, staff meetings, and administrative collaboration. Compatibility across computers, tablets, and smartphones can also accommodate varied institutional device environments.

However, features should be matched to approved purposes. Breakout rooms may support classroom work, while recording and streaming require additional decisions about audience, lawful basis, and retention. Open-source foundations can support technical scrutiny, but they do not replace an assessment of the hosted deployment.

The described subscription model is based on simultaneous connections rather than the total number of conferences. This may suit institutions running many sessions across a timetable. Confirm how connections are counted, how capacity limits are handled, and whether storage, recordings, or streaming introduce additional limits or charges.

Before procurement, conduct a pilot that tests both operational suitability and privacy controls:

  • Run representative lessons and meetings across supported devices.
  • Test organiser permissions, guest admission, and participant restrictions.
  • Create a test recording, restrict its access, and verify deletion procedures.
  • Review the data processing agreement, subprocessor information, and hosting evidence.
  • Confirm retention settings and the scope of relevant certifications.
  • Assess accessibility, user guidance, support arrangements, and peak-capacity needs.

Record the outcome in a decision document that identifies verified safeguards, unresolved questions, and institutional responsibilities. Involve the data protection officer, IT security team, procurement staff, and representative users.

The strongest choice is not simply a platform with European servers or a GDPR claim. It is a service whose contracts, technical safeguards, and everyday operation meet your institution’s documented requirements—and whose configuration you can continue to review throughout its use.