Privacy & Source
Privacy
How this redirector handles your data, the short version, because there isn’t much.
Last updated · June 2026
- Static pages only. Every page is a plain file. There is no application server and no database.
- No logs. Nothing on my side records who you are, what you scan, or where you go.
- No cookies, no analytics, no trackers. Nothing is stored on your device.
- No third-party resources. No external fonts, scripts, or assets load. Your browser talks only to this host, then to whatever source you choose to open.
How the app works
Each QR code in the book points to a short address on this site, like liesabove.app/v1/fn5/1/. That address is a small HTML file, prepared ahead of time from the book’s list of citations, that shows you where you’re going and then forwards you to the source it cites. Nothing runs on a server when you visit: the routing is baked into the file, so the whole site is just a folder of static pages that GitHub serves as-is.
The technical version
- Book / QRA printed QR code holds one address, like
liesabove.app/v1/fn5/1/. - Your browserOpens that address over
HTTPS, an encrypted connection. - GitHub PagesThe static host looks for a file at that exact path. No program runs, there are only files.
- 200 OK the file exists, so its page is sent back.
- 404 no file matches, so the branded Not Found page is sent instead.
- Redirect pageA plain HTML file. It shows you where you are going, then your browser forwards itself there. No
301or302server redirect, so nothing logs a hop in between. - Cited sourceYou arrive at the third-party page the book cites, which has its own rules.
HTTPS: the padlock in your address bar. The whole site loads over an encrypted connection, so the page cannot be read or changed on its way to you.200 OK: the reference exists and its page reached you. The ordinary “it worked” response.404 Not Found: the address matches no reference, so the branded Not Found page appears (usually a wrong or mistyped code).No 301 / 302: there is deliberately no server redirect (the usual way one address bounces you to another). The page arrives as an ordinary file and forwards you from inside your browser, so you see where you’re going first and nothing logs a hop in between.
In short: a folder of plain pages, served over an encrypted connection, each one showing its destination before it hands you off.
Why there are no logs
Because the site is static, I never run any program when you load a page, so there is no place for me to log anything. I receive no analytics, no IP addresses, no visit counts, and no record of which links get scanned or followed. There is nothing on my side to collect, because nothing on my side runs.
That said, I want to be completely straight about one thing: the host does receive your data, and I can’t prevent it. To open this site, your browser has to connect to the server that serves it, GitHub Pages. By the basic nature of how the web works, GitHub receives that request and can see data such as your IP address and which page you asked for, in order to deliver the file and guard against abuse, under GitHub’s own privacy statement. This is true of any web host I could use; it is not something this site adds or could turn off. I don’t have access to that data and receive no reports from it.
I chose GitHub Pages deliberately, with that trade-off in mind. Because the code is public and served straight from the repository, anyone can see exactly what is running at any moment. There is no hidden backend you have to take on faith. I decided that being able to show you the code was worth more than routing your traffic through a host that would be harder to verify.
Where your scans go
Following a QR code sends you to a third-party source chosen for the book’s citations, such as a website, document, video, or archive. Those destinations have their own privacy practices, which this site does not control. This site does not track which links you open.
See it for yourself
You don’t have to take my word for any of this. The entire site (every page and the short script that generates the redirects) is open source. You can read exactly what gets served, confirm there are no trackers, and see how a citation becomes a redirect.
View the app source code on GitHub, then check the generator (gen.sh) and the citation list (redirects.json).
Security
This app is built to be hard to get wrong. It is only static files: no server-side code, no database, no accounts, and no third-party scripts, which leaves very little to attack or break. The small amount of JavaScript here is plain (no frameworks, no libraries) and is used only where it is genuinely needed, such as forwarding you to a source or remembering your preference. All of it runs in your browser.
It is also auditable by design. Every change to the site is a public commit on GitHub, so what is being served can always be checked against the source, and the history shows exactly what changed and when.
If you ever find a page here serving malware, or anything that looks tampered with or otherwise wrong, please tell me.
The book’s site, liesabove.com
This page covers the redirector you’re on now (liesabove.app). The book’s main website is a separate site, liesabove.com, with the landing page, the trailer, and the articles. If you typed the .com address, or came for the trailer, here’s how that site treats your data.
That site isn’t static like this one. It runs on Ghost, a hosted publishing platform, on Ghost’s own infrastructure, with its data kept in the EU. As with any real host, Ghost receives the usual request data (such as your IP address) in order to serve pages and guard against abuse; that part is governed by Ghost’s privacy policy, not this one.
liesabove.com keeps simple visitor analytics, held to the bare minimum Ghost provides. They’re privacy-friendly by design: first-party (served from the site itself, not a third party), cookie-free (nothing is stored on your device, so there is no cookie banner), and a repeat visit within a 24-hour window isn’t counted as a new person. What I can see is only aggregate: how many people visited, which country they were in, and which link or site sent them. I don’t see who you are, and I’ve added no Google Analytics, advertising pixels, or third-party trackers.
One thing does reach me personally, and only if you choose it: subscribing to the newsletter hands Ghost your email address so the book updates can be sent, and that address is visible to me in Ghost. It’s opt-in, it happens only when you submit the form, every email carries an unsubscribe link, and I don’t sell or share it.
A note on AI
Artificial intelligence was a tool in making this book and this site, never a replacement for the people doing the work. A human verified every fact, and every original idea is the author’s own. No AI-generated audio, interviews, or video appears anywhere, and the cover art and trailer were made by a human designer. For the longer account of what AI helped with and where it fell short, read the AI use page.
Changes & contact
If this policy changes, the “last updated” date above changes with it. Questions about privacy or the book? Visit liesabove.com.