FAQ
Short answers, with links to the detail.
Security
Section titled “Security”Can SafeHanded read our passwords? : No. Credentials are encrypted in the browser and the server only ever holds ciphertext with no key to decrypt it. See How SafeHanded protects secrets.
What if someone forwards the link? : They could submit a credential (if they also pass verification), but never read one — reading needs a recipient’s private key. See encrypted to a person, not a link.
Is it really zero-knowledge, or marketing? : The reveal is browser-only, the server has no decryption API, and an automated test rejects any response carrying secret material. See the security overview.
Keys and reveals
Section titled “Keys and reveals”I’ve got a new laptop — will I lose access? : No. Sign in and unlock with a passkey or your recovery code. See Losing or replacing a device.
My passkey signs me in but won’t reveal. : It’s probably “sign-in only” (no PRF). See passkey compatibility and I can’t reveal.
What happens if a technician leaves? : Their outstanding requests are sorted into needs-a-new-link, team-recoverable, and unrecoverable. See When a technician leaves.
Tickets and integrations
Section titled “Tickets and integrations”Do I have to remember to delete the credential? : No — closing the linked ticket destroys it automatically. See how ticketing works.
My ticket closed but the credential wasn’t purged. : See The ticket closed but the credential wasn’t purged.
Which ticket systems are supported? : 13 native adapters (6 in preview) plus a generic webhook (in preview) and the API. See the capability matrix.
Is there a free plan? : Yes. See Billing & plans.