Aug 23, 2026
We killed the delivery engine mid-flight
A reminder was due while the engine was down for 13 minutes. On restart, the alert fired 150 milliseconds later — late, recorded as late, and not lost.
Trust, shown — not claimed.
Sureday guards dates people cannot afford to miss, so "trust us" isn't good enough. This page shows the live numbers, the machinery, the drills where we break our own system on purpose, and exactly what happens if we ever fail you.
The numbers, live
Computed at page load from the same append-only tables we'd hand a lawyer.
Reminders under guard right now
6
Alerts delivered to hands and inboxes
16
Confirmations recorded
5
Guaranteed dates missed
0
The number this company exists to keep at zero.
Median time from due moment to first alert
384.7s
Alerts out within 2 minutes of the due moment
33.3%
We are new, so the numbers are small — they are also real, and include our own drills. Safety-net recoveries to date: 1 — each one an alert that arrived late instead of never, and each one recorded.
How the guarantee works
Nothing is ever silently lost. When you save a date, the reminder and its scheduled alert are written to the database in a single transaction — there is no moment where one exists without the other. Every alert, reply, confirmation, and failure is appended to a permanent audit log that nothing in our system can edit or delete.
Escalation until a human confirms. Push and email first; then a text; then automated phone calls; then your emergency contact; on Guardian, a human being calls. Any confirmation — a tap, a YES, pressing 1 — stops the ladder. Silence never does.
Three watchdogs, one of them outside our walls. Every five minutes our system re-proves five invariants against the live database (among them: no alert has ever gone to an opted-out number, and no scheduled date is sitting unhandled). A dead-man switch at an independent monitoring service alarms the founder if our delivery engine goes quiet for 15 minutes — that one works even if all of Sureday is down. A third probe checks us from GitHub's infrastructure every 30 minutes.
We break Sureday on purpose
Before trusting the system with your dates, we attacked it with ours. The drill log, with real timestamps from production:
Aug 23, 2026
We deleted a scheduled job on purpose
The safety net noticed the orphaned date on its sweep and fired it 6 minutes past due, writing a “recovered by the safety net” entry to the timeline.
Aug 24, 2026
We corrupted our own database
We planted a record that violated our invariants. The next 5-minute sweep detected it, and the founder's phone buzzed one second later.
Aug 24, 2026
We let the engine die silently
No crash, no error — just silence. The independent dead-man switch alarmed the founder at minute 13, from infrastructure that shares nothing with ours.
If we ever fail you
If a guaranteed reminder is missed because of us — the ladder didn't run as promised — you get a full refund of your current billing period, a $50 credit, and a personal apology call from the founder. The audit log decides what happened; it's the same record either way. The full refund policy.
Security, in plain words
- Your data lives in a managed Postgres database in the United States, encrypted in transit and at rest, with daily backups.
- Confirmation links are single-purpose random tokens, stored only as hashes, and die as soon as the alert is resolved. They never log you in.
- Phone numbers are masked in our logs (+1***1234). Full numbers are shown to staff only on an audited, recorded reveal.
- Texting STOP halts messages to that number immediately and permanently, account or not — a rule our watchdog re-proves every five minutes.
- We keep only what the service needs: name, email, phone, timezone, your reminders. We don't sell data. We have no advertising relationships.
- We never ask for case numbers, SSNs, or document numbers — a reminder title like “I-751 window opens” needs none of them.
Questions this page didn't answer? Email the founder. Computed 2026-08-24 03:49 UTC.