People decide the response
BackBy is not a dispatch center and not a rescue service. It sends no one to look for you. The person in town decides what to do using the trip plan you prepared.
Reliability & independent review
Trust built into the design.
A traveler may be out of contact for days. BackBy is designed to preserve the Plan and its history while the Backer checks for updates from home. Recoverable records and independent verification are central to that vision.
The design
Keep the plan intact. Make the history checkable.
Backer phones check for updates
Backer apps are designed to check the server and notify locally. The server sends no messages. Internet access, phone settings, and background delays affect when a Backer learns about a change.
A record of every change
Each change adds an event instead of overwriting history. The audit design uses signed proofs so independent reviewers can check that history.
Recovery after an outage
Recoverable Plan records and copies of public integrity proofs will help preserve the record through outages.
Behind your check-in
Designed to last beyond one check-in.
The design brings together private access, recoverable records, and independently checkable history. Explore how these parts work together in the technical documentation.
| Protection | Design purpose |
|---|---|
| Plan history that survives a restart | Plan records that can be restored and rebuilt after a restart. |
| Independently verifiable history | Signed proofs that let independent reviewers check for changes to history. |
| Private access to Plan updates | Secret-gated discovery that keeps precise timing out of public lookup. |
| Outage recovery | Recovery paths and independent copies of integrity records. |
| Private or offline maps | A future option to view maps without sharing the viewed area with a third-party provider. |
A product open to scrutiny.
Explore how BackBy handles Plan history, protects private details, and makes its design open to independent review.
Review the public repository