Is there any built-in safe storage api for securely storing secrets?

[HuakunShen]

Electron has a safe storage API for "protecting data stored on disk from being accessed by other applications or users with full disk access".

I need to store a encryption key used to encrypt data on disk. Is there a Tauri or Rust way of doing this on all platforms?

Mac has a security-framework for keychain.

It would be nice if we can have a similar cross-platform plugin for tauri.

[FabianLars]

Right now, we generally recommend the stronghold plugin (or stronghold itself for rust since the plugin doesn't expose a rust api yet) but that does not use the keychain. If you want/need that, there should be rust crates available.

stronghold is no longer recommended and will be deprecated and therefore removed in v3.

[HuakunShen]

@JonasKruckenberg An off-topic question: when will V2 be released? I saw a few features in alpha that I really need like the deep linking.

[FabianLars]

https://beta.tauri.app/blog/roadmap-to-tauri-2-0/

[archcorsair]

Is integrating with keyring still the recommended approach for storing oauth tokens/session information?

[NoelJacob]

What about android? keyring doesn't support android

[Blankeos]

Does using stronghold imply that your user has to remember a Master password? (I lightly just consulted ChatGPT about this, and it said something about this, is it true?)

[angelorc]

Any update on the keyring?

[sondreb]

I'm also looking for support for Android.

[isanjary]

Any update on the keyring?

[amitnos123]

HuakunShen implemted keyring plugin for Tauri V2
https://github.com/HuakunShen/tauri-plugin-keyring

[belkadimehdi98-commits]

I ran into a similar challenge while building a Rust + Tauri desktop AI app that stores encrypted session data locally.

One thing I’ve been exploring is a hybrid model:

• Use OS-native secure storage (Keychain / Windows Credential Manager) when available
• Fall back to encrypted local vault storage (e.g. SQLite + file-level encryption)
• Keep the encryption key lifecycle separated from app runtime state

The tricky part seems less about storage itself and more about cross-platform consistency and developer ergonomics.

Curious whether the Tauri core team sees this as something that should live in official plugins long-term, or if the ecosystem model (community plugins like keyring) is the intended direction?