Privacy
Last revised: 2 November 2026.
MyHelpGroup is an app for Android phones — with an optional Wear OS watch — and for iPhone. It lets a small group of people know you are well, and tells them quickly when you are not. This page explains what the app collects, where it goes, and what never leaves your phone.
Most of it is the same on both systems. Where they differ, the text says so: a part marked Android applies only to the Android app and its watch, and a part marked iPhone applies only to the iPhone app. Everything else applies to both.
Who is responsible
The controller of your personal data is Cesar Bremer Pinheiro. Write to support@myhelpgroup.com about anything on this page, including to exercise the rights described below. Further identification details of the controller are provided on request to the data subject, or to the Brazilian data protection authority (ANPD).
Before anything else
MyHelpGroup does not replace public emergency services, and it is not a medical device or a monitoring service. In an emergency, call your local number first — 911 in the United States, 112 in Europe, 190 or 192 in Brazil.
What the app collects
| What | When | Why |
|---|---|---|
| The identifier, name, e-mail address and language you type | Once, when you register | To create your account and confirm your e-mail address |
| A device identifier and cryptographic keys generated on your phone | Once, when you register | To authenticate this phone to the server |
| Your location | Only if the Location options are on (they are, unless you turn them off) — see the section below; it differs between Android and iPhone | So your group can find you when you raise an alert, and on iPhone also when you miss a check-in |
| Network status: the address your phone uses, connection quality, round-trip times | With every status message, about every 25 seconds | To keep the connection alive and to choose the nearest server |
| The next five scheduled check-in times | With every status message, and whenever the schedule changes or is paused | So the server knows your schedule even after a long interruption, and can alert your group if no device of yours reports a check-in |
| Alerts and emergencies you send, and who confirmed, is on the way, or arrived | When you use them | To show everyone in the group what is happening |
| Groups, invitations and roles | When you use them | To keep the group together |
| If you report someone: who you are, who you reported, the reason you chose, the text you write if any, where it happened, and — when you report an alert or a voice message — a copy of that message | When you send a report | So our support team can review it. See the section below |
| If you block someone: the pair of user identifiers — who blocked whom | When you block, until you unblock | So no more invitations pass between the two of you |
| An activity log of the app itself, sent to our own server | Sent in batches | To diagnose failures |
| Android — if you link a watch: an identifier for the watch, its position while an emergency it raised is open, and your answers to check-ins made on it | When you link it, and when you use it | So the watch can ask for help on its own, and your group can find you |
| Android — if you turn on the watch’s sensors: which detection fired — a fall, no pulse, a heart rate out of range, sudden running, low battery — and whether it was an emergency or an alert | Only when a detection fires and you do not cancel it | To tell your group why they are being called. Your heart readings and steps stay on the watch; see below |
| If your group has an administrator: who it is, which settings are hidden, and a check derived from the password — never the password itself | When the administrator is set or changes something | So the settings stay as the administrator left them, on every phone of yours |
| Audio from the microphone | Only while the voice monitor is running — on iPhone, only while the app is open on the screen | To hear a keyword or a shout. It is turned into words on the phone itself, and is neither recorded nor sent anywhere; see below |
| A voice recording of up to 20 seconds | When the countdown of an emergency of yours opens — on an Android phone or an iPhone, or when you press SOS on a linked watch — if Record voice on SOS is on (it is, unless you turn it off) and you allowed the microphone | So your group hears what is happening. See the section below |
Neither app shows advertising or tracks you, and neither contains analytics or advertising SDKs. The iPhone app contains no third-party SDK that receives your data.
About your location, precisely
Sharing your position is optional. Two options in the settings — Send location periodically and Show location in an emergency — come switched on and can be switched off at any time, and the choice applies to all your devices. See how the choice works.
Android. The app asks for location permission and collects new positions in two situations only: while it is open in the foreground, and while an alert or emergency of yours is open — then it keeps taking positions even with the screen off, through a foreground service that shows a notification the whole time, until the message is closed or 24 hours have passed. It deliberately does not use Android’s background location permission.
However, the last known position stays in the app’s memory and, if Send location periodically is on, is sent to the server with every status message — about every 25 seconds — for as long as the background service is running. If you never grant location permission, the position sent is zero.
iPhone. The app first asks for location While Using the App, and then asks you to allow Always. With Always, it keeps running in the background and, if Send location periodically is on, shares your position periodically with your own group only — with the status message, about every 25 seconds — even with the screen locked, so that your group can find you during an emergency or when you miss a check-in. This is a real difference from Android: on iPhone, positions keep being collected in the background whenever you have allowed Always, not only while an alert is open. If you keep While Using the App, new positions are collected only while the app is open; if you refuse location, your group will not see where you are. You can change this at any time in the iPhone’s Settings → MyHelpGroup → Location.
You decide whether your position is shared
The app’s settings have a Location section with two switches, both on by default:
- Send location periodically — your last known position goes to the server with every status message, about every 25 seconds.
- Show location in an emergency — during an emergency of yours, your group sees your position on the map and can share the live location link.
The choice belongs to your account, not to one device: it applies to every phone of yours and to a linked watch, and our server enforces it. A position that reaches the server while the option is off is stored as hidden, and nobody is shown it.
When you turn an option off:
- Your group sees Location not shared where your position would be — no map and no live location link. The e-mail with the voice recording goes without your position and without the link.
- An emergency carries your position only if Show location in an emergency is on. An alert — a check-in nobody answered, for example — is left without a position only when both options are off.
- Positions already stored stop being shown.
- A linked watch still takes a GPS fix for its message, but the server discards the position. iPhone: the app keeps low-accuracy location running so that it stays alive in the background, but does not send the position.
Whichever you choose, your position is shown only to your own group — and to whoever opens a live location link that someone in your group shares — and is never used for advertising or tracking.
Why we recommend keeping it on. With Send location periodically on, your last position stays on record. If you lose signal, your battery dies, or you get lost and do not know where you are, the alert and the emergency still show your group where you were last seen.
What turning it off costs. In an emergency, your group can only reach you — or tell responders where you are — if they know your position. Without it, your group and the emergency services may not know where to look for you. MyHelpGroup does not replace your local emergency number.
About the watch’s sensors (Android)
The watch’s detections are all off until you turn them on. When they are on, the watch reads your heart rate, your steps, its movement and Wear OS’s own fall detection, and decides on the watch whether something is wrong. Those readings are kept on the watch only as long as the detections need them, and are never sent to our server or to anyone else. What leaves the watch, when a detection fires and you do not cancel it, is the same message the SOS button sends: the kind of detection, whether it is an emergency or an alert, and your position.
The age and heart-rate limits you type on the phone go from the phone to the watch through Wear OS’s own connection between the two; our server does not receive them.
About the voice recording
The voice recording works the same way on Android and on iPhone. When an emergency of yours starts its countdown, the phone records up to 20 seconds of sound: your voice, or whatever is around you. Cancelling the countdown erases it and nothing is sent. Once the emergency has gone out, the recording goes to our server, encrypted on the way like every other message. It is not encrypted with your group’s key, because the server has to read it to attach it to an e-mail.
- On our server it is held only in memory — never written to disk, never in a log — and deleted when everyone in the group has received it, when the emergency is closed, or after one hour, whichever comes first.
- By e-mail, it goes to every participant of the group who has an e-mail address, you included, with the time, the identifier of the emergency, what started it, your last known position, the emergency’s live location link (see below) and a SHA-256 fingerprint of the file. The e-mail is meant as the lasting record, and it stays in each recipient’s mailbox for as long as they keep it.
- On the phones of your group it is kept inside the app, and deleted 30 days after the emergency is closed. Each person can delete it from their own phone sooner. A watch deletes its recording as soon as it has been sent.
- When the emergency went as a text message because there was no internet, the recording stays on your phone only.
About the live location link
When an emergency of yours goes out over the internet, the server creates a link of the form
https://loc.myhelpgroup.com/…, with a long random code that cannot be guessed. Alerts do not get
one, and neither does an emergency that went only as a text message.
- Who sees it. The link does not leave anyone’s phone by itself. It is sent only when someone taps Share live location and chooses where to send it — you, on the emergency screen, or any member of your group, from the map of your emergency, because the person who asked for help may not be able to do it. Whoever receives the link can open it, with no account and no app.
- What it shows. Your identifier in the group, your latest position on a map and how long ago it was taken — the same position your group sees, refreshed about every 25 seconds — with buttons to navigate there. Nothing else: no recording, no group, no messages.
- When it stops. As soon as the emergency is closed, the page shows no position at all, only that the emergency has ended. After 24 hours the link expires even if the emergency is still open.
- On our server the link exists only in memory, never on disk, and is deleted at the latest 24 hours after it was created. The page asks for nothing from whoever opens it; if they tap How far am I?, their browser works out the distance on their own device and sends their position nowhere.
About reports and blocks
From inside the app you can report a user, an invitation, an alert or a voice message, and block a user. The rules are in the Terms of use.
- A report is stored on our server with who filed it, who was reported, the reason you chose, the text you write if you add any, where it happened — a group, an invitation, an alert or a voice message — and, when you report an alert or a voice message, a copy of that message. It is sent by e-mail to our support team, who review it. The text of a report is never written to the server’s logs.
- A block is stored as a pair of user identifiers: who blocked whom. It is used to keep the two of you apart — no more invitations pass between you — and is deleted when you unblock.
Where your data goes
The server stores the data above so your group can see it. Beyond that, these third parties receive something:
| Who | What they receive |
|---|---|
Overpass (overpass-api.de) | Coordinates, when the app looks up places near you |
Google Maps or Apple Maps (maps.google.com, maps.apple.com) | Coordinates, when you open navigation |
| iPhone — Apple Maps (MapKit) | The area of the map the app shows you, so the iPhone can draw it |
| Your mobile operator | Only when an emergency goes out as a text message. Android, version downloaded from this site, when the internet could not carry the emergency: the number it is sent to, and one short encrypted line — not your name, not your position, nothing readable. iPhone, and the Android version on Google Play: the app prepares a readable message — your name, what happened, a map link to your position, your battery level — in your messaging app (on iPhone, the system Messages screen), and it goes only if you send it yourself |
| Amazon SES | Your e-mail address, to deliver the validation code when you register — and, if you are a group’s administrator and ask for it, the code that resets the password. When an emergency carries a voice recording: the recording, with the time, what started the emergency, the last known position and the live location link, sent to the e-mail address of every participant of the group. When someone files a report: the report, sent to our support team |
| Cloudflare | When someone opens a live location link: the page and your latest position pass through Cloudflare on their way to that person’s browser |
OpenStreetMap (tile.openstreetmap.org) | Nothing from the app. The browser of whoever opens a live location link downloads the map around your position from OpenStreetMap |
| iPhone — Apple, to deliver notifications to your iPhone | A push token: the address Apple gives this app on your iPhone |
Android — alphacephei.com, github.com, storage.googleapis.com, drive.google.com, drive.usercontent.google.com | Nothing about you. The Android app downloads voice and language model files from these addresses. The iPhone app downloads none |
This site (myhelpgroup.com) | When you tap Help, a ? or a link to the terms: the address of the page, which carries only the app’s language and the step you asked about. The page opens in your browser |
YouTube (youtube-nocookie.com) | Nothing from the app. On this site, only if you tap a video: your browser then loads YouTube’s player and asks YouTube for that video. Until you tap, the page shows a picture served from here and YouTube receives nothing |
What never leaves your phone
- The sound the voice monitor hears. It is turned into words to find your keywords. While it listens, the audio is not recorded, not stored and not sent to anyone. Android: it is turned into words on the phone itself — by Android’s on-device recognition, or by an offline engine you download once. iPhone: the monitor runs only while the app is open on the screen, and only on the device — Apple’s speech recognition, working on the iPhone itself. If your iPhone cannot recognize the chosen language on the device, the monitor stays off, and the app tells you why. What leaves the phone, when one of your words is heard, is the same emergency the button sends — and, like any emergency, it carries the voice recording described above.
- The movement your phone feels. The fall, impact and crash detectors — on iPhone, through the motion sensors (Motion & Fitness) — decide on the phone whether something is wrong. The readings are not sent; only the emergency is, with what started it.
- The phone numbers you pick for emergencies. So that an emergency can reach someone by text or call when the internet cannot, you may pick a number out of your own address book. Android: you link it to a member of your group; that link stays on this phone, is never sent to the server, and is left out of Android’s backup and of a transfer to a new phone. iPhone: you choose it through the system contact picker, which hands over only the number you choose; it stays in the app on this iPhone and is never sent to the server.
- The key your group shares. It is agreed among your group’s own devices; the server stores sealed envelopes it cannot open, and never sees the key. On Android, the emergency text messages between phones in the same group are signed and encrypted with it.
- Your private cryptographic key. Only the public half is sent.
- The administrator’s password. The phone turns it into a check the server can compare but not reverse; the password itself is never sent.
Permissions the app requests, and why
Android
| Permission | What it is for |
|---|---|
ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION | Share your position with your group during an alert |
RECORD_AUDIO | Hear an emergency keyword or a shout, while the voice monitor is on; record up to 20 seconds of voice when an emergency countdown opens |
READ_CONTACTS | Not requested by this version of the app; linking a member’s number uses Android’s contact picker, which hands over only the contact you choose |
HIGH_SAMPLING_RATE_SENSORS | Read the motion sensors fast enough to tell a fall, an impact or a shake apart from normal movement. The readings are analysed on the phone and are not sent |
SEND_SMS | Send an emergency to your group as a text message when it cannot go over the internet |
RECEIVE_SMS | Read your group’s emergency text messages, and answer them. The app opens only messages carrying its own mark; every other message in your inbox is ignored, unread. |
READ_PHONE_STATE | Know which SIM cards are active, so a text message that fails on one can be tried on the other |
CALL_PHONE | Place an emergency call from inside the app |
ACTIVITY_RECOGNITION | Tell a car crash apart from a dropped phone |
POST_NOTIFICATIONS, USE_FULL_SCREEN_INTENT, SYSTEM_ALERT_WINDOW, VIBRATE, MODIFY_AUDIO_SETTINGS | Show and sound an alert, even over the lock screen |
SCHEDULE_EXACT_ALARM, REQUEST_IGNORE_BATTERY_OPTIMIZATIONS, WAKE_LOCK | Make the check-in happen at the time you chose, and not minutes later |
FOREGROUND_SERVICE, FOREGROUND_SERVICE_HEALTH, FOREGROUND_SERVICE_MICROPHONE, RECEIVE_BOOT_COMPLETED | Keep the connection alive, keep listening while you have the voice monitor on, finish an emergency’s voice recording after the countdown screen closes, and restore the connection and the monitor after the phone restarts |
FOREGROUND_SERVICE_LOCATION | Keep your position up to date for your group while an alert or emergency of yours is open, even with the screen off |
INTERNET, ACCESS_NETWORK_STATE, ACCESS_WIFI_STATE, CHANGE_WIFI_STATE | Reach the server, and survive a change of network |
The version on Google Play does not ask for SEND_SMS, RECEIVE_SMS or READ_PHONE_STATE: it
neither sends nor reads text messages, so the emergency by text message when there is no internet
exists only in the version downloaded from this site. When it offers to text someone for you, it
opens your messaging app with the text ready, and you send it.
On a linked watch the app also asks for: BODY_SENSORS, BODY_SENSORS_BACKGROUND,
health.READ_HEART_RATE and health.READ_HEALTH_DATA_IN_BACKGROUND to read your heart rate for the
detections you turned on; ACTIVITY_RECOGNITION to count steps and tell exercise apart;
FOREGROUND_SERVICE_HEALTH to keep reading while you walk; RECORD_AUDIO and
FOREGROUND_SERVICE_MICROPHONE for the voice recording of an SOS; and location, notifications,
exact alarms and full-screen notifications for the same reasons as on the phone.
iPhone
| Permission | What it is for |
|---|---|
| Location — While Using the App | Send your position to your group when you ask for help |
| Location — Always | Keep your position up to date for your group in the background, even with the screen locked, so they can find you in an emergency or when you miss a check-in |
| Motion & Fitness | Detect falls, crashes and sudden stops, and ask if you are OK |
| Microphone | Record a voice message of up to 20 seconds for your group when you trigger an SOS, and listen for help keywords while the app is open |
| Speech Recognition | Recognize help keywords on the iPhone itself, never on a server, while the app is open |
| Local Network | Check the local network connection, so your group’s alerts keep reaching you |
| Notifications, including Time-Sensitive notifications | Show and sound alerts, emergencies and check-ins, and let them through a Focus if you allow it |
The iPhone app does not ask for access to your contacts: choosing a number uses the system contact picker, which hands over only the number you choose. It cannot send or read text messages by itself: when an emergency should go by text, it opens the system Messages screen with the text ready, and you send it. An emergency call is placed through the iPhone’s own Phone app.
Every automatic detector — fall, impact, shake, shout, pressure, running, flip, and on the watch fall, no pulse, heart rate and sudden running — is off by default, on Android and on iPhone. You turn on the ones you want.
Legal basis
Under the Brazilian LGPD (Law 13.709/2018), we process your data on the basis of your consent (art. 7, I), of the performance of the service you asked for (art. 7, V), and, for alerts, of the protection of life and physical safety (art. 7, VII). Under the European GDPR, the corresponding bases are art. 6(1)(a), (b) and (d). Reports and blocks are processed to provide the service safely and to enforce the Terms of use (LGPD art. 7, V and IX; GDPR art. 6(1)(b) and (f)).
How long it is kept
Account data and group membership are kept while your account exists. Alerts and their delivery status are kept while the message is open and for as long as your group may need to consult it. A voice recording is kept as the section above describes: at most one hour on our server, 30 days on the phones, and in each recipient’s e-mail for as long as they keep it. A live location link is kept only in our server’s memory, and deleted at the latest 24 hours after it was created. A block is kept until you unblock. A report is kept while it is being reviewed, and deleted at the latest 365 days after it is resolved. Activity logs are kept for diagnosis and discarded as they age. Delete your account from the app (the app’s menu → Delete account) or ask us by e-mail, and everything tied to it is removed; the Delete your account page lists the few things that stay, and for how long.
When you delete your account, the blocks that involve you are deleted, and the reports you filed are anonymized: your name and identifier are removed from them. Reports about you are kept, as evidence, for up to 365 days after they are resolved.
Your rights
You may ask to confirm whether we process your data, to access it, to correct it, to delete it, to receive it in a portable form, to withdraw consent, and to know with whom it has been shared. Write to support@myhelpgroup.com; we answer within the period the law allows. To delete your account you do not need to write: see Delete your account.
Children
MyHelpGroup is not directed at children under 13, and we do not knowingly create accounts for them.
Security
Every message between the app and the server is authenticated and encrypted. The server is operated on nodes in more than one country, deliberately, so that a failure in one place does not leave anyone without help.
Changes
When this policy changes, the date at the top changes with it. Material changes are announced in the app.