Privacy-first schedulingthat still finishes the job.
When you send a scheduling link to your board, your class, or your band, you're making a privacy decision for people who never got a say. Here is exactly what happens to their data — every claim on this page is verifiable in your browser's devtools.
The four commitments
Data lives in Frankfurt
The application runs on Vercel functions pinned to the Frankfurt region (fra1) and the database is Neon Postgres in AWS eu-central-1 — also Frankfurt. Static assets are cached on a global CDN; your poll data is not.
Voter emails never reach public pages
Emails are optional for voters and are stripped server-side from every public surface: the poll page, its data payload, the event page, and calendar downloads for anyone but the organizer. What isn't sent to the browser can't leak from it.
No ads, no third-party trackers
Open devtools on any poll page: no ad networks, no fingerprinting scripts, no Google Analytics. Traffic counting uses Vercel's cookieless, first-party analytics. Error monitoring runs with personal data collection disabled.
Privacy and a finished job
Free EU tools like Framadate and nuudel share this privacy posture — and stop at the grid. Meetsched closes the loop: finalize the winning time, notify everyone, hand out calendar files, collect RSVPs.
What your voters actually hand over
A name. That's the requirement. Email is optional (it exists so voters can be notified of the result), there is no account wall, and anonymous responses can only be edited from the browser that cast them — enforced cryptographically, not by trust.
The complete cookie list
Session and CSRF-protection cookies from our auth system. Voters who never sign in never get them.
A first-party, 30-day cookie remembering which link brought you here (e.g. a shared poll badge), so we know what's worth building more of. No third party ever sees it.
That's the whole list. Nothing from ad networks, nothing cross-site.
Who else touches the data (subprocessors)
| Service | What it does |
|---|---|
| Vercel | Application hosting — functions pinned to Frankfurt (fra1); global CDN for static assets |
| Neon | Postgres database — AWS eu-central-1 (Frankfurt) |
| Resend | Transactional email delivery (invitations, results, reminders) |
| Stripe | Payment processing — paid plans only; we store no card data |
| Upstash | Rate limiting — short-lived, IP-keyed counters only |
| Sentry | Error monitoring — personal data collection (PII) disabled |
| Google / GitHub | Optional sign-in (OAuth). Calendar sync only ever creates its own 'Meetsched' calendar — it cannot read your primary calendar |
Data retention is boring on purpose: free-plan polls are kept 90 days, Pro polls one year, and deletion means deletion. Questions, or want your data removed? Email rudi@rudidev.no — you'll get the founder, not a ticket queue.
Schedule the next one privately
Free to start. Your voters never need an account — and never see an ad.
Create a poll