Request deletion of your events from Nostr relays
Your private key never leaves your browser
⚠️ Your nsec is used ONLY to sign deletion requests. It never leaves your browser.
Choose which relays to delete events from
Select which events to delete
Understanding NIP-09
Nostr uses Kind 5 events to request deletion. You sign a deletion event listing the IDs you want removed.
Your nsec never leaves your browser. All signing happens locally using nostr-tools library.
Relays choose whether to honor deletion requests. Most do, but it's not guaranteed.
Always backup your events before deletion. Once deleted from relays, recovery is difficult.
No. Deletion is a REQUEST to relays via NIP-09. Relays may or may not honor it. This tool cannot force deletion. Events may still exist on other relays or in archives.
Yes. Your nsec is ONLY used in your browser to sign deletion events. It is never sent to any server. All cryptography happens client-side using nostr-tools.
When you delete events, a Kind 5 deletion event is broadcast to selected relays. Well-behaved relays will stop serving those events, but they may still exist elsewhere.
YES! Always backup your events before deletion. Click "Backup First" to download a JSON file of your events. Recovery after deletion is difficult or impossible.
Yes! You can select which events to delete. Filter by kind, or manually check/uncheck individual events before deletion.
It can delete Kind 4 (DM) events from relays, but the recipient may still have copies. DM deletion is particularly unreliable in Nostr.
You can delete your Kind 0 (profile) event, but you'll need to create a new one if you want to keep using Nostr. Most users keep their profile and only delete notes.
No. Nostr is decentralized and doesn't guarantee deletion. This tool does "best effort" deletion but cannot ensure compliance with data protection regulations.