✓Direct Answer

No. Oyma operates within macOS security boundaries and only accesses the specific vault directory you explicitly select. It cannot read your personal photos, documents, browsing history, or system files outside that folder.

Modern macOS incorporates sophisticated security protections designed to prevent applications from silently snooping on user files, reading keystrokes, or indexing unauthorized directories.

Oyma adheres strictly to Apple’s least-privilege security model.

Explicit Directory Scoping

When you first open Oyma, you use the native macOS file picker (NSOpenPanel) to select your vault folder. Under macOS security architecture:

  1. Security-Scoped Bookmarks: macOS grants Oyma a cryptographic, persistent permission token specifically and exclusively for the selected directory tree.
  2. Strict Boundary Enforcement: The application cannot traverse upwards in the directory tree (../) to inspect your home folder, access ~/Desktop, or read system directories.
  3. Zero Background Scanning: Oyma does not run background daemons that scan other storage volumes, external drives, or hidden user folders.
/Users/username/
├── Documents/
│   └── MyVault/         <--- [Oyma GRANTED ACCESS HERE ONLY]
│       ├── Notes.md
│       └── Audio/
├── Desktop/             <--- [BLOCKED BY MACOS SECURITY BOUNDARY]
├── Downloads/           <--- [BLOCKED BY MACOS SECURITY BOUNDARY]
└── Library/             <--- [BLOCKED BY MACOS SECURITY BOUNDARY]

Auditing File Access via macOS Terminal

Security administrators and curious operators can audit Oyma‘s exact filesystem access calls in real time using the macOS fs_usage command:

# Monitor all filesystem calls made by Oyma
sudo fs_usage -w -f filesys Oyma | grep -v "CACHE"

You will observe that disk read and write operations are strictly confined to your designated vault path and the standard temporary cache directory in ~/Library/Caches/.

Apple’s macOS operating system enforces strict permission boundaries through the Transparency, Consent, and Control (TCC) framework. Under this system:

  • Protected User Folders: Folders such as ~/Desktop, ~/Documents, and ~/Downloads require explicit user consent via system authorization dialogs before an application can read their contents.
  • No System-Wide Permissions Required: Unlike remote screen-monitoring or meeting-bot utilities that demand sweeping Accessibility, Full Disk Access, or Screen Recording permissions to capture entire desktop displays, Oyma only requires audio capture permission for ScreenCaptureKit.
  • Sandboxed Directory Boundaries: Oyma operates strictly within the security-scoped bookmark granted when you pick your vault folder. If a script or link attempts to reference files outside that folder, macOS blocks the read attempt at the kernel level.

You retain complete governance over your filesystem: you determine exactly which directory Oyma can view, and everything else remains strictly off-limits.

Hardened Sandbox Architecture and System Entitlements

In addition to user-scoped folder boundaries, Oyma runs with Apple’s hardened runtime enabled. It contains zero entitlements for reading system address books, camera hardware, or personal photo libraries. The application cannot execute arbitrary external binaries or load unsigned third-party dynamic libraries at runtime.

By enforcing the principle of least privilege, Oyma operates with fewer system permissions than standard web browsers or office suites. If an external script attempts to access directories outside your chosen vault, macOS kernel security filters immediately block the call.

Related Questions & Architecture Guides