GDPR

GoUpTower processes personal data strictly adhering to Article 5 GDPR principles:

• Lawfulness, Fairness & Transparency: Data is collected under clear legal bases (Art. 6) with full user notice.
• Purpose Limitation: Collected solely for job aggregation, profile management, certificate tracking, internal statistical analysis, rotation planning, the airports board, the CV Builder and Wind Farm Builder, the partner programme for employers, and, in the iPhone app, wind readings, notifications and emergency map searches you have asked for, and platform security.
• Data Minimization: Only data strictly necessary for platform functions is requested. For example, the defibrillator map sends only a position rounded to about one kilometre, and it goes through GoUpTower's own server, so the map service never learns who is asking; visitors without an Account are counted in statistics with one-way hashes, never by name or IP address.
• Accuracy: Users maintain direct control over profile data in their Account Dashboard.
• Storage Limitation: Each kind of data has its own retention period (Privacy Policy, Sections 3 and 10), enforced automatically every day. Data is purged upon account deletion, and statistics are made anonymous, except records the law requires to be kept.
• Integrity & Confidentiality: Password hashing (bcrypt) and SSL/TLS encryption protect data against breach. The administration panel requires a second sign-in step.
• Accountability: The Controller is responsible for meeting these principles and can show how each one is met.
• Scope: These principles apply to the website and to the GoUpTower app for iPhone alike, and to the representatives of employers who use the partner programme (Privacy Policy, Sections 6A and 6B). The app additionally involves Apple as a processor and, for App Store transactions, as an independent controller — for distribution, in-app purchases, push notifications, wind data and "Sign in with Apple". The hospital map is searched by Apple Maps directly from your device. The defibrillator map is looked up by the Controller's server in OpenStreetMap using a rounded position that is neither stored nor logged. Your packing list, events exported to your iPhone's calendar, CV drafts not saved to your Account and PDFs made in the app, Safety Book progress, the offline Education Hub, emergency map results, and your widget layout and appearance choice stay on your device and never reach the Controller.

Under GDPR Articles 15-22, Users possess the following actionable rights:

• Right of Access (Art. 15): Obtain confirmation and a copy of all stored personal records.
• Right to Rectification (Art. 16): Modify inaccurate data instantly via the Dashboard.
• Right to Erasure (Art. 17): Request complete account deletion and data purge.
• Right to Restriction (Art. 18): Pause processing under contested accuracy or legal disputes.
• Right to Data Portability (Art. 20): Receive the data you provided in a structured, commonly used, machine-readable format (JSON or CSV), or have it sent to another controller where that is technically feasible.
• Right to Object (Art. 21): Object to processing based on Controller legitimate interests, including statistics and the monitoring of public mentions.
• Right to Withdraw Consent (Art. 7(3)): At any time, as easily as it was given, without affecting processing already carried out.
• Automated Decision-Making (Art. 22): GoUpTower does not use fully automated profiling producing legal effects.

REQUEST PROCEDURE

3.1. Users can exercise any right, including data deletion, by emailing gdpr@gouptower.com from their registered email address. An Account can also be deleted directly, without writing to anyone: on the website from the Dashboard, or in the app under Account → Delete account.

3.1a. Consent given on a device — location and notifications in the app — is withdrawn in iOS Settings → GoUpTower, or from the switches in the app itself. Withdrawal takes effect immediately and does not affect processing already carried out.

3.2. Requests are free of charge and are answered without undue delay, and in any event within one month of receipt. Where requests are complex or numerous, that period may be extended by two further months; you will be told of the extension, and why, within the first month. Requests that are manifestly unfounded or excessive may be refused or charged for as Art. 12(5) GDPR allows.

3.3. To protect your data, the Controller may ask for information confirming your identity before acting on a request, for example a message from the email address registered on the Account.

RIGHT TO LODGE A COMPLAINT

4.1. If a User believes processing violates GDPR, they have the right to file a complaint with a supervisory authority, in particular in the EU country where they live or work. In Poland: President of the Personal Data Protection Office (Prezes Urzędu Ochrony Danych Osobowych, UODO), ul. Stawki 2, 00-193 Warsaw, uodo.gov.pl.

5.1. Controller and contact. The controller is the Service Provider named in Section 1 of the Terms of Service and the Privacy Policy. The Controller has not appointed a Data Protection Officer, as Art. 37 GDPR does not require one for this processing; gdpr@gouptower.com is the contact for every data protection matter.

5.2. Processors. Hosting, e-mail and payments are handled by processors bound by data processing agreements under Art. 28 GDPR. Other recipients, such as Apple, Google and the OpenStreetMap Foundation, act as independent controllers for their own services. The list is in Section 4 of the Privacy Policy.

5.3. Personal data breaches. If a breach is likely to put people's rights and freedoms at risk, the Controller notifies UODO within 72 hours of becoming aware of it (Art. 33 GDPR), and tells the people affected without undue delay where the risk is high (Art. 34 GDPR). Every breach is recorded, with what was done about it.

5.4. Transfers outside the EEA. Only on the safeguards Chapter V GDPR allows: an adequacy decision, the EU–US Data Privacy Framework, or the European Commission's Standard Contractual Clauses (Privacy Policy, Section 9).

5.5. Data protection by design. New features are built to collect as little as they need: for example, statistics use one-way hashes instead of IP addresses, and retention periods are enforced by the system rather than by hand.