PRIVACY & YOUR CHOICES

Privacy policy

Understand what information is used, where and why.

Effective 14 Nov 2026 · v2.1OcmS Company Ltd.Previous policies & changes ↗

Trips and notes stay local

Trips and notes are not automatically uploaded to Flightable.

Ticket recognition stays on device

Only your selected image is used, without external OCR upload.

Sharing is your choice

Review booking details and notes in files/PDFs before sharing.

01

Operator and scope

OcmS Company Ltd. (business registration number 858-08-03227, “we”) explains how information is processed in the Flightable app and support website. This policy is version 2.1, effective 14 November 2026.

The current app is Flightable (Incheon). The iOS app for iPhone and iPad is available; Android is in development. This policy covers iOS travel planning, ticket text recognition, maps, weather and sharing. Features may vary by installed version. Android-specific processing and permissions will be described before processing begins.

Privacy contact: OcmS Information Protection Team / Privacy Administrator
Flightable_Support@ocms.tools

02

Information and purposes

CategoryInformationPurpose
Device authenticationAnonymous authentication and installation IDs, session data, device model, OS/app version, IP and integrity-check dataRegistration, server access and abuse prevention
Favorites and notificationsFavorite flight IDs, notification choices, push token and delivery/receipt recordsMY FLIGHT synchronization and selected alerts
Local trips and notesTrip title/dates, flights and itinerary items, places/addresses/coordinates/time zones, booking references, notes and display/language preferencesLocal planning, backup and sharing. Trips and notes are not synchronized to the Flightable server
Photos, camera and text recognitionA booking/e-ticket image selected or captured by the user, with transient recognized text and flight segmentsOn-device recognition; save the flight details you review into an itinerary
Ads and consentAdvertising/device identifiers, approximate location inferred from IP, ad interactions, diagnostics and consent choicesAdMob ad delivery, measurement, security and UMP consent management
SubscriptionsProduct ID, transaction verification data, subscription status and expiryStoreKit purchase verification, restoration and ad removal. We do not receive payment card numbers
Places, maps and weatherPlace queries, selected locations/map regions/coordinates, request IP and connection dataApple MapKit search/maps, WeatherKit destination forecasts and NOAA airport observations
Sharing and exportItinerary, note and booking data in travel files, backups, PDFs, calendar exports and print outputTransfer to apps, recipients or storage chosen by the user
Support and operationEmail address, inquiry/attachments, access time, request path, browser information and operational recordsSupport, security and troubleshooting

Even without name/email registration, device authentication data is processed for service access. Server synchronization of MY FLIGHT is separate from locally saved trips and notes.

03

Ticket photos and on-device recognition

The system PhotosPicker provides only the image you select; this feature does not request full photo-library access. Choosing capture requests camera permission. You can select an existing photo or enter details manually without granting camera permission.

Apple Vision performs recognition on the device. Original selected/captured images are not sent to Flightable or an external OCR server, or stored in the app’s travel/backup file. Image and text data are used temporarily during recognition; the flight details you review and save become itinerary entries. Existing originals in your photo library are not deleted by this process.

The original may contain personal details such as a name or booking reference. Check the recognition result and keep only the details you need. This website does not access photos/camera or run document recognition.

04

Basis and choices

Device authentication, saved-flight processing and subscription verification needed for a requested service are used to provide that service and perform the agreement with you. Records subject to legal retention duties are held to fulfil those duties. Processing that requires separate consent, including applicable advertising or international transfers, is subject to the required consent.

Use available app and operating system settings to change notification and ad choices. Contact support to request withdrawal or restriction. Refusing essential authentication can prevent app access; disabling notifications stops change alerts.

05

Retention periods

Swipe the table sideways to see all columns.

