Control your data
Data deletion
QuietHand’s durable data is kept on the owner’s Mac. Revoking account access and deleting the local record are separate steps so an accidental disconnect does not erase the owner’s history.
1. Stop future Google access
- Open QuietHand → Connections → Google.
- Select Disconnect. QuietHand attempts to revoke the grant at Google and deletes its local OAuth token.
- For an independent check, open your Google Account’s third-party connections page and remove QuietHand.
2. Remove optional relay data
If cloud relay was enabled, do this before deleting the local database. Run QuietHand’s pairing command and note the island identifier in its pairing link, then use the contact form at quiethand.ai to request deletion of that relay island. Supabase relay content is encrypted, but server-side ciphertext and transport records must be removed separately.
3. Delete the local QuietHand record
- Quit the QuietHand daemon.
- Open
~/.quiethand/config.jsonand note the configureddataDir,tenant, andkeychainService. - Delete the folder
<dataDir>/<tenant>. The default is~/.quiethand/data/<tenant>. - In macOS Keychain Access, search for the configured
keychainServiceand delete its QuietHand generic-password items.
This removes the encrypted database, memory files, audit ledger, connector tokens, and relay keys for that local QuietHand owner. Make a backup first if you may need the history.
Need help?
Send a deletion-help request through the contact form at quiethand.ai. Because the primary record is local and encrypted with keys on the owner’s Mac, QuietHand’s operators cannot remotely erase or recover that local copy.