No telemetry
No analytics, no usage tracking, no automatic crash reporting.
On-premises & security
Ovo Logger uploads nothing. Other cloud research tools upload participants' faces, voices, and screens. With Ovo Logger, capture, storage, and AI analysis run on-premises, on hardware you own. A study can run start to finish with the network cable unplugged.
01 / How it stays local
There is no hosted backend. None to opt out of, none to trust. From capture to final report, data touches only hardware you control.
Recording and encoding run locally. No upload. No streaming.
One study is one self-contained database file on your disk. No database server. No bucket.
Transcription, screen text, and the findings model run on-premises. Nothing is sent to an outside service. No prompt leaves the machine.
Search, highlights, and reports read the local project directly. No server round-trips.
02 / Nothing phones home
The questions an IT or infosec team will ask - answered by architecture, not policy.
No analytics, no usage tracking, no automatic crash reporting.
The installer bundles every dependency. At runtime, no external service is reached.
Install, activate, record, and analyze on a machine with no internet connection.
Node-locked, cryptographically signed, activated by file exchange. No license server.
Installs and updates without admin rights. No elevation, even on locked-down machines.
Projects live on your disks, under your disk encryption, backup, and retention policy.
03 / Compliance
Ovo Logger is not a certification. It keeps custody with you, so the controls you already passed audit with stay in force. Data that never leaves your environment fits the regimes that rule cloud research out.
Recordings and PII stay within your approved systems and retention rules.
PHI captured in a study never transits a third-party processor.
Controlled-environment research stays on controlled hardware.
Data physically stays where your policy (or GDPR) requires it.
04 / Full disclosure
A remote observer can watch a live session over the internet. It is the product's only outbound path. Its controls:
The default posture is fully local. Remote access starts off and stays off until you enable it.
Enabled per session, never persisted. Every new session starts with it off.
Left off, the product is air-gapped. No other component makes an outbound connection.
05 / Security-review FAQ
No. Ovo Logger initiates two kinds of network traffic: the observer console on your LAN, and - only if you enable it - the per-session remote-observer relay. There is no analytics, usage tracking, or automatic crash reporting.
In a self-contained project on a drive you choose. There's no database server to stand up and no cloud storage - video, events, transcripts, and findings all live in one local project you can encrypt, back up, and retain under your own policy.
No. Transcription, on-screen-text recognition, and the findings/report model all run on-premises. There are no API keys, and no prompts or media leave the machine.
Yes. Installation, activation, recording, and analysis all work with no internet connection. Licensing is offline and node-locked, activated by a file exchange rather than a server call.
By re-running a new signed, self-contained installer - an in-place, per-user upgrade that needs no admin rights and no network. Your projects, settings, and license are untouched.
Optional and opt-in per session (see above). Left off, the product is air-gapped. When on, it's the single outbound path, and it's never persisted between sessions.
On-premises & security
We'll walk your IT and infosec team through the architecture, answer your security questionnaire, and scope a deployment that satisfies your controls, on-premises, air-gapped, or somewhere in between.