Privacy and Local Processing
Tuna is built to keep your command input private by default.
In practice, that means Tuna's servers are not meant to collect the content you are working with inside the launcher.
What Tuna Tries Not To Collect
Tuna does not intentionally collect:
- search queries
- clipboard contents
- dictation transcripts
- file contents
That is the basic privacy boundary to keep in mind.
Local Working Memory
Features like clipboard history and Shelf are part of Tuna's local working memory on your Mac.
They exist so you can reuse things without pushing that content to Tuna's servers.
See Clipboard History and Shelf for the workflow side of that.
Talk Mode
Talk Mode is designed around local-first transcription paths.
The key idea is that dictation should feel like a way to feed text into Tuna without turning your speech into a cloud workflow by default.
Networked Features Still Exist
Some Tuna features naturally involve the network.
Examples include:
- app downloads and update checks
- purchases and license activation
- optional app telemetry and app crash/error reporting when telemetry sharing is enabled
- extensions that connect to outside services
When you use those features, the relevant service still has to handle that request.
So the right way to think about Tuna privacy is not "nothing ever touches the network." It is "your command content is not the thing Tuna is trying to collect."
Practical Rule Of Thumb
If you are choosing between Tuna features, the private path is usually the one that keeps the work inside:
- local search
- local text handling
- local clipboard history
- local dictation engines
If you need the legal version of this, read the Privacy Policy.