✓
No telemetry
No analytics, no usage tracking, no automatic crash reporting.
On-premises & security
Your research stays on your hardware.
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.
Data flow · your environment
How it stays local
Every stage of the pipeline runs on your machine.
There is no hosted backend. None to opt out of, none to trust. From capture to final report, data touches only hardware you control.
Capture & encode
Recording and encoding run locally. No upload. No streaming.
Storage
One study is one self-contained database file on your disk. No database server. No bucket.
AI analysis
Transcription, screen text, and the findings model run on-premises. Nothing is sent to an outside service. No prompt leaves the machine.
Review
Search, highlights, and reports read the local project directly. No server round-trips.
Network activity · during a study
Capture → cloudnone
Storage uploadnone
AI / model APInone
Telemetry / analyticsnone
License checkoffline
Observer consoleoff until switched on, then your LAN only
⬤ a study can run start-to-finish with the network cable unplugged
Nothing phones home
Built to pass a security review, not dodge one.
The questions an IT or infosec team will ask - answered by architecture, not policy.
✓
No cloud dependencies
The installer bundles every dependency. At runtime, no external service is reached.
✓
Runs air-gapped
Install, activate, record, and analyze on a machine with no internet connection.
✓
Offline licensing
Node-locked, cryptographically signed, activated by file exchange. No license server.
✓
Per-user install
Installs and updates without admin rights. No elevation, even on locked-down machines.
✓
Your storage, your keys
Studies live on your disks, under your disk encryption, backup, and retention policy.
Compliance
You keep custody, so your controls apply.
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.
IRB
Recordings and PII stay within your approved systems and retention rules.
HIPAA
PHI captured in a study never transits a third-party processor.
ITAR / export
Controlled-environment research stays on controlled hardware.
Data residency
Data physically stays where your policy (or GDPR) requires it.
Remote observers · optional
Full disclosure
One optional egress path. Documented here.
A remote observer can watch a live session over the internet. It is the product's only outbound path. Its controls:
Off by default
The default posture is fully local. Remote access starts off and stays off until you enable it.
Opt-in, per session
Enabled per session, never persisted. Every new session starts with it off.
Or never at all
Left off, the product is air-gapped. No other component makes an outbound connection.
Security-review FAQ
The short answers your reviewers want.
Does the app call home or send telemetry?
No. Ovo Logger initiates two kinds of network traffic: the observer console, which answers only the computer it runs on until you turn on other computers on your network, and - only if you enable it - the per-session remote-observer relay. Until then nothing listens to the network, so Windows never asks to let it. There is no analytics, usage tracking, or automatic crash reporting.
Where is participant data stored?
In a self-contained study 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 study you can encrypt, back up, and retain under your own policy.
Does the AI send recordings to a model provider?
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.
Can it run fully air-gapped?
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.
How are updates delivered?
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.
What about remote observers?
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.
Bring us to your security review.
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.