Home

Guardme Privacy Policy

Effective date: November 5, 2026

1. Who we are

Guardme is a personal safety app operated by SAFEIM.AI LTD, a company registered in England and Wales (number 17342838), registered office 2nd Floor College House, 17 King Edwards Road, Ruislip, London HA4 7AE, United Kingdom. We are the data controller for the personal data described here.

Contact us about anything in this policy at info@safeimai.com.

Where Guardme is offered. Guardme is currently available in the United Kingdom only. If you are reading this from anywhere else, the app is not being offered to you and we are not processing your data as a user of it. If we make Guardme available in other countries, this policy will be updated first - including, where the law requires it, with the name and contact details of a representative in that region.

2. What we collect

3. Why we process it, and our legal basis

The article numbers below are those of the UK GDPR - the General Data Protection Regulation as it forms part of the law of the United Kingdom, defined in section 3(10) of the Data Protection Act 2018. The ones cited here are the same as in the EU Regulation, so if you have read a European privacy notice these will look familiar; the law being applied here is the United Kingdom one, and the regulator is the ICO.

DataPurposeLegal basis
Email, provider identifierCreating and securing your accountPerformance of a contract, Art. 6(1)(b)
Your name and phone numberTelling your emergency contacts who the alert is fromPerformance of a contract, Art. 6(1)(b)
Your emergency contacts' detailsReaching them when you trigger an alertContract with you, Art. 6(1)(b); as regards the contact, protection of vital interests, Art. 6(1)(d), and our legitimate interest in operating a safety service, Art. 6(1)(f)
Location during an alert, including one hour of live trackingTelling your contacts where you are, and letting them follow you if you moveProtection of vital interests, Art. 6(1)(d); performance of a contract, Art. 6(1)(b)
Incident recordingLetting you review what happenedPerformance of a contract, Art. 6(1)(b)
Incident history: the alert message, its time and location, the detector's result, and whether your contacts were reachedLetting you review past alerts and what happened in themPerformance of a contract, Art. 6(1)(b); for the detector's result, see the distress detection row below
Distress detection, after you tap Violence detectionRaising an alert when you may be unable to ask for help yourselfYour tap, which we treat as your explicit consent, Art. 6(1)(a) and Art. 9(2)(a); see section 4
Medical emergency, after you tap Medical emergencyAlerting your contacts immediately, with a short recordingPerformance of a contract, Art. 6(1)(b); protection of vital interests, Art. 6(1)(d). That you are in a medical emergency is data concerning health: your tap, which we treat as your explicit consent, Art. 9(2)(a), and where you cannot consent, vital interests, Art. 9(2)(c); see section 4
Subscription statusManaging access to paid featuresPerformance of a contract, Art. 6(1)(b)
Subscription record kept after you delete your accountStopping one subscription being used on two accounts and dealing with billing questionsOur legitimate interest, Art. 6(1)(f)
Account emailsTelling you about your own accountPerformance of a contract, Art. 6(1)(b)

4. Automatic detection and health-related data

Violence detection tries to recognise a violent emergency from the audio and video recorded after you tap it. Medical emergency detects nothing: you tell us you need help. Some of what Guardme works out, or is told, such as that you may be in distress or need medical help, can say something about your health. The law calls this special category data and asks for extra protection, so we handle it only on the basis of your tap, which we treat as your explicit consent, or, in a life-threatening situation where you cannot give it, to protect your life.

Automatic detection is a machine judgement and it will sometimes be wrong in both directions. It is an addition to your own judgement, never a replacement for it, and it is not a medical device or a medical diagnosis.

5. If someone has added you as their emergency contact

Your details reached us from the person who added you, not from you, and you may never have used Guardme. This section is for you.

6. On-device face detection (Google ML Kit)

Guardme uses Google ML Kit's on-device Face Detection API to locate a face in the live camera preview during active recording, so the app can crop the relevant region before running our own detection models. This runs on your device: we do not send any image or video to Google, and Google's disclosure does not list images or face data among what it collects. Like other Google software libraries, ML Kit does send Google technical diagnostics about the app, such as device model, operating system version and performance figures. Google's disclosure lists no images, video or face data among them. In Medical emergency nothing is analysed, so the result is not used.

7. Who else is involved

Your emergency contacts receive your alert, and only when you trigger one. Beyond that, a small number of providers process data on our behalf or receive technical data from the app, each receiving only what their part requires:

Alert messages include a Google Maps link to your location. If a contact opens it, Google receives that request under its own terms.

