How-to guides
Enterprise security
Control outbound access and export independently verifiable activity records.
Two controls in Settings → Security exist for organizations that have to prove things, not just believe them: Air-Gap Mode, which stops all outbound network traffic, and the Audit Ledger, which exports a tamper-evident record signed by the Secure Enclave.
Both are in the standard application. Neither requires a separate edition.
Air-Gap Mode
"Stop all external network traffic and keep every turn on this Mac."
One switch. When it is on, the panel shows Active; when off, Ready. Four protections are listed, and all four are enforced in native code:
| Protection | |
|---|---|
| Cloud AI blocked | No provider call, regardless of chat or agent settings. |
| Web search blocked | No public web search, by either route. |
| Remote connections blocked | No connector, no channel, no marketplace. |
| Local routing enforced | Every turn resolves on this Mac. |
How it is enforced
Air-Gap Mode is not a flag the networking code is asked to check politely. Every outbound operation in OOMU must first acquire an egress permit from a process-wide guard. When the mode is on, the permit is refused and the operation fails with air_gap_mode_active.
Two properties are worth knowing:
- It fails closed at startup. The guard initializes to blocked before the setting is read from the encrypted database. If OOMU cannot determine your setting, nothing goes out.
- Turning it on drains in-flight work. Activating does not return until operations that already hold a socket permit have finished. There is no window where the switch reads Active while a request is still on the wire.
The application's own update check is skipped entirely while Air-Gap Mode is on.
What still works
Everything local, which in OOMU is most of it: chat on the on-device assistant, project files, Ask Documents, document comparison, document generation, Apple app automation, application control, the Quick Launcher, and quick actions.
The cloud model chooser explains itself rather than failing silently: "Cloud providers are unavailable in Air-Gap Mode. Turn off Air-Gap Mode in Security to use external AI providers."
The Audit Ledger
"Export tamper-evident activity records for governance and SIEM review."
Choose a date range and a format (JSONL or CSV) and Export to Downloads. The file is written privately to your Downloads folder, and the panel confirms {count} verified records.
What a record contains
One record per turn:
| Field | |
|---|---|
| Turn and session identifiers, and timestamps | |
| Reasoning route, provider, and model | |
| Tools invoked | |
| Files touched | |
| Verification status and receipt count | |
| Evidence digest | |
| Failure category, where one applies | |
| Previous entry digest | |
| Entry digest |
That last pair is the point. Each entry's digest covers the previous entry's digest, so the records form a hash chain. Removing, reordering, or editing an entry breaks the chain, and the break is detectable by anyone with the file: no access to the original Mac required.
The signature
The export ends with a signature record over a cryptographic manifest covering the format, record count, date range, digest of all records, and the chain head.
| Property | |
|---|---|
| Signer | The Mac's Secure Enclave |
| Algorithm | ECDSA over SHA-256 |
| Key | Non-extractable, held by the Secure Enclave |
| Key ID | secure-enclave: plus a prefix of the public key's SHA-256 |
The Settings panel labels this Hardware-backed signature.
OOMU verifies its own signature before it will accept the export. If verification fails, or if the signature is not hardware-backed, the export is refused outright rather than produced with a caveat. The public key is included in the file so a third party can verify it independently.
Export safety
The output path must be absolute, must carry the extension matching the chosen format, and must not already exist, including as a symlink. An audit export cannot be tricked into overwriting a file or following a link somewhere else.
If the Secure Enclave is unavailable on the machine, the export fails with a specific reason. It does not silently downgrade to a software key.
Data residency and retention
Settings → Storage & Privacy covers the rest:
- "Chats, projects, documents, and settings are kept on this Mac."
- "Deleted chats, projects, and workflows are removed permanently after the Undo period ends."
The database is SQLCipher-encrypted, keyed from the macOS Keychain, with cipher_memory_security and secure_delete on. Credentials never live in the database: they live in the Keychain under a Beta 2-specific service namespace, and the database holds only opaque references.
Settings → GDPR & EU AI Act sits directly below it, and is the surface to send to a reviewer who needs specifics rather than assurances. It states what the encryption does not cover (exports, generated files, and caches can remain unencrypted on disk), what each deletion actually removes, and what the AI provenance metadata in generated DOCX and XLSX files is and is not. Its own framing is that these are statements of product behavior, not a certification, which is the correct thing for a vendor to say and the correct thing for a reviewer to hear. See Privacy & security for the full treatment.
See Local database schema and Privacy & security.
Where the app stops, and OOMU Control begins
Everything on this page is per-Mac, and deliberately so. The OOMU application governs one machine: the person sitting at it decides, macOS enforces, and the audit export is how that machine reports outward.
That means these are not things you configure inside the app:
| Not in the app | How it behaves instead |
|---|---|
| Centrally managed policy | Settings are per-Mac. There is no remote policy push into the application. |
| Directory or SSO integration | The application has no account system. It authenticates to services as you. |
| Fleet dashboards | No cross-device console. The signed audit export is the integration point. |
| A private Mod catalog | Mods install from files you choose. |
| Central key escrow | Keys live in each Mac's Keychain and Secure Enclave, and cannot be extracted. |
Governing OOMU across an organization, rather than one Mac at a time, is what OOMU Control is for. It is a separate, licensed product; the free application does not change when you adopt it, and nothing that protects an individual user sits behind it.
If you are evaluating OOMU for a fleet, this page is the per-machine half of the answer. Control is the other half.
Analytics, which nobody has to turn off
Analytics is opt-in and ships off. A Mac that is installed and never touched again sends nothing. There is no telemetry to negotiate away, no setting an administrator has to remember, and no gap between the default and the answer your policy requires.
If a user does opt in, three lifecycle events can be sent: app_launch, first_run_completed, and session_start. The request carries a random installation identifier and no values from the user's work, because the request has no parameter capable of carrying one. Any event name outside those three is rejected before assembly.
Air-Gap Mode blocks analytics regardless of consent, since it is subject to the same egress guard as everything else. For an organization that cannot accept outbound telemetry, that is now a second lock rather than the only one.
For evaluation purposes, the useful version is short: the outbound telemetry surface of an untouched installation is empty, and the maximum outbound telemetry surface of a consenting one is three event names and a random identifier.
Related
- Privacy & security: the full model.
- Local database schema: what is stored and how.
- Evidence & receipts: what the audit records are records of.