Use Case

Receive Client Credentials

Ask clients to send you passwords, API keys, and access credentials through an encrypted channel — not over email. Structured, tracked, and end-to-end encrypted.

Receive Credentials Securely

The Problem

Credentials arrive over email

Clients reply to emails with passwords in plain text. Those sit in your inbox indefinitely, creating ongoing exposure.

No acknowledgment or tracking

You don't know when a client sent credentials or if they used the right format. Manual follow-up wastes time.

How it works

1

Create a credential intake request

Build a structured form asking for the specific credentials you need — logins, API keys, tokens, files.

2

Send the encrypted intake link

Your client receives a professional, branded page to submit their credentials securely.

3

Credentials are submitted encrypted

All data is encrypted in the client's browser before submission. You receive a notification when it's ready.

Benefits

  • —No credentials ever sent via email
  • —Full audit trail of the exchange
  • —Branded, professional client experience

The liability starts the moment a client sends their password

A client emails you their hosting credentials. It takes them ten seconds. For you, it creates a liability that lives in your inbox until you actively delete it, and possibly long after that, depending on your email provider's backup retention.

The email contains their password in plain text. Your sent folder contains their password in plain text. If either inbox is ever compromised, those credentials are exposed alongside everything else.

Most service providers accept this as normal. It isn't. And it's easy to stop.

How the intake flow works

You create a doconvoy intake request specifying exactly what you need: CMS login, FTP credentials, API keys, whatever the project requires. You send the client a link.

They open a branded form with your workspace name and logo. They fill in the fields and submit. Everything they enter is encrypted in their browser before it reaches our servers. We store ciphertext. You receive a notification.

You open the submission in your workspace and decrypt it. The credentials arrive without ever having touched an email thread.

What your client experiences

Nothing unusual. A link, a form, a submit button. No account required, no app to install, no confusing setup. For them it takes the same amount of time as writing a message. For you, it's categorically different.

The audit trail is yours

When a client submits, the event is logged: timestamp, submission status, verification method used. If your process or your contracts require documented data handling, you have it, with no extra work.

Built for the way your field collects credentials

The same encrypted intake fits any credential exchange, but the language and the keys differ by field. If you run an AI or automation agency, see how it maps to collecting LLM API keys, SaaS tokens, and database secrets. A version for IT and security consultants is on the way.

Handle sensitive client information securely — from onboarding to handoff. Try any workspace free for 3 days — no credit card required.

Receive Credentials Securely