RecordPeriod / starting pointDetails
Flight data & change history3,650 days from the flight datePublic flight information and history; this period does not apply to all user personal data.
Device registration, server My Flight & notification preferencesDuring use; cleaned after 180 days without accessA valid deletion request is handled earlier under the request procedure.
Notification delivery / receipt records90 days from creationIncludes linked device delivery results and receipt confirmations
Administrator access / activity logs180 days from creationOperational and security records
Flight collection execution logs30 days from collection startSeparate from retention of flight data itself
Web server access logs180 days from creationAccess, error and security handling
Database backupsUp to 180 days from backup creationDeletion-request procedures also cover backup copies
General support email180 days after support closesStatutory complaint / dispute records are subject to the exceptions below
Subscription verification recordsDuring the subscription and any applicable statutory retention periodOnly necessary transaction evidence is retained separately; this does not extend every identifier’s retention.
On-device flight cacheUp to 7 daysSeparate from server and note retention
Local notes & user-exported backupsUntil deleted by the userExported files must also be deleted from the selected storage location
Local trips, itinerary and booking detailsUntil deleted by the userBack up before changing devices. Delete exported copies separately at their destination
Recognition image/textTemporary during recognitionReviewed and saved itinerary fields follow the local-trip retention rule
Temporary place information/map imagesValidity of up to 24 hours after retrievalExpired entries stop being used and are pruned based on the displayed deadline. User-written itinerary text remains separate
Airport weather/destination forecastAirport observations and destination forecasts are reused for 30 minutesExpired data is due for refresh; older cache files may remain on the device. Observation/fetch times are shown. Temporary weather is excluded from travel backups

Server cleanup runs once daily. Where Korean e-commerce recordkeeping duties apply to us, contract / withdrawal and payment / supply records are retained for five years from the relevant record, complaint / dispute records for three years, and display / advertising records for six months. Such records are segregated, used only for the required purpose and deleted when the period ends.

06

Deletion and destruction

In iOS, use Support & Privacy → Delete device registration and anonymous account to remove server registration, synced favorites, notification records and the Firebase anonymous account. If completion is not shown, retry online or email support. Local MY FLIGHT, notes, trips and itineraries are retained by this action and must be deleted separately by the user.

When retention ends or the purpose is fulfilled, personal information is destroyed without undue delay unless a legal exception requires retention. Electronic records are deleted so they cannot be recovered; any paper copies are shredded or otherwise destroyed.

After checking the device and the requester’s authority, the privacy contact takes the required deletion steps for server records, Firebase authentication / installation identifiers and relevant backups, then communicates the result. Deleted information is prevented from being reused through backup restoration. Final removal within Firebase’s own live and backup systems may follow the provider’s published timeline.

User-exported files and Apple / Google’s independent transaction records are not erased by deleting our server records. Uninstalling or requesting data deletion does not cancel a subscription; cancel separately in the purchase store.

07

External services and disclosures

Our app server and database operate on our own infrastructure in South Korea. Firebase supports authentication, app integrity and push; AdMob/UMP supports ads and consent; Apple App Store/StoreKit supports purchases and restoration. This support website does not include a visitor-analytics tool.

Apple MapKit provides place search/maps, Apple WeatherKit provides destination forecasts and the US NOAA Aviation Weather Center supplies airport observations. A selected place’s coordinates are different from the phone’s live GPS location; the current iOS implementation does not request location permission to track your position. External map apps apply their own permissions and policies.

Aircraft-location links open Flightradar24; travel preparation links open the selected booking/travel provider. That provider’s policy governs IP, browser, cookie, booking and payment information it collects after opening. Affiliate links may contain referral identifiers and may generate revenue for us after a booking or service use.

We do not disclose personal information to unrelated third parties outside the notified purposes except where permitted by law or with any required separate consent. Check each external service’s policy for information it processes independently.

08

International processing and choices

External services can process information internationally even though our own server is in Korea. Google services are operated by Google and the entities / affiliates identified in the applicable service terms; Apple services use the relevant regional Apple entity. Global services do not fix processing to a single country. The official location and privacy resources below provide provider locations and contact routes.

Swipe the table sideways to see all columns.

Recipient serviceLocationData, timing, method, purpose and retention
Google · Firebase AuthenticationUnited StatesHTTPS during authentication: anonymous authentication identifiers, IP, etc. → authentication. IP logs: a few weeks. Anonymous authentication records: until deletion is requested, with provider removal taking up to 180 days.
Google · FCM / App CheckGoogle global facilitiesHTTPS for notifications / verification: installation identifiers, push-related data and attestation data → delivery and security. FCM installation-ID removal: up to 180 days after a deletion request. App Check does not retain attestation material; token validity is at most 7 days. Attestation providers apply their own terms.
Google · AdMob / UMPGoogle global facilitiesHTTPS for ads / consent: ad and device identifiers, IP, interactions, diagnostics and consent → ads and security. Data-specific retention follows Google’s retention policy.
Google Play / AppleStore providers’ global facilitiesStore connections during purchase / restore / validation: transaction data → billing and subscription management. Store legal and transaction-retention policies apply. Apple applies to the current iOS app; Google Play applies when Android launches.
US NOAA / NWS · Aviation Weather CenterUnited States serviceDirect HTTPS weather request: IP and request details → observations and service operation. Logs follow the agency’s records and privacy policies.
Apple · MapKit / WeatherKitApple’s global processing facilitiesEncrypted requests during map/search/forecast use: queries, chosen locations, coordinates, map regions and request IP → place, map and weather services. Retention and deletion follow the applicable Apple service privacy rules.

