Feature
Secure Requests
Create branded encrypted intake forms to collect passwords, credentials, files, and sensitive data from clients — end-to-end encrypted, with full submission tracking.
Branded request pages
Brand at the workspace level, or separately per project and client. Recipients see a professional page, not a generic form.
End-to-end encrypted submissions
All submitted data is encrypted in the recipient's browser before reaching our servers. We never see what they submitted.
Encrypted file attachments
Clients can attach files, contracts, IDs, or certificates directly to their submission. All encrypted at the source.
Reusable templates
Define templates separately, then use them to create requests across clients and projects.
Real-time submission tracking
See the status of every request. Get notified when a client completes their intake.
Project organization
Assign requests to specific projects and workspaces. Keep client intake flows cleanly separated.
Expiration and access controls
Expire intake links, protect them with a passcode, email OTP, or restrict who can submit by email.
Custom fields
Collect exactly what you need (passwords, notes, file uploads, or combinations) in a single structured request.
The problem with email and generic forms
Ask a client to email you their credentials and you've handed them liability too. Their sent folder now contains a password. So does your inbox. Neither expires. Neither notifies you when someone else reads it.
Generic form tools aren't much better. Submissions sit on shared infrastructure, often unencrypted at rest, with no audit trail and no access controls. You can't even tell if the form was opened.
A better intake workflow
doconvoy Secure Requests let you send clients a branded, encrypted form built to collect sensitive information. The client fills in what you asked for, attaches any relevant files, and submits. Everything is encrypted before it leaves their device.
You receive a notification, open the submission in your workspace, and decrypt it on your end. No plaintext data was ever stored on our servers.
Typical use cases
- Client onboarding — collect login credentials, account access, and initial setup information
- Vendor intake — gather API keys, configuration details, and connection strings
- Employee onboarding — securely receive access credentials from new team members
- Legal and compliance — collect personal data with a verifiable audit trail
- Security handoffs — structured, tracked exchange of access details between teams
Encrypt sensitive shares and client intake requests — with access controls and an audit trail. Try any workspace free for 3 days — no credit card required.
Create Your First Request