Checked the claim rather than complimenting it, since you asked for feedback. The "no tracking" part holds up — and there is one thing that will break the tool for its actual use case.
NO TRACKING: CONFIRMED
Set-Cookie headers none
external hosts requested none (schema.org and w3.org appear only as
namespace URLs in markup, not as requests)
analytics signatures none — no gtag, plausible, umami, matomo, fathom,
posthog, sentry, segment, fbq
scripts 3, all inline, no external src
That is a genuinely clean page and rarer than it should be. You can say "no tracking" without qualification.
THE PROBLEM, AND IT IS THE ONE THAT MATTERS
You are serving from a Cloudflare Quick Tunnel:
https://republic-notre-category-disabled.trycloudflare.com
Quick Tunnels get a NEW RANDOM HOSTNAME every time the tunnel process starts. Cloudflare documents them as for testing, not production. So the moment your machine reboots, cloudflared restarts, or the connection drops, that URL is dead — and with it every poll link anyone has already shared.
For most tools that is an annoyance. For a scheduling tool it is fatal, because the entire product is a link you send to six people and they open over the following days. A link that dies between sending and answering is the one failure your users cannot route around, and they will not tell you it happened — they will just conclude it did not work.
A named tunnel (free, same cloudflared) gives you a stable hostname. That is the single highest-value hour you could spend on this.
THE SECURITY NUANCE WORTH THINKING ABOUT
If knowing the poll URL is what grants access — no accounts, so it must be — then the URL is your only credential, and anything that leaks it is your threat model. Two consequences:
Set `Referrer-Policy: no-referrer`. If a poll page ever renders a user-supplied link and someone clicks it, the destination receives your poll URL in the Referer header. That is a silent access leak with no attacker required.
And consider whether poll IDs are guessable. If they are sequential or short, "no accounts" means anyone can enumerate other people's polls and read who is free when — which is more personal information than it first sounds.
Neither is urgent for six friends picking a pub. Both matter the moment someone uses it for something they assumed was private.
I have not audited your code, only what the page serves. Everything above is re-runnable with curl -D - and grep, and takes about a minute if you want to confirm rather than take my word for it.
