Common Questions

The browser monitor is available from this website. The native iPhone app and optional Watch companion are available through private TestFlight invitations. A Home Screen browser icon still runs the website. Choose your setup path; a public App Store release is planned.

Camera frames are analyzed on your device. Supported monitoring does not record or upload camera video. Optional sharing sends selected summaries rather than camera frames; see the privacy and data controls.

Core local monitoring works without an account. Protected cloud and fleet features require sign-in and applicable sharing consent. Published fleet plans describe possible commercial options; they do not by themselves activate a subscription or payment.

The browser monitor needs camera permission and supported camera/graphics features. Safari on iPhone and Chrome on Android are the setup paths documented here. Compatibility and sustained monitoring vary by device, browser and conditions; there is no guarantee for every phone. The native iPhone pilot has its own installation requirements.

Lighting, mounting and eyewear affect tracking. Prototype observations and session scores are not validated accuracy measurements or proof that a driver is safe to continue. Occulert can miss events and produce false alerts. Review observations while parked; if you feel tired, stop safely and rest.

Keep camera monitoring visible in the foreground with the screen awake. Locking the phone or leaving the app can interrupt monitoring. An optional Watch notification is separate from camera analysis; check the displayed readiness or restart steps when you return while parked.

The browser downloads detection files from Occulert. Visit while online and let the offline bundle finish before trying cached startup. Browser storage can be cleared, so offline availability needs later confirmation on your device. Maps, cloud sharing and protected fleet records need connectivity. Native local monitoring and History do not require cloud sign-in.

Native History and browser History are separate local stores. The iPhone keeps up to 50 recent local summaries; use the available History filters and deliberate sharing controls. Recovered interrupted sessions are partial. An assessment is your observation, not an accuracy result. Native refinements reach installed users through TestFlight updates.

Native cloud summaries exclude location and alert assessments. Browser GPS is optional, and browser location sharing has separate consent requirements. Protected fleet browsing and exports exclude location and personal media. Review the location policy for each flow before enabling sharing.

Use password recovery and signed-in Account Settings on the website. An account created without a password needs a password before native password sign-in. Removing local history does not delete separately synced records; account deletion is a separate permanent action.

Live dashboard cards and recent history show up to 50 stored sessions. The separate 7-day or 30-day printable report states whether a fresh full-period server result is available; treat it as partial unless that coverage is confirmed. Older History loads up to 50 per request and at most 500 records in the browser. Its filters, CSV and printing cover only loaded records. No report can count a session that was never synced. Protected values are unverified client reports.

You can compose a message to hello@occulert.com in your own email app. Opening a feedback draft does not send it. New native updates provide an explicit share-draft fallback when Mail is unavailable. See support for useful details to include.