GeodeQR

Privacy

This isn't a policy. It's a description of how the thing is built.

We never see what's in your code

Your Wi-Fi password. Your contact details. The URL. Whatever you type is turned into a QR code entirely inside your browser, by maths, on your machine. It is never sent anywhere, because there is nowhere to send it — this site has no server, no database and no backend of any kind.

We couldn't read your code's contents if we wanted to. That is a property of the architecture, not a promise you have to take on faith.

Check it yourself

Open your browser's developer tools, switch to the Network tab, and make a code. Watch the list: nothing new appears. The page loads its own files like any page does, and then it never talks to anything again — no request carries what you typed, because there is nowhere to carry it to.

The entire source is on GitHub — read it, fork it, or load the page and then turn your Wi-Fi off. It still works. That is the proof, and you don't need to trust us for it.

What we do collect

Request counts, and nothing else. Our host handles each request at the server level, including your IP address, the way every web server has since 1993, and shows us totals — roughly how many people arrived and from where. There is no analytics script on this page, no cookie, no tracking pixel, no fingerprinting, and no third-party JavaScript of any kind. We cannot tell one visitor from another, and we never see what you put in a code.

We do not have accounts, so there is nothing to log in to and nothing to leak.

The honest exceptions

Your codes outlive us

A static QR code contains its data directly. It does not point at our server, because there isn't one. If this site vanishes tomorrow, every code you ever made here keeps working — forever. Nobody can expire them, revoke them, or hold them hostage. Not even us.