Your customers' addresses never leave your machine
A shipping label carries a real person's name, home address and phone number. The safest thing to do with that is not to collect it.
How this works, plainly
When you choose a PDF, your browser reads the file from your disk into its own memory. The cropping, the SKU reading, the sorting and the writing of the new PDF all happen there, in JavaScript, on your machine. The finished file is handed straight back to your browser as a download.
At no point is the file — or anything read out of it — sent over the network. There is no upload endpoint. This site is static files on a CDN; it has nowhere to put a label even if it wanted one.
Check it yourself, in about thirty seconds
- Press F12 to open developer tools (or right-click and choose Inspect).
- Go to the Network tab.
- Tick Preserve log, and clear what is already listed.
- Go back to the tool, choose a label PDF and sort it.
- Watch the list. You will see the page's own scripts load, and then nothing. No request carries your file.
That is the whole verification. You do not have to trust a policy page — you can watch it.
Why this design, and not the usual one
It would be easier to build this as an upload: send the PDF to a server, do the work there, send a file back. Almost every tool of this kind does.
Under India's Digital Personal Data Protection Act 2023, accepting customer names and addresses onto a server makes the operator a data processor, with real obligations attached and penalties that run to crores. And a breach at your processor is your breach — the seller's, not only the tool's.
Doing the work in the browser removes that entire category of risk instead of managing it. There is no database to leak, no backup to secure, no retention period to argue about, and no employee who can look at your customers.
What is stored, and where
| What | Where | Why |
|---|---|---|
| Your product groups — names and SKU strings | Your browser's local storage, on your device | So you do not rebuild them every morning |
| Your label PDFs | Nowhere. Held in memory while the tab is open | — |
| Customer names, addresses, phone numbers | Nowhere. Never read out of the file for any purpose but printing it | — |
Your groups are yours. There is a button to save them to a file, and the format is documented and plain JSON, so you are never locked in.
When accounts arrive
Paid accounts will need a phone number, an OTP, and a record of whether the subscription is live. That is the entire purpose of the account, and it is the only thing a server will ever hold.
Labels will still never be uploaded. The sorting will still happen in your browser, and this page will still tell you how to check it. If that ever changes, it will be written here first, in these words.
Questions
This is new and there is not a support address yet. One will be published here as soon as there is a domain to host it on — an address that bounces would be worse than saying so.
Common questions
- Do you store my shipping labels?
- No. They are never sent to us, so there is nothing to store. The PDF is opened, cropped and rewritten by JavaScript running in your own browser.
- Do you store my customers' names, addresses or phone numbers?
- No. That information only exists on the labels, and the labels never leave your machine.
- What is stored in my browser?
- Your product groups — group names and SKU strings, one set per marketplace. Nothing from a label. You can export them to a file or clear them by clearing this site's data in your browser.
- How can I check any of this?
- Open your browser's developer tools, go to the Network tab, and sort a file. No request carrying your PDF will appear. The page is static and has no upload endpoint to send one to.
Try it on your own file
No signup, no card. Your PDF is read in your browser and never uploaded.