The app does not work without an internet connection.

We do not sell personal data, we do not use it for advertising, and we do not share it with law enforcement except where the law requires it.

8. Where your data goes

The data we hold ourselves is stored in the United Kingdom. Our hosting provider keeps our servers, our database and our file storage in its London region, and we have not switched on any other region. Some of the providers in section 7 also handle parts of your data, and not all of them are in the United Kingdom.

Where it is stored is not the whole picture, and we would rather set out the rest than leave you to assume it. Fly.io, RevenueCat and Twilio are United States companies. With Fly.io the data stays in London, but the law still treats our use of it as a transfer out of the United Kingdom; RevenueCat and Twilio handle the data in the United States. These transfers are covered: Fly.io participates in the UK Extension to the EU-U.S. Data Privacy Framework, and RevenueCat and Twilio operate under the UK International Data Transfer Addendum to the Standard Contractual Clauses. Google Firebase is provided to us by Google Ireland Limited, an Irish company, and the United Kingdom recognises the European Economic Area as offering equivalent protection. IONOS is contracted through IONOS Cloud Ltd, a company registered in England and Wales, and the parts of its service we use are run from Germany, so nothing there leaves the United Kingdom or the European Economic Area.

Two more services receive only technical data from the app, never your content: Expo, a United States company, which delivers app updates and states that it participates in the UK Extension to the EU-U.S. Data Privacy Framework, and Google, which for the Android integrity check and the face detection library's diagnostics may process that technical data in the United States.

One thing does travel, and it is worth being clear about it: if you add an emergency contact who lives abroad, their name and contact details are stored here in the UK and an alert is sent to them wherever they are. That is the point of the feature, and it happens only when you trigger an alert.

Incident recordings are a special case: they are encrypted on your device before they are uploaded anywhere, so wherever they are stored, their contents are not readable by us or by the provider holding them.

9. How long we keep it

Uninstalling the app does not delete your account. Use Profile > Danger Zone if you want your data removed.

10. Security

Incident recordings are encrypted on your device with a key only your device holds. Everything is sent to our servers over an encrypted connection (HTTPS). Every request that touches your data is checked on our server against your signed-in account, so you can only reach your own; the exceptions are the live location link, which works for anyone who holds it, and anonymous usage counts. We do not see your password: sign-in is handled by Firebase, Google Sign-In or Apple. The sign-in token stored on your phone is itself encrypted. We can technically read the data held on our servers, except the contents of your recordings, which we cannot decrypt. No system is perfectly secure, and we do not claim otherwise.

11. Your rights

Depending on why we process your data, you have the right to access it, correct it, have it erased, restrict how we use it, receive it in a portable form, and object to our processing of it. Some of these rights have limits set by law, and we will tell you if one applies. Where we treat your tap as consent, in Violence detection and Medical emergency, you give it again with each tap. You can withdraw it at any time by writing to us or by deleting your account; withdrawing it does not affect what was done before.

Most of this is immediate and in your hands: view and edit your profile in the app, and delete your account and your data from Profile > Danger Zone (the subscription record described in section 9 is the one exception). For anything else, write to info@safeimai.com; we answer within one month.

If we get something wrong, you can complain to the privacy regulator where you live: in the United Kingdom, the Information Commissioner's Office (ico.org.uk). We would rather you told us first, but that is your right and not conditional on asking us. If you do come to us, we will look into what happened, tell you what we find and what we are doing about it, and we will not ask you to give up the right to go to your regulator as a condition of us dealing with it.

12. Children

The minimum age to use Guardme is 13, which is the age UK law sets for a service like this. We recommend that anyone under 18 uses Guardme with a parent or guardian's knowledge, so that they can help set up emergency contacts and understand what the app shares. If we make Guardme available in countries whose law sets a higher age - several set 16 - the higher age will apply there and this policy will say so before that happens.

We do not knowingly collect data from anyone below that age. If you are a parent or guardian and believe your child has created an account, write to info@safeimai.com and we will delete it.

13. Changes to this policy

We will post any change here with a new effective date. Where a change materially affects you, we will tell you in the app rather than relying on you to re-read this page.

14. Contact

SAFEIM.AI LTD - info@safeimai.com

Our Privacy Officer is accountable for how this policy is applied, and is who to write to about any of it - a question, a request about your data, a complaint, or a concern that something has gone wrong. Use the address above. We publish the role and not an individual's name, so that the contact point stays valid whoever holds it.