Privacy and data
Egypt Paragliders Privacy Policy
Last updated: October 2026
Egypt Paragliders is committed to protecting personal data and privacy in accordance with applicable Egyptian laws and regulations, including the Egyptian Constitution, Personal Data Protection Law No. 151 of 2020, and its Executive Regulations issued by Decision No. 816 of 2025, as applicable to the service.
Article 57 of the Egyptian Constitution protects private life and the confidentiality of postal, electronic, telephone, and other communications. This policy explains how the Egypt Paragliders app and Flight Log handle information in practice; it does not claim any licence or accreditation from the Personal Data Protection Center.
1. Introduction
This policy applies to the Egypt Paragliders Android app and its Flight Log service. It distinguishes information kept locally on your device, information you choose to upload to Egypt Paragliders, and information you intentionally send to another app or service.
2. Information We Process
Depending on the features you use, we may process account and profile information, authentication tokens, precise location, flight tracks, timestamps, altitude and sensor readings, flight statistics, uploaded IGC files, equipment information, SOS information you enter, language preferences, and limited operational diagnostics. We do not use this information for advertising or marketing tracking.
3. Account Information
A Flight Log account may include your username, email address, password hash, name, country, profile photo, biography, pilot experience, home flying site, equipment, disciplines, visibility choices, and other profile details you choose to provide. Mobile access and refresh tokens support app authentication and are stored on the device using Android security facilities. The website uses necessary session and language-preference cookies; it does not use advertising cookies.
4. Location and Flight Data
The app uses precise GNSS location during flight recording, live maps, GPS-altitude and AGL-related features, navigation, and flight statistics. The app uses a foreground location service during Flight Recording and while Live Tracking is actively sharing location, including when Live Tracking starts before Flight Recording. A flight may include latitude, longitude, timestamps, GPS altitude, pressure altitude when available, speed, track data, and derived values such as distance, duration, climb and sink. Location is not used for advertising.
5. Saved Flights and Uploads
Saved Flights can remain locally on your device until you remove them. When you choose to upload or synchronize a flight, the app sends the IGC file and associated track, time, altitude, calculated flight information, and account association to the Egypt Paragliders Flight Log. Public flights and selected public profile information can be viewed by other visitors; private flights remain subject to the service access rules.
Live Tracking
Live Tracking starts only when you explicitly choose to start it, including before Flight Recording if you wish. Private is the default; Public requires an explicit choice and can be viewed without login. Private sessions never appear in public lists. Viewers with a valid server-generated, read-only share link can view a private session while it is retained, so share the link carefully. Authorized Egypt Paragliders administrators may access or export retained Live session data through internal administrative tools when reasonably necessary for service operation, support, security, incident handling, or data administration. This administrative access does not make a private session public.
During Live Tracking, the app sends latitude, longitude, and recorded_at_utc (the time the point was recorded), plus ground_speed_mps, course_deg, and horizontal_accuracy_m when available. Live V1 does not send altitude or AGL. These points are received and stored by the Flight Log server; the displayed last known location is the last point received by the server, not a guarantee of the pilot’s current location.
Stopping Live stops new updates but does not immediately erase the saved route. A session without END becomes STALE and then EXPIRED after more than 24 hours without server activity. If Android is offline during sign-out, it may be unable to send END; it does not retain an authentication token solely to complete END later, so server expiry and cleanup apply. Ended public sessions may appear in Recent Live Pilots for 24 hours; private sessions never appear there.
Daily server cleanup removes an ended Live session and its points once they are eligible, seven days after ended_at_utc; an abandoned session becomes eligible seven days after its 24-hour expiry time. Until purged, its previous track and last known location remain viewable through a valid private share link or public direct viewer, as applicable. After purge, requests for that session’s Live data return 404, so neither viewer can show the track; the stored share-link hash and session identifiers are deleted. Because cleanup runs daily, deletion may occur after, not exactly at, the eligibility time.
6. SOS and Emergency Features
You may manually enter an emergency contact name, phone number, category, and optional area description. These contacts are stored locally; the app does not read or write your device contacts and does not request Contacts permission. SOS uses the current location, a last known location, or reports that location is unavailable. The app does not send SMS automatically or request SEND_SMS permission: choosing Send SMS opens your messaging app with a prepared SOS message, which may include coordinates, and you decide whether to send it.
7. Sharing and Third-Party Apps
Choosing Share Location opens the Android Share Sheet with the SOS text, coordinates, or map link, and you select the receiving app. A country or terrain request similarly opens your email app with a prepared message to egyptparagliders@gmail.com; it is not sent automatically. Information copied to the clipboard or sent through another app is then also handled under Android controls and that app’s privacy practices. Egypt Paragliders does not sell user data or share it with advertisers.
8. Maps and Terrain Services
The app may obtain map content from OpenFreeMap and satellite map content from MapTiler. A shared-location link may open Google Maps. Terrain packages are downloaded from Egypt Paragliders servers for local AGL functionality and may be cached for offline use; terrain package data is not personal data. The Flight Log website may load map tiles from OpenStreetMap and Esri; its Live map requests those basemap tiles directly in the viewer’s browser. Those providers receive requests for the displayed map area and technical connection data such as the viewer’s IP address; they do not receive the Live point-upload payload as part of those tile requests. Their own privacy practices apply.
9. Sensors, Audio and Device Features
GNSS, barometer, compass, and orientation sensors may be used for flight, variometer, direction, detection, and calculation features. Audio Vario generates sound locally and Flight Data Voice uses Android text-to-speech. These features do not record your voice or upload microphone recordings. Automatic takeoff and landing detection uses available flight, location, and sensor data and is not used for advertising.
10. Notifications and Background Operation
The app uses notifications and foreground services when needed for Flight Recording, Live Tracking, and other continuous flight functions. The foreground location service may remain active while Live Tracking that you explicitly started is running, even if Flight Recording has not started. These notifications are operational, not advertisements. If you grant notification-policy or Do Not Disturb access, it is used only to manage the phone experience during flight and does not provide access to the content of your messages.
11. Local Storage and Android Backup
The app stores operational data locally so its features can work. Under the current implementation, designated sensitive or operational data is excluded from Android backup or device transfer, including API tokens, SOS contacts, Saved Flights, active-flight recovery data, terrain payloads, and designated diagnostics. Data you intentionally export, copy, or share is outside those app-managed exclusions.
12. Diagnostics
The app maintains limited local diagnostics to help identify operational problems. These diagnostics are not advertising analytics. The Flight Log server also writes limited upload, email-delivery, startup, and error diagnostics. Upload diagnostics can include an attempt identifier, processing stage, original filename, flight identifier, result, and timing. Diagnostic records are not removed automatically by the account-deletion workflow.
13. Third-Party Services
Hostinger provides the Flight Log hosting infrastructure, including the website and database where Live sessions and received points are processed. The configured transactional-email provider receives the recipient address and verification or password-reset message. When reverse geocoding is enabled, the server can send a flight takeoff latitude and longitude to the configured OpenStreetMap Nominatim service to identify a nearby place. Map and terrain providers receive the requests needed to deliver their content, not the Live point-upload payload. We do not currently use advertising, Advertising ID, Firebase Analytics, or advertiser data sharing, and we do not send Live tracks to advertisers.
14. Data Retention
We retain account and flight data for as long as needed to provide the service, unless you delete the data or account or a longer period is required by law or for legitimate security purposes. Live Tracking has the specific server-side cleanup periods described above. Local data remains on your device until removed through the app, application storage controls, or uninstalling, as applicable. The application code does not specify a fixed retention period for hosting-provider access or error logs or backup copies; these may be governed by infrastructure configuration and applicable requirements.
15. Account and Data Deletion
You can permanently delete your Flight Log account from the authenticated account-deletion screen or use the public deletion page below. The server deletion flow removes the account record, profile information, wings and disciplines, flights, flight points, uploaded IGC files, database authentication and API-token records, and associated Live sessions, Live points, stored share-link hashes, and session identifiers. Requests for their Live data then return 404; the public and private viewers can no longer show those tracks. The current web session ends; profile-photo and IGC cleanup occurs as part of the process. Limited technical logs and provider-managed backup copies may remain where the application deletion flow does not control them. Deletion does not remove data kept only on your device or information you previously sent to another app or service.
16. Data Security
Production connections to the Egypt Paragliders service use HTTPS. We use reasonable technical and organizational measures intended to protect accounts and data, including hashed passwords and tokens and access controls. No storage or transmission method can be guaranteed to be completely secure.
17. Children
The service is intended for paragliding pilots and users of the Egypt Paragliders platform and is not specifically designed for children.
18. Changes to This Privacy Policy
We may update this policy when the app, service, legal requirements, or data practices change. The updated date at the top identifies the current published version.
19. Contact Us
For privacy questions, account-deletion assistance, or questions about how your information is handled, contact Egypt Paragliders. Do not send passwords, raw access tokens, or sensitive flight files by email unless specifically requested through a secure support process.