Why most digital business cards aren't private
A typical digital business card service stores your name, phone number, email address and social links in plain text on its servers. That makes it easy for the company to analyse your network, sell contact data to marketers, or expose it in a data breach. Even when a service promises not to, it is technically able to.
OmniProfile is built so that we can't. We never receive your card's contents in a readable form, so there is nothing for us to sell, analyse or leak.
Step 1: Your password never leaves your device
When you sign up, your browser runs your password through PBKDF2 (100,000 iterations of SHA-256) twice, with two different salts:
- One result becomes an authentication token that proves to the server it's you when you log in.
- The other, using a separate random salt, becomes your master key. It is created and used only inside your browser and is never sent to us.
Because the two values are derived with different salts, the login token can't be turned into the master key.
Step 2: Each card gets its own key
Every card you create gets a fresh, random 256-bit key. Your name, title, contact details, links, bio and photo are bundled together and encrypted with that key using AES-256-GCM, the same standard used by banks and messaging apps. The server receives only the encrypted result.
Even your profile photo is cropped and encoded in your browser, then encrypted along with the rest of your card. We never receive the original image.
Step 3: Your keychain ties it together
The keys for all of your cards are kept in a single keychain, which is itself encrypted with your master key. When you log in, your browser downloads the encrypted keychain, unlocks it with your master key and can then open each of your cards. On our side the keychain is just another unreadable blob.
Step 4: Sharing without giving us the key
A shared card link looks like this:
https://omniprofile.me/c/your-card?id=…#k=…
Everything after the # is called the URL fragment. Web browsers never include the fragment when they request a page, which is part of how the web has always worked. So when someone opens your link:
- Their browser asks our server for the encrypted card, without the key.
- Our server returns the encrypted data.
- Their browser reads the key from the fragment and decrypts your card locally.
The recipient doesn't need an app or an account, and they can save your details straight to their contacts as a standard vCard file.
Step 5: If you forget your password
Because we never have your master key, we can't reset it for you the way a normal website would. Instead, when you sign up you are shown a one-time recovery key. It can unlock a backup copy of your master key, so you can set a new password without losing your cards. Store it somewhere safe: without your password or your recovery key, nobody can get your data back, including us.
What our server does see
Zero-knowledge doesn't mean zero data, and we'd rather be upfront about what we do keep:
- Your account email address, so you can log in and receive verification emails.
- Encrypted blobs for your keychain and cards, which we cannot read.
- Basic card settings needed to serve your card: its public link name, theme colour, whether sharing is switched on, and the display name shown on the card (your first and last name).
- For Pro analytics: view and link-click counts, a hashed (not raw) visitor IP address and a broad browser category such as "Chrome/Mobile". Analytics events are deleted after six months.
Compare Free vs. Pro cards or check the FAQ.