Skip to content
AUNOR SOS
Features Groups Android & iOS How it works Pricing FAQ
Log in Download free
Features Groups Android & iOS How it works Pricing FAQ Log in
Back to home

AUNOR SOS Privacy Policy

Last updated: August 5, 2026

This Privacy Policy describes how AUNOR SOS (“Aunor”, “the app”, “we”) collects, uses, stores and protects your personal information.

1. Who we are

Aunor is a personal and family safety app for sending emergency (SOS) alerts, sharing your location with people you trust, and coordinating safety groups (family, transport, events).

Contact: support.aunorsos@gmail.com

2. Information we collect

2.1 Data you give us directly

When you create your account with Google or Apple (the only sign-in methods available), we collect:

  • Full name
  • Email address
  • Profile photo (optional). If you pick one from your gallery, the app asks for photo library access only so you can select that image; we do not read or upload the rest of your photos.
  • Preferred language.

Phone number — not asked for when you sign up. We ask for it later, only when you need it for a specific action (creating a group, making a purchase, or so you can be reached as part of a safety group). It is stored encrypted in our database and never in plain text; we use an encrypted lookup value (a hash) to verify it without exposing the real number.

2.2 Location data

  • Real-time location, shared with the members of your groups (Family, Transport, SOS) according to the settings you choose.
  • Location windows in Transport groups — the team admin can set working-hour windows. Your location is shared with the team only during an active route or within those windows; for the windows, only after you agree to share it from the app.
  • SOS alert location — the coordinates of an SOS alert and its track are stored encrypted (AES-GCM) in our database; only your group's members see them decrypted, on the alert map.
  • Location history (Premium feature), kept so authorised group admins can consult it later.
  • Location-consultation log — every time an admin consults a member's location history, we record who consulted, about whom and when, so that access is audited rather than invisible to the group.
  • Safe zones (Family groups) — if an admin defines zones (home, school, work), we record members' entry and exit events so the group can be notified according to its settings.
  • Life pattern (Premium feature, Family groups) — if the group turns this on, we analyse safe-zone events to learn protected members' usual routine (when they tend to leave or come back) and warn the admins if that routine breaks. You can turn it off at any time from the group.
  • Activity heartbeats during trips and routes — while a safe trip or a route is active, the app periodically sends a small sign of life to our servers. It only serves to detect that the phone was switched off or stopped responding and to warn the group; it carries no extra location.
  • Route calculation — to draw the street-level path between stops, we send only those points' coordinates to a public routing service (OSRM). Your name, your phone number and any identifier of your account are not sent.

2.3 Device sensor data

  • Accelerometer / motion sensors — used locally on your device to detect falls, vehicle crashes and suspicious movement (possible phone snatching). The analysis happens on the device; an alert is transmitted only if an event is detected.
  • Anonymous data to improve detection — when a detector reacts (a fall, a crash, hard braking, a possible snatch or a danger sound), the app may upload a short anonymous fragment to our servers, together with the phone model and the technical characteristics of its accelerometer: for motion events, a fragment of the accelerometer readings; for sound events, only the volume level and the type of danger sound detected (for example “a scream” or “breaking glass”) — never a recording or the audio itself. It is used solely to tune the detection algorithms and reduce false alarms. These fragments do not include your location, any audio recording or data that identifies you: they are stored under a non-reversible pseudonymous reference. “Near-detection” fragments (events a detector weighed up and discarded) are deleted automatically after 30 days if they get no label; those from events that did fire an alert, and those you label yourself when responding, are kept to calibrate the detectors for as long as your account exists (they are deleted when you delete it). This feature is on by default and you can switch it off at any time in Settings → Safety → “Help us improve detection”.
  • Alert survey answer (anonymous) — when you close or open an automatically detected alert, if the previous feature is on the app may ask you whether it was a real emergency or a false alarm, with an optional note. The answer is stored under the same pseudonymous reference, without any identifier of the alert, and is used to reduce false alarms.
  • Microphone audio for danger detection (Premium feature) — danger sounds are analysed by an artificial-intelligence model running locally on the device; that analysis audio is not transmitted or stored on our servers. If you turned on the detection improvement (above), when sound protection fires only the volume level and the type of sound detected are uploaded — never the recording.
  • Ambient audio during an SOS alert (“black box”) — while an SOS alert is active, the app can record ambient audio and upload it encrypted to our servers in small chunks as it records, so it remains available as evidence even if the phone is switched off or destroyed. This audio is tied to the alert, is visible only to the members of the group receiving it, and is deleted when the alert is deleted or, at the latest, after 7 days.
  • Black-box audio transcript — so the group can quickly read what was heard, the phone itself can turn that audio into text as it records and upload the text alongside the fragment. The transcript is produced on the device, stored encrypted, visible only to the group's members and deleted on the same 7-day schedule as the audio it describes.
  • Front-camera photo or video during an SOS alert (“black box”) — if you granted camera access, when a visible SOS is sent the app can automatically take one or several photos — or, if you set it that way, a short low-resolution video — with the front camera during the first minutes of the alert, and attach them to it as evidence. Nothing is captured in silent SOS mode or when the operating system does not allow using the camera in the background. It is stored encrypted, can only be consulted by authorised group members and authorised Aunor admins, and is deleted when the alert is deleted, when an admin removes it, or automatically after 7 days.
  • Voice notes in alert replies — whoever replies to an alert can record a short audio instead of typing. It is stored encrypted alongside the alert, visible only to their group, and deleted on the same 7-day schedule.
  • Battery level — included in SOS alerts and, in Family groups, admins can be warned when a protected member's battery is low.
  • Heart rate (Apple Watch) — if you use the watch app, sharp changes in your heart rhythm are analysed on the watch itself as an extra risk signal. We do not store your heart-rate readings on our servers; only the alert is transmitted, if one is raised at all.

