Built like it's holding your career. Because it is.

Your credential documents carry your license numbers, your certifications, sometimes your home address. Here is exactly how they're protected — in plain language, because you shouldn't need an IT background to trust the filing cabinet.

Private by architecture

Every document lives in private, encrypted storage tied to your account alone. There are no public files, no shared folders, no “oops” setting. Documents are encrypted at rest and in transit, always.

Access on your action only

Nobody — not an employer, not another user, not our own staff in day-to-day operations — can view a document unless you explicitly send it or download it. When you do open a document, access happens through a link that expires in minutes.

Sending, done safely

When you send a package, the recipient gets a secure download link that expires after seven days — not a permanent attachment sitting in their mail archive for years. Every send is recorded in your delivery log.

Your account, locked down

Sign-in runs on a managed authentication provider. Two-factor authentication (TOTP) is available from day one, and we'll encourage you to turn it on when you join.

Accountability, recorded

Document access and every package delivery are written to an audit log. If you ever wonder what happened and when, the record exists.

Your exit, built in

Export all documents and data any time, self-service. Delete your account and your documents are removed from storage — not archived into a “deactivated” limbo. If we ever confirmed a breach affecting your data, we commit to notifying you within 72 hours.

What we'll never do

Use your documents for advertising. Use them to train AI models. Sell or share your information. Show a document to anyone you didn't send it to. These aren't promises bolted on afterward — the system was designed so they'd be hard to break.

SendMyLicense stores your own professional records, not patient information. We adopt healthcare-grade technical safeguards because our users expect them, not because we're claiming a regulatory certification we don't hold.