When the meeting cannot go to a cloud notetaker

Wrengle writes the recording as authenticated encrypted blocks in its private app-data folder on your machine, outside your notes vault and its sync history. The blocks are bound to the exact vault and recovery-directory identity that created them. No Wrengle server or account receives them. A cloud transcription choice still sends bounded audio chunks to that provider.

Choose a model that runs on your own machine and the audio is never sent anywhere. A cloud provider needs three things before any meeting audio leaves: the provider selected in settings, cloud meeting transcription switched on, and a stored key for it.

Every note is an ordinary file in your folder. You can encrypt the folder, keep it on an encrypted volume, or hand it to a client without exporting anything.

Wrengle removes its encrypted audio timeline after canonical finalization succeeds. Deletion is recorded before secure cleanup, so a restart resumes an interrupted quarantine before new capture. If finalization needs attention, Wrengle retains that local timeline so recovery remains possible; elapsed time alone does not authorize deletion, and unresolved timelines count against bounded recovery capacity. Deleting a finished note does not reach any cloud provider that already received audio; its logging and retention terms still apply.