Security Architecture

Your files never leave your machine.

Not a privacy policy. An architecture decision. Ugle has no server-side infrastructure to receive your recordings.

Local-First Engine

Most transcription tools send files to a server, process them remotely, and return results. This creates data exposure — however briefly. Ugle is architecturally different. The transcription model runs on your device. The index writes to a local folder. Search executes locally. At no point does content leave your machine.

This is not a feature toggle or private mode. It is how Ugle works, every time.

Data locations

Data type	Where it lives
Audio/video files	Original location on your device. Ugle reads from the path. Nothing is copied.
Transcripts	Generated locally. Stored in your Ugle Library folder. Never transmitted.
Search index	Encrypted local database in your Library folder. Never transmitted.
Search queries	Executed locally. Not logged. Not transmitted.
Licence activation	Email address + device ID sent once at activation. No content data.
Update checks	Version numbers only. Optional — can be disabled. No content/usage data.
Crash reports	Opt-in only at time of crash. Technical diagnostics only. No file content.

IT & compliance Q&A

Firewall exceptions needed?

No. Outbound: licence validation, update checks (optional), opt-in crash reports. No content traffic.

Air-gapped deployment?

Yes. Activate on a networked machine, then move to air-gapped environment. Manual update packages available on request.

Where does the index live?

macOS: ~/Library/Application Support/Ugle/ Windows: %APPDATA%/Ugle/ Location is configurable.

Index on encrypted drive?

Yes. Ugle reconnects wherever the Library folder is located.

Is the index encrypted?

AES-256 at rest. Encryption key derived from machine hardware ID.

MDM deployment?

MSI for Windows MDM. macOS PKG for Jamf. Contact enterprise@ugle.ai.

Usage analytics collected?

No. No data about which files you index, what you search, or usage frequency.