Canonical Technical Definition

An Apple operating system security technology that isolates applications within tightly restricted containers, restricting access to system hardware, network sockets, and user files.

The macOS Application Sandbox is an integrated operating system security framework introduced by Apple in macOS 10.7 Lion. It enforces the principle of least privilege by containing each running application process inside a restricted boundary, preventing software from accessing resources it has no business touching.

In traditional desktop computing, any application launched by a user inherits the user’s full permissions. A malicious or compromised program could quietly scan your ~/.ssh keys, harvest browser cookies, activate the webcam, or exfiltrate private documents. The macOS App Sandbox eliminates this threat vector.

How the macOS Sandbox functions

The App Sandbox enforces strict kernel-level access controls through three primary mechanisms:

1. Entitlements

Entitlements are signed XML property lists bundled into the application’s binary code signature. They declare the precise hardware and filesystem capabilities the application requires:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "...">
<plist version="1.0">
<dict>
    <!-- Explicit user file selection permission -->
    <key>com.apple.security.files.user-selected.read-write</key>
    <true/>
    <!-- Native audio hardware capture entitlement -->
    <key>com.apple.security.device.audio-input</key>
    <true/>
</dict>
</plist>

2. Security-scoped bookmarks

When a user grants an application access to a folder using the native macOS NSOpenPanel, macOS generates a cryptographic security-scoped bookmark. This token allows the application to retain persistent read-write access to that specific directory across application restarts without granting blanket filesystem permissions.

3. Containerized isolation

Sandboxed applications receive a dedicated sandbox container directory under ~/Library/Containers/. Temporary files, caches, and application state are isolated from other processes.

The App Sandbox in Oyma

Oyma leverages macOS security architectures to guarantee user privacy. When you launch Oyma, you select your notes folder once; macOS grants Oyma a security-scoped bookmark for that directory alone.

Oyma never requests broad disk access or root permissions. Because core operations—such as Whisper speech transcription, SQLite FTS5 search indexing, and Markdown parsing—execute locally inside the application’s sandbox, your data remains fully protected against external compromise.

Frequently asked questions about macOS Application Sandbox

What is the purpose of the macOS App Sandbox?

The App Sandbox prevents compromised or malicious software from reading private files, recording unauthorized microphone audio, accessing system peripherals, or transmitting data over the network without explicit user consent.

How does an application access user files within a sandboxed environment?

Through explicit system entitlements (such as com.apple.security.files.user-selected.read-write) paired with native macOS Open Panels that require affirmative user file selection.

How does Oyma interact with the macOS sandbox and security model?

Oyma requests explicit user permissions only for the notes folder you select and for ScreenCaptureKit meeting audio. It requires zero cloud network entitlements for core operations.