Frequently asked questions

It takes the access signal your existing turnstile produces and derives a live presence list, occupancy, a draft attendance sheet, parent notifications and an emergency roster from it. The turnstile, panel and reader stay where they are.

School administrators, teachers, security staff and parents; each role sees only its own scope.

If a turnstile and card reader are already installed, no. If not, you choose the company that will install them; we do not sell hardware.

No. Your existing turnstile and its panel stay in place; the product evaluates the signal they produce.

Wiegand, OSDP, dry contact and the vendor interface. What each of them cannot measure is listed one by one on the compatibility page.

No. The gate decision belongs to the panel and it keeps working with its local rules; we collect the passes from that window once the link returns.

Records held in the panel's own memory are collected when the link returns and marked as late arrivals; they are never dropped silently.

The list arrives pre-filled from the gate signal; the teacher does not fill it from scratch, they correct the difference and confirm.

Yes. Period-level attendance is kept alongside day-level attendance and partial absence is recorded with its time range.

No. Records collect in a queue, are corrected on screen, the user presses prepare and a batch is produced; a staff member enters it into the official system themselves and then marks the declaration.

It can, and the correction leaves a trail: the old value, the new value, who and when.

From the mobile app and the browser they do the same things: notifications, permission requests, the dismissal plan and the handover report.

If the institution wants it, the camera frame at the gate can be sent to the parent; this is a separate choice, not a default, and it is written in the privacy notice.

The parent opens the request in the app, the school decides, and the result lands at the gate and with the teacher; every step is recorded.

The parent defines the authorised person themselves and that person is verified at the gate; where a custody restriction exists, the restriction wins.

They all appear in one account and each notification carries the child's name.

No — and it is not offered as an option either. With decision 2026/921 dated 29 April 2026 the board banned processing biometric data for access and working-time tracking.

In the cloud or on the institution's own local network, as the institution prefers; the data belongs to the institution.

Retention and destruction periods are set from the institution's own admin screen; when the period ends the record is destroyed, not deactivated.

A parent sees only their own child, a teacher their own class, security that day's appointments, and the administration the whole institution.

You can; a data subject request is opened from the support form and answered in writing.

The moment an incident opens, presence is frozen; movement after that is kept separately and the two lists are never merged.

They can: they scan a code and several stations see the same list.

They run through the same flow; the duration is measured and the evidence record is used in the post-incident review.

Plans are built by opening scope, not by cutting features: the number of campuses, the modules enabled and the channel coverage change. Entry and exit notifications, late notifications and emergency information are never charged in any plan.

We define the scope together and in writing: which gates, which classes, who does what and when we review it.

The company installs the hardware, we provide the software layer; applications are open to everyone and the technical gate is the same for all.

The written channel is always open; response times vary by plan and are written into the contract.