Necessary outsourced processing / storage is carried out within applicable contract-performance and disclosure requirements. Where separate transfer consent is required, it is a prerequisite. Email us to request restriction or deletion. Refusing essential authentication transfers may prevent app use. Use advertising privacy settings for available ad choices and notification settings for alerts. Viewing this website does not run the app SDKs.

If you do not want Apple map/weather processing or related international transfers, you can enter itinerary details manually without using search, maps or forecasts. Booking-site and sharing transfers involve services you choose; review the recipient and its policy before use.

09

Permissions, sharing, ads and alerts

Manage push notifications in the app and iOS Settings → Notifications. Manage tracking in iOS Settings → Privacy & Security → Tracking and available consent choices in the app’s ad privacy settings. Flight lookup remains available without tracking or notification permission.

The camera is used when you choose to capture a booking document; control access in iOS Settings. Photos use the system picker. Travel import/backup restoration reads a file you choose with the file picker. Calendar export creates an .ics file and does not read your entire calendar. The app does not request contacts access.

Travel files, PDFs and printouts can contain booking references, addresses and itinerary notes. The flight-memo option does not exclude all personal details; inspect the export before sharing. We cannot directly recall or delete copies held by your chosen apps, recipients or storage. If OS/device/cloud backup is enabled, that service’s policy may also apply.

An ad-free subscription removes native and rewarded ads. Travel preparation promotional banners continue to appear after subscribing, and affiliate booking links remain. Necessary authentication/subscription checks and selected notifications also continue. Android permissions and features will be announced at launch.

10

Your rights and guardians’ rights

Request access, correction, deletion, restriction or withdrawal at Flightable_Support@ocms.tools. Use “Privacy request” in the subject and include your platform, app version and request. We will ask only for the minimum additional information needed to verify authority and identify the device record. Do not send passwords, authentication tokens or full card numbers.

Our general support target is 14 business days. Statutory deadlines take priority for privacy-rights requests. Under applicable Korean rules, we notify the result of a correction / deletion request, or the reason for refusal and how to object, within ten days of receipt. Access, restriction and other rights follow their own applicable deadlines and exceptions.

If a legal duty prevents some deletion, we explain the affected records and basis and retain only what is required for the limited purpose. A legal guardian or properly authorised representative may also exercise rights.

11

Children under 14

Flightable is a general travel service and is not primarily designed for children. Where processing a child under 14’s personal information requires legal-guardian consent, that consent is required. Posting this policy or launching the app does not constitute guardian consent.

A legal guardian may contact support about access, deletion, restriction or consent procedures for a child’s information. If we learn of processing without required consent, we will stop that processing and take appropriate action, including deletion.

For children: information about your phone may be used for alerts and ads. Ticket photos and trip notes may contain personal details. Review them with a guardian before sharing.

12

Support website and safeguards

This website has no signup, checkout or enquiry form, advertising SDK or visitor analytics script. Language is preserved in separate Korean and English URLs, without a language cookie or browser-storage entry. Email links only open your mail app; they do not send automatically.

Web access logs are retained for 180 days for security and operations. The site also works over HTTP, which is not encrypted. We therefore do not collect sensitive form input here. App APIs and external store / service connections retain HTTPS URLs.

We limit personal-data handling and use service authentication, integrity checks, retention controls and deletion-request procedures.

Country searches and filters in Entry guides run in your browser; search terms are not sent to Flightable or separately stored. Viewing or downloading a PDF retrieves a file from the web server and may generate ordinary access logs. This guide feature does not collect passport numbers, declaration entries or personal travel documents. Downloaded PDFs remain on the device or storage you choose.

13

Contact, remedies and policy history

오씨엠에스컴퍼니 (OcmS Company Ltd.)
Business registration number: 858-08-03227
OcmS Information Protection Team / Privacy Administrator
Flightable_Support@ocms.tools

You may ask the same contact to review a decision. For external privacy-rights assistance in Korea, visit the Privacy Portal.

When the policy changes, we publish the changes and effective date and follow any applicable separate consent/notice requirements. Previous policies remain available in the history.

View all policy versions →

Effective: 14 November 2026 · Version: 2.1
Korean and English are provided. Translation differences do not limit rights under applicable law.