2.4 Group and contact data

The name, phone number and status of other members of the groups you belong to are visible to you according to your role in the group (admin or member).

2.5 Group chat and event photos (Premium feature)

  • Chat messages — each group's internal chat is stored encrypted on our servers (the same encryption scheme as the phone number) and is visible only to that group's members. An admin can export their group's chat history.
  • Photos attached to events — when you add a note to a group event (for example, in Family groups) you can attach a photo; it is stored in our database and is visible to the members of the corresponding group.
  • An event's album — photos members upload to an event album are stored encrypted, are visible only to that group and are deleted automatically after 7 days.

2.6 Walkie-talkie

When you talk on the walkie, your voice travels live through our servers to the other participants of the group or channel. We do not keep voice transmissions: the audio is relayed and discarded. From each session we temporarily keep only the minimum coordination data — which group or channel is active, who is connected and when the last activity was — and it deletes itself shortly after the session ends.

For your own channels (Premium feature) we store the name, colour, icon and list of participants, until whoever created it deletes it.

2.7 Bluetooth: relaying alerts and proximity search

  • Relaying an SOS with no signal — if your phone has no internet when you send an SOS, the app can broadcast the alert over Bluetooth so a nearby phone with Aunor delivers it to our servers. The message is signed so nobody can alter it but, since the phone carrying it needs to be able to read it in order to forward it, its content (who is sending the alert, to which group, your location and your message) is readable by the phones with Aunor within your range while they carry it. Your phone can act as a carrier for other members' alerts in your groups in the same way.
  • Searching for a member — when an admin declares a search for a member of their group, the group's phones can look over Bluetooth for the sought phone's signal and report that they detected it nearby. What is shared is the detection and the approximate proximity, not the identity of third parties outside the group.
  • Walkie over Bluetooth — the voice clips that travel between nearby phones without internet are encrypted with a key derived from the group itself, so only that group's members can play them.
  • The app does not use Bluetooth for advertising, tracking or profiling, and does not gather an inventory of the devices around you: it only attends to signals in Aunor's format.

2.8 Transport groups

  • Route track — during an active route we store the points of the path so the team can follow it and review it afterwards. Kept for 45 days.
  • Start-of-route photo — if the admin requires it, whoever drives takes a photo when the route begins. It is stored against that route, is visible to the group's admins and is deleted automatically after 30 days.
  • Passenger heads-up by QR — a vehicle's QR code is an opaque value with no personal data inside it. If someone uses it to report an incident, we keep that heads-up for the group's admins for 90 days.

2.9 Earthquake, weather and civil-protection notices

