Camera processing
Live camera frames are handled by on-device platform detection and immediately discarded. EyeJolt does not create a photo or video archive of monitoring sessions.
EyeJolt uses your camera as a live sensor during an active monitoring session. The strongest privacy promise is also the simplest: no camera frames are recorded, saved, or sent to EyeJolt.
Live camera frames are handled by on-device platform detection and immediately discarded. EyeJolt does not create a photo or video archive of monitoring sessions.
On supported iPhone and iPad models, EyeJolt uses the TrueDepth camera through Apple's ARKit face tracking to read only two live signals during an active session — eye-blink values and head position — to estimate drowsiness and trigger an alarm. This face data is processed entirely on your device in real time. It is never recorded, saved, or stored; it is never transmitted to EyeJolt or shared with any third party; and it is discarded the moment each frame is used. No face images, depth maps, or facial geometry are retained, and there is no EyeJolt account and no cloud face processing.
Settings, session summaries, selected alarms, and custom recordings are stored on your device. Session metadata does not contain face images.
The microphone is used only when you choose to record a custom alarm. The recording remains local unless you explicitly export it through the operating system share controls.
Core monitoring does not require an EyeJolt account. The released apps do not use a cloud face-processing service or sell personal information.
Written by the EyeJolt Editorial Team. Published and last reviewed 2026-07-29. Editorial policy.