Privacy Policy

1. Information We Collect

On iOS, the exploration map converts location into H3 grid cells and stores them only on your device and in your own private iCloud storage (Apple). Raw exploration locations and explored cells are not sent to Fitrip servers. The iCloud backup restores your exploration map on a new device or after reinstalling the app with the same Apple ID; Fitrip cannot access it, and Apple's iCloud terms and privacy policy apply. If you are not signed in to iCloud, the map stays on the device only. You can turn off exploration recording or erase it at any time, which also deletes the iCloud backup.

When you search for nearby places in Korea on iOS, your precise current location is sent to Fitrip and Kakao Corp. only after separate consent. Fitrip uses the exact coordinates and Kakao Local API place results only while processing the request and does not store them in server logs, databases, caches, or backups. If you save a Kakao result or add it to an itinerary, Fitrip stores only the Kakao place ID and detail URL that may be retained as provider references. If Apple MapKit or Google Places confirms the same place, Fitrip may also retain only the place ID for live re-fetching. Provider-supplied names, addresses, phone numbers, coordinates, and ratings are not stored permanently. Saving still completes when neither Apple nor Google confirms the place; the app then presents a generic place card and the Kakao detail link. Searches outside Korea use Apple MapKit. Android nearby-itinerary distance calculations continue to occur only on the device.

On the web, nearby place search also sends the precise current location provided by your browser to Kakao Corp. through Fitrip servers only after separate consent. The website does not distinguish between locations in Korea and abroad and searches through the Kakao Local API; as on iOS, exact coordinates and Kakao place results are used only while processing the request and are not stored. Your choice is saved in your account settings. You can withdraw it at any time with Withdraw location consent on the Saved Places page, and the related usage and disclosure records are then deleted without delay. When you save a place or add it to a place list or itinerary on the web, provider-supplied addresses, coordinates, and ratings are not stored; only the place ID and detail URL are kept as provider references, and names are not stored for Kakao places.

When you sign in on the iOS app, the photos, vouchers, booking documents, and cover photo in your trips are stored in your account trip library so they appear on your other devices. Files are end-to-end encrypted (AES-256) on your device before upload. The decryption key exists only in your iCloud Keychain, so no one, including Fitrip, can view the file contents. Fitrip's servers encrypt the received ciphertext once more for storage. A recovery key is issued when you first upload a file; if you lose both your keychain and the recovery key, Fitrip cannot recover the files. Fitrip stores only a key identifier and a copy of the key locked with your recovery key, which Fitrip cannot unlock without the recovery key. Without signing in, these files stay on your device. Travel companions on a shared trip do not receive your photos, vouchers, or notes. On Android, photos and documents you add stay in app-private storage and are not uploaded automatically.

The website, the iOS app, and any AI tool you connect all use the same account trip library. Trips created on the web appear in the app, and trips created or edited in the app or by an AI tool appear on the web. Trips created on the web without signing in are stored as before, only in your browser and in guest trip storage.

Apple or Google handles payment card details. Fitrip does not receive your card number. The original installation UUID used for limited analytics stays on your device. The server uses the hash to validate the event format and stores daily aggregate counts.

Fitrip is intended for people aged 14 or older. We do not knowingly collect personal information from children under 14. Please contact us if you believe a child has provided information to Fitrip.

2. How We Use Information

• Authenticate users and maintain account sessions.
• Generate, save, sync, and manage travel plans, including notes, checklists, expenses, vouchers, and photos, across the web and your devices.
• Let AI tools that you connect view, edit, or create your trips when you ask them to (AI connections).
• Find nearby places from your current location.
• Build exploration-map and trip-recap statistics on your device.
• Verify purchases, restore subscriptions, and prevent fraud.
• Review reports about inaccurate, unsafe, or inappropriate AI output.
• Protect the website and apps from automated abuse.
• Respond to support requests and diagnose errors.
• Measure a small set of product events through daily aggregates.
• Send product updates only when you have chosen to receive them.

You can withdraw marketing consent at any time. Refusing marketing does not limit access to the service.

3. Retention

• Account data: retained until account deletion unless law requires a longer period.
• Guest travel data: deleted no later than 30 days after creation.
• Account trip library: kept until you delete the trip or your account. When you delete a trip, its contents and attached files are cleared immediately. A deletion marker (trip ID and deletion time) is kept for 90 days so your other devices learn about the deletion, then removed permanently. Deleted files are erased from disk during cleanup within one day. Only the 30 most recent edit versions are kept for each trip, and they are removed when the trip or account is deleted. Attached files are removed immediately when you delete your account.
• AI connections: tokens stop working immediately when you disconnect, delete, or let them expire, and the records are removed 30 days later. Authorization requests are valid for 10 minutes and authorization codes for 2 minutes. Hashes of used authorization codes are kept for 31 days to detect code reuse. Everything is removed immediately when you delete your account.
• Marketing email: retained until you unsubscribe.
• Subscription records: retained until account deletion or for a legally required period.
• AI output reports: retained for 90 days and then removed during scheduled cleanup.
• Analytics: installation hashes are not retained. Only daily aggregate counts remain.
• Nearby-search location: exact coordinates and Kakao place results are discarded after the request and are not stored in logs, databases, caches, or backups. Legally required location usage and disclosure records do not contain coordinates or place results and are retained for six calendar months from creation. They are deleted without delay if you withdraw location consent or delete your account.
• Provider references for saved nearby places: Kakao place IDs and detail URLs, and Apple or Google place IDs, remain until you delete the saved place or itinerary entry, or delete your account. Provider-supplied names, addresses, phone numbers, coordinates, and ratings are not retained permanently.

The following processors support Fitrip operations:

5. International Data Transfers

Core account and trip data is stored in the Supabase Seoul region. When you use an AI feature (recommendations, itinerary generation, checklist suggestions, day regeneration, route-time repair, conversational editing, or parsing pasted or imported itinerary text), the travel information you enter, the existing itinerary sent with the request (for checklist suggestions, the place names in it), your regeneration and editing requests, and any itinerary text you paste or import are transferred to OpenAI, L.L.C. or Google LLC in the United States according to the model configured for that feature. OpenAI API requests are not used to train OpenAI models. Abuse-monitoring logs may be retained for up to 30 days unless a longer period is legally required. Gemini API request processing and retention depend on the service tier and project logging settings; limited abuse-monitoring logs may be retained.

Google also processes map search terms or location information, Google Play purchase identifiers, and Android integrity tokens in the United States or other countries only when you use the relevant map, payment-verification, or integrity feature. Apple processes destination coordinates, App Store transaction identifiers, and DeviceCheck tokens with a per-device monthly free-usage count in the United States for weather, maps, subscription checks, and per-device free usage checks. City search terms are sent to OpenMeteo GmbH (Switzerland): directly from your browser, together with your IP address, for city search on the web, and through our server for other city searches and weather lookups, along with destination coordinates. When web city search gets no result from Open-Meteo, your browser sends the search term to the OpenStreetMap Foundation (United Kingdom). Flight numbers and flight dates you enter, and airport codes if you provide them, are sent from our server to Apilayer Data Products GmbH (Austria) for flight lookup. Cloudflare processes IP addresses, browser information, and security tokens for content delivery and security.

If you connect an AI tool whose provider is outside Korea, information is sent to that provider over the network whenever the tool makes a request, based on the consent described in section 4.

We use providers subject to contractual and technical safeguards. You can stop future transfers by avoiding the relevant feature or deleting your account. Some features will no longer work if the required transfer is not made.