To warn you about a nearby earthquake, about the weather for an event or about a civil-protection alert, we consult public third-party sources. Weather services receive coordinates only — an event's, or a member's rounded off — with nothing that identifies you; earthquake and civil-protection notices come from public listings and we do the cross-checking against your location ourselves. Responses are kept in a short-lived shared cache so the provider is not queried over and over.

2.10 Technical data

  • Push notification token (Firebase Cloud Messaging), so we can send you alerts.
  • Session identifiers (JWT) to keep your session authenticated.
  • Notification history — the notifications we send you are stored so you can review them in the app; some include an alert's location. They are deleted after 90 days.
  • Biometric lock — if you turn on Face ID, Touch ID or your fingerprint to enter the app or confirm an SOS, the check is done by your phone's operating system. We neither receive nor store your biometric data; we only learn whether the check passed.
  • Support messages — if you write to us from the app or by email, we keep your message and your contact address only so we can reply to you and follow up on your case.

2.11 Medication reminders (Family groups)

If a Family group uses medication reminders, we store the medication name, the schedule (times and days) and the confirmations that it was taken, so we can remind the person and let their carer know. This information is entered voluntarily by the group, is visible only to its members according to the settings, and is deleted when the reminder or the group is deleted. We do not use it for anything else.

2.12 Content and user reports

If you report a message or other content from a group, or report a user directly from the in-app assistant, we store the report so it can be reviewed: who reports, who is reported, and a copy of the reported content or of the samples you attach (for example, copied messages or up to 3 photos or screenshots). These reports are used solely for moderation, are shared only with our support team and are deleted after 180 days. If after the review we decide to ban an account, it is disabled and cannot sign in again with either its phone number or its email address.

2.13 In-app purchases

Subscriptions (Aunor Premium, extra group seats, your own walkie channels) are processed through the Apple App Store or Google Play. We neither receive nor store your card or payment method details — we only receive a purchase confirmation from the corresponding store.

2.14 Founders' Hall (public list, only if you turn it on)

