Privacy
Live location data about students carries duties that ordinary attendance data does not.
ProposedNot yet callable
This documents a design under review. Endpoints, payloads and field names may change before release.
Presence is not proof of attendance and must never be written into a permanent register on its own. Use the Attendance API for anything a student could be penalised by.
Retention
- Presence records expire automatically once a student has been gone for the grace period. They are not a location history.
- There is no endpoint to query where a student was yesterday. That is a deliberate design choice, not a missing feature.
- If you need a durable record that someone attended, that is an attendance record, and it belongs in the Attendance API.
Scoping
- Presence is scoped to spaces your institution operates. There is no cross-institution lookup of a person.
presence:readis a separate scope fromattendance:read. Grant it only to the systems that display live state, and never to a reporting key.- Prefer room-level queries to institution-wide ones. A dashboard showing occupancy does not need every student’s position.
Your obligations
Tracking where identifiable people are, in real time, is a materially different act from recording that they attended a class. In most education and data-protection regimes it needs its own lawful basis, its own notice to students, and often a documented assessment before you switch it on.
Onetap gives you the controls — scopes, room-level access, automatic expiry. It cannot give you the basis. Confirm your institution has one, and has told students plainly, before enabling live presence.
This is not legal advice. Your institution’s counsel or data protection officer should sign off on live presence before it reaches production.