Privacy Policy

Oculovis records camera footage on the device acting as the recorder. Account services, remote access, guided setup, optional AI, feedback and diagnostics can send data to Oculovis or other providers. The Android app also includes Google ML Kit for camera-label recognition; its diagnostic collection is described below. We do not sell or rent your camera footage or use it for advertising. Read the feature-specific details in Face Recognition & Biometrics, AI Analysis, Cloud Integration, and Camera Setup below.

Most of this policy is about the app. We hold this website (oculovis.com) to the same standard, so here is everything it records about you:

• Downloads. When you click a download button, our own server counts the click before handing you the file. We record the platform, the app version served, your browser’s user-agent string, and the page you came from — never your IP address, and never a cookie or identifier. Download counts are deleted after 90 days.
• Server logs. Like every web server, ours keeps an access log that includes your IP address. It exists to keep the site running and secure — it is never used for analytics, never joined to the download counts above, and never leaves our server.
• Visits. We count page visits with analytics software that we host on our own servers. It sets no cookies and stores no IP address — your IP is used only momentarily to estimate a rough location and to derive an anonymous visitor identifier that resets every day. Visit data never leaves our infrastructure and is deleted after 90 days.
• Demo requests. If you fill in the contact form, we store what you submit — your name, email, company, and message — and use it only to get back to you.

Oculovis connects to compatible cameras reachable by your recorder, and to recorders linked to your account.

By default, camera features work locally between your device and your local cameras.

Recording storage remains on your recorder. If you turn on Cloud Integration for remote access, or AI Analysis, specific data leaves your device as described in those sections — including, in some cases, images that may contain people’s faces. These features are off by default.

When you add a camera, the setup wizard can use Oculovis to find the best way to set it up. This is called Guided activation; it is on by default, and you can turn it off at the start of any setup. Guided requests depend on the selected model and available service connection; disabling remote recorder access is not a general switch for AI, feedback or SDK network traffic.

With Guided activation on, your device sends Oculovis the camera’s make, model and firmware version and which setup steps worked. It never sends the camera’s serial number, network or hardware address, name, video or images, or any password. Oculovis keeps these records to learn which way of setting up works for each camera model; they are not stored with your account or your device. To suggest the next step, an AI assistant — reached through Oculovis and run by a third-party AI provider — may receive the same model details and where the setup stands, and look the model up on the web.

Turning Guided activation off disables those guided requests. Camera discovery and connection still communicate with the camera. Scanning a label uses Google ML Kit; see Diagnostics & SDKs below.

Face recognition is an optional add-on, not part of the app: the app ships with no face-recognition software, and nothing on your device can create a faceprint until you choose to download and install the add-on. Recognition is then enabled per camera, and matches faces seen by that camera against people you have chosen to enroll.

Installing the add-on is recorded. The add-on is downloaded from Oculovis, and Oculovis keeps a record of each download — your account, the add-on version and platform, the country the request was made from, the time, and whether it was allowed. This record is evidence of where and to whom face-recognition software was provided; it contains no biometric data and no IP address. The add-on may not be available in every country.

Your biometric data stays on your device. A faceprint (the numeric template used for matching) is stored only for people you enroll, and only on your device — it is never uploaded to or received by Oculovis. People you have not enrolled are never stored as faceprints; only their face images are kept, and those are deleted automatically (see below). Face images used for matching are also stored on your device.

Consent is your responsibility. You should only enable face recognition and enroll people where you are permitted to do so, and only enroll people who have given you permission. When you enroll someone, the app asks you to confirm that the person has been told and has agreed; your device keeps a local privacy log of when that confirmation was made and when deletions were requested and completed — the log records how and when, never a face or a faceprint. Laws in some places (for example, Illinois’ BIPA and the EU/UK GDPR) require notice and consent before collecting biometric data, and some restrict or prohibit it entirely.

Retention & deletion. Detections of people you have not enrolled (“unknown” faces), including their face images, are automatically deleted after 7 days. Enrolled people remain until you delete them; deleting a person removes their faceprints, face images, and the link to past detections from your device, and they stop being recognized. You can turn off face recognition at any time in the camera’s settings, and uninstalling the add-on deletes everything it stored — enrolled people, faceprints, and face images — from your device.

