This Privacy Policy explains how Veromtec / Roman Liskin ("Veromtec," "we," "us," or "our") collects, accesses, uses, stores, shares, and deletes information when you use SOS Alert (the "App" or "Service"). The App provides emergency alerts, trusted-contact messaging, safety tools, account-based live-location sharing, approved-device pairing, maps, optional location email alerts, advertising, and in-app purchase features.
This Policy applies to the current Android package identified above. Feature availability and data handling may vary by App version, device, country, permissions, account state, and build configuration. The Google Play Data safety disclosure and any in-App notices should be read together with this Policy.
The information collected or accessed depends on the features you use, the permissions you grant, whether you create an account, and whether live sharing is enabled. Some safety data remains primarily on your device. Account, profile, pairing, and live-location data is transmitted off the device to Firebase as described below.
The current live-tracking experience uses Firebase Authentication. To register, the App may ask for an email address, password, full name or display name, phone number, numeric pairing PIN, and profile photo. Firebase creates a unique user identifier and maintains authentication and session state. Password-reset requests are also processed by Firebase.
Firebase Authentication may process account credentials, email address, user identifier, authentication events, IP address, user agent, device/browser information, and related security data. We do not store your readable password in the App's Firebase Realtime Database. Google processes authentication credentials through Firebase Authentication according to its terms and privacy documentation.
The App stores a cloud profile that may include:
The profile photo is used as a map marker and may be shown to an account that locates you by an exact account-identity search or pairs with you. Do not choose a photo you do not want used for this purpose.
To let users pair with a specific person, the App maintains an account directory in Firebase. A signed-in user who enters another account's exact email address or authenticated identity may retrieve a matching directory record. That record may contain the user ID, account identity, display name, device model, profile photo, sharing status, and update timestamp.
The directory is not intended for open browsing and is restricted by current database rules to signed-in exact-match queries. The directory is not intended to contain a readable PIN, pairing-code hash, or phone number. However, a person who already knows your exact account identity may see the directory profile before completing pairing. Use an account identity and profile photo appropriate for this feature.
When live sharing is enabled, the App may collect and upload location data periodically. This may occur while the App is visible, in the background, closed, or not actively in use. Location data may include:
Update frequency is adaptive and may change according to whether the live map is open, device movement, battery conditions, Android background limits, GPS availability, and network state. Live location is not guaranteed to be continuous, current, or accurate.
The current implementation is designed to overwrite a latest-location state rather than build a chronological route-history timeline. Some builds may also write a compatibility copy of the latest state to legacy database fields. This design does not prevent older values from existing temporarily in service logs, backups, caches, screenshots, recipient devices, previously sent messages, or third-party systems.
Android background location and a foreground location service are used to support live sharing when the App is not actively visible. While this service is running, Android should display an ongoing notification. The service may retain limited local session state, such as the signed-in user ID, update mode, and compatibility configuration, so Android can resume the same sharing session after the operating system stops and restarts the service.
The App intends to stop the local live-location service when sharing is turned off or the user signs out. Because the current sign-out action stops the local service but may not first change the cloud sharing flag, users should turn Live Sharing off before signing out to revoke approved viewers' cloud access under the current rules. Uninstalling the App stops local execution but does not automatically delete or disable the Firebase account, cloud profile, last uploaded location, or cloud sharing flag.
A user may generate a pairing code or use a pairing PIN to approve another signed-in account. Generating a pairing code may also turn live sharing on. Pairing credentials should be shared only with people you trust.
When pairing succeeds, the viewer's Firebase account may store a private device summary containing:
Under the current Firebase rules, an approved viewer is intended to read your live-location state only while your sharing status is on and the viewer's tracking entry is enabled. Turning sharing off blocks new live-location reads, but the paired viewer's stored profile summary may remain until the viewer removes the paired device, the relevant account data is deleted, or we perform administrative cleanup. Information already seen, copied, photographed, or exported by another user cannot be recalled by the App.
The App lets you manually add trusted contacts who may receive SOS messages. This may include a name, phone number, relationship label or note, and enabled/disabled status. The App does not need to read or upload your phone contacts list for this feature. Trusted-contact records are primarily stored locally unless you send or share an alert.
You are responsible for having an appropriate reason and, where required, permission to enter another person's contact information and send that person alerts.
You may enter optional emergency details such as your name, allergies, medical notes, safe phrase, or safety instructions. This information can be sensitive. It is primarily stored on your device and may be included in an SOS SMS or email if you save it and use the relevant feature. Do not enter information you do not want sent to your chosen recipients.
The App is not a medical device and does not diagnose, treat, cure, prevent, or monitor a disease or medical condition.
If you trigger SOS, the App may send SMS messages directly to trusted contacts you selected. Message content may include the App name, trigger source, timestamp, location link, coordinates, accuracy, approximate address where available, emergency profile details, and a callback request.
SMS delivery is handled by your Android device and mobile carrier. Veromtec does not maintain a server-side archive of the SMS body sent by the App. The App does not read your SMS inbox, call log, or incoming messages. Your carrier and recipients may retain message and delivery records under their own practices.
The App may let you configure optional email location alerts using SMTP. Depending on your settings, it may store locally the SMTP host, port, username, password or app password, sender email/name, recipient email, enabled state, and interval. An email may contain current or last known location, coordinates, map link, timestamp, and SOS context.
Email is sent through the provider you configure, such as Gmail, Outlook, Yahoo, a private SMTP server, or another provider. The provider and recipient may process and retain the email under their own privacy practices. Use an app password where supported and select encrypted SMTP settings when available. You can change or remove SMTP settings in the App or by clearing local App data.
The App may offer an optional Android Accessibility Service used only to detect a configured sequence of Volume Up or Volume Down presses so SOS can be triggered while the App is closed, backgrounded, or the screen is off.
The Accessibility Service is not designed to:
The service is optional, must be enabled manually in Android Accessibility settings, and can be disabled at any time.
When you choose a profile photo, the App receives access to the selected image. The App may resize and compress it, encode it, store it in Firebase, and display it on live-map markers, account screens, exact-match directory results, and paired-device summaries. The App does not require general access to all photos when the platform's selected-photo picker is available.
The App uses notifications, foreground services, and scheduled/background work to show when SOS, live location, or email tasks are active. It may store local settings and state needed to operate these features, including permission state, active user/session identifiers, sharing mode, last local location, and retry/task status.
If you contact us, we may receive your email address, message, screenshots, logs, device and App information, transaction details, or other information you choose to send. Do not send passwords, pairing PINs, pairing codes, or unnecessary medical/location information in a support request.
Firebase, Google Play, Google Mobile Ads, Android system services, map services, and other providers may automatically process information needed to operate, secure, measure, bill, or advertise the App. Depending on the service and device settings, this may include:
The App does not intentionally provide your precise Firebase live-location coordinates to AdMob for ad targeting. AdMob may nevertheless infer a general location from IP address and process other advertising data under Google's policies and your consent/device settings.
We use information as reasonably necessary to:
Where applicable law requires a legal basis, processing may rely on providing the Service you request, your consent or permission choices, our legitimate interests in operating and securing the Service, and compliance with legal obligations. You may withdraw optional permissions or turn off live sharing, although doing so can prevent related features from working.
A newly created live-tracking profile is intended to begin with sharing off. The App does not begin cloud live-location updates until the user activates the relevant sharing flow and grants the necessary location permissions. Generating a new pairing code may activate sharing so the other account can complete pairing.
When you turn sharing on, the App verifies location readiness, publishes a location state, sets the cloud sharing status to on, and starts or maintains the Android foreground location service. Your location can then be read by accounts that have successfully paired with you and have tracking enabled, subject to the Firebase rules and service availability.
Turning sharing off is intended to stop the local tracking service, stop new location uploads, mark the cloud state as not sharing, and block approved-viewer reads of the live state under the current rules. It does not automatically delete the last latitude/longitude, timestamps, profile, directory entry, pairing summaries, or account. Use Section 14 to request deletion.
Sign-out stops the local foreground service, but users should turn sharing off first because sign-out may not change the existing cloud sharing flag. Clearing App data or uninstalling the App removes or disables local functionality but does not automatically delete cloud records. If your device is lost, stolen, or unavailable while sharing may still be on, contact us from the account email as soon as practical and request that sharing/account data be disabled or deleted.
Your live location is made available to signed-in accounts that complete the App's pairing process and remain enabled, but only while your cloud sharing status is on under the current database rules. Profile information used for lookup and pairing may be visible or copied as described in Sections 1.3 and 1.6.
When you trigger SOS or send a location update, selected recipients may receive location, map links, timestamps, message content, and emergency profile information. When you choose to open a map, SMS composer, phone dialer, browser, or another app, that third party handles the information you provide to it.
Firebase Authentication and Firebase Realtime Database process account, profile, directory, pairing, and live-location data on our behalf and as otherwise described in Google's terms. Veromtec can access data in the Firebase project as needed to operate, secure, support, or delete the Service.
Google AdMob may process advertising and measurement data; Google Play processes purchases and entitlement; Google Maps or another selected map service processes map requests; an SMTP/email provider processes emails; and a mobile carrier processes SMS delivery. Each provider may act under its own terms and privacy practices.
We may disclose information when reasonably necessary to comply with law, legal process, or a valid government request; investigate fraud, abuse, security incidents, or threats; protect the rights and safety of users, Veromtec, or others; enforce applicable terms; or establish, exercise, or defend legal claims.
If the Service or Veromtec is involved in a merger, acquisition, financing, restructuring, bankruptcy, or transfer of assets, information may be transferred as part of that transaction, subject to applicable law and appropriate notice.
The App may use or interact with services including:
These providers may process information in accordance with their own policies. Relevant links include:
Ad-supported versions may show banner or interstitial ads through Google AdMob / Google Mobile Ads SDK. Google may collect or process IP address, general location inferred from IP, device or account identifiers, advertising ID where available, app interactions, ad impressions/clicks, diagnostics, consent signals, and fraud-prevention information.
Users may be able to manage ad personalization, reset or delete the advertising ID, or change consent choices through Android, Google, or in-App settings where available. Availability depends on country, age, device, and Google settings.
The App may offer an Add Devices + Remove Ads paid product using product ID
add_devices_remove_ads_monthly. Google Play processes payment information. We do
not receive or store your full payment-card number. The App and Google Play may process or store
entitlement, purchase-token, product, restore,
and related status necessary to provide the paid feature and prevent abuse. The App stores a
limited local entitlement/cache state.
Veromtec does not sell personal information for money. Ad-related processing may be treated as "sharing," "targeted advertising," or a similar concept under some laws; users can contact us about applicable rights and use available Google/device privacy controls.
Local App data may include trusted contacts, emergency profile, SMTP settings and credentials, last local location, language, appearance, navigation preference, emergency number, onboarding status, permission state, feature switches, purchase/cache state, and foreground-service session information.
Local data generally remains until you edit it, remove it, clear App data, or uninstall the App. The current Android package is configured with standard Android App backup disabled. Device-manufacturer tools, screenshots, exported content, recipient devices, or other services outside the App may still create copies.
Clearing local data or uninstalling does not delete Firebase Authentication, Firebase Database, Google Play, AdMob, email-provider, carrier, or recipient records.
Firebase account, profile, directory, and live-tracking records may remain until the account is deleted, we delete the records, or retention is otherwise required or permitted. The App does not currently apply an automatic expiry to the cloud profile or last live-location state.
New live-location writes are designed to replace the current/latest state. The latest coordinates may remain after sharing is switched off. Service-provider backups, security logs, caches, and compatibility data may be retained for limited periods under provider practices, even after primary records are deleted.
A paired viewer's device summary and compatibility links may remain until that viewer removes the paired device, the relevant account is deleted, or records are removed administratively. Turning off your sharing blocks live reads but is not the same as deleting all pairing-profile copies.
We may retain support communications for as long as reasonably necessary to answer requests, document actions, prevent abuse, and protect legal interests. Google, carriers, email providers, recipients, and other third parties retain data under their own policies and legal duties.
We use reasonable technical and organizational safeguards appropriate to the Service, including Firebase authentication and database access rules, one-way hashing for pairing credentials, restricted Android components, and encrypted network transport where supported. However, no app, credential, database, device, wireless connection, SMS network, email system, or electronic storage method is completely secure.
Pairing PINs and codes protect access but may be guessed, copied, photographed, forwarded, or misused. Choose a hard-to-guess PIN, keep pairing codes private, generate a new code when needed, review paired devices, remove unknown devices, and turn sharing off when it is not needed.
SMS generally is not end-to-end encrypted. Email security depends on the configured SMTP provider and settings. Profile photos, account profile data, and latest location stored in Firebase are protected by service access controls but are not guaranteed against every breach, account compromise, misconfiguration, or recipient misuse.
Permissions are requested only where needed for enabled features. You can manage permissions in Android settings. Denying or revoking a permission may disable or reduce the reliability of the related feature.
| Permission / Access | Why It Is Used |
|---|---|
| Approximate and Precise Location | Used to create location links, include coordinates in SOS messages, show the user’s location, and upload the current/latest live location to Firebase while sharing is enabled. |
| Background Location | Used for live tracking, closed-app SOS, the optional accessibility-volume SOS feature, and configured background location emails when the App is not actively visible. Live tracking may continue while the App is closed or not in use if sharing remains enabled. |
| Selected Photos / Media | Used when the user chooses a profile image from the device. The selected image is resized/compressed and uploaded to the live-tracking profile for map markers and pairing displays. |
| SMS | Used to send direct SOS SMS messages to trusted contacts selected by the user. The App does not read the SMS inbox. |
| Accessibility Service | Optional. Used only to detect the configured Volume Up or Volume Down sequence for closed-app SOS. It is not used to read screen content, passwords, chats, notifications, or messages. |
| Notifications / Foreground Service | Used to show visible status while live location, SOS, or background email work is running and to support Android background execution requirements. |
| Internet / Network State | Used for Firebase account and live-location features, maps, ads, Google Play Billing, password reset, optional SMTP email, and opening web/map links. |
| Vibration / Wake Lock | Used for emergency feedback and to help complete urgent SOS and background tasks. |
| Google Play Billing | Used to purchase or restore the Add Devices + Remove Ads product. |
In the current reviewed version, the App is not designed to:
Voice-keyword SOS is not active in the reviewed version, and the App does not request microphone permission for always-on hotword listening. Future versions that materially change these practices require an updated Policy and related disclosures.
To request deletion of your SOS Alert account and associated cloud data, send an email from the email address connected to the account to:
Email:
veromtec@gmail.com
Subject: SOS Alert Account Deletion Request
Deletion information page:
https://veromtec.com/sos-alert-privacy-policy.php#account-deletion
Please include:
Never send your password, pairing PIN, or pairing code. We may ask for reasonable verification to protect the account from unauthorized deletion. Requests will be handled within the period required by applicable law.
Subject to verification, technical feasibility, and lawful retention exceptions, deletion may include:
Account deletion cannot automatically retract SMS messages, emails, screenshots, map links, copied profile information, or location information already received or saved by another person. It also does not directly delete records independently controlled by Google Play, AdMob, an email provider, a carrier, a map provider, or another third party. Contact those providers or recipients where appropriate.
We may retain limited information where reasonably necessary for legal obligations, security, fraud prevention, dispute resolution, enforcement, backup integrity, or proof that a deletion request was completed. Residual copies may remain temporarily in provider backups before being overwritten under normal retention cycles.
To remove local data, edit or clear records inside the App, clear the App's storage in Android settings, and/or uninstall the App. Revoke SMTP app passwords with the email provider and delete sent messages from provider/recipient systems separately when needed.
Depending on where you live and applicable law, you may have rights to request access, correction, deletion, restriction, portability, or information about processing; object to certain processing; withdraw consent; or complain to a data-protection authority. These rights may be subject to legal exceptions and identity verification.
To submit a privacy request, email veromtec@gmail.com and identify the App, account email, request type, and the information reasonably needed to locate the relevant data. Do not send a password or pairing credential.
The App is not directed to children under 13, or a higher minimum age where local law requires it, and we do not knowingly create accounts for such children without valid parental or guardian authorization where required. Live location, profile photos, phone numbers, and emergency data are sensitive and should be used for a minor only under responsible adult supervision and with all legally required consent.
A parent or guardian who believes a child provided personal information without appropriate authorization should contact veromtec@gmail.com. We will take reasonable steps required by applicable law.
The App may be used in multiple countries, and Google/Firebase, advertising, billing, email, carrier, and map providers may process information in countries other than your country of residence. Those countries may have different data-protection laws. Where required, we and our providers use recognized contractual or legal safeguards for international transfers.
The native App does not directly use browser cookies in the same manner as a traditional website. Firebase, ads, billing, maps, embedded web content, or linked websites may use cookies, app-instance identifiers, advertising identifiers, local storage, tokens, or similar technologies for authentication, security, functionality, billing, advertising, and measurement.
The App may open websites, ads, navigation apps, browsers, an SMS composer, a phone dialer, an email provider, or map content. Once information is sent to or opened in another service, that service's terms and privacy practices apply. We are not responsible for third-party content, delivery, availability, emergency response, or security.
We may update this Policy when the App, data practices, providers, legal requirements, or platform rules change. We will update the Effective Date above and may provide additional notice in the App, on the website, or through another appropriate channel when required.
Review the Policy periodically, especially after an App update. Material new data practices will be disclosed and consent or permission will be requested where required before the new processing begins.
For privacy questions, account deletion, data requests, or concerns about this Policy, contact:
Veromtec / Roman Liskin
Email: veromtec@gmail.com
Website: https://veromtec.com
Privacy Policy: https://veromtec.com/sos-alert-privacy-policy.php
| Feature / Data Type | Data That May Be Accessed or Processed | Purpose | Primary Storage / Recipient |
|---|---|---|---|
| Account and authentication | Firebase user ID, email address, password credential handled by Firebase Authentication, authentication status, password-reset requests, timestamps, IP address, and user-agent or device information processed by Firebase | Create and secure an account, sign the user in, maintain an authenticated session, and support password reset | Firebase Authentication and related Google systems |
| Live-tracking profile | Full name or display name, phone number, email/account identity, profile photo, device manufacturer/model, user ID, sharing status, PIN hash, pairing-code hash, and profile timestamps | Create the live-tracking profile, display map markers, manage sharing, and verify approved pairing | Firebase Realtime Database; selected profile data may also be cached locally |
| Exact-match account directory | User ID, authenticated email/account identity, normalized identity, display name, device model, profile photo, sharing status, and update timestamp | Let a signed-in user locate a specific account by entering its exact email/account identity for pairing | Firebase Realtime Database |
| Live location | Precise or approximate latitude and longitude, accuracy, timestamp, update mode, user ID, sharing status, and profile marker photo; optional legacy builds may mirror the latest state to compatibility fields | Show the user’s current or latest location to approved paired accounts and support live safety tracking | Firebase Realtime Database and temporary/local device state |
| Pairing and approved devices | Target user ID, email/account identity, display name, phone number where available, profile photo, device model, user-defined label, tracking and sharing status, pairing proof hash, and timestamps | Authorize and manage accounts that the user chooses to track or that are approved to view live location | Firebase Realtime Database under the paired viewer’s account and compatibility records |
| Trusted contacts | Names, phone numbers, relationship labels, and enabled/disabled contact status entered by the user | Send SOS SMS messages or allow quick emergency contact actions | Primarily local device storage; transmitted to the carrier and recipient when the user sends an alert |
| Emergency profile | Optional name, allergies, medical notes, safe phrase, and other emergency notes entered by the user | Add emergency context to SOS messages when selected by the user | Primarily local device storage; transmitted when included in an SMS or email alert |
| SMS emergency alerts | SOS message text, trusted-contact phone numbers, trigger source, timestamp, map link, coordinates, location accuracy, approximate address where available, and optional emergency profile details | Send emergency alerts to trusted contacts selected by the user | Processed by the Android device, mobile carrier, and recipient; not uploaded to Veromtec as an SMS archive |
| Email location alerts | SMTP host, port, username, password/app password, sender email/name, recipient email, interval, location, timestamp, and message content | Send optional SOS or scheduled location emails through the provider configured by the user | SMTP settings are stored locally; messages are processed by the configured email provider and recipient |
| Accessibility volume shortcut | Volume Up and Volume Down key events only when the optional accessibility service is enabled | Trigger SOS after the configured volume-button sequence while the App is closed, backgrounded, or the screen is off | Processed on the device; not used to read screen content or communications |
| Notifications and foreground services | Notification permission/status, foreground-service state, tracking mode, and task status while SOS or location work is active | Keep background emergency and live-location work visible and help Android continue urgent tasks | Primarily processed on the device |
| Ads and paid package/purchase | IP address, advertising or app-instance identifiers, device/account identifiers, app interactions, ad views/clicks/impressions, diagnostics, consent signals, and Google Play purchase or entitlement status | Show and measure ads, prevent fraud, process the Add Devices + Remove Ads package, and restore entitlement | Google AdMob, Google Play, and limited local entitlement/cache state |
| App settings and preferences | Language, appearance, navigation preference, emergency number, onboarding state, permission status, feature switches, purchase/cache state, and saved configuration | Provide functionality, personalization, and continuity between sessions | Local device storage unless a setting is part of the Firebase live-tracking profile |
| Support communications | Email address, message content, screenshots, logs, device/app details, and any other information the user chooses to provide | Respond to support requests, investigate problems, and protect the Service | Veromtec email/support records and the relevant email service provider |