✓
No telemetry
No background analytics, usage tracking, or crash-phone-home. What you run is what runs.
On-premise & security
Your research never leaves your walls.
Every cloud usability tool ships your participants' faces, voices, and screens to servers you don't control. Ovo Logger doesn't move any of it. Capture, storage, and even the AI analysis run entirely on hardware you own — so your studies stay inside your environment, under your controls.
Data flow · your environment
01 / How it stays local
Every stage of the pipeline runs on your machine.
There's no hosted backend to opt out of — because there was never one. From the moment a session is recorded to the moment a report is written, the data only ever touches hardware you control.
◉
Capture & encode
Recording and video encoding happen locally — no upload, no streaming to a service.
▤
Storage
Each study is a self-contained database on a drive you own — no database server, no cloud bucket.
✦
AI analysis
Transcription, screen-text, and the findings model all run on-device. No API keys, no prompts leaving the box.
◱
Review
Search, highlights, and reporting read straight from the local project — nothing round-trips a server.
Network activity · during a study
Capture → cloudnone
Storage uploadnone
AI / model APInone
Telemetry / analyticsnone
License checkoffline
Observer consoleyour LAN only
⬤ a study can run start-to-finish with the network cable unplugged
02 / 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
Self-contained installer bundles everything. No external services to reach at runtime.
✓
Runs air-gapped
Install, activate, record, and analyze on a machine that has never seen the internet.
✓
Offline licensing
Node-locked, cryptographically signed, activated by file exchange — no license server call.
✓
Per-user install
Installs and updates without admin rights or elevation on locked-down machines.
✓
Your storage, your keys
Projects live on your disks, under your disk encryption, backup, and retention policy.
03 / Compliance
You keep custody, so your controls apply.
Ovo Logger isn't a certification — it's the tool that lets your existing controls stay in force. Because participant data never leaves your environment, it 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
04 / Full disclosure
There's one optional door — and you hold the key.
Ovo Logger can invite a remote observer to watch a live session over the internet. We're upfront about it because it's the only outbound path in the product — and it's built to be controlled:
○
Off by default
The out-of-the-box posture is fully local. Remote access is never on unless you turn it on.
⟳
Opt-in, per session
Enabled per study and never persisted — it doesn't quietly stay on between sessions.
⦸
Or never at all
Leave it off and the product is air-gapped. Nothing else in Ovo Logger reaches outside your network.
05 / Security-review FAQ
The short answers your reviewers want.
Does the app call home or send telemetry?
No. There's no background analytics, usage tracking, or automatic crash reporting. The only network traffic Ovo Logger initiates is the local observer console on your LAN, and — only if you enable it — the opt-in remote-observer relay.
Where is participant data stored?
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.
Does the AI send recordings to a model provider?
No. Transcription, on-screen-text recognition, and the findings/report model all run on-device. 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.
On-premise & security
Bring us to your security review.
We'll walk your IT and infosec team through the architecture, answer the questionnaire, and scope a deployment that satisfies your controls — on-premise, air-gapped, or somewhere in between.