Role-Based Access
Not every user sees every student, every movement event, or every diagnostic record.
Trust Center
Privacy, governance, and school-control boundaries.
Valkor collects operationally justified data, explains why it exists, restricts access, logs sensitive actions, supports school-controlled retention, and avoids unrelated uses like advertising, consumer tracking, or automatic discipline.
What Valkor collects and why
Depending on deployment scope, Valkor may process badge identifiers, zone-level movement events, timestamps, confidence/freshness status, pass status, device health, incident workflow records, admin actions, audit logs, diagnostics, and pilot metrics.
Approved school operational awareness
Attendance and accountability review
Device-health and reliability monitoring
Incident documentation and staff response
Pilot evaluation and system improvement
School-controlled deployment
Included zones
Approved badges
Authorized users
Retention rules
Approved use cases
Parent communication
Pilot approval and expansion decisions
Access, audit logs, and retention
Audit Logs
Sensitive actions such as viewing restricted records, changing badge assignments, exporting data, acknowledging incidents, dismissing incidents, and resolving alerts should be logged.
Retention & Deletion
Schools define how long live events, incident records, audit logs, historical tracks, diagnostics, and pilot metrics are retained.
Clear product boundaries
No GPS
No home tracking
No microphones
No cameras
No facial recognition
No biometrics
No student phone monitoring
No automatic discipline
Does not replace emergency procedures or trained staff judgment
Valkor supports human-reviewed workflows. School personnel verify facts and decide what action is appropriate.
Signal infrastructure boundary
Valkor may integrate with approved RTLS infrastructure providers, such as Blueiot/LocalSense, to receive building-local location, badge, zone, device-health, attendance, roll call, historical track, and alarm signals. The infrastructure provider supplies the physical positioning layer; Valkor provides the school-facing command, workflow, privacy, and reporting layer.
Parent-facing explanation
Valkor is designed around approved school operations, zone-level presence, authorized staff access, school-controlled retention, and human-reviewed workflows. It does not require GPS, phone tracking, cameras, microphones, biometrics, or automatic discipline.
IT/security review questions
Which zones are included in the pilot?
Which badges are approved and who manages assignment?
Which users can see live status, history, diagnostics, exports, and audit logs?
How long are live events, incidents, diagnostics, historical tracks, audit logs, and pilot metrics retained?
How are stale data, offline anchors, low-battery tags, feed delays, and parser failures displayed?
What data can be exported or deleted at school request?
Request a limited pilot review.
Pilot reviews cover operational pain points, privacy and governance boundaries, infrastructure readiness, pilot scope, reliability expectations, success metrics, and end-of-pilot reporting.