Zero telemetry and differential privacy

In the modern software landscape, applications often embed dozens of third-party telemetry SDKs that log keystrokes, window switches, and usage patterns to cloud servers. Oyma is engineered under an uncompromising privacy doctrine: zero third-party tracking, zero session replays, and zero surveillance.

What is NOT in the application

Oyma contains:

• No third-party analytics suites or mobile trackers
• No cloud event brokers or behavioral funnels
• No third-party session replay recorders or keystroke loggers
• No customer data platform SDKs or marketing pixels
• No advertising identifiers or machine fingerprinting

The opt-in crash reporting architecture

If an unhandled exception occurs, Oyma does not transmit crash data silently. If you explicitly choose to submit an error report:

1. Zero Note Content: Note text, file titles, folder paths, and audio buffers are completely excluded from crash payloads.
2. Sanitized Stack Traces: File paths are normalized to relative module names (e.g. renderer/editor.ts) to avoid leaking local username directories.
3. No Persistent Identifiers: Reports include no user ID, email address, or tracking cookie.

Verifying privacy with Little Snitch

To independently verify our privacy architecture using third-party network monitoring:

1. Install Little Snitch or LuLu on your Mac.
2. Launch Oyma and record a meeting.
3. Observe network monitors: while recording and transcribing, Oyma initiates zero outbound network connections.

Related guides

• Audit network calls in Egress log.
• Lock network access in Local-only mode.
• Credential protection in macOS Keychain credential security.