One thing that I couldn't understand from the website: how is this triggered?

This sounds useful, but I also want an automated way to distribute the information when needed. Maybe a dead man's switch of sorts?

For example, suppose I'm a single adult, and I set this all up. Then I go for a hike and disappear forever. How can the trigger of distribution happen?

▲

sbrown12 2 hours ago | parent [-]

In our earliest versions we experimented with a dead mans switch, but feedback was that folks would forget to reply to the monthly keep alive and we'd risk triggering too many false alarms. So we opted for picking trusted family members who you grant ongoing read only access. That way in an emergency, they already have the access they need to act.

We're 100% open to the idea of a dead man's switch, just want to find a way to avoid triggering too many false alarms. Any ideas on how to do that?

▲

Calazon 2 hours ago | parent | next [-]

Optional feature, off by default, customizable time interval, and a warning about false alarms?

Even with that you'd likely still trigger false alarms regularly, though they would be the responsibility of the user. Not sure whether it would be a worthwhile tradeoff overall.

	▲	sbrown12 an hour ago \| parent [-]
		Those are good suggestions. Thanks for sharing.

▲

graerg 2 hours ago | parent | prev | next [-]

I built if-i-go-missing.com along these lines. Weird, I’m also a Brown!

	▲	sbrown12 an hour ago \| parent [-]
		Hahah, great minds think alike :)

▲

sublinear an hour ago | parent | prev [-]

Maybe an optional app? Send the keepalive email and alert the trusted family members when the app stops pinging back.

This would at least indicate that the phone is turned off or lost signal. All of this should be configurable by the user including thresholds before alert, reply timeout, etc.

I think expecting a ping from the app every 24h is a sensible default. Most people already "call to see if their phone is dead". This just automates it.