FlightPoint Data Processing Agreement
Effective from 16 November 2026
This Data Processing Agreement ("DPA") forms part of the Agreement between the Organisation (the "Controller") and FlightPoint, Business ID 2347832-2 (the "Processor"), and is accepted when the Organisation Account is registered. It implements Article 28 of the GDPR. Terms with capital letters have the meaning given in the Terms of Service.
1. Subject matter and duration
1.1. The Processor processes personal data on behalf of the Controller to provide the Organisation Account functions of the Service described in the Service Description.
1.2. The DPA applies for as long as the Processor processes personal data on behalf of the Controller, including the exit and retrieval periods in Section 27.4 of the Terms and the retention periods set by the Controller.
2. Nature and purpose of processing
Hosting, storing, organising, displaying, transmitting, exporting and deleting data in order to manage the Controller's students, members, staff, fleet, calendar, logbooks, documents, messages, theoretical-knowledge training records, reports and notifications, as configured by the Controller.
3. Categories of data subjects and personal data
Data subjects: the Controller's students, aero-club members, instructors, administrators, dispatchers and other staff; persons invited by the Controller.
Personal data: identification and contact data; group, instructor and status; study progress, practice-exam results, study time and readiness data (shared by the student when connecting to the Controller); official exam results recorded by the Controller; logbook entries and signatures; bookings, block times and flight times; licences, ratings, medical-certificate validity and other documents with expiry dates; staff working time, rates and calculated pay; messages and attachments; action logs.
Special categories: data in medical certificates may reveal health data (Article 9 GDPR). The Controller decides whether such data are entered and ensures a legal basis for them.
4. Obligations of the Controller
4.1. The Controller is responsible for the lawfulness of the processing, for informing data subjects (Articles 13–14 GDPR), for the accuracy of the data, and for determining retention periods in accordance with aviation law (including ORA.ATO.120 or DTO.GEN.220).
4.2. The Controller's instructions are given by these documents and by the configuration and use of the Service by the Controller's authorised users. Further instructions must be given in writing and must be technically feasible; instructions going beyond the standard Service may be charged.
5. Obligations of the Processor
The Processor shall:
a) process personal data only on documented instructions from the Controller, including with regard to transfers to third countries, unless required by EU or Member-State law; in that case the Processor informs the Controller before processing unless the law prohibits this; b) inform the Controller without delay if, in its opinion, an instruction infringes the GDPR; c) ensure that persons authorised to process the data are bound by confidentiality; d) implement the technical and organisational measures set out in Annex 1 (Article 32 GDPR); e) assist the Controller, by appropriate measures and insofar as possible, in responding to requests of data subjects (Articles 12–23 GDPR), in particular through the export and deletion functions of the Service; f) assist the Controller in ensuring compliance with Articles 32–36 GDPR, taking into account the nature of processing and the information available to the Processor; g) make available to the Controller all information necessary to demonstrate compliance with Article 28 GDPR, and allow for and contribute to audits (Section 9); h) not use the Controller's personal data for its own purposes, except in anonymised or aggregated form for the security, maintenance and improvement of the Service.
6. Sub-processors
6.1. The Controller gives a general authorisation to the Processor to engage sub-processors. The current sub-processors are listed in Annex 2.
6.2. The Processor informs the Controller of any intended addition or replacement of sub-processors at least 30 days in advance by e-mail or in the Service. The Controller may object on reasonable data-protection grounds within that period. If the parties cannot resolve the objection, the Controller may terminate the Agreement with effect before the change; this is its sole remedy.
6.3. The Processor imposes on each sub-processor data-protection obligations equivalent to this DPA and remains liable to the Controller for the sub-processors' performance.
7. International transfers
The Processor hosts the data in the EU/EEA. Transfers outside the EU/EEA take place only where an adequacy decision or other appropriate safeguards under Chapter V GDPR (in particular the standard contractual clauses) apply.
8. Personal-data breaches
The Processor notifies the Controller without undue delay and where feasible within 48 hours after becoming aware of a personal-data breach affecting the Controller's data, and provides the information available to it under Article 33(3) GDPR, updating it as it becomes available. The Processor takes reasonable measures to contain the breach.
9. Audits
The Processor provides the information needed to demonstrate compliance, as a rule in writing (description of measures, answers to questionnaires). On-site or technical audits may be carried out by the Controller or an independent auditor bound by confidentiality, with at least 30 days' notice, during business hours, not more than once a year unless there has been a breach or an authority requires it, and without access to other customers' data. The Controller bears its own costs and reimburses the Processor's reasonable costs.
10. Support access
Authorised staff of the Processor may access the Controller's account only in a logged, read-only support session for the purposes listed in Section 8 of the Terms.
11. Deletion and return of data
11.1. During the Agreement the Controller can export and delete data with the functions of the Service. Training records are deleted automatically at the end of the retention period configured in the Service (as a rule 3 years after the end of training), with a warning to the Controller 30 days in advance.
11.2. After termination, the Controller can export its data during the periods set out in Section 27.4 of the Terms. The Processor then deletes the Controller's personal data, including copies, unless EU or Member-State law requires storage. Data in backups are deleted in the normal backup cycle (as a rule within 30 days).
11.3. Data in the data subjects' own Personal Accounts, for which FlightPoint is the controller, are not affected.
12. Liability and precedence
12.1. Liability under this DPA is subject to the limitations in the Terms of Service, unless mandatory law provides otherwise. Each party is responsible towards data subjects and authorities in accordance with Article 82 GDPR.
12.2. In data-protection matters this DPA prevails over the other parts of the Agreement.
Annex 1 – Technical and organisational measures
1. Hosting in data centres in the European Union operated by a professional hosting provider; network access restricted by a firewall. 2. Encryption in transit (HTTPS/TLS) for all connections to the Service. 3. Access control: individual user accounts, passwords stored only in hashed form, e-mail verification, protection against automated sign-ups, role-based access rights following the need-to-know principle. 4. Administrative access: restricted to authorised personnel, with strong authentication; support access read-only and logged. 5. Logging of changes to important records. 6. Availability: regular backups and the ability to restore; regular security updates. 7. Separation of the production environment from development and test environments. 8. Retention: automatic deletion at the end of the retention period; export and deletion functions. 9. Organisation: confidentiality obligations of personnel; regular review of the measures.
Annex 2 – Sub-processors
| Sub-processor | Service | Location of processing |
|---|---|---|
| Hetzner Online GmbH, Germany | hosting, backups | EU (Finland) |
| Migadu-Mail GmbH (Switzerland) | e-mail delivery | Switzerland – adequacy decision |
Stripe Payments Europe, Ltd. processes payment data of the Organisation as an independent controller and is not a sub-processor for the Controller's training data.