Camera frames are processed locally and discarded.

Data processed while monitoring

• Camera frames supplied by the operating system.
• Face-presence confidence, selected facial blendshape values, and facial landmarks needed for blink, mouth, and posture signals.
• Runtime timestamps, cooldowns, and reminder state.

These values exist to run the current monitoring session. Camera frames and raw inference arrays are not written into the activity timeline.

Data stored locally

The 30-day timeline stores six factual event types:

• A detected complete blink.
• A detected yawn.
• The start and end of an observed screen interval.
• The start and end of a seated interval.

Preferences such as reminder switches, sedentary interval, monitoring windows, Lumi settings, and language are also stored locally so the app can restore your choices.

Data the app does not store

• Photos or recorded video.
• Screen contents, browser history, document text, or keystrokes.
• Raw face landmarks or biometric templates.
• Mouth-opening footage or posture calibration coordinates.
• A cloud identity, email address, or account profile.

When the camera runs

The camera can run when monitoring is enabled, the current time falls within an active monitoring window, the computer is awake and unlocked, and camera permission is available. Pausing monitoring, leaving the schedule, locking the screen, or putting the computer to sleep stops collection and releases the camera.

Hiding Lumi or the status widget does not imply that monitoring has stopped. The interface keeps those presentation controls separate from the monitoring switch.

Retention and deletion

Timeline events older than 30 days are removed automatically. Because the data is local, uninstall behavior can vary by operating system and whether the application profile is removed. A future account sync or cloud backup feature would require a new privacy design and is not part of the current product.

Security and preview-build limitations

Current public packages are unsigned preview builds. Code signing and notarization are still required before the download experience can provide normal operating-system publisher verification. Download only from the official GitHub repository and review the public source if you are unsure.

Inspect the source repository →