About
Why this exists, and why it's built the way it is
Most emergency ID products want you to download an app or make an account before a stranger can read your information. That's backwards. The person who needs to read your allergy list is a bystander who's never heard of the app, or a paramedic with thirty seconds to spare, not someone who's going to install something first.
So TagLineID works the other way. You fill in a form once, get a QR code, and print it onto whatever you're already carrying, a bag tag, a wallet card, a bracelet. Scan it and the information just shows up in a browser. No app, no login, no waiting.
How it actually works
There's no database behind this. When you fill in the form, your information gets packed into the link itself, after the # symbol in the URL. That part of a web address is called a fragment, and browsers never send it to a server, not on the page that generates it, not on the page that reads it back. Your data travels from your screen into the QR code and back out again without ever passing through anything we run.
That also means there's genuinely nothing for us to lose in a breach, because there's nothing stored anywhere to breach. If this project disappeared tomorrow, every QR code already printed would keep working, since the page itself just needs to load once in a browser to decode what's already in the link.
What this doesn't do
It isn't encrypted. Anyone with the link or the QR image can read what's on it, and that's intentional, since the whole point is that a stranger can read it without a password. Read the privacy page for the full detail on what that trade-off means in practice.
Supporting this
This stays free, always, since charging for something people rely on in an emergency doesn't sit right. If it's been useful to you and you'd like to help keep it running, there's an optional way to chip in below. Nothing here is asked for anywhere you'd actually be scanned, only on this page, for people who came looking.