Skip to content
SafeHanded Docs

What SafeHanded is

SafeHanded gives a technician a safe, auditable way to receive a credential from a user when it genuinely has to happen — a profile rebuild, a mailbox migration, a device setup, a cached credential a reset won’t fix. Instead of the password travelling over the phone, chat, email or a ticket comment and living there forever, it travels once, in one place, and destroys itself.

How it works, in four steps

Section titled “How it works, in four steps”
  1. A technician creates a request: who it’s for, why, which ticket, and how long it may live. The user receives a short-lived, branded link.
  2. The user opens the link, confirms the request is genuine, and types the credential. It is encrypted in their browser to the technician’s own key before anything leaves their device.
  3. The technician reveals it in their own browser after a passkey touch. The server, its database, its backups and its operators never hold the plaintext or a key that can decrypt it.
  4. The record self-destructs when the technician finishes, when its time runs out, or the moment the linked ticket closes — and every step is written to a tamper-evident audit log.

The two things that make it different

Section titled “The two things that make it different”
  • Encrypted to a person, not a link. The secret is sealed to a specific technician’s key, unlocked only by that technician’s passkey. A leaked or forwarded link lets someone submit a credential, never read one. Our servers hold ciphertext they cannot decrypt.
  • Destroyed when the ticket closes. The record is tied to your helpdesk ticket and purges itself when the ticket closes — automatically, with a note back to the ticket and a line in the audit trail. No orphaned passwords left in an inbox or a link tool.

Everything else — encrypted files, QR codes, view limits, custom domains, SSO, an API — is there too. These two properties are why SafeHanded exists.

What it is not

Section titled “What it is not”
  • Not a password manager or vault. Records are ephemeral by design.
  • Not a password reset tool. It’s for the cases a reset can’t fix — and it integrates with reset tools rather than arguing with them.
  • Not privileged access management. There’s no session brokering or credential injection.
  • No end-user accounts. The people you request from interact through links only.

Next

Section titled “Next”