// LEGAL — WHAT THE CODE ACTUALLY DOES

Privacy Policy

LAST UPDATED: 9 OCTOBER 2026

Groundrush is a phone companion for the FlySight 2, a GPS logger worn by skydivers and wingsuit pilots. It connects to the logger over Bluetooth, keeps your jump tracks on your phone and analyses them. An optional Groundrush account lets you keep tracks online, analyse them on the website and share the ones you choose.

This policy was written by reading the source code of the app, the website and our server, not from a template. Everything below describes what the code actually does.

The short version

What the app handles

Flight tracks

.CSV files written by a FlySight, and .GPX files. A track contains latitude, longitude, altitude, speed and a timestamp for every sample — that is, a precise record of where you were and when. Tracks get onto the phone either because you imported a file, or because the app downloaded it from a connected FlySight over Bluetooth.

They are stored in the app's own storage area:

Live telemetry over Bluetooth

While you are connected to a FlySight, the device streams position, altitude, velocity, accuracy estimates and satellite count to the phone. This is used to draw the live display. It is not sent anywhere.

Settings, landing zones and the remembered device

The app stores a few small values in the phone's standard app-preferences store: the Bluetooth identifier of the FlySight you last connected to (so it can reconnect without a new scan), interface preferences such as the timezone toggle, the landing zones and reference points you have saved (name and coordinates), and the last firmware list fetched from GitHub. A landing zone you choose is also written to your FlySight over Bluetooth, because that is what the HUD points at. None of it is sent anywhere else.

The phone's own location

The app can ask the phone where it is, for two things only, both on the landing-zone screen:

The operating system asks for your permission the first time, on that screen, never at startup. You can refuse: the warning then stays quiet, and a point can still be typed in or picked on the map by hand. The position is used on the phone and not stored — unless you save it yourself as a point — and the app does not send it anywhere. It is never read in the background.

A weather cache

When wind data is fetched (see below), the answer is cached in the app's own folder under weather_cache, in a file whose name contains the position rounded to two decimal places (about 1.1 km) and the hour. This is so that re-opening the same jump does not re-request the same data.

What leaves your phone, and to whom

Unless you use a Groundrush account (described in its own section below), the app talks to a server of ours for one thing only: the reports described at the end of this section. Apart from that, it talks to three kinds of outside service, and only when you use the feature that needs it. As with any internet request, each of them also sees your phone's IP address, which it may log; what they do with it is governed by their own policies, linked below.

Wind for a jump — weather services

When it happens. Opening the analysis view for a track triggers a wind lookup for that track. The app takes the exit point of the jump being analysed — its latitude, longitude and timestamp — and asks the services below, in order, stopping at the first one that answers. Nothing is requested in the background, and nothing is requested if you never open the analysis view. A cached answer is reused instead of repeating the request.

What is sent. The coordinates and the date of the jump, and nothing else. No device identifier, no name, no track file, no list of your other jumps.

Service What is sent When
Open-Meteo — api.open-meteo.com (open-meteo.com) Latitude, longitude and the jump's date, as URL parameters, plus the list of wind variables requested First choice for every wind lookup
Open-Meteo archived forecasts — historical-forecast-api.open-meteo.com The same parameters Only if the forecast API has no data for that date — in practice any jump older than about two weeks
OpenSky Network — opensky-network.org (opensky-network.org) A bounding box of roughly ±75 km around the position, and the jump's timestamp, with an OpenSky username and password you would have to enter yourself Only if OpenSky credentials have been set. There is no screen to set them in this release, so this request is never made — see the note below

About the last row. The code is in the app, but in this release nothing calls it: OpenSky needs credentials that no screen can enter. It is listed anyway, because the code ships and a future version may enable it — and because a privacy policy that only lists what is convenient is not worth reading.

Note that a jump location is personal information. A dropzone position plus a date says where you were. If that matters to you, do not open the analysis view for tracks you would rather not look up the wind for.

Maps — Google

Two screens show a Google map: Map View, which draws a jump's route over a satellite or road map and opens only from its own button on the analysis screen, and Pick on map on the landing-zone screen. Both use the Google Maps SDK, which downloads the map imagery for the area on screen from Google — so Google learns which part of the world you are looking at, together with your IP address. The route itself is drawn by the app on top of the map.

Google documents that the Maps SDK also sends Google its own usage and diagnostic data: request metadata such as the phone's model and system version, crash reports, a pseudonymous identifier for the SDK, and map interactions such as panning and zooming. Google processes this under the Google Privacy Policy; the app adds nothing to it.

Firmware — GitHub

