Where Does Coracle Keep Your Nostr Keys?
Coracle stores keys in browser local storage, with signer extensions keeping them out of pages.
Last updated
Coracle is a browser based Nostr client. It holds the login key in local storage on your machine, or defers to a NIP-46 remote signer or NIP-07 extension when you choose one. No Coracle server ever sees the key.
The backup story matches every Nostr app. Write the nsec down before you need it. Wiping browser data ends the session at once, which is good hygiene on shared machines and a small disaster otherwise.
Where Coracle stores this, by platform
Browser localStorage or signer (nsec)
Local only key handling. Remote signer options keep keys on another device you own. Keep relay settings noted separately for fast rebuilds.
Browser localStorage or signer (nsec)
Same pattern as other web clients. Private windows forget the key on close, so only log in there for quick reads.
Browser localStorage or signer (nsec)
Self hosted Coracle changes nothing about keys. The instance operator still cannot recover a lost nsec.
Frequently asked questions
How do I use Coracle without pasting nsec?
Connect a browser signer extension or a remote bunker signer. Coracle then asks per signature. The raw key never enters page storage.
I cleared browser data, am I locked out?
Only if the nsec backup is also gone. Reimport the saved nsec to resume. Without it, the account is unrecoverable on every client.
Notice an outdated path? Let us know.