In development · Android first
If you can't respond, GABI asks for help for you.
You have people you can turn to. GABI helps reach them when you can't respond. An extra layer of support for people with type 1 diabetes and those who care for them.
GABI does not replace your alarms, medical advice or emergency services.
Meet GABI
If you can't respond, GABI asks for help for you.
From the first check-in to a message for your support network. Discover the thinking behind GABI.
Original presentation with Portuguese audio and English subtitles. Product in development. Location depends on the position available, which may be outdated or inaccurate. Glucose data integrations are in development and require authorization. Read the English transcript.
Presentation transcript in English
There is a gap no alarm can bridge on its own: the moment it sounds and the person cannot respond.
GABI asks whether you are OK, waits for your response and, if you do not respond, notifies the person you chose as your emergency contact.
The presentation describes an ordinary message with real-time location, no app needed by the recipient, and follow-up until you say you are OK. Location availability and accuracy are subject to the limitations described above.
If you can't respond, GABI asks for help for you. In development.
The gap that matters
The alarm sounds.
What if you can't respond?
Confusion, deep sleep or being alone can make it harder to ask for help. GABI was designed with that gap in mind.
- When thinking clearly is difficultConfusion can make it harder to respond.
- When sleep runs deepHearing an alarm does not always mean being able to act.
- When you are aloneThe people who support you may be elsewhere.
How it works
A path from an alert to someone who cares.
A check-in, your support network and a record of what happened.
Starts a check-in
A scheduled check-in or an SOS starts the process. Glucose data integration is in development and requires authorization.
Asks if you are OK
A deliberate tap confirms that you can respond. This interaction does not establish your state of health.
Tries to notify your contacts
If there is no response, GABI attempts to send an SMS to your chosen contacts. The available location helps them know where to look.
Keeps the episode in view
The episode stays in your history. Responding to the app does not mean the risk has passed. A better location can update the same alert.
Notifications depend on configuration, permissions, battery and mobile signal. Sending, delivery and a response from contacts can fail.
Inside the app
A clear action.
At every step.
Illustrative screens Excerpts from the visual identity guide. Sample data only.
On mobile, swipe to explore the flow. Go to the first screen.
Check-in
A tap to respond.
The screen asks for a deliberate action to confirm that you can interact.
Follow-up
Responding is part of care.
Your interaction is recorded. Follow-up continues until the alert is closed.
Manual SOS
You can ask for help, too.
An intentional action starts a request to your contacts. It does not depend on glucose data integration.
Caregiver dashboard
People who care need to know where to look.
The dashboard shows the location available for the episode to linked caregivers. Always check the timestamp and location accuracy.
Discuss institutional useLocation in the context of an alert
The location may be outdated, inaccurate or unavailable. The dashboard does not provide continuous tracking.
Directions in development
Access to directions through mapping services in the caregiver dashboard is in development and will require internet access.
Calm technology
Clear rules.
Careful attention to context.
Explore the logic behind GABI's check-ins and notifications.
No black box
The app engine uses deterministic rules. It does not diagnose conditions or recommend treatment.
On your phone
The safety logic runs locally. Device permissions and restrictions affect how it works.
A deliberate response
A deliberate tap records that you can respond to the check-in.
Location with a fallback
Current, last known or last valid stored location. The first notification does not wait for a new position.
One alert, one record
The history brings the episode together. A new location adds context to the same alert.
SMS notifications
Sending from the phone depends on signal and permissions. Manual sending requires confirmation; server sending requires a connection and an enabled service.
For health technology partners
An alert is the beginning.
Connecting people to help comes next.
GABI aims to bridge the gap between an alert and help. A communication layer connecting monitoring with people who can act.
More context for your technology. More support for the person.
A check-in turns a missed response into a request to the chosen network, with the available location and a record of the episode.
Safety through explainable logic
Deterministic rules that can be explained and audited. No diagnosis or treatment decisions.
A layer that runs on the phone
Local logic organizes check-ins and notifications within the device's operating conditions.
Privacy by design
Careful handling of sensitive data under Brazil's LGPD. Location shared only during an alert.
Room to build together
Architecture designed to accept authorized glucose data sources. An episode history that can support reporting.
Glucose data integration is in development and requires authorization. This is where we build together.
Discuss a partnershipWho it is for
For you.
And the people who care about you.
People with type 1 diabetes
A support network for people who live alone, travel or sleep without someone nearby.
Parents and families
Chosen contacts who receive notifications and agree on how to respond.
Health programs
A communication layer that brings follow-up closer to a person's support network.
People working alone
Scheduled check-ins and SOS to help communicate with your network.
The people behind GABI
Technology built by people who understand care.
BWJ SYSTEM LTDA
A Brazilian health technology company founded by a physician.
We build digital platforms used in the daily work of clinics and health services. That experience connects engineering with the needs of people who provide care.
At GABI, we work with independent review and a focus on safety and Brazil's LGPD. Every stage of development must be understandable, open to review and responsible.
Talk to the people building GABIPrivacy and safety
You choose who gets notified.
Health and location information require care. We handle this sensitive data in accordance with Brazil's LGPD.
Read the Privacy Policy- Contacts chosen by you
Agree on availability and confirm who accepts your notifications.
- Location during an alert
The available location is shared in the context of the episode, without continuous tracking.
- No forms on this website
Speak directly with the team. Please do not include health information in your first message.
Before you ask
Frequently asked questions
Does GABI replace my alarms?
No. GABI is a communication layer for when you cannot respond. Keep using your alarms and following your care team's advice.
Do my contacts need to install the app?
Not to receive SMS messages. Choose your contacts, check their numbers and agree on what to do when a notification arrives.
How does glucose data integration work?
It is in development and requires authorization. Scheduled check-ins and SOS already work without this integration.
Does GABI contact emergency services?
No. GABI attempts to notify your chosen contacts. In immediate danger, contact local emergency services. Do not wait for the app or a response through this website.
What if my phone has no signal?
SMS requires a mobile signal. Permissions, battery and device restrictions also affect notifications. Agree on a backup plan with your support network.
When will GABI be available?
GABI is in development, starting with Android. There is no launch date yet. Talk to the team to learn about the project's current stage.
