makeprivacy.com · private business systemsLooking for free guides and browser tools? makeprivacy.org ↗
makeprivacy.comContact

Everyday problems · Firms that collect passports and IDs

Is it safe for clients to send passport copies by email or WhatsApp?

It's common, but every copy stays in each inbox and phone it passed through. A portal upload or an expiring link keeps one copy, in a place you control.

What usually happens

The common setup, and its catch

  • IDs by email and chat. Copies spread across mailboxes, phones and backups that nobody tracks.
  • A shared folder link. Easy to set up, easy to forward, and rarely closed again.
  • Attachments to the bank. Another mailbox holding the client's passport for as long as it exists.

What we set up

In accounts your company owns

  • A client portal with passkey sign-in, plus an upload link per request that needs no login
  • Documents filed straight into the client's own folder and record
  • No file-sharing service in the middle: links and uploads run in your own account
  • Expiring links with a code or PIN for sending files out, deleted automatically after 8 days

Already running

Live in our own companies

See our work.

Sensitive files sent safely

Passports and statements leave as expiring links from our own system, not a file-sharing service.

Our own mail server

Company mail on a server we run, with a separate address for every sign-up, switched off when one leaks.

Every client conversation in one place

45,610 messages from email and chat apps, in an archive we own, kept even when someone deletes them.

A first step

Where we'd start

Usually the upload links and the client portal, so the next passport arrives in one place. Every project is quoted after a conversation about what you run today.