Oculovis offers optional AI features (for example, describing an event or using the Assistant). Assistant and AI Analysis require a configured model. When you use them, camera images, your messages and instructions, and relevant camera or event context may be sent to the selected model endpoint. Images may include faces. Recording-analysis actions can also send video clips, including camera audio present in those clips, to the configured model endpoint. Depending on the feature and configuration, requests go directly to your provider, to a local endpoint you configure, or through Oculovis. OpenRouter connects to external model providers and may charge your account. It does not require the recorder to be linked to the Oculovis cloud, but it does use external services. Provider retention and use of requests depend on that provider and your settings; check its policy before sending sensitive footage. AI output is not a guarantee that an event was detected or described accurately.

Some features are optional and disabled by default. When you choose to enable them, limited data may be sent to Oculovis servers, and in some cases to a third-party provider, solely to provide that feature (see AI Analysis). We do not sell your data or use it for advertising.

If you choose to enable Cloud Integration, the following data is sent to the Oculovis cloud server to establish and maintain a network tunnel for remote access:

• Your account identifier and sign-in profile, including the name and email held by our identity service
• The recorder name, generated device identifier and public device key
• Pairing information, connection status and the network information needed to connect your devices

Remote requests for camera information, event images and recording playback, including camera audio when available, may pass through Oculovis servers to reach your recorder. This is separate from storing a continuous recording in the cloud. Images or files submitted for AI or support are handled as described in those sections.

For live WebRTC viewing, when a direct connection between your viewing device and your camera device is not possible (for example, behind certain mobile-carrier networks), the encrypted video stream is relayed through Cloudflare’s TURN relay service. The stream is end-to-end encrypted between your two devices — the relay cannot view your video; it processes only the encrypted packets and the network addresses needed to forward them, for the duration of the stream. This describes the WebRTC media connection, not every remote API request or AI upload.

If you choose to submit feedback, the information you provide is sent to Oculovis and used only to improve the app. This may include your message, an optional rating, an optional email for follow-up, and any screenshots you attach, along with app/device information. Support correspondence and selected attachments may be delivered to our support email and issue-tracking service (ClickUp). If you are signed in to the app, the feedback is linked to your account, so deleting your account deletes it (see Account Deletion below).

Oculovis diagnostics are off by default. If you enable them, the app can upload crash reports and diagnostic logs to help us investigate failures. You can also choose to include logs with feedback. Reports may contain app/device versions, error details, technical identifiers and operational context. Turning diagnostics off stops Oculovis’s automatic diagnostic uploads; it does not control a separate SDK’s collection or delete reports already received. Uploaded reports are handled as support records under Feedback and Account Deletion.

Camera-label recognition uses Google’s ML Kit Android SDK. Google documents collection of device and app information, installation identifiers, performance/error metrics and feature-usage details for diagnostics and usage analytics. This SDK traffic uses HTTPS. See Google’s ML Kit data disclosure. The Oculovis diagnostics switch does not disable ML Kit’s collection.

Oculovis’s public account and cloud APIs use HTTPS. Transport for cameras and custom model endpoints depends on their configuration; the app permits HTTP model endpoints and camera protocols that are not encrypted. We therefore do not claim that every supported data transfer is encrypted. Use trusted networks and an HTTPS model endpoint when sending data off your device.

You can delete your Oculovis account at any time on our account deletion page. Deletion happens immediately, with no grace period: your sign-in stops working, your devices are unlinked, your AI assistant key is cancelled, and your registration codes, our copies of the files your devices sent to the AI assistant, any custom relay settings, and the feedback you sent while signed in to the app, with its attachments, are deleted. The service that handles sign-in keeps an audit record of your account’s creation, sign-ins, changes and deletion, including the email address and name it held, and our server’s logs record activity on your account, such as linking devices, issuing credentials and the deletion, under your account ID. Your recordings stay on your devices, and each device keeps its identity so it can be linked again. Security and operational records, such as the add-on download records described above and the records of relay credentials issued to your devices, are kept with your account removed from them; add-on download records are deleted after 90 days, and relay credential records after about 180 days. Feedback you sent while signed out, or before the app linked feedback to accounts, isn’t stored with your account: we retain it as support correspondence, along with the copies of any feedback already delivered to our support team and the demo requests sent through this website.

The app may request only the permissions needed for its features. You can change any permission in your device settings at any time.

If the app or this website changes in the future, this policy will be updated before those changes ship. Continued use after an update constitutes acceptance of the revised policy.

Have a question about this policy?

support@oculovis.com