Notes on Building a Safer Everyday
Company history, mission and team, written by the people who build Keep Me Safe.
Where it started
Keep Me Safe began with a simple observation. Most people who need help cannot easily ask for it. A phone is out of reach, a message takes too long to write, and a location is hard to describe when you are frightened.
Our first team sat together in one small room and tested every idea on real walks home. We kept what worked with one thumb and removed everything else.
The first prototype had one button and a list of three trusted contacts. Everything else was cut until it worked on a cold morning with gloves on.
What we believe
Safety tools should be quiet until they are needed. They should ask for little, explain what they share, and never make a person feel watched for the sake of it.
- Location is shared only when the person chooses to share it.
- An alert reaches trusted contacts without opening a full menu.
- Every setting is written in plain language and can be changed at any time.
- Data stays on the device unless a user turns on sharing.
Design reviews happen at a table with printed routes. We mark where a signal drops, where lighting is poor, and where a person would hesitate.
The team today
The team is small and mixed. Engineers, designers, a safety researcher and a support lead work on the same weekly review, and every one of them has a say in what ships.
We also talk with community workers and campus staff who use the app with the people they support. Their feedback has changed the contact flow more than once.
Most screens are sketched by hand first. A paper version tells us quickly whether a warning is clear to someone who has only a second to read it.
Keep Me Safe is a support tool, not an emergency service. In an emergency, call your local emergency number first.
Looking ahead
We are working on clearer check-in reminders and better support for shared households. Each change will be tested with the people who asked for it.
To see what the app does today, read our services page, or ask a question on the FAQ.
The reason for all of this is an ordinary evening walk. We design for the moment someone decides to turn back, cross the road, or simply send one message.