Help and support
Setup guidance for the iPhone app, optional Watch companion and website.
Configure or troubleshoot while safely parked. Camera monitoring requires Occulert to remain in the foreground. If you feel tired, pull over safely and rest, whether or not an alert appears.
Account and sign-in problems
I cannot sign in to the iPhone app
- Use the email address for your existing Occulert driver account. Local monitoring and History remain available without signing in.
- If you created an account with an email link or passkey and have no password, use password recovery to set one before native password sign-in.
- For a temporarily unavailable cloud-status message, retry while connected. Do not clear local history to fix a sign-in problem.
I need account or cloud-data controls
Open signed-in Account Settings in your browser. Browser sign-in is separate from iPhone sign-in. Local deletion and permanent account deletion are separate actions; review each confirmation before continuing.
Camera setup and interruptions
- Secure the phone before starting and keep your face and eyes visible to the front camera. Improve lighting or reposition the phone while parked if tracking is unavailable.
- If camera access is denied, allow it in iPhone Settings for the native app, or in your browser and website permissions for the web app. Return to Occulert and repeat the parked setup.
- Leaving the app, locking the phone or losing camera analysis can stop monitoring. Return while parked and follow the displayed setup or restart instructions; do not assume monitoring resumed.
- If a browser page cannot finish loading, reconnect and reload. Avoid clearing browser storage as a first step: doing so can remove locally saved history.
The iPhone app and browser app are separate. Installing a website update does not update the iPhone or Watch app.
Phone and Watch alerts
Phone sound and vibration
While parked, review Occulert's sound and vibration preferences, the phone's volume and audio output, and any connected headphones or car audio. Browser sound and vibration availability varies by device. An enabled preference does not guarantee an alert will be heard or felt.
Optional Watch companion
Confirm the companion app is installed on the paired Watch. Open it and review the phone app's Watch setting, connection status, notification permission and Focus settings. A connection reply confirms receipt; it does not prove that a notification appeared or a vibration was felt. Tell support separately what appeared and what you felt, including whether the Watch app was open or in the background.
The iPhone is the primary alert device. Watch alerts may be delayed or unavailable. You can use core camera monitoring without a Watch, headphones or Apple Health access.
Session history and privacy controls
- In the iPhone app, open Session History to review up to 50 recent local summaries. Share the summaries you intend to keep before older records roll off. Settings → Privacy & Local Data provides history and recovery-data controls.
- Browser history belongs to the browser and device where it was saved. It is separate from native history and protected fleet records.
- A recovered interrupted session is a partial record, not a completed drive. Missing values are not measured zeroes.
- If saving fails, follow the displayed retry or recovery guidance. Before removing local data, review or share the summaries you intend to keep.
- Deleting local history does not delete separately synced cloud records. Signed-in account and cloud-data controls are on the website's Account Settings page.
Fleet invitations and older sessions
Accept the invitation from your fleet owner using the intended account. If the invitation has expired or was already used, ask the owner for a new one. Drivers must choose whether to enable cloud sharing; a local session alone does not establish a synced fleet record.
Managers should sign in as the fleet owner to see protected records. Live dashboard cards, the recent-session list and the shared TV view summarize up to 50 recent sessions. Browse older sessions opens a separate view that loads up to 50 at a time, with a limit of 500 loaded records.
The 7-day and 30-day printable report has its own coverage message. When it confirms a fresh full-period server result, that report includes all stored sessions in the selected window; otherwise treat it as partial. It cannot count sessions that were never synced. Protected history requires a connection and clears when the account or page changes. History filters, CSV and printing still cover only the records loaded and selected in this browser. Session scores and counts are unverified client reports.
Contact Occulert
Email hello@occulert.com for help, feedback, or assistance locating a data control. Opening the email link does not send a message; review the details before sending. If no email app opens, compose a message in your usual email service. Updated iPhone builds also offer a separate Share draft choice after Mail fails; you choose the destination and whether to send.
For trial planning, roster scope or a proposed paid plan, email fleet@occulert.com. A trial request or plan discussion does not activate service or begin billing.
Useful details to include
- Whether you used the iPhone app or website, and the app version/build or browser version.
- Your phone model and operating-system version. If a Watch is involved, include its model and watchOS version.
- What you expected, what happened, any displayed error text and the steps leading to it.
- For an alert issue, whether the app was open or in the background and the audio route or Focus setting used.
No passwords, verification codes, face images, camera video, audio, precise locations, Health records or private fleet exports are needed. If you choose to include a screenshot, remove names, account details and other personal information first.
Occulert is a supplemental prototype and may produce false alerts or miss drowsiness. Support is not an emergency service.