The earliest Aunor Premium subscribers can appear in the Founders' Hall, a public list on our website. It works like this:

  • You only appear if you turn it on (opt-in) from the app and choose an alias; we never show your real name, your email or your phone number.
  • Next to the alias we show your country (derived from your number's international prefix, without revealing the number) and your Premium seniority badges.
  • You can leave the list whenever you want by switching the option off in the app; your entry stops being shown at the next daily update.

3. How we use your information

  • To send and coordinate SOS alerts among your group's members, including relaying them over Bluetooth when there is no signal.
  • To share your location with the people you authorise.
  • To automatically detect falls, crashes or thefts (automatic safety features, Premium).
  • To allow walkie-talkie communication inside your groups and channels.
  • To verify your identity with a one-time code (OTP) by SMS or WhatsApp.
  • To process your subscription and apply the corresponding benefits.
  • To send you relevant notifications (alerts, your group's activity, earthquake or weather notices).
  • To moderate content shared in groups (messages, photos and files) and handle the reports users send.
  • To give you support when you contact us.

We do not use your information for advertising and we do not sell it to third parties.

4. Who we share information with

We share data only with providers that help us operate the app:

ProviderPurpose
Firebase / Google CloudAuthentication, push notifications
TwilioSending verification codes by SMS
WhatsApp Business (Meta)Sending verification codes by WhatsApp
BrevoSending service emails (notices and support replies)
MongoDB AtlasDatabase storage
RenderBackend server hosting
CloudflarePublishing the website and, when configured, storing already-encrypted files (profile photos and evidence)
OSRM (router.project-osrm.org)Working out the street-level path between a route's stops (coordinates only)
Open-MeteoWeather forecast for an event or a location (coordinates only)
USGSPublic listing of recent earthquakes (receives no data about you)
National Weather Service (NWS)Public civil-protection alerts (receives no data about you)
Apple / GoogleSocial sign-in and purchase processing

None of these providers may use your data for their own purposes beyond providing us the contracted service.

We may also share your location and status with the members of your own groups, according to what you configure — this is the app's central purpose.

We may retain or hand over information when an applicable law or a valid order from a competent authority requires it, or when it is necessary to protect someone's life or physical safety.

5. Security

  • Phone numbers and email addresses are encrypted with AES-GCM before being stored.
  • Group chat messages, SOS alert locations and all black-box evidence (audio, transcript, photos and video) are also stored encrypted; they never sit in plain text in the database.
  • Cancellation and duress PINs are stored as a hash (just like a password); we can never see the real PIN.
  • We use a derived lookup value (HMAC) to authenticate without exposing the real number in the database.
  • Uploaded files and photos are verified at byte level to make sure they really are the type they claim to be (image, PDF, audio).
  • Sessions expire automatically and can be renewed securely.
  • We limit verification attempts to prevent abuse.

6. How long we keep each thing

Data that is heavy or sensitive deletes itself, even if you never ask us for anything. These are the maximum periods:

  • Walkie voice transmissions — not stored.
  • Black-box evidence (audio, transcript, photos, video and reply voice notes) and event album photos — 7 days.
  • Start-of-route photo, “near-detection” fragments, join requests already decided and finished medication reminders — 30 days.
  • Route and trip tracks, work location history and daily life-pattern profiles — 45 days.
  • Notification history, location-consultation log, passenger heads-ups and anonymised security logs — 90 days.
  • Content and user reports — 180 days.
  • Purchase transaction records — up to 5 years, for accounting and tax obligations.
  • Everything else (your account, your groups, your messages) is kept while your account exists and is deleted when you delete it, as described below.

7. Your rights

You can ask us at any time to:

  • Access the data we hold about you.
  • Correct incorrect information.
  • Delete your account and the data associated with it.

To exercise these rights, write to us at support.aunorsos@gmail.com.

Accounts created but never verified (for example, after a social sign-in without verifying the phone number) may be deleted automatically after a period of inactivity.

8. How to delete your AUNOR SOS account and your data

Option 1 — From the app (instant): Open Aunor → Settings → Delete account → confirm. Your account and the associated data are deleted instantly, with no waiting.

Option 2 — If you cannot get into the app (you lost the phone, you cannot sign in, etc.): write to support.aunorsos@gmail.com with the subject “Delete my account”, stating the phone number or the email address (Google/Apple) you signed up with. We will verify your identity as the account holder and process the deletion within up to 15 business days, with confirmation by email.

What gets deleted (in both cases): your account, name, profile photo, email, phone number (encrypted), the groups you run (with their alerts and black-box evidence), your walkie channels, your membership in other groups, location and location history, join requests, and notification tokens.

What is kept temporarily, and why:

  • Purchase transaction records: up to 5 years, for accounting/tax obligations.
  • Anonymised security logs (for fraud/abuse prevention): up to 90 days, then permanently deleted.
  • Anonymous motion fragments to improve detection, not tied to a confirmed alert: 30 days, then automatically deleted.
  • Content reports where you appear as the reported or reporting party: up to 180 days, so a moderation decision can be backed up.

You can ask to delete only some data (for example, your location history) without deleting your account, by writing to the same address with the subject “Delete specific data” and detailing what you want removed.

9. Minors

Aunor is aimed at adult users who manage the safety of their family or group. An adult (the account holder) may include relatives — minors among them — as protected members inside a group, but the app itself is not designed to be used directly by children under 13 as account holders.

10. Limits of the automatic safety features

Aunor offers automatic detection features (falls, crashes, hard braking, possible phone snatching) that rely on the device's own motion sensors (accelerometer and similar).

It is important that you know:

  • The sensitivity, accuracy and availability of these sensors vary by phone model and manufacturer. Some devices may detect events more or less accurately than others, or not detect them at all.
  • The operating system (battery optimisation, power-saving modes, background restrictions) can delay or prevent an automatic detection from being processed in time, especially if the app does not have the necessary permissions enabled.
  • These features are best-effort and are not a guarantee of detection in every case.
  • The manual SOS button inside the app is the main and most reliable way to ask for help — do not rely on automatic detection alone in a real emergency.

We recommend testing these features on your own device and adjusting the permission and battery settings as the app indicates.

11. Changes to this policy

We may update this policy from time to time. We will publish any important change on this same page with a new “Last updated” date.

12. Contact

If you have questions about this Privacy Policy or about your data, write to us at: support.aunorsos@gmail.com

AUNOR SOS

Your safety network,
always close.

ProductFeaturesAndroid & iOSPricingLog in
InformationHow it worksFAQContact
LegalPrivacyTerms of use
© 2026 AUNOR. All rights reserved.Made to protect ◉