Privacy-First Video Conferencing: A Procurement Checklist for European Schools and Public Institutions
08.11.2026Selecting a video conferencing platform requires more than European hosting and security certification. This practical guide helps school leaders, IT administrators, procurement teams and data protection officers assess legal bases, data processing agreements, recording policies and access controls. Discover how to evaluate providers such as bbbserver.com and establish an evidence-based procurement process that supports GDPR obligations throughout the service lifecycle.
For European schools and public institutions, selecting a video conferencing platform is a data protection decision as well as an IT procurement exercise. Online lessons, administrative meetings and public consultations may involve children’s personal data, confidential discussions or sensitive information. A privacy-first evaluation must therefore consider how the service will be used—not simply which features it offers.
Begin by documenting the intended activities and the personal data they require. This may include participant names, email addresses, IP addresses, chat messages, audio, video and session recordings. Distinguish information needed to deliver the service from optional collection, such as analytics or recordings.
Your institution must identify an appropriate legal basis for processing. Depending on the activity and applicable national law, this may be a public task or a legal obligation. Consent should not be treated as the default: in schools and public-sector settings, individuals may have limited freedom to refuse, making valid consent difficult to establish.
Initial evaluation checklist:
- Define the purpose of each conferencing use case.
- Identify the participants and data categories involved.
- Document the legal basis and any additional conditions required for processing special-category data.
- Assess whether less intrusive options, such as joining without a camera, can meet the same purpose.
- Determine whether a data protection impact assessment is required, particularly where processing is likely to create high risks.
- Prepare clear privacy information, using age-appropriate language where children are involved.
This groundwork provides the criteria against which providers should be evaluated. A platform can support compliant processing, but it cannot determine every legal or organisational requirement on your institution’s behalf.
2. Examine European Hosting and Security Certification Carefully
European hosting can simplify data protection due diligence by reducing some international-transfer risks. However, “hosted in Europe” is not a complete answer.
First, establish the exact countries in which data is processed. Europe is a geographic region, while the European Economic Area is a specific legal area relevant to GDPR transfer rules. Hosting outside the EEA requires a separate assessment of applicable transfer arrangements, even if the location is geographically European.
Second, investigate the full service chain. Video streams may remain in one country while backups, support tickets, diagnostic logs or analytics are processed elsewhere. Access by a separate support provider outside the EEA may also raise international-transfer considerations.
According to the supplied service information, bbbserver.com hosts its servers in Europe and uses ISO 27001-certified data centres. These are relevant starting points for schools and public institutions seeking a privacy-focused BigBlueButton service. Procurement teams should nevertheless request current evidence of the specific hosting locations and the scope of certification.
ISO 27001 concerns an information security management system. It provides useful assurance about systematic security risk management within a defined scope. However, a data centre’s certification does not automatically cover the conferencing provider’s application, support operations or your institution’s configuration.
Hosting and certification checklist:
- Confirm the locations of primary hosting, backups and disaster recovery systems.
- Identify where logs, account data and support information are processed.
- Check which organisations can access data and from which countries.
- Assess any international transfers and the safeguards required.
- Request a current ISO 27001 certificate and examine its scope.
- Review application-level security, patching, encryption and incident response separately.
Neither European server location nor ISO 27001 certification establishes GDPR compliance on its own. Compliance also depends on lawful processing, transparency, contractual safeguards, retention policies and effective operational controls.
3. Require a Clear Data Processing Agreement
Where a provider processes personal data on your institution’s behalf, an Article 28 GDPR data processing agreement is a central procurement requirement. It should describe the actual service and responsibilities—not merely make a broad promise to “follow GDPR.”
Your institution will generally act as controller for its educational or administrative conferencing activities. The provider will typically act as processor for delivering those services. However, roles should be checked for each activity, particularly if the provider uses any information for its own purposes.
The agreement should specify the subject matter and duration of processing, its nature and purpose, the types of personal data and the categories of data subjects. It must also address confidentiality, security, subprocessors and assistance with your institution’s obligations.
For a platform such as bbbserver.com, request the agreement and associated technical and organisational measures before uploading participant information or starting a pilot involving personal data.
Contractual checklist:
- Does the provider process personal data only on documented instructions, including instructions concerning transfers?
- Are staff confidentiality obligations and security measures clearly addressed?
- Is a subprocessor list available, with an authorisation process and notice of proposed changes?
- Will the provider assist with access, erasure and other data subject requests?
- Does it support impact assessments and relevant regulatory consultations?
- Must it notify your institution of personal data breaches without undue delay?
- Are audit rights and access to compliance information included?
- Can personal data be returned or deleted at the end of the service, subject to applicable legal storage requirements?
Incident procedures deserve particular attention. A processor’s notification must enable the controller to assess its own obligations, including the GDPR’s 72-hour supervisory-authority notification deadline where applicable. Agree on operational contacts and the information the provider will supply during an investigation.
4. Control Recordings, Retention and Participant Access
Recordings create a lasting copy of information that might otherwise exist only during a live session. In a classroom, that copy could include pupils’ voices, images, names and contributions. In a public institution, it could capture confidential case details or internal deliberations.
Recording should therefore be a deliberate decision with a defined purpose, rather than a routine default. Evaluate recording and live streaming separately: broadcasting a session to a wider audience introduces disclosure risks beyond those of a restricted meeting.
The supplied description of bbbserver.com includes scheduling, recording and live streaming options alongside BigBlueButton collaboration tools. These capabilities may be valuable, but their availability should be matched with appropriate restrictions. Ask the provider to demonstrate the available controls rather than assuming every required setting exists.
Recording and retention checklist:
- Disable recording by default where it is unnecessary.
- Limit recording permissions to authorised roles.
- Inform participants in advance about purpose, access and retention.
- Define a justified retention period for each recording category.
- Apply retention rules to chats, attendance records and logs as well.
- Check how deletion works across active storage and backups.
- Restrict downloads and onward sharing where supported and appropriate.
- Identify who is responsible for deleting exported copies.
There is no single GDPR retention period for all conference recordings. Retention must reflect the purpose and applicable legal obligations, with periodic review to prevent indefinite storage.
Access controls are equally important. Invitations and meeting links should not provide unrestricted entry to sensitive sessions.
Access-control checklist:
- Require authenticated access where justified by the session’s sensitivity.
- Use admission controls or waiting rooms where available.
- Separate administrator, moderator and participant permissions.
- Restrict screen sharing, uploads and other disruptive capabilities as needed.
- Protect privileged accounts with multifactor authentication where supported.
- Remove access promptly when staff leave or responsibilities change.
- Review administrative activity without collecting excessive monitoring data.
Test these controls with realistic scenarios, including an accidentally forwarded invitation, an unauthorised recording attempt and a departing administrator.
5. Turn the Checklist into an Ongoing Procurement Process
A privacy-first selection process should produce evidence, not just a favourable product comparison. Maintain an assessment record covering legal basis, data flows, contractual terms, security measures, retention settings and unresolved risks.
bbbserver.com is a relevant candidate for institutions seeking a European-hosted service based on the open-source BigBlueButton platform. Its stated collaboration features and subscription model based on simultaneous connections may also suit organisations running multiple lessons or meetings. These operational benefits should be assessed alongside, rather than substituted for, data protection requirements.
Before committing, conduct a controlled pilot. Use test data initially, verify the joining experience across relevant devices and confirm that privacy settings are understandable to staff. Involve IT administrators, the data protection officer, procurement personnel and representatives of the intended users.
Final approval checklist:
- Obtain and review the data processing agreement and subprocessor information.
- Verify hosting claims and certification scope.
- Complete the necessary risk and transfer assessments.
- Test access restrictions, recording permissions and deletion procedures.
- Publish appropriate privacy notices and internal usage guidance.
- Train moderators and administrators.
- Schedule periodic reviews and reassessment after significant service changes.
The objective is not to find a platform whose marketing language removes your institution’s responsibilities. It is to select a provider whose architecture, contracts and controls enable you to meet them—and to maintain those safeguards throughout the service’s use.