Navigation by Flycomm App Privacy Notice
Published by Flycomm Networks LTD, company no. 516202223
Effective date: 10 November 2026
Applies to: the Android app "Navigation by Flycomm" (package com.flycomm.nav), published on Google Play by
Flycomm Networks Ltd.
Flycomm Networks Ltd. (company no. 516202223), 21 HaVa'ad HaLe'umi St., Jerusalem, Israel ("Flycomm", "we") is the controller of the personal data described in this notice. Privacy questions and requests: legal@flycomm.co.
This notice covers the Navigation by Flycomm app only. The Flycomm website, the Flycomm Platform and the "Internet Speed Test by Flycomm" app have their own notices: Website Privacy Policy · Flycomm App Privacy Notice.
1. The short version
- The app needs your location while you use it to show where you are and guide you. Navigation itself never runs in the background.
- With your agreement, the app also measures the cellular network for Flycomm (see 2.4): nearby cell towers, signal quality and your location, while the app is open or navigating and, if you grant "Allow all the time", in short sessions every 15 minutes or so while it is closed, plus a short speed test about once an hour. You agree to this on the "Help map cellular coverage" page during onboarding, where you can also decline; you can switch it off at any time in Settings → Network measurements. Flycomm's customers see these measurements as aggregated coverage maps and as individual measurement records without any identifier (see 4).
- An account is optional. Without one the app collects no name, e-mail address, telephone number, contacts, calls, messages, advertising ID or hardware identifier such as the IMEI. The only device identifier that leaves the phone is the Android ID, which the measurement SDK sends with each measurement upload (2.4); it is never shown to Flycomm's customers and never used for advertising. Flycomm customers may sign in with their Flycomm account to use Flycomm Pro (cell-tower positioning); then we hold your e-mail address, display name and customer organisation (see 2.5 and 2.11).
- Routes, place search and addresses come from Google Maps Platform. To do that, the app sends Google your current position, your destination and what you type in the search box. Google's privacy policy applies to that processing.
- To show posted speed limits and lane guidance, the app sends the shape of your route (a thinned line of points, without place names or any account or device identifier) to Mapbox (see 2.3).
- Your drive history (saved places, recent places, drive logs) stays on your device unless you share it yourself.
- Sending diagnostics to Flycomm is off until you turn it on in Settings. When on, we receive logs and crash reports that never contain coordinates, addresses, routes or search queries. Separately, the app checks Google Firebase for its configuration (minimum supported version, feature switches) at most every 12 hours; that check is not analytics and runs regardless of the diagnostics setting (see 2.12).
- Cell-tower positioning (Flycomm Pro: requires a signed-in Flycomm customer account) sends Flycomm the identities and signal strengths of the cell towers your phone sees during a drive, and gets back one estimated position, used when GPS is weak (see 2.5). Neither feature reads your phone number, calls, SMS or SIM identity.
2. What the app collects and why
2.1 Location (while the app is in use)
| Item | Details |
|---|---|
| What | Latitude, longitude, accuracy, speed, heading, altitude and the time of each fix from Android's location services; satellite status (number and signal quality of GNSS satellites). |
| When | For navigation: only while the app is open, or while a navigation session you started is running. A running session shows a persistent Android notification; stopping navigation or closing the app stops the navigation location updates. The network-measurement feature (2.4) has its own, separate location use. |
| Permission | ACCESS_FINE_LOCATION (precise) or ACCESS_COARSE_LOCATION (approximate). With approximate location only, the app runs in a reduced "approximate" mode and neither network measurements nor cell-tower positioning run. ACCESS_BACKGROUND_LOCATION ("Allow all the time") is requested separately, after an in-app explanation, and is used only by the network-measurement feature (2.4); you can decline it. |
| Why | To show your position on the map, follow the route, announce turns, detect when you have left the route and request a new one, and estimate your arrival time. |
| Where it goes | Processed on the device. Your current position is sent to Google when the app requests a route, a reroute or a route refresh (see 2.3); the line of the planned route, not your live position, is sent to Mapbox for speed limits and lanes (see 2.3). It is sent to Flycomm as part of network measurements (see 2.4) unless you switched them off. Cell-tower positioning (see 2.5) sends Flycomm cell-tower readings, not your position. It is written to the on-device drive log (see 2.6). |
2.2 Places you search for, choose and save
| Item | Details |
|---|---|
| What | Text you type in the search box, the places you select, places you long-press on the map ("dropped pins"), recently used places and places you save. |
| Why | To find destinations, plan routes and let you return to places quickly. |
| Where it goes | Search text and your approximate position are sent to Google Places API to produce suggestions; the coordinates of a dropped pin are sent to Google Geocoding API to obtain an address. Recent and saved places are stored only on your device and are not sent to Flycomm. |
2.3 Map services: Google Maps Platform (map, routes, places, addresses) and Mapbox (road attributes)
The map is drawn by the Google Maps SDK for Android, and routes, live traffic, place search and reverse geocoding are provided by Google Maps Platform services. To provide them, the app sends Google: the map area you are looking at, your current position, your origin and destination, your search text and the identifiers of places you select. The Google Maps SDK may also collect device and usage information as described by Google. Google processes this data under the Google Privacy Policy and the Google Maps/Google Earth Additional Terms of Service. Flycomm does not receive your routes or searches from Google.
Posted speed limits, lane layouts, tunnels, road classes and exit signs come from OpenStreetMap data through the Mapbox Map Matching API. After a route is planned or changed, the app sends Mapbox the route geometry: the line of the route, thinned to at most about 100 points per request. The request contains no origin or destination name, no search text, no account identifier and no device identifier; it is authenticated with Flycomm's public Mapbox token, which identifies Flycomm's Mapbox account, not you. Your IP address reaches Mapbox as with any internet request. The answer is held in app memory for that route only and discarded when the route ends or changes. Mapbox, Inc. processes this data as an independent service provider under the Mapbox Terms of Service and the Mapbox Privacy Policy. You can hide speed limits in Settings → Route options; when the app is built without a Mapbox token the feature is off entirely and nothing is sent to Mapbox.
2.4 Network measurements (every user who agrees in onboarding; off at any time in Settings)
Like the Flycomm Speed Test app, this app carries the Flycomm measurement SDK, which collects cellular-network
measurements to build Flycomm's coverage maps and to improve positioning from cell towers alone. During onboarding
the "Help map cellular coverage" page explains this and asks for your agreement before any measurement is taken;
choosing "Not now" leaves the feature off. The app then asks for the "phone" permission (READ_PHONE_STATE) and for
location "Allow all the time"; you can decline either, and you can switch the whole feature off at any time in
Settings → Network measurements, which withdraws your agreement for the future. Navigation works either way.
| Item | Details |
|---|---|
| What | For each nearby cell tower: radio technology (2G/3G/4G/5G), network operator codes (MCC/MNC), cell identifier, area code, physical cell identity, frequency channel and band, bandwidth, signal strength and quality (RSRP, RSRQ, SINR, RSSI), timing advance, whether the device is registered to that cell, the SIM slot index, and the time of the reading; your current location (latitude, longitude, accuracy, speed, heading); device motion from the accelerometer (to tell moving from stationary); network type and throughput; device model, Android version and app version; battery temperature; the number and signal quality of the GNSS satellites in view; a random session identifier created each time the measurement service starts; and the device's Android ID (Settings.Secure.ANDROID_ID), an identifier that Android generates for this app on this device (on Android 8 and later it is specific to the app's signing key and the device user, so it is not the same value another app sees, and it changes when the device is factory reset). About once an hour while the service is running, the SDK also runs a short speed test against a Flycomm test server (download and upload throughput and latency; up to about 25 MB of test data in each direction, so up to about 50 MB per test). |
| What it is not | Your telephone number, IMEI, IMSI, SIM serial number, calls, SMS, contacts, data usage or browsing. |
| When | While the app is open or a navigation session is running. If you granted "Allow all the time", also in short background sessions (about one minute, roughly every 15 minutes) while the app is closed. The SDK also sends small connectivity checks to a Flycomm server; these carry no measurements, but your IP address reaches that server as with any internet request. |
| Why | To build and maintain Flycomm's cellular coverage maps and to train the models that estimate a position from cell towers alone (which is what cell-tower positioning, 2.5, relies on). |
| Where it goes | To Flycomm's collector, hosted by Amazon Web Services (United States, Ohio region): the same measurement platform that receives the Flycomm Speed Test app's data; its analytics database runs on ClickHouse Cloud and its speed-test servers on Cloudflare (section 4). Measurements are stored under the random session identifier, which is not linked to any account or to other sessions. The Android ID arrives with each upload and may be kept with the measurement record for the record's retention period (section 6). It is never shown to Flycomm's customers or partners, never combined with your account, your drive logs or your diagnostics, and never used for advertising or tracking. Through the Flycomm Platform, Flycomm's customers and partners see the measurements as aggregated coverage maps and statistics and, for radio-network analysis, as individual measurement records (location, time and signal readings) that contain no identifier, under contracts that forbid using them to identify, locate, track or profile anyone (section 4). |
| Identifier shown to you | Settings → Network measurements → Cell measurement details shows the current session identifier and sample counters, so you can quote them in a rights request (section 9). |
2.5 Cell-tower positioning (Flycomm Pro; signed-in customers only)
When GPS is weak or lost (tunnels, dense urban areas, parking structures) the app can estimate your position from the cellular network. This feature is available only to users who sign in with a Flycomm customer account whose plan includes navigation (section 2.11). In Settings → Flycomm Pro you choose how the app uses the answers: Off (the default; the app still sends position requests and records the answers on your device to improve the service, but your position on the map follows GPS only), Weak GPS (the answers fill in while GPS is weak or lost) or Cell only (a testing mode that ignores GPS). Signing out stops the requests, and GPS navigation still works. It reads the cell towers itself and does not depend on the Network measurements switch (2.4); it needs the "phone" permission and precise location, like 2.4.
| Item | Details |
|---|---|
| What | Each position request from the app to the Flycomm Hub carries the LTE cell towers your phone sees at that moment (up to 64): for each, the cell identifier, network operator codes (MCC/MNC), radio technology, signal strength (RSRP), whether it is the cell your phone is registered to and, for that cell, the timing advance (a coarse distance to the tower); plus a random request identifier and your account's sign-in token. The request carries no GPS position, no time window, no measurement session identifier and no device identifier. The Hub compares the readings with Flycomm's coverage model (built from the measurements of 2.4) and answers with one estimated position and its uncertainty radius, or asks the app to retry while it is still building that area. |
| When | Throughout a navigation session while you are signed in with an entitled account, in every one of the three settings above: about every 10 seconds (every 20 seconds in battery-saver mode). While GPS is good the answers only calibrate the estimate and are never shown; with "Off" they are never shown at all. The app sends nothing when no cells are visible or outside a navigation session. |
| Why | To estimate your position when GPS cannot, and to keep that estimate calibrated against GPS while it can. |
| Where it goes | To the Flycomm Hub and positioning core, hosted by Amazon Web Services. Position requests are logged against your account for security, billing and rate limiting (at most 60 requests per minute per account). The answers stay in app memory and in the on-device drive log (2.6). |
2.6 Drive logs (on your device)
Each navigation session is recorded to a file on your device: position fixes and estimates, the routes requested and received, guidance events, voice announcements, and technical log lines. These logs exist so that you can share one with Flycomm support when something goes wrong on a real drive (Settings → Drive logs → Share). They are kept for the last 30 sessions or 200 MB, whichever is smaller, and are deleted automatically after that. They are excluded from Android backup and never leave the device unless you share them. A shared log may contain the coordinates of where you drove.
2.7 Diagnostics (opt-in: "Share diagnostics with Flycomm")
When you turn this setting on, the app sends Flycomm technical telemetry so that we can find and fix navigation bugs:
- Log lines and structured events: what the app was doing (route requested, reroute, position quality change, Google call latency and outcome), with the session identifier. Before anything is sent, the app removes coordinates, polylines, addresses, place names, destinations and search queries. Values are truncated and bounded.
- Crash reports and non-fatal errors: stack traces, the log lines preceding the crash, device make and model, Android version, app version, free memory and similar technical state.
- A diagnostics identifier: a random code the app creates on first launch and stores on the device. It lets us group reports from the same installation. It is not an advertising ID and is not linked to any account or hardware identifier. Uninstalling the app deletes it.
- Your IP address, which reaches our providers' servers as with any internet request.
We use these providers to receive diagnostics: Coralogix (log and session analytics, hosted in the EU) and Google Firebase (Crashlytics for crash reports, Analytics for app usage events). Advertising-ID collection and ad personalisation are disabled in the app, and the related Android permissions are removed from it.
When the setting is off (the default) nothing is sent to Coralogix, Firebase Crashlytics or Firebase Analytics. Turning it off stops sending from the next moment; data already sent is kept for the periods in section 6. The configuration check described in 2.12 is not diagnostics and is not controlled by this setting.
2.8 Settings, language and other on-device state
Your preferences (language, units, voice on/off, map and display options such as "Show speed limits", the diagnostics choice) are stored on the device only.
- Resuming an interrupted drive. If Android stops the app during navigation, the destination of that drive is kept on the device for up to 30 minutes so that the app can offer to resume it, and is then deleted. It never leaves the device.
- Connectivity and battery state. The app reads whether the device is online and whether battery saver is on, to adapt its behaviour (for example, an "Offline" indication or a lighter route drawing). These readings are used on the device only and are not collected.
2.9 Voice guidance and notifications
Turn instructions are spoken by the Android text-to-speech engine installed on your device. The app does not record audio and does not use the microphone. The app asks for notification permission to show the ongoing-navigation notification required by Android for a foreground location service, and, on some Android versions, a brief "Measuring cellular coverage" notification while a background measurement session runs (2.4).
2.10 What the app does not collect
No telephone number, contacts, calendar, photos, microphone, camera, SMS, call log, advertising ID, IMEI, MAC address or other hardware identifier. The one device identifier the app transmits is the Android ID inside network-measurement uploads (2.4). No name or e-mail address unless you sign in (2.11). No sale of personal data, no advertising, no cross-app tracking.
2.11 Flycomm account (optional; Flycomm Pro)
| Item | Details |
|---|---|
| What | When you sign in: your e-mail address, display name, Flycomm customer organisation and role, as held by Flycomm's customer directory (Amazon Cognito) and returned by the Flycomm Hub; sign-in tokens, stored encrypted on your device (Android Keystore) until you sign out or they expire (30 days). Each request to the Hub carries the sign-in token and a random request identifier. |
| Why | To confirm that your organisation's Flycomm plan includes navigation (the "Pro" entitlement) and to switch cell-tower positioning on for you. Signing in is optional; the app works on GPS without it. |
| Where it goes | Amazon Cognito (Amazon Web Services, EU-Ireland) handles sign-in; the Flycomm Hub (api.flycomm.co, Amazon Web Services) answers the entitlement check and position requests. If you sign in with Google or Microsoft, their privacy policies apply to that sign-in. |
2.12 App configuration and updates (Firebase Remote Config, Google Play)
| Item | Details |
|---|---|
| What | At app start, at most once every 12 hours, the app asks Google Firebase Remote Config for its configuration: the minimum supported app version, an emergency switch that can stop a faulty version, and feature switches. To do this, Firebase Installations creates an installation identifier for this copy of the app, which is sent to Google with the request together with the app version, device locale and your IP address. The last configuration received is stored on the device and used when the device is offline. |
| What it is not | Analytics or diagnostics: nothing about your location, routes, searches or use of the app is sent. Because it keeps the app safe to use, this check is not controlled by the "Share diagnostics" setting. |
| Updates | Google Play's in-app update service may show a prompt to install a newer version. It uses the Play Store already on your device and sends no additional data to Flycomm. |
| Where it goes | Google LLC (Firebase), as Flycomm's processor. |
3. Legal bases
- Israel: we collect personal data with your informed consent under Section 11 of the Protection of Privacy Law, 5741-1981 (as amended by Amendment No. 13): for navigation, when you grant the location permission after the in-app explanation; for network measurements (2.4), when you agree on the "Help map cellular coverage" page during onboarding and grant the related permissions; for cell-tower positioning (2.5), when you sign in with a Flycomm account (the position requests run while you are signed in, whichever Settings → Flycomm Pro choice you make, and stop when you sign out); for diagnostics (2.7), when you turn the setting on. You are under no legal obligation to provide any of this data; the only consequence of refusing is that the feature concerned does not run (navigation itself needs location). We also rely on our legitimate interests in operating and securing the service, and the data is held in databases maintained under the Protection of Privacy (Data Security) Regulations, 5777-2017.
- EEA / UK (GDPR, UK GDPR): performance of the service you request (Art. 6(1)(b)) for location, routing, places and road attributes (speed limits, lanes), including the device access they strictly need; consent (Art. 6(1)(a), which is also the basis required by Article 5(3) of the ePrivacy Directive and its national implementations for reading cell-tower, location and sensor information from your device for a purpose other than the navigation you asked for) for network measurements (2.4), cell-tower positioning (2.5) and diagnostics (2.7). You give that consent in the app: for network measurements on the "Help map cellular coverage" page during onboarding, for cell-tower positioning by signing in with a Flycomm account, for diagnostics by turning the setting on. You may withdraw it at any time in Settings (Network measurements off, sign out in Flycomm Pro, Share diagnostics off) or by changing the app's permissions, without affecting earlier processing; measurements already received are then kept only as described in section 6. Legitimate interests (Art. 6(1)(f)) cover security, abuse prevention, detecting falsified measurements, service reliability (including the configuration check of 2.12) and improving our models with data already collected; legal obligation (Art. 6(1)(c)) applies where we must retain or disclose data.
- Singapore (PDPA): consent, given as described above after notification of the purposes in this notice; you may withdraw it in Settings or by changing the app's permissions.
- California: this notice serves as the notice at collection. We do not sell or share personal information for cross-context behavioural advertising.
- Where data collected through the app does not relate to an identifiable person and is therefore outside these laws, we nevertheless apply the safeguards described in this notice.
4. Who receives data
| Recipient | What | Role |
|---|---|---|
| Google LLC (Maps SDK, Routes API, Places API, Geocoding API) | Position, viewport, origin/destination, search text, place ids, device and usage data collected by the SDK | Independent service provider under Google's own terms and privacy policy |
| Mapbox, Inc. (Map Matching API) | Thinned route geometry, IP address; no place names, account or device identifiers | Independent service provider under Mapbox's own terms and privacy policy; only when the app is built with a Mapbox token |
| Flycomm collector (Amazon Web Services, United States, Ohio region) | Network measurements (2.4): cell measurements with location, motion, throughput, speed-test results, battery temperature, satellite status, session id, device model, app version, and the Android ID | Flycomm (controller); AWS as processor; every user who keeps network measurements on |
| ClickHouse Cloud | Measurement records, in the analytics database of Flycomm's measurement platform | Processor; every user who keeps network measurements on |
| Cloudflare, Inc. | Speed-test traffic (test data and the IP address of the connection) and network security / content delivery for Flycomm's services, as in the Flycomm App Privacy Notice | Processor; every user who keeps network measurements on |
| Flycomm Hub and positioning core (Amazon Web Services) | Position requests (2.5): the cell towers currently seen (identifiers, operator, technology, signal strength, timing advance), a request id and the account token; no GPS position | Flycomm (controller); AWS as processor; signed-in Pro users only |
| Amazon Web Services (Cognito, EU-Ireland) | Account e-mail, name, sign-in credentials and tokens | Processor, signed-in users only |
| Coralogix Ltd. (EU) | Diagnostics logs and events, diagnostics identifier, IP address | Processor, only when diagnostics are on |
| Google Firebase (Crashlytics, Analytics) | Crash reports, breadcrumb logs, usage events, diagnostics identifier | Processor, only when diagnostics are on |
| Google Firebase (Remote Config, Installations) | Firebase installation identifier, app version, device locale, IP address | Processor, every user (configuration, not analytics; see 2.12) |
| Flycomm customers and partners (mobile operators, infrastructure and tower companies, system integrators, public bodies and other organisations), through the Flycomm Platform | Network measurements (2.4) as aggregated coverage maps and statistics and, for radio-network analysis, as individual measurement records (location, time and signal readings) that contain no identifier; they receive neither your account data, your drive logs nor your diagnostics | Under written contracts that prohibit using the data to identify, locate, track or profile any individual or device and any attempt at re-identification, as described in the Flycomm App Privacy Notice (sections 5 and 6); partners may resell Flycomm services under their own brand on the same terms |
| Research collaborators (universities, research institutions) | Network measurements (2.4), in aggregated form or under written agreements with the same restrictions | As described in the Flycomm App Privacy Notice |
| Authorities, courts, successors | When required by law, to protect rights and safety, or in a corporate transaction | As required |
We do not sell personal data and do not share it for advertising.
5. International transfers
Flycomm is based in Israel. Google and Mapbox process data in the United States and elsewhere; Flycomm's account directory runs in the EU (Ireland); its measurement platform (collector and analytics database) is hosted on Amazon Web Services in the United States (Ohio region) and on ClickHouse Cloud; its Hub and positioning core run on Amazon Web Services in the same United States (Ohio) region; Coralogix stores diagnostics in the EU. Flycomm's customers and partners are located in Israel, Singapore, the United States, Japan, Europe and other countries and may access identifier-free measurement data (section 4) from those countries through the Flycomm Platform. Israel is recognised as providing adequate protection by the European Commission (Decision 2011/61/EU, confirmed in January 2024) and by the United Kingdom; where personal data is transferred from the EEA or the UK to a country without such recognition, we rely on the European Commission's Standard Contractual Clauses (with the UK Addendum or International Data Transfer Agreement where relevant). Transfers out of Israel comply with the Protection of Privacy (Transfer of Data to Databases Abroad) Regulations, 5761-2001, and transfers out of Singapore with the PDPA's transfer limitation obligation. Copies of the safeguards are available from legal@flycomm.co.
6. Retention
| Data | Kept |
|---|---|
| Location, routes, places during use | In app memory only; discarded when the session ends |
| Speed-limit, lane and road data received from Mapbox | In app memory only, for the current route |
| Route geometry received by Mapbox | Processed to answer the request under Mapbox's Product Privacy Policy, which does not state a retention period for request coordinates; Mapbox deletes the IP address of the request within 30 days and does not associate it with the location data |
| Destination of an interrupted drive (resume) | On device, up to 30 minutes, then deleted |
| Drive logs | On device, last 30 sessions / 200 MB; deleted by the app or when you uninstall |
| Recent and saved places, settings, diagnostics identifier | On device until you delete them or uninstall |
| Network measurements received by Flycomm (location, time, signal readings, device data, session identifier) | Individual records 24 months from collection, after which they are deleted or further aggregated so that individual records no longer exist; aggregated coverage statistics, maps and derived data indefinitely (they contain no individual records); trained models for as long as they are in use |
| Android ID received with network measurements | With the measurement record, for the same period as the record (24 months) |
| Account data (e-mail, name, organisation) | For the term of your organisation's Flycomm customer agreement, per that agreement |
| Sign-in tokens on the device | Until you sign out, they expire (30 days) or you uninstall |
| Hub request logs (account, request id, time, cell towers sent, estimated position, outcome) | 30 days |
| Diagnostics logs and events (Coralogix, Firebase Analytics) | Up to 14 months |
| Crash reports (Crashlytics) | Up to 90 days |
| Cached app configuration (Remote Config) | On device until replaced by the next fetch or you uninstall |
| Firebase installation identifier | On device until you uninstall; at Google until Flycomm deletes it through the Firebase API, after which Google removes it from live and backup systems within 180 days (Firebase privacy documentation) |
| Connection and security logs (IP addresses) | 30 days |
| Data needed for legal claims or obligations | For the period the relevant law requires |
7. Security
All traffic uses TLS; cleartext connections are disabled in the app. Data at rest with our providers is encrypted. Access to diagnostics and cell data is limited to Flycomm staff who need it, is role-based and is logged; customer access to measurement data through the Flycomm Platform is governed by role-based permissions and contractual restrictions. We maintain these measures in accordance with the Israeli Protection of Privacy (Data Security) Regulations, 5777-2017, and the security requirements of the GDPR. If a breach affects you we will notify you and the competent authority as the law requires; where we cannot reach individuals we will publish the notice on our website.
8. Children
The app is designed for drivers and is not directed at children. We do not knowingly collect personal data from anyone under 18. If you believe a child has used the app with diagnostics or cell positioning enabled, contact legal@flycomm.co and we will delete what we can locate.
9. Your choices and rights
In the app and on your device
- Deny or revoke the location (including "Allow all the time"), phone-state and notification permissions in Android settings at any time.
- Switch network measurements off in Settings → Network measurements (this withdraws your agreement for the future and also stops the background sessions and the hourly speed test).
- Turn "Share diagnostics with Flycomm" off in Settings.
- Hide speed limits in Settings → Route options.
- Sign out of your Flycomm account in Settings → Flycomm Pro to stop position requests. The "Off" choice there only stops the answers from being used for your position on the map; requests continue while you are signed in (2.5).
- Delete drive logs, recent places and saved places in the app; uninstalling the app deletes everything the app stores on the device, including the diagnostics identifier and the Firebase installation identifier.
Under applicable law you may have the right to access, correct, delete, restrict or object to processing of your personal data, to data portability, to withdraw consent (without affecting earlier processing), and to complain to a supervisory authority: in Israel the Privacy Protection Authority; in the EEA your national data-protection authority (members list: edpb.europa.eu); in the UK the ICO (ico.org.uk); in Singapore the PDPC; in California the CPPA.
To delete your Flycomm account or the data linked to it, or to get a copy of your data, e-mail office@flycomm.co:
Settings → About → "Delete account or request your data" opens a prefilled message, and the deletion page
https://www.flycomm.co/navigation/delete-account explains the same
steps for anyone who no longer has the app. Other privacy requests go to legal@flycomm.co. You can ask for deletion
without signing in to the app. If you have not signed in, the app holds no account or name and we usually
cannot find your data from your e-mail address alone (the GDPR, Article 11, and similar laws do not require us to
collect more information in order to identify you); to locate diagnostics or cell records we may ask for the
diagnostics identifier, the approximate dates and times of use, and the device model. Signed-in users can quote their
account e-mail address; for measurement records anyone can quote the session identifier shown in Settings → Network
measurements → Cell measurement details; quoting your Android ID lets us find and delete the measurement
records (it is shown by many device-information apps, or we can tell you how to read it). We respond within 30 days (one month under the GDPR,
45 days under the CCPA), extendable where the law allows. We will not discriminate against you for exercising your
rights.
10. Google Play disclosures
Before requesting the location permission the app shows an in-app explanation of what it uses location for, and before requesting "Allow all the time" it shows a prominent disclosure ("Help map cellular coverage") that location and cell measurements are collected for Flycomm's coverage maps and cell-only positioning even when the app is closed or not in use, and that they are shared with Flycomm's customers in a form designed not to identify you; network measurements start only if you choose "Continue" on that page. The Data safety section of the Play listing is kept consistent with this notice:
| Play data type | Answer |
|---|---|
| Location (precise and approximate) | Collected; required for navigation (app functionality: your position is sent to Google to plan routes) and, for network measurements, analytics; collected in the background when "Allow all the time" is granted; the network-measurement use can be declined in onboarding and switched off in Settings → Network measurements; encrypted in transit; route geometry also reaches Mapbox and positions reach Google, both as service providers, so not "shared" in Play's sense |
| Personal info (e-mail address, name) | Collected only if you sign in; optional; account management |
| Crash logs, Diagnostics | Collected only when you turn diagnostics on; optional; off by default |
| Device or other IDs | Collected; optional. The Android ID, sent with each network-measurement upload (2.4; only if you agree to network measurements); the diagnostics identifier (only with diagnostics on); the Firebase installation identifier (configuration, 2.12). Purpose: analytics (coverage measurements). Not shared with third parties; encrypted in transit; deletable on request (section 9) |
| Advertising ID | Not collected |
The listing gives the deletion request page of section 9 as the account-deletion URL. You can request deletion of data as described in section 9.
11. Changes
We may update this notice. Material changes are shown in the app and on Google Play, with the new effective date, and where the law requires we will ask for your consent again. Earlier versions are available on request.
12. Contact
Flycomm Networks Ltd., 21 HaVa'ad HaLe'umi St., Jerusalem, Israel · legal@flycomm.co (privacy) · office@flycomm.co (support).
Related documents: Navigation by Flycomm — Terms of Use · Website Terms · Website Privacy Policy.