GibGate ("we", "us", "the app") is published by Digital Nafta, Terrassa, Spain. This policy explains exactly what the app does with data, what it does not do, and why. It is written to be checkable against the app's own behaviour rather than to sound reassuring.
1. Location
GibGate can use your location, and it is entirely optional. The feature is called Approach alerts, it is off by default, and it only starts after you switch it on yourself in Settings.
When it is on, iOS watches a single circular region of about one kilometre around the level crossing where the barrier drops (36.15125, -5.34870). Entering that region wakes the app for a few minutes so it can work out whether you are walking or driving towards the barrier while a closure is due, and warn you if the timing is against you.
- Your location never leaves your device. It is not sent to our servers, not written to our logs, not shared with anyone, and not stored beyond the few minutes the calculation takes. Everything happens inside your iPhone.
- We ask for the "Always" permission because iOS will not wake a closed app for a region crossing with anything less. Without it the warning could only arrive while you already had GibGate open, which defeats the purpose.
- Outside that one-kilometre region the app does not look at where you are at all.
- You can turn it off at any moment in GibGate Settings, or revoke the permission in iOS Settings. Both stop the monitoring immediately.
Continued use of GPS running in the background can decrease battery life. GibGate only turns it on inside that region, and switches it off again as soon as it has an answer or after twelve minutes, whichever comes first.
2. What we never collect
- Your name, email address, phone number or any account details. There is no login, no account and no profile.
- Your contacts, photos, calendar, microphone, camera or health data.
- Your location history, or any location data at all on our servers (see section 1).
- Advertising identifiers. The app shows no advertising and does not track you across other apps or websites, so it never presents the App Tracking Transparency prompt.
3. Analytics and crash reporting
GibGate uses Google Firebase Analytics and Firebase Crashlytics to understand use of the app and diagnose faults.
- Pseudonymous analytics. The app generates a UUID and stores it in the iOS Keychain. Firebase Analytics receives this UUID as a user identifier. It does not contain your name, email or Apple ID, but usage and purchase events are linked to it and are not anonymous.
- Product interaction. Events include screens opened, alert and preference interactions, and the identifiers of flights whose details or cards you view. These events do not contain your location coordinates.
- Purchase history. Verified purchase events include the StoreKit transaction identifier and product, value and currency information. The same UUID is supplied to Apple as the StoreKit appAccountToken.
- Diagnostics. Crash and performance data can include crash traces, app version and device information. GibGate does not set the analytics UUID as a Crashlytics user ID, so these diagnostics are not linked to that pseudonymous analytics identity.
- Google processes these data under its Firebase privacy terms. Firebase may also use its own app-scoped identifiers.
- Meta and TikTok SDKs are included but are not configured or initialized in GibGate 1.6. They do not collect app events in this configuration. GibGate does not use IDFA or track you across other apps or websites.
4. What stays on your device
Your crossing preferences, safety buffer, quiet hours, habitual crossings and approach-alert setting are stored locally using iOS UserDefaults and SwiftData. If you enable iCloud sync in Settings, they also sync through your own private iCloud account, which we cannot read.
5. Data our server sees
The app fetches the runway schedule and gate state from https://gibgate.digitalnafta.com/api/*. Each request carries only your device IP address, visible in standard nginx access logs, and a generic user-agent identifying the app version. Logs are rotated every 7 days and purged after 30, and are used only to keep the service running and prevent abuse. No request contains your location, and nothing in the logs is linked to an identity.
6. Where the flight data comes from
To predict closures the backend consults the published Gibraltar (LXGB) airport schedule, public ADS-B feeds (airplanes.live, adsb.lol, adsb.fi), FlightAware for filed flight plans, and public METAR weather. Nothing about you is sent to any of them.
7. In-app purchase
Apple handles the optional one-time GibGate Pro payment through StoreKit 2. We do not receive your payment card details or Apple ID. The app reads verified transaction information and records the purchase analytics described in section 3, linked to its Keychain UUID. Family Sharing is enabled for eligible purchases.
8. Notifications
All notifications are scheduled locally on your device from the runway schedule. We operate no push server and send nothing to your phone from our side.
9. Children
GibGate is rated 4+ but is not directed at children. It contains no advertising, user-generated content or chat. The analytics and diagnostics described in section 3 apply when the app is used. Contact us if you believe a child has provided personal information that should be removed.
10. Security
The API is served over HTTPS with TLS 1.3 and a Let's Encrypt certificate, from a private VPS in Germany.
11. Your rights (GDPR / CCPA)
There is no GibGate account, but pseudonymous identifiers, usage and purchase data, diagnostics and server logs are processed as described above. You can contact support@digitalnafta.com to request access, correction or deletion of data, or exercise applicable privacy rights. We may need information to locate the relevant records. Deleting the app stops new app events but does not automatically delete previously collected data. The Keychain UUID can survive an uninstall and may be reused after reinstalling. Location permission can be revoked separately in iOS Settings.
12. Changes
Material changes are reflected here with a new date. This update for GibGate 1.6 explains the pseudonymous analytics identifier, flight interactions and purchase history introduced by the analytics integration. Optional location processing remains on your device.