Changelog

An automated battery runs the full journey daily (sign-up, protocol, missed deadline, alert delivery) on classic, location and recurring protocols. If the chain breaks, we know before you do.

Check-ins made offline are queued and sent when you reconnect, deadlines follow your device timezone, and the server applies its own grace period rather than trusting the clock it is given.

Access controls, rate limits and PIN attempt caps were tightened across the account, contact and data-export paths. Nothing to do on your side.

Retention-based deletion no longer just runs: an automated check confirms every day that it actually removed what it should have.

A contact whose key could not open an encrypted link used to see an empty result that looked like success. It now says plainly that the link could not be opened.

A badge on the protocol shows any contact the alert failed to reach, instead of leaving the failure buried in a log.

A contact who lost the PIN protecting your emergency package can get a new one, with rate limiting so the flow cannot be abused.

Contacts who never accepted their invitation can no longer be selected, and launching is blocked if one slipped through. An alert going to nobody is worse than no alert.

Running out of monthly SMS no longer means an alert is silently dropped. It goes out by email instead.

Location confirmations are checked against the geofence, and the alert pipeline no longer sends the same alert twice under load.

Plan entitlements are now server-controlled end to end, with no permissive fallback when a price reference is missing.

The product had been shipping under two names. It is now Safety Checkpoint in the app, the emails your contacts receive, and the store listings.

End-to-end tests now cover sign-up, protocol creation, missed deadlines and alert delivery: the paths where a regression would be unacceptable.

After nine months of building and four months of private beta, sign-up is open. The beta gate, the waitlist and the invitation codes have been removed.

A launch rate for the people who show up first, alongside the permanently free plan.

Eleven pages setting out where Safety Checkpoint differs from other safety apps, including where another tool is the better fit.

Around thirty guides (solo travel, night shifts, caregiving, protests, living alone) rewritten to a single standard, with sources.

A native app with push notifications and local reminders before each deadline, so a check-in does not depend on having a browser open. Android is in progress.

Fixes reach your phone without waiting days for a store review. On a product that has to work on the worst day, that matters.

A one-off option for people who would rather not think about a subscription for something they hope never to use.

An automated security suite now gates every change, and the admin security views were consolidated into one.

A contact's language is set on their record, so the alert and the emergency page they open arrive in the language they actually read.

Images converted to modern formats, the bundle split, and heavy pieces like the map loaded only when needed.

Changing a heartbeat interval left the previous reminders scheduled. They are now cancelled, and the frequency shown matches the one in effect.

A link your contacts can open to see a live countdown and the current state of your protocol, so an alert never arrives without context.

Optional notification by email or SMS the moment you arm a protocol. Useful when someone is expecting you.

Deadlines and reminders are computed in your timezone instead of the server's, and push notifications arrive translated.

A recurring protocol could get stuck on a past occurrence and stop generating the next one. It now recovers on its own.

Access by invitation, with a waitlist. Small enough to watch every alert that goes out.

Alerts now reach contacts by push and SMS as well as email, in English, French or Spanish.

Being someone's emergency contact is a commitment. It can now be withdrawn at any time, as an action distinct from being deleted.

Record a message in your own voice for the emergency package, encrypted like everything else in it.

Row-level access rules were reviewed and hardened on every table, and a content security policy was added to the site.

Alerts are now composed and sent server-side, deduplicated and throttled, instead of depending on a browser being open.

Pick a destination and a radius on a map; the protocol closes itself when you arrive. With a manual override for when GPS will not cooperate.

Both available directly in settings, without going through support.

A PIN is generated when a contact accepts their invitation, and it is what unlocks your emergency package for them, and only them.

A disclosure form for security researchers, so a finding reaches us privately rather than publicly.

Confirm at the cadence you choose, with a grace period, and pause or resume when your plans change.

Written guides for each protocol type, because a safety tool you do not understand is a safety tool you will not arm.

Sensitive actions (stopping a protocol, deleting one, opening encrypted content) now require your PIN, with role-based limits behind them.

Error monitoring was wired in, along with quota checks so an account cannot silently exhaust its alert allowance.

Message, files and links are encrypted before they leave your browser, wrapped per contact. We hold the ciphertext and cannot read it.

Scheduled server-side so they fire whether or not the app is open. The point of a dead man's switch is that it does not need you.

Documents, scans and photos can be added to the package and are encrypted with it.

Contact edits are audited and deletion is soft by default, so an accidental removal does not quietly empty your safety net.

The alert pipeline goes live: a missed deadline now produces a real email to your emergency contacts.

Invitations by email with a real choice at the end. Nobody becomes your emergency contact without agreeing to it.

No password to forget on the day you need the app most.

A missed deadline now has a proper state of its own, with a way to resolve it after the fact.

The core mechanism: a deadline you confirm, and a consequence if you do not.

The editor for the message that gets delivered on your behalf: what happened, where you were, who to call.

Who receives what, and in which order.

Daily and weekly schedules, for routines rather than one-off trips.

The emergency access portal: what someone sees when they receive an alert about you, designed to be readable by someone who is worried.