When a FlySight is connected, the app checks whether newer FlySight firmware has been published — on its own at most once a day, and again whenever you open the firmware update screen — by asking GitHub's public API (api.github.com) for the list of releases. When you install an update, the firmware file for your FlySight's manufacturing batch and its checksum file are downloaded from GitHub. Nothing about you or your device is sent with these requests; GitHub sees an ordinary download. GitHub's handling is governed by the GitHub Privacy Statement.

The app can also open a few links — the firmware installation guide on groundrush.io, the firmware pages on GitHub — in your browser, when you tap them.

Reports to us from the app

When it happens, and what is sent. The app sends a short report to groundrush.io on four occasions, one request each time:

Every report also carries the version of the app and whether the phone runs Android or iOS. Like every request to our website, it is recorded in the website's access log, together with your IP address, the country our content delivery network works out from it, and the app's name and version. The IP address is not stored anywhere else.

What is not sent. No name, no email, nothing about a Groundrush account even if you are signed in, no tracks, no coordinates, no phone location and no identifier of the phone.

Why. To know which firmware versions and batches are in use, and where; how many FlySights have glasses linked; which versions of the app are in use; which connection errors people run into; and at which step a firmware update fails — so that it can be fixed.

How long, and how to opt out. The access log is deleted after 30 days. There is no switch for these reports in the app. If you would rather they were not kept, write to support@groundrush.io with your FlySight's Device ID, and we delete the reports that carry it from the logs.

This website

If your FlySight comes from a manufacturing batch we have never seen, the firmware flasher on groundrush.io has no firmware for it, and — as the page says on screen — it sends us that batch's public key together with the firmware and Bluetooth-stack versions, so support for your device can be added. We store those, plus the country the request came from (as worked out by Cloudflare from your IP address — the address itself is not stored), when that batch was first and last reported, and how many times. Nothing else from the file goes into that report: not the device ID, not your name, nothing that identifies you. Write to support@groundrush.io if you would rather it was not kept.

With a Groundrush account

Everything above holds whether or not you have an account. This section describes what changes if you create one — on groundrush.io, or in the app where your version offers it.

Signing in

You sign in with Google or with Apple; there is no Groundrush password. The provider passes on your email address, your name (Apple only the first time you sign in, and only if you share it — Apple also lets you hide your email behind a relay address) and an identifier for your account with them. These are kept by the sign-in service that runs Groundrush accounts, so that you can sign in again. They are not shown to anyone else and are not part of your public profile. Google and Apple learn that you signed in to Groundrush, under their own privacy policies.

On the website, signing in sets one first-party cookie on api.groundrush.io. It holds a random identifier that keeps you signed in, nothing else, and it ends when you sign out, after 30 days without use, or 90 days after you signed in. A second cookie lasts for at most 10 minutes while a sign-in is in progress. The pages also keep, in your browser's own storage, a note that you are signed in and your username and photo for the page header — no password and no token. None of this is used for tracking or advertising. In the app, the sign-in is kept in the phone's own secure storage (Keychain on iPhone, Keystore on Android).

What we store

If you add a wingsuit or a dropzone that is not in our lists yet, its name joins the shared list that everyone picks from. Others do not see who added it, and the link to you is removed when you delete your account.

We do not read your tracks for anything but providing the service to you.

Where it is kept, and who handles it

Our servers and storage are in the European Union (Ireland), run by a cloud hosting provider that processes the data only on our behalf. Public profiles and public tracks are delivered through a content delivery network with servers around the world, which may hold copies of those public pages for a few minutes close to the people reading them.

To keep the service working and secure, our servers keep logs of requests: the IP address a request came from, what was asked for, the time, the browser's description of itself and, for a signed-in request, your internal account number — not the content you send. They are deleted after 30 days. Database backups are kept for 7 days, so something you deleted can remain in a backup for up to a week before it is gone for good.

Wind for an uploaded track

After a track is uploaded, our server looks up the wind for it at Open-Meteo (historical-forecast-api.open-meteo.com): it sends the position of the track's first GPS fix, to four decimal places (about 10 m), and the date, and nothing else — no name, no account, no file. The answer, wind speed and direction at twelve heights, is stored with the track. This is the same service the app asks when you open a jump's analysis.

Private and public tracks

An uploaded track is private unless you choose Public — on upload, or later on the track. A private track is seen only by you.

A public track can be seen by anyone, without signing in. It is listed in the public feed at groundrush.io/tracks and on your profile page, and has its own page. It shows:

It never shows the GPS coordinates, the height above sea level, the original file or its name, or anything about your device.

A public track is not anonymous: it carries your username. If that matters, keep the track private.

Your profile page, groundrush.io/u/<username>, shows your username, display name and photo and lists your public tracks. It exists as soon as you choose a username, even before you publish anything.

Making a public track private, or deleting it, takes it off the site at once, but copies already delivered can be served for up to 5 more minutes, and copies other people have already downloaded cannot be recalled.

Reports and moderation

Anyone can report a public track or profile, with “Report this page” or by email. A report stores what was reported, the reason given and the time; in place of the reporter's IP address it keeps only a keyed fingerprint of it, to stop one person from flooding us with reports. We look at every report. We may withdraw a public track from public view, block an account, or close an account that breaks the terms. A blocked account keeps its data and can still sign in, download and delete, but all of its tracks become private, its profile page is no longer served, and uploads, profile edits, catalogue additions and reports are refused.

Exporting your data

In your account, Export my data builds a download of everything we hold for you: every uploaded track as the original file, and your profile, wingsuits and track details in a machine-readable file. It stays available for 7 days. You can also download any single track from your track list.

Deleting tracks and your account

For 35 days after the deletion we keep a deletion record: the identifier the sign-in service gave your account and the date — no name, no email, nothing else. It is what keeps a deleted account deleted if we ever have to restore our database from a backup.

Keeping your tracks after you delete your account — only if you agree

When you delete your account, we ask whether we may keep a copy of your finished tracks, unlinked from the account, to improve jump detection and analysis. The box is unticked; leaving it so is a complete answer, and all your tracks are deleted with your account. We do not ask at any other time, and the answer does not change how your account works.

If you agree, each copy is rebuilt from the track data and keeps: the track itself with its GPS coordinates (rounded to about 1 km for BASE jumps), altitude and speed at each point, time counted from the start of the track, the year and month of the jump, the jump type, a summary computed from the track (its length, top speeds, and exit and deployment times counted from its start), the wingsuit model if you picked it from our list, for a skydive the dropzone if you picked it from our list, the wind profile stored with the track, the SHA-256 checksum of the original file (so the copy can be found and erased), and the date the copy was made. Your name, email, username and photo, the exact date and time, the device and session serial numbers, the original file name and title, and the link to your account are not kept.

This is not anonymisation. Coordinates, a year and month and a wind profile can be enough to work out whose jump a track is, so these copies are still personal data, and we treat them as such. They are not published, not shared with anyone, and only we can access them. We keep them while your consent stands and the purpose remains, review the need once a year, and delete them when the purpose ends.

Changing your mind. When you agree, you are given a management code. Keep it: we store only a fingerprint of it, so we cannot show it to you again. After your account is gone, enter the code at groundrush.io/retained/withdraw — no account and no sign-in needed — and every track kept under your consent is erased. Without the code, write to support@groundrush.io with your original track files, or with their SHA-256 checksums (which you can work out on your own computer, so the files never leave it), and we erase the matching copies. Files you send us for this are deleted once the request is done, within 30 days.

What the app does not do

Verified by going through the app's complete dependency list:

Permissions, and why

Android

iOS

Sharing and export are yours to trigger

The app can hand a track to the system share sheet, so you can save it to Downloads, send it to another app, put it on a cloud drive or give it to a friend. It happens only when you ask for it, and it is you who chooses the destination. Once a file has left the app that way, this policy no longer covers it — the receiving app's does.

Deleting your data

On the phone:

Without an account, the app gives us nothing to delete on your behalf except the reports it sends us, which are deleted after 30 days, or earlier if you write to us. With one, see Deleting tracks and your account: deleting a track or the account deletes what we hold. If you sent an unknown-batch report from the website flasher, write to us and it goes.

Children

Groundrush is a tool for licensed skydivers and is not directed at children.

If you are in the EU / UK

Without an account there is no database of app users on our side: the only thing the app sends to a server of ours is the reports described above, which we keep in our access log for 30 days to see which firmware and app versions are in use and where things fail, and which we delete earlier if you write to us. Everything else is on your device and under your control, and uninstalling removes it.

With an account, Groundrush is responsible for the data described in With a Groundrush account. We hold your profile and tracks to provide the account you asked for; we keep copies after account deletion only with your consent, which you can withdraw at any time as described there; and we keep the request logs, the backups, the deletion record and reports to keep the service secure and working. You can see and download your data (Export my data), correct your profile, delete tracks or the whole account yourself, and object to or ask about anything here by writing to us. You can also complain to the data protection authority where you live.

The flows that involve data leaving your device are the ones described above: a jump's coordinates and date to the weather services, the map area to Google, firmware requests to GitHub, and the app's reports to us. The outside services act on their own account and under their own privacy terms; the app sends them no identifier of its own that would let them tie a request to you personally, though they will see your IP address like any other web server does, and the Google Maps SDK sends the usage data Google describes in its own documentation.

Changes

If the app starts doing something this document does not describe, this document changes first. The date at the top says when it was last revised.

Contact

Questions about this policy: support@groundrush.io