Most classroom display tenders are not lost on price or on specification. They stall in the ministry's IT security review, weeks after the technical evaluation is complete. The questionnaire is usually the same: where does student data go, who holds the accounts, what does the device send back to the manufacturer, and can the ministry manage the estate without a vendor cloud. Suppliers who can answer those questions with documents rather than assurances get through. This guide sets out what ministries across the GCC and Africa ask, and how to answer it.
Quick reference: the six questions that decide approval
- Data residency: where is any student or usage data stored, in which country, under which law?
- Account provisioning: do pupils and teachers need vendor accounts, or can the ministry use its own identity system?
- Device management: can the estate be managed on-premise, or does it require the manufacturer's cloud portal?
- Telemetry: what does the panel send to the manufacturer by default, and can it be switched off verifiably?
- Offline capability: does the teaching function still work with no internet?
- Lifecycle: what happens to stored data when a panel is repaired, redeployed or disposed of?
Data residency and what actually gets stored
Start by establishing what data exists at all. A panel used purely for annotation and local file playback may store nothing about a pupil beyond a filename. A panel running a cloud whiteboard, a class management app or a screen-sharing service with named sessions may store a great deal more, in a region the ministry has not approved. The answer that passes review is a written data map: what is collected, where it is processed, where it is stored at rest, and how long it is retained.
Many GCC ministries now require that education data remains in-country or within an approved region, and several African ministries apply similar conditions through their data protection authorities. Where the manufacturer's platform cannot meet this, the practical route is to disable the cloud services and run the panel with local storage and the ministry's own platform, which most commercial panels support. Specify that route explicitly in the tender rather than discovering it during review.
Accounts, identity and who pupils sign in as
Ministries do not want to create a second identity estate. The strong answer is that the panel supports the ministry's existing identity provider, or that it requires no per-pupil account at all. Panels that force a vendor account for each teacher, with an email address and a password held by the manufacturer, create an ownership and offboarding problem that IT security teams correctly object to.
Ask bidders three precise questions: whether the panel can operate with a single shared device account rather than per-user accounts; whether it supports the ministry's identity system for teacher sign-in where sign-in is wanted; and what happens to a teacher's stored content when they leave. EDLA-certified Android panels handle Google-based identity cleanly where a ministry already uses Google for education, but the certification is about the presence of licensed services, not about where data lands, so it does not answer the residency question on its own.
Device management: on-premise or not at all
A ministry deploying several thousand panels needs to push firmware, lock settings and see device health. The question is whether that can be done without routing the estate through a manufacturer's cloud. The best answer is an on-premise management server under the ministry's control. The acceptable answer is a management platform hosted in an approved region with a contractual data processing agreement. The answer that usually fails is a consumer-grade cloud portal with no agreement and no regional choice.
Where the panel's own platform cannot meet this, the standard workaround is to manage the compute rather than the panel: fit a slot-in module from our OPS PC and compute range, apply the ministry's existing workstation image and management tooling to it, and lock the panel's built-in Android down to a display function. This is the same architecture we describe for secure sites in our guide to defence and police academy procurement, and it is well understood by ministry IT teams because it reuses controls they already operate.
Telemetry and the default-on problem
Commercial panels commonly send usage analytics, crash reports and firmware check-ins to the manufacturer by default. Most ministries will accept firmware check-ins and reject behavioural analytics. The requirement to write into the tender is a statement of every outbound connection the device makes in its default state, the purpose of each, and which can be disabled, with confirmation that disabling them does not void the warranty or disable a needed function.
Then verify it. A competent ministry network team will put a sample panel on a monitored segment during evaluation and watch what it talks to. Suppliers should expect this and should be able to predict the result. Discovering an undeclared connection during evaluation is usually fatal to a bid.
Offline operation and lifecycle
Ask whether the teaching function survives a connectivity failure, because in much of the region it will. Whiteboarding, annotation over any source, playback of stored lessons and local save should all work with the network down. This matters for continuity, and it also strengthens the privacy position: a panel that does not need a connection to teach is a panel that can be run on a closed network.
Finally, close the lifecycle. Specify how storage is wiped before a panel is repaired off site, redeployed to another school or disposed of at end of life, and require a certificate of erasure where a drive leaves ministry control. Our guide to end-of-life and asset disposal covers the physical side; the data side belongs in the same policy. Getting all of this into the technical schedule at tender stage, rather than answering it later, is what keeps an education rollout on programme, as our tender-ready guide sets out.
FAQ
Do interactive panels store student data?
It depends entirely on configuration. A panel used for annotation and local playback may store almost nothing. A panel running cloud whiteboarding, class management or named screen-sharing sessions can store considerably more, potentially outside the country.
Can a ministry manage panels without the manufacturer's cloud?
Often yes. Either through an on-premise management server, or by managing a slot-in OPS module with the ministry's existing workstation tooling and locking the panel's built-in platform down to a display function.
Does EDLA certification answer the data residency question?
No. EDLA certification concerns the presence of licensed Google services on the panel. It does not determine where data is stored or under which jurisdiction, so residency must be established separately.
What telemetry do panels send by default?
Commonly firmware check-ins, crash reports and usage analytics. Ministries generally accept firmware check-ins and reject behavioural analytics, so require a declared list of outbound connections and confirmation that each can be disabled.
Should teaching still work offline?
Yes. Whiteboarding, annotation, stored lesson playback and local save should all function with no connectivity, both for continuity and because it allows the estate to run on a closed network.
Preparing a ministry-scale classroom display programme? Request a quote from Smart-Boards.com and browse our interactive flat panels and OPS PC and compute range.