Jumpbase Dev

Privacy notice

This notice explains what personal data [club name] collects through Jumpbase, why we collect it, who can see it, how long we keep it, and what rights you have.

1. Who is responsible for your data

The data controller is [club registered name], registration number [registration number], [club address].

For any question about your data, or to use your rights, write to [contact email].

2. What we collect

Account details: first and last name, email address, password (stored only in encrypted, unreadable form), the role you jump in (for example licensed jumper, student, instructor, pilot) and your account status.
Contact and emergency details: phone number and an emergency contact's name and phone number, if you provide them.
Licence and qualifications: licence number and expiry date, ratings and qualifications with their expiry dates, and copies of documents you upload as evidence.
Jumping activity: jump requests, the loads you are placed on, exit altitude, aircraft, date, whether the jump was completed, your total of jumps made elsewhere, and any suspension of jumping privileges.
Tandem passengers: first and last name, entered by the manifest so the jump can be scheduled.
Notifications: messages the app sends you, your choices about which notifications you receive, and, if you turn on notifications on a device, a technical address for that device. You can turn this off at any time.
Acceptance records: when you accepted the terms of use, the safety acknowledgement and this notice.
Security records: sign-in sessions (device and IP address), two-step verification settings if you use them, and a log of important actions (for example changes to loads, accounts and jump records), with the time and the person who made them.

3. Why we use it

To run jump operations and your membership: to manage requests, build loads, notify you about your loads and keep your jump history. This is necessary to provide the service you asked for.
For safety: to check that people jump within valid licences and qualifications, and to reach your emergency contact if something happens. This is in our legitimate interest and in your vital interest.
To meet legal and regulatory obligations that apply to the club, for example keeping records of flights and jumps.
To keep the system secure and to be able to investigate mistakes or misuse. This is in our legitimate interest.

We do not sell your data, use it for advertising, or make automated decisions about you.

4. Who can see it

Other members: your name, role and exit altitude appear on the published manifest and on the hangar screen when you are on a load.
Pilots see who is on the loads they fly.
Manifest and club administrators see what they need to run operations; only system administrators can see contact details, documents and the security log.
Service providers that host and run the system for us, under contract: [hosting provider and country]. If you turn on notifications, the notification service of your device's maker (Apple, Google or Mozilla) delivers an encrypted message to your device; it cannot read your data.
Authorities, only when the law requires it, for example after an incident.

5. How long we keep it

Jump records are kept for [number of] years after your account is closed, because they form the club's operational record and your logbook.
Other personal data (contact details, documents, notification devices) is deleted [number of] years after your last activity, or earlier if you ask and we have no legal reason to keep it.
Security logs and sessions are kept only as long as needed to keep the system safe.

6. Your rights

You have the right to see the data we hold about you, to have it corrected, to have it deleted or its use restricted, to object to its use, and to receive it in a portable format. Most details can be viewed and updated in your profile; for anything else, write to [contact email]. We reply within 30 days.

If you believe we handle your data unlawfully, you can complain to [data protection authority].

7. Cookies

Jumpbase uses only the cookies it needs to work: one that keeps you signed in, one that protects forms against forgery, and, on hangar screens, one that remembers the screen's access code. There are no tracking or advertising cookies, so no consent is needed.

8. Changes to this notice

If we change this notice in a way that matters, you will be asked to read it again the next time you open Jumpbase.