Oyma collects zero telemetry, document analytics, or tracking beacons. All notes, audio recordings, and transcripts remain strictly on your local Mac disk. Oyma never transmits your files, search queries, or meeting contents to remote servers.
Zero-Telemetry Architecture by Default
Most modern productivity and note-taking applications embed third-party tracking libraries, cloud analytics event collectors, and session replay recorders. These tools continuously transmit behavioral telemetry: which buttons you click, how long you edit documents, your IP address, device hardware identifiers, and frequently even unredacted document titles and search queries.
Oyma rejects this surveillance model entirely. We believe that personal notes, private meeting deliberations, and intellectual reflections require an absolute privacy guarantee. Software running on your personal machine should serve you, not broadcast your work habits to remote cloud dashboards.
What Never Leaves Your Machine
In Oyma, the following invariants are enforced at the architecture level:
- Zero Document Telemetry: Your Markdown files, folder names, and wikilink connections are never transmitted to any server.
- Zero Audio Uploads: Meeting audio recorded via ScreenCaptureKit is buffered in local RAM and stored directly in your local vault folder.
- Zero Search Query Logging: Full-text searches run against a local SQLite FTS5 index stored on your local NVMe storage; search terms never cross the network.
- Zero Typing & Keystroke Telemetry: Your typing cadence, word counts, and writing habits remain strictly confidential.
| Data Dimension | Typical Cloud Note App | Oyma Architecture |
|---|---|---|
| Document Text & Markdown | Transferred to remote cloud servers | 100% on local NVMe disk |
| Meeting Audio & Transcripts | Transmitted to cloud ASR servers | Transcribed on-device via Apple Neural Engine |
| Search Queries | Indexed on remote cloud clusters | Local SQLite FTS5 index |
| Usage Telemetry | Transmitted to analytics platforms | Zero telemetry beacons emitted |
| Third-Party Trackers | 5 to 12 embedded analytics SDKs | 0 embedded analytics libraries |
Auditing Network Silence with the Network Egress Monitor
Rather than asking you to take our privacy commitments on blind trust, Oyma provides an auditable network egress monitor. Located in the application settings under Security & Egress, this panel displays a real-time ledger of every outgoing network socket connection requested by the application.
When operating in standard local mode, the egress monitor confirms that zero network bytes are transmitted. If you configure optional remote AI providers via Bring Your Own Key (BYOK), the egress log displays the exact API payload and target URL for full operator transparency.
Independent Verification via macOS Firewall Tools
For users who prefer operating system level verification, you can confirm that Oyma makes zero network calls using native macOS tools or third-party packet firewalls:
- Little Snitch / LuLu: Run Oyma under Little Snitch in alert mode. You will observe zero outbound connection requests during normal editing, searching, and local audio transcription.
- Terminal Verification: Use
netstatandlsofto inspect active sockets opened by the binary:lsof -nP -p $(pgrep Oyma) | grep -i tcp - Wireshark Packet Capture: Running a promiscuous packet capture on your primary network interface confirms zero background beaconing or telemetry dispatch.
