Pre-release product demos
Capture unreleased interfaces, roadmaps, staging environments, and internal tools without first copying them into a recorder vendor's workspace.
Zero-cloud trust · for teams
The safest recording cloud is the one your footage never enters.
Customer records, roadmaps, admin consoles, source code: a screen recorder can see the work your team protects most. Verismo records, edits, renders, and exports on the Mac — without a Verismo content cloud or analytics pipeline.
VERISMO CONTENT CLOUDNone
VIDEO PROCESSINGOn device
AI CREDENTIALYour OpenAI key
VERISMO TELEMETRYNone
The normal data path
The recording never needs a vendor boundary.
The core workflow moves through files and processes controlled by the signed-in Mac user. Optional AI is a visible off-ramp, not a hidden stage in every render.
01 · CAPTURELocal projectVideo · system audio · mic · webcam · cursor → .osmoproj
→
02 · EDITOn-device studioTimeline · preview · compositor · renderer
→
03 · DELIVERLocal exportMP4 · GIF · SRT · VTT
OPTIONAL · USER INVOKEDDirect to OpenAINarration audio or transcript text · your API key · your account
Plain-language boundary: Verismo does not receive your footage. If you invoke an AI action, the requested audio or transcript text is handled under your OpenAI account and terms.
Threat model, not adjectives
Ask where every sensitive thing goes.
A privacy claim is useful only when a security reviewer can turn it into a concrete question.
| Asset | Default path | Team control |
|---|---|---|
| Raw footage | Written into a local .osmoproj bundle; not uploaded to Verismo | Choose the recordings folder, back it up, move it, or delete it with normal file controls |
| Frames and edits | Previewed and rendered on-device | Run the core workflow offline; inspect the resulting project and export files |
| AI payload | No traffic until an AI action is explicitly invoked | Supply or remove the OpenAI key; review the confirmation and provider terms |
| API credential | Owner-readable local file, mode 0600, with complete file protection | Remove it at any time in Settings → AI |
| Finished export | Created in the folder and filename the user chooses | Your team decides if, where, and under whose policy it is shared |
| Software update | DMG edition checks a signed appcast; App Store edition updates through Apple | This is version metadata, not a recording-content service |
Where the boundary matters
Record the work without creating another content repository.
Customer support walkthroughs
Keep source material local while redacting account details, then share only the finished file through the destination your team already approves.
Code and incident context
Explain source, logs, and local environments without requiring a hosted recording library. Export only the cut your review allows.
Verify it yourself
The architecture leaves receipts.
No procurement deck is required to see the boundary. A disposable recording can demonstrate the core claims on any test Mac.
- 01Run offlineDisconnect the network, then record, edit, preview, render, and export a test project.
- 02Inspect the filesOpen the recordings folder and inspect the .osmoproj bundle plus the export destination.
- 03Test the AI gateRemove the OpenAI key; optional transcript and AI actions become unavailable while the local studio continues to work.
- 04Observe the boundaryUse your normal network monitor: AI calls occur only when invoked; the DMG updater may check verismo.work for signed version metadata.
Why this is a product feature now
Screen pixels are sensitive data.
The category has moved privacy into the architecture itself. Microsoft's current Recall documentation emphasizes opt-in capture, local processing, encrypted device storage, and explicit sharing controls. For a deliberate recording tool, Verismo chooses an even simpler vendor boundary: the normal content pipeline never enters a Verismo cloud.
Read Microsoft's Recall privacy architecture ↗Term boundary
“Zero-cloud trust” is product shorthand.
It means Verismo does not ask teams to trust a Verismo recording cloud with source footage. It is not a claim of conformance to NIST SP 800-207, which defines a broader enterprise access-control architecture.
Read NIST SP 800-207 ↗The honest boundary
Local-first does not make risk disappear.
Disk encryption, account access, backups, malware controls, and physical security remain your team's responsibility.
Requested audio or text is processed by OpenAI under your account, provider configuration, and applicable terms.
Once your team uploads or sends an exported file, that destination's access and retention policy applies.
Verismo does not claim SOC 2, HIPAA, GDPR, NIST, or other regulatory certification on the basis of local processing.
Security review questions
The short answers
Does Verismo upload recordings to a Verismo cloud?
No. Verismo has no hosted project service. Screen recordings are local .osmoproj bundles, and editing, rendering, and export run on the Mac.
Can the core workflow run offline?
Yes. Recording, editing, rendering, Library management, and local export do not require a content cloud. Optional OpenAI actions and software update checks require a network connection.
Where is the OpenAI API key stored?
In an owner-readable local file with 0600 permissions and complete file protection. Remove it at any time in Settings → AI.
Is zero-cloud trust a compliance certification?
No. It describes Verismo's data path and trust boundary. It is not a claim of compliance with NIST SP 800-207 or any regulatory certification.