This page summarises the data the mobile apps collect and how it is handled. It mirrors the answers given in
the Google Play Console “Data safety” form for the Android app; rows and notes marked iOS describe
the iOS app. For full details see our Privacy Policy.
Summary
- Data is encrypted in transit (HTTPS/TLS).
- Location is collected only while the user enables a GPS Tracker or sends an SOS.
- The device calendar permission (Android only, optional, off by default) is used
only locally on the device; nothing from the calendar is sent to the server.
- Users can export their data and delete their account in the app (see
Privacy Policy §8).
- No data is sold or shared with advertisers / data brokers.
- No third-party advertising or analytics SDKs.
Data collected & shared
| Data type | Collected | Shared | Processing purpose | Optional? |
| Location — Precise location |
Yes | Yes* |
App functionality — vehicle GPS tracking (during a shift / active incident) and member GPS tracking
(the user’s own location, always-on while the user keeps it enabled); SOS. Collected only while the
user enables a tracker; reporting continues while the app is backgrounded or the screen is off.
Android: “location”-typed foreground service with a persistent notification; the Android
background-location permission is not used. iOS: “While Using the App” authorization only
(not “Always”), with the iOS location indicator shown while tracking. *Shared with the team’s live map
and, on SOS, with the team (push and the team’s Telegram channel). |
Optional (user-initiated) |
| Personal info — Email address |
Yes | No |
Account management, authentication (Google Sign-In; iOS: also Sign in with Apple, where the
user may choose Apple’s “Hide My Email” relay address). |
Required |
| Personal info — Name |
Yes | No |
Account management, identifying the user within the team. |
Required |
| Personal info — Other (profile photo, user ID) |
Yes | No |
Account management (Google profile photo and account identifier; iOS: Apple account
identifier). |
Required |
| Personal info — Phone number |
Yes | Yes* |
Saved in the user profile. *Shared with the team only when the user triggers SOS and has
explicitly opted in by turning on the “show my phone” privacy option themselves. This option is off by
default, so the phone number is never sent without the user’s own consent. |
Optional |
| App activity — Other user-generated content / in-app actions |
Yes | No |
App functionality (shifts, incidents, vehicles, equipment and related operational records). |
Required |
| Device or other IDs (push token, device label) |
Yes | No |
App functionality — delivering push notifications (Firebase Cloud Messaging; iOS: Apple Push
Notification service) and managing device sessions. |
Required |
“Shared” = transferred to a third party for their own use. Google (Sign-In, Firebase Cloud
Messaging), Apple (Sign in with Apple, Apple Push Notification service — iOS), the team’s messaging channel
(Telegram, used to deliver SOS/coordination messages), the email delivery provider (Brevo) and the hosting
provider act as processors for the purposes above. Location and (optionally) phone number marked with * are
shared with the user’s own team for operational coordination, not with advertisers or data brokers.
Security practices
| Practice | Answer |
|---|
| Data encrypted in transit | Yes — HTTPS/TLS; cleartext disabled |
| Users can request data deletion | Yes — in the app (Profile → “Αποχώρηση από την ομάδα” → confirm in the “Αποχώρηση και διαγραφή” dialog) or on the web (Profile → “Αποχώρηση από την ομάδα” → confirm), with immediate irreversible anonymisation, or by email request (Privacy Policy §8; Account & Data Deletion) |
| Committed to Play Families Policy | No — app is not targeted at children |
| Independent security review | Not declared |
Play Console — key answers
Does your app collect or share any of the required user data types? Yes.
Is all of the user data collected by your app encrypted in transit? Yes.
Do you provide a way for users to request that their data is deleted? Yes — in the app (Profile → leave the team → confirm “leave & delete”) or on the web (Profile → leave the team → confirm); either way the account is irreversibly anonymised immediately. Users can also request deletion via the contact email in the Privacy Policy, completed within 30 days.
Is any of the collected data sold or shared with third parties for advertising? No.
Foreground location justification: The App reports location only while the user explicitly enables an in-app GPS Tracker — either the Vehicle tracker (the operated vehicle, during the user’s shift / an active incident) or the Member tracker (the user’s own location, always-on while enabled, for team coordination and SOS). Both use a location-typed foreground service with a persistent notification and keep reporting while the app is backgrounded or the screen is off. The ACCESS_BACKGROUND_LOCATION permission is not requested; tracking never runs unless the user has turned it on.