Guardian journey
Set where you are going, when you expect to arrive and who you want informed.
The first WITH. app is planned around journeys, short safety timers and asking for help. You would choose when to start and who should be involved.
WITH. is in development. These pages explain the plan, not a live safety service.
Before starting, the app should explain the help steps and show whether location permission, connection and chosen contacts are ready.
Set where you are going, when you expect to arrive and who you want informed.
Set a short timer, then confirm you are okay when it ends.
Choose friends, relatives or other people who can receive your updates.
Open an example to see the planned steps. Timings and names here are illustrative, not fixed app rules.
You finish work at 21:00 and expect to be home by 21:45. Before leaving, you start a Guardian journey and choose your brother and a friend as trusted contacts.
The benefit is a shared plan. Your contacts would know what you expected to happen, rather than having to guess from a missing message.
You expected to arrive at 18:30, but traffic slows the trip. WITH. would ask you to check in. You confirm you are okay and update the plan.
If you do not answer, it would follow the steps you chose: for example, try you again and then notify a trusted person. That person might call to check on you.
A missed check-in does not automatically dispatch help or prove you are in danger. Professional response would depend on an available service and the rules agreed for your plan.
You expect the walk to take eight minutes. You set a Safety Countdown and choose what should happen if you do not check in.
If you reach the car and confirm you are okay, the timer ends normally. If it expires without a response, the app would follow your reminder and contact plan.
You would not have to wait for the timer if you need help sooner. SOS is a separate action, explained below.
You leave a place with Wi-Fi and have no mobile data. GPS may still give your phone a location, but the app cannot send fresh updates to other people without a connection.
Your trusted people would see the last successfully shared location and its time, not a moving dot pretending to be live. The app should clearly say that updates are paused.
If a help request had already reached WITH., the plan is to keep it open. A new SOS that cannot leave the phone must not be presented as sent. SMS and other backup connections are future work, not current promises.
In the planned app, SOS would skip routine reminders and immediately start the available help process. It would not mean that a professional team is already on its way.
A response provider is an organisation, such as a connected security or medical service. A responder is the person or team it assigns. Professional help would only be offered where a real service and agreement exist.
The app should show each step honestly. These are proposed labels, not live request updates:
We should only say help is on the way after the provider confirms it. This website and its preview cannot receive or dispatch a live emergency request.
The important limits should be as easy to understand as the features.
Not as a universal rule. Before starting, the app should explain which contacts and services are involved and what would trigger each step. An unanswered check-in would follow that plan. SOS should not wait for ordinary reminder steps.
WITH. is still defining and testing these arrangements. It does not offer automatic dispatch today.
The app should try further contacts or help options only if they are part of your agreed plan and available. It must show when no one has accepted the request, rather than imply that someone is responding.
A request already received by WITH. should remain open, using the information last shared. That does not create new location information or prove what happened to you. If the phone never sent the request, WITH. cannot act as if it received it.
You confirm you are okay and routine location sharing ends. If a help request is still active, ending the journey or closing the app should not quietly close it. That request needs a separate resolution process.
That is part of the longer-term goal. A watch could make check-ins or SOS easier to reach. Vehicle and transport connections could add useful information with permission. Device support, battery limits and connections must be tested first; none is promised today.
We want to explore discreet check-ins and carefully chosen support for these situations too. Privacy controls and specialist advice are especially important. This needs separate safety testing and is not a live feature or a promise that an app can judge a relationship.
Tell us what we have missed or which step feels unclear. That is exactly the kind of feedback this website is here to collect.
Read short answers about the planned app. This guide uses prepared answers and cannot monitor you or send help.