The AutoSOS App respects your privacy as follows:
- In order to alert effectively, AutoSOS sends SMS with location data (coordinates: latitude / longitude) of the person in distress only in case of emergency / alarm and only to alarm recipients registered by the user.
- AutoSOS reads incoming SMS only to respond to specific instructions which increase the effectiveness of the alarming process.
- Notifying alarm recipients of incoming alarm SMS even if the mobile is in silent mode.
- Initiating a callback in handsfree mode in case the alarming person is unable to answer incoming calls on his/her own.
- AutoSOS does not store any personal information except those necessary for the operation of the App (e.g., tel. no. of alarm recipients).
The data is only locally stored on the mobile and will not be transmitted.
- AutoSOS does not send any personal data.
- When alarms are triggered, SMS with location data are sent only to alarm recipients registered by the user.
- When the user manually sends log messages by email from AutoSOS.
Following message will then be presented to the user:
The generated log messages are anonymized.
You can also verify them by sending the logs to yourself beforehand.
We use the logs exclusively for troubleshooting and will delete them immediately.
- AutoSOS does not access the address book.
- However AutoSOS uses the following Google’s Firebase library modules, if you do not disable its usage during the installation process of AutoSOS:
- Firebase Crashlytics
Detects stability issues. It collects the following data:
- An RFC-4122 UUID which permits us to deduplicate crashes
- The timestamp of when the crash occurred
- The app\s bundle identifier and full version number
- The device’s operating system name and version number
- A boolean indicating whether the device was jailbroken/rooted
- The device’s model name, CPU architecture, amount of RAM and disk space
- The uint64 instruction pointer of every frame of every currently running thread
- If available in the runtime, the plain-text method or function name containing each instruction pointer.
- If an exception was thrown, the plain-text class name and message value of the exception
- If a fatal signal was raised, its name and integer code
- For each binary image loaded into the application, its name, UUID, byte size, and the uint64 base address at which it was loaded into RAM
- A boolean indicating whether or not the app was in the background at the time it crashed
- An integer value indicating the rotation of the screen at the time of crash
- A boolean indicating whether the device’s proximity sensor was triggered
- Firebase Performance Monitoring
Detects performance issues. It collects the following data:
- General device information, such as model, OS, and orientation
- RAM and disk size
- CPU usage
- Carrier (based on Mobile Country and Network Code)
- Radio/Network information (for example, WiFi, LTE, 3G)
- Country (based on IP address)
- App version
- App foreground or background state
- App package name
- Firebase installation IDs
- Duration times for automated traces
- Firebase Remote Config
To inform you about important AutoSOS updates. It collects Firebase installation IDs that are related to the AutoSOS app and not to the user.
- Google Analytics for Firebase
We use “Google Analytics Events” to detect unexpected app internal behavior that does not directly cause a crash but could eventually lead to problems. For the type of information collected through the Google Analytics for Firebase see: Google Analytics for Firebase data collection
No other Firebase modules are utilized. The collection of any other personal data has been disabled.
For more and updated information about Google’s Firebase see: Privacy and Security in Firebase
The quality and stability of AutoSOS are crucial to us.
We rely on being able to quickly detect any problems on all different devices to fix them rapidly.
Therefore, we hope that you will allow us to use the Google Libraries listed above.
- Firebase Crashlytics
This Web Site
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
Who we share your data with
We do not share any data. If you request a password reset, your IP address will be included in the reset email.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.