Security and data protection
Written for the IT manager and the data protection officer. Every line describes how Viafocus works today.
A data processing agreement under GDPR Art. 28 is signed before any pilot starts.
Version 1.2 · Last updated 15 October 2026
The pupil's device
Never leaves the device
- Keystrokes
- Passwords
- Cookies
- Camera
- Microphone
- History
Viafocus
- DatabaseGermany
- Sign-inGermany
- ServersNetherlands
- Web appStockholm
- AIEU
Holds class lists and the live lesson. History only if the school turns it on.
The teacher's dashboard
Sees
- Pupils in their own classes
- During school hours
- Nothing from other schools
- Screen images only while a teacher watches
- The pupil sees when it happens
- Servers and databases in the EU
- DPA signed before the pilot
01What Focuspilot sees
The same list the pupil sees. Open the Focuspilot extension on any school device and it shows what is collected. This page says nothing more and nothing less.
Collected while the computer is connected
The tab in front
Its address and title. Titles of tabs playing sound and of windows in the background. When the teacher enlarges a pupil: all open tabs.
Status
Active, idle or away, and whether sound is playing.
Blocked attempts
The site and the count, when a pupil tries a page the lesson does not allow.
Screen images in live view
Only while a teacher has the pupil in view, as a thumbnail or full size. The tab on Chromebook, the screen on Windows. They are never stored.
Device basics
Platform, app version and when the device was last connected.
The school account
The pupil's school email and the school's ID.
Never collected
Keystrokes
Nothing the pupil types is read or sent.
Passwords and cookies
Never read or sent.
Camera and microphone
No permission is requested. Sound is never recorded.
Browsing history
No permission is requested. We never save which websites or apps a pupil used.
Screen recording
Screenshots are shown live and never stored.
Mood, attention or ability scores
No inference about the pupil. The teacher looks, and the teacher decides.
02When
Activity while the computer is connected. Screen images while a teacher watches. A connected computer sends which page is open. Only the latest is kept, so the teacher's view fills in at once, and it is deleted when the computer disconnects. It is never saved to a database.
The teacher watches.
Screenshots are sent only while a teacher has the pupil in view, and stop when the teacher stops looking.
The pupil can see it.
The pupil always sees when the teacher is looking: a green dot on the Focuspilot icon in Chrome, and a message and a tray icon on Windows.
School hours apply.
Access to the dashboard follows the school's calendar. The school switches on sleep outside school hours once its school hours are set, and then no activity is sent.
03Where it lives
Named providers. Named places. Not "a leading cloud provider". The systems that hold school data are on one list, by name and place.
See the full list of sub-processors
Vendor, what it does for us, where the data lives, whether it leaves the EEA, and the legal mechanism.
Support for the school's impact assessment (DPIA)
Each item of data with its purpose and retention, and a template to fill in.
04How it is protected
Verified people. Verified devices.
Every request passes four checks before any pupil data moves.
- Check 01
Who are you?
Google, Microsoft or a one-time email code. No passwords to steal.
sign-in · run by us, inside the EU
- Check 02
Which school?
Database queries are scoped to the school automatically.
school data stays in the school
- Check 03
Which device?
Chromebooks are verified through Google and Windows computers through Microsoft. Once the school has connected its account, unverified devices are refused.
managed devices only
- Check 04
Which role?
Six roles, from pupil to administrator. The role you are acting in decides what you can reach, not the roles you hold.
one role at a time
Encrypted on the way.
All traffic is encrypted. Databases and file storage are encrypted at rest.
Mode changes are on record.
Which teacher set which mode for which class or group, and when.
What the data protection officer asks first.
See all questions ↓Who is the controller?
The school. Viafocus AB is the processor and acts on the school's instructions. A data processing agreement under GDPR Art. 28 is signed before a pilot starts.
What is the legal basis?
For Swedish schools, a task in the public interest (uppgift av allmänt intresse). It supports the school's duty under skollagen chapter 5 to maintain trygghet och studiero.
Is it high-risk under the EU AI Act?
No. Viafocus does not assess learning outcomes, decide access to education or infer emotions. The teacher makes every decision, so it falls outside Annex III point 3.
Do you hold ISO 27001 or SOC 2?
No, not today. Instead you can audit us directly: the data processing agreement with Annex 1 on security measures, the open sub-processor list and the DPIA material. Under the agreement, the school or an auditor it appoints may check that we comply.
05How long
Short by default. The school decides how much history exists at all.
Off
Activity history. No history is kept until the school switches it on. Then only mode changes and when the pupil connected are kept, never which websites or apps the pupil used.
90 days
Default once it is on. The school sets 7 to 365 days.
Never
Screen images. They are shown live to the teacher and are not stored. The school can switch them off entirely.
All of it
On deletion. When an account or a school is removed, its data is deleted from every part of the service.
Yes, while the teacher has the pupil in view, the teacher sees still images of the pupil's screen. The pupil always sees when this happens. The images are never stored, and the school can switch them off.
No. Nothing typed is read or sent, and passwords and cookies are never read. The extension has no permission for the camera or the microphone.
A school computer that is on and connected sends which page is open, also at home. Only the latest is kept, and it is deleted when the computer disconnects. The school switches on sleep outside school hours once its school hours are set, and then no activity is sent.
The school. Viafocus AB processes it on the school's instructions under a data processing agreement, signed before a pilot starts.
No. Pupil data is never sold and never used for ads. It is used to run the service for the school and for nothing else.
All AI runs within the EU (Microsoft Azure), including the teacher's assistant that reads the class overview, and Microsoft does not train models on it. A school can use its own AI key with a provider it has its own agreement with; the questions then go there.
Delete the account or the whole school, and the data is deleted from every part of the service. Paid accounts are deleted at the end of the period, pilots at once.
Write to security@viafocus.net. A person reads it, and you get a reply.
Change history
Passwords and cookies: the page now says they are never read, instead of saying the extension has no permission to read them.
You sign with
Viafocus AB
Org. number
559547-4882
Based in
Göteborg, Sweden
Data protection contact
Adam Almasri, CEO · dataskydd@viafocus.net
Send this page to your data protection officer.
Then ask us for the agreement. It is signed before the pilot starts.