Aug 2026: a breach at Trezor's shipping partner exposed the home addresses of nearly 12,000 customers. Read why →

Client side encryption

Addresses are encrypted in the shopper's browser at checkout, before the order reaches your store or us.

2 min read

Most stores protect customer data on their servers: encrypted disks, access controls, audit logs. All of that matters, but the address still arrives in plain text and is readable by every system that touches the order afterwards. Cirdan moves encryption to the first place the address exists: the checkout form in the shopper's browser.

What happens at checkout

When the checkout page loads, a small Cirdan script loads with it. When the shopper submits the form, the script encrypts the protected fields before the request is sent:

  • Full name
  • Street address and address line two
  • City and postal code
  • Phone number

Your store receives the order with each of those fields replaced by ciphertext, plus an order token. Items, quantities, prices, discounts and payment status are untouched, so payments, inventory and reports keep working.

The shopper sees the same form, fills it in the same way and pays with the same methods. Encryption takes a few milliseconds on the device.

What changes with Cirdan

Checkout
Before: Address sent to the store in plain text
With Cirdan: Encrypted in the buyer's browser
Warehouse
Before: Pick lists show name and address
With Cirdan: Pick lists show an order token
Storage
Before: Readable customer database
With Cirdan: Encrypted orders only, keys kept offline
After delivery
Before: Address kept indefinitely
With Cirdan: Address deleted, deletion verifiable
6
Fields encrypted on every order: name, street, line two, city, postal code and phone
0
Private keys held by your store, Cirdan servers or warehouse staff
1
Place the address is decrypted: the paired label station

What stays readable, and why

The country stays readable. Your store needs it to calculate shipping rates, duties and tax, and it does not identify anyone on its own. Order totals and products stay readable for the same reason: they run your business, and they say nothing about where a person lives.

“The safest copy of an address is the one that never reaches a server in readable form. So we encrypt it before it leaves the shopper's device.”
CirdanHOW WE DESIGN IT

How the encryption works

Cirdan uses public key encryption. Each packing site you ship from has a key pair. The public key is published to the checkout script; the private key exists only on the paired label station at that site.

For every order, the script:

  1. Generates a fresh random key and encrypts the protected fields with it, using authenticated encryption so any tampering is detected.
  2. Seals that order key to the public key of each site that may ship the order.
  3. Sends only the ciphertext and the sealed keys with the order.

Because every order has its own key, nothing learned from one order helps with another. Because the public key can only encrypt, holding it gives an attacker nothing.

Who can decrypt

Only a paired label station, and only at the moment it prints a label. Your store admin, the Cirdan dashboard, our servers, the warehouse system and the people who use them all handle ciphertext. A breach of any of them exposes tokens and item lists, not names and addresses.

What you need to do

Install the app on your store. Orders are encrypted from that moment on. There is no setting to forget and no workflow to change at checkout.