facecard.ink
Two different things happen here, and only one of them touches a server.
The QR code and the dithering are computed in your browser. The picture you upload is never sent anywhere — it is read into a canvas on your own machine and stays there.
If you use Use profile photo, the handle you typed is sent to our server, which fetches that public avatar through unavatar.io and passes the image back. We do not keep the picture or the handle.
A tracked card encodes a link on this site rather than your destination, so we see each scan. Untracked cards point straight at your link, and we never see them being used at all.
For each scan of a tracked card we store:
The IP address itself is never written down. Because the salt changes every day, a hash from today cannot be matched against one from yesterday — it can count how many distinct people scanned a card today, and nothing beyond that.
Link previewers — the crawlers that fetch a URL when you paste it into a chat — are recorded separately and never counted as scans.
Whoever holds its manage link, and the device that first scanned it. There are no accounts, so we hold no name, email or password for you.
Your browser keeps a list of the cards you have made in local storage, and we set one cookie holding a random device identifier so a card can recognise the device that claimed it. Neither is used for advertising, and neither is shared.
Clearing site data removes the cookie and your local list. To delete a card and its scan history from our side, open its manage page and ask — for now, email maxmorel@pisanvs.cl with the code and it will be deleted.
We use Vercel Web Analytics for aggregate page counts. It sets no cookies and does not fingerprint visitors.