Flightsaver

Privacy Policy

This Privacy Policy explains what data the Flightsaver app uses, why it is needed, where it is stored, and how users can delete their data.

Effective date: July 23, 2026 Contact: developermash@mail.ru

Flightsaver does not sell personal data, does not use advertising tracking, and does not share boarding passes with advertising networks. Data is used to provide app features: flight history, boarding pass presentation, sync, weather, maps, flight status data, and Live Activities.

1. Who is responsible for data processing

The Flightsaver app is operated by DeveloperMash, the app developer. For privacy questions, contact developermash@mail.ru.

2. Data stored by the app

Flightsaver stores data entered manually by the user, imported from a boarding pass, or received through app features.

Flight history

Flight number, departure and arrival airports, date, departure time, airline, seat, notes, aircraft type, aircraft registration, and other details the user adds or the app retrieves for the flight card.

Boarding passes

Barcode data and recognized boarding pass fields: passenger, flight, route, date, seat, terminal, gate, zone, boarding group, boarding time, booking reference, sequence number, loyalty program data, baggage tag numbers, and technical fields when present in the pass.

App settings

Interface preferences, measurement units, iCloud sync state, Live Activities setting, and other local app settings.

3. Where data is stored

The main flight history is stored in the app's local database on the device.
Boarding passes are stored locally in the app's storage and are used to display a boarding pass inside Flightsaver.
If the user enables iCloud sync, flight history is synced through Apple iCloud/CloudKit across the user's devices.
Temporary files received through the Share Extension are placed into the app group container and removed after processing or when the import queue is cleared.

4. Location

Flightsaver requests "While Using the App" location access. Location is used to show the nearest airport, calculate relevance of airport cards, and hide a boarding pass when the user is already at the arrival airport.

The current location is processed by the app on the device. Flightsaver does not send the user's precise current location to its own aviation data server. When Apple system services are used, such as location, reverse geocoding, iCloud, or WeatherKit, data processing is also governed by Apple's terms and policies.

5. Camera, photos, PDFs, and files

The camera is used to scan boarding pass barcodes and recognize text. Photos, PDFs, and files are used only when the user selects or shares them with the app.

Camera frames, selected photos, and PDFs are processed on the device.
Original photos and PDFs are not uploaded to the Flightsaver aviation data server.
After import, the app stores only the data needed for flight history and boarding pass display.
If a file is shared through the system share sheet, it is temporarily copied to the app group container for processing.

6. iCloud/CloudKit

iCloud/CloudKit is used to sync flight history between the user's devices. The system iCloud account is used automatically. No separate Flightsaver account or Sign in with Apple authentication is created or required.

Data in iCloud is processed by Apple and is available to the user through the user's Apple ID. If iCloud is unavailable or the user does not enable sync, the app continues to work locally.

7. Live Activities and push tokens

If the user enables Live Activities and the feature is available, the app may create a Live Activity for a flight. To update the Live Activity remotely, the app sends the following data to the Flightsaver server:

Live Activity push token;
activity identifier and internal flight identifier;
flight number, flight date, departure airport, arrival airport, and route text;
departure time, terminal, gate, baggage belt, and flight status when available;
app language and technical push environment.

This data is used only to update the Live Activity through Apple Push Notification service. The server-side subscription is deleted when the activity ends, expires, or receives an explicit end request. The maximum server-side Live Activity subscription lifetime is limited to 36 hours.

8. WeatherKit

Flightsaver uses Apple WeatherKit to display airport weather. To retrieve a forecast, the app sends Apple the coordinates of the relevant airport or selected forecast point. Passenger name, boarding pass content, and booking reference are not sent to WeatherKit.

9. Aviation data through the Flightsaver server

To retrieve flight statuses, departure times, terminals, gates, aircraft details, and airport delay data, the app contacts the Flightsaver server. The server keeps API keys out of the app and adapts requests to the selected aviation data provider.

The server may use API.market/AeroDataBox, RapidAPI/AeroDataBox, or FR24. The active provider is selected server-side. Requests use only the data needed for the feature: flight number, flight date, airports, route parameters, and technical request parameters. Original boarding pass files, photos, and PDFs are not uploaded to the aviation data server.

The server may keep a technical cache of successful responses to improve performance and reduce the number of provider requests. Flight cache is stored within the calculated lifetime for the particular flight, airport delay cache is stored for up to 2 hours, and general technical cache is stored for up to 1 hour unless a shorter period applies to a particular request.

10. Apple Maps and MapKit

Flightsaver uses Apple's system MapKit technology and Apple Maps map content to display airports and routes. When the map is opened, Apple may process technical data needed to load the selected map region, including the IP address, device parameters, and coordinates of the displayed region. These requests do not include the passenger name, booking reference, or boarding pass content and are governed by Apple's policies.

11. Sharing data with third parties

Flightsaver shares data with third parties only to the extent necessary to provide the selected feature:

Apple - for iCloud/CloudKit, WeatherKit, Apple Maps/MapKit, location, system permissions, Live Activities, and push notifications;
aviation data providers through the Flightsaver server - to retrieve flight and airport data.

Flightsaver does not sell personal data and does not use it for advertising profiling.

12. Retention periods

Flight history and boarding passes are stored until the user deletes them in the app, deletes the app, or clears the corresponding iCloud data.
Local settings are stored until changed by the user or until the app is deleted.
Live Activity subscriptions are stored on the server only while the activity is active and no longer than 36 hours.
Aviation data server cache is stored for a limited period according to the request type.

13. Deleting data

The user can delete individual flights and boarding passes inside the app. When the app is deleted, local data is removed from the device by iOS. If iCloud sync was enabled, data synced through iCloud/CloudKit may remain in iCloud until the user deletes the corresponding data through the app, iCloud, or Apple system tools.

For requests related to data associated with the Flightsaver server, contact developermash@mail.ru.

14. Security

Flightsaver uses iOS system mechanisms, iCloud/CloudKit, and HTTPS connections to exchange data with the server and third-party services. Server-side API keys for aviation data providers are not stored in the app.

15. Children

Flightsaver is not specifically directed to children and does not knowingly collect data from children. If you believe a child has provided personal data without parental or guardian consent, please contact us.

16. Changes to this policy

We may update this Policy when app features, data providers, or legal requirements change. The current version is always available on this page.