LeafTime operates the TripNaru website and app. This policy explains feature-specific processing; describing an unreleased product does not itself collect its data. When an account is deleted, personal information linked to that account is deleted or separately retained where law requires it, while technical or cost records that do not need to identify the user may remain for service operation and quality review. The Korean text is the reference version, without excluding mandatory rights under applicable law.
1. What we process and why
What we process depends on the feature and the information you provide. Information needed to operate the service is distinguished from optional inputs and device permissions. Do not submit identity documents or full payment credentials unrelated to your request.
| Category | Data | Purpose |
|---|---|---|
| Account | Sign-in provider identifiers, language preferences, anonymous-use identifiers and account-linking data. Authentication email and profile data are managed through AWS Cognito and the authentication flow; names and contact details supplied for a booking or enquiry are addressed separately below. | Sign-in, keeping your account, continuing a trip across devices |
| Trip planning | Destination, dates, party, budget, interests, mobility needs such as walking amount, wheelchair use and stroller use, dietary restrictions and allergies you choose to enter (which may be health information), imported flight and hotel bookings, generated itineraries | Building itineraries, recommending and excluding places and restaurants |
| AI Guide | Voice audio of voice conversations, conversation text, camera images you send, trip memories you ask the guide to keep | Generating guidance and translation responses |
| Camera translation and flight import | Text recognized on your device, image crops you ask us to re-read, flight ticket images, files or text | Translation, extracting flight details |
| Location | Your current location while a feature you started is in use (route guidance, camera guide, where am I, trip memories) | Route and distance calculation (Kakao Map and TravelTime, section 4), nearby guidance. Route guidance and trip memories keep receiving location while the app is in the background only if you allow background location, and stop when you turn the feature off. |
| Community | Nickname (if you do not set one, "Traveler" plus six digits is assigned), reviews, ratings, comments, replies and photos, likes, share records and share links, reports (reason and up to 500 characters of detail), block list, guideline acceptance record (version, time, language), sanction records | Providing the community, handling reports and restrictions |
| Notifications | Device push token (stored encrypted), in-app notification history | Reply, moderation result and reservation updates |
| Restaurant reservation assist | Booker name (passport Latin spelling, plus kana or Hangul where the restaurant needs it), phone number, email (optional), party size, requested date and time, special requests | Requesting the reservation and reporting the result |
| Payments and points | Payment results and receipts from payment providers and app stores, refund records, points earned and spent. We never receive card numbers or other payment instrument details. | Charging and refunds, operating points, statutory record keeping |
| Hotel booking | Booker and guest names and contact details (stored encrypted), booking details | Fulfilling and confirming the booking |
| Launch notifications | Phone number or email address, the language and page you signed up from, arrival airport (if you signed up from the destination page), nickname and message (optional) | Managing the request and sending launch news |
| Enquiries and rights requests | Sender email, message and attachments, handling records and the minimum data needed to verify a request | Support, refunds, disputes and privacy requests. All email is not automatically erased immediately after a reply; section 5 explains retention. |
| Ads (when enabled in Free trip restaurant recommendations) | IP address and approximate region, device and advertising identifiers subject to device permissions and privacy choices, ad interactions, diagnostics and consent choices processed by Google. TripNaru records trip-linked ad sessions, slots, times, impressions, clicks and SDK-reported revenue amounts, currency and precision. | Ad delivery, privacy choices, ad performance and estimated revenue measurement, fraud prevention |
| Automatically generated information | Access time, IP address, request path, browser, device, operating system and app version, errors and service-use records | Delivering and securing the service and diagnosing errors. Cookies and device storage are addressed in section 13. |
2. What is public
Nicknames and reviews, ratings, comments and replies you publish are visible according to the feature’s audience. Viewing photos can depend on app or account access. Creating a share link can make information readable by anyone holding that link; check its contents before sharing.
Share landing pages (tripnaru.com/s/…) can display the place name, rating, review summary and nickname. They carry a search-exclusion directive and do not display uploaded review photos. A noindex directive is not authentication or a guarantee of secrecy. Hiding or deleting a post ends normal public display on our service, but does not retrieve copies held by others.
3. AI processing
We distinguish editing public place and event information from processing a traveller’s personal trip or conversations. A request containing personal data is processed for the relevant feature; calling a dataset a public catalogue does not make private conversations public data.
AI Guide: feature-specific audio, text, images or recognized text and necessary trip context may be sent to Google Gemini or OpenAI. The configured TypeSafe route classifies request intent and interprets itinerary-related requests. Audio is transmitted through the device or TripNaru’s voice-processing route.
Camera translation, menu interpretation and flight import send selected images, crops, recognized text and flight documents or text to OpenAI. Mask unnecessary names, booking numbers and other people’s faces where possible.
Community checks send comment and review text to OpenAI moderation. Photos, nicknames and account identifiers are not added as separate fields, but personal data typed into the text can still be included. We record the applicable categories and actions.
Turning off request storage is not immediate deletion of every record. Our OpenAI Responses requests set store:false, while safety logs and caches have separate rules. Standard abuse logs are retained for up to 30 days by default, with legal or safety exceptions; moderation and other endpoints have their own rules. See OpenAI API data controls.
Google Gemini can apply different data-handling terms depending on the API type and account configuration. TripNaru sends only the data needed for the feature it actually uses under the applicable service terms. See the current Gemini API terms.
TypeSafe and other external AI processors handle data under their own privacy notices and service terms. TripNaru distinguishes provider-side processing from technical records it keeps itself. See the current TypeSafe privacy policy.
4. Processors and international transfers
TripNaru uses the server, AI, payment, notification, routing and booking providers listed below. When you use the relevant feature, the information needed for that feature may be sent to the provider over an encrypted connection. The tables distinguish service processors from recipients fulfilling an external booking you requested. If you do not want a particular external processing step, you can choose not to use that feature; only the feature that requires the data may then be limited.
| Recipient (country) | Data | Purpose | Retention | Privacy contact |
|---|---|---|---|---|
| Amazon Web Services, Inc. (servers in Seoul, Republic of Korea) | All data in this policy | Servers, database and authentication | Until the contract ends or the retention period in this policy ends | aws-korea-privacy@amazon.com |
| OpenAI OpCo, LLC (United States) | Conversation and trip context, menu images and recognized text, flight images and text, guide search questions and community comment/review text | Guide responses, menu interpretation, translation, flight extraction, search and moderation | Endpoint-specific safety logs and caches separate from request-storage settings. Standard abuse logs: up to 30 days by default, subject to legal or safety exceptions. See section 3 and official API controls. | privacy@openai.com |
| Google LLC — AdMob and User Messaging Platform (United States) | Ad SDK IP address, device and advertising identifiers, ad interactions, diagnostics and privacy choices | Ad delivery, measurement, fraud prevention and privacy choice management | Under the Google Privacy Policy | Google privacy contact |
| Google — Gemini API (United States and countries hosting provider/subprocessor facilities) | AI Guide voice and text conversations, photos you send, trip details needed for a response | Generating AI Guide responses | Temporary paid-API abuse-prevention and legal records under provider terms. Unpaid services have different conditions; see section 3. | Google privacy contact |
| TypeSafe AI, Inc. (United States) | AI Guide request text and generated responses | Intent classification, response checks | As reasonably necessary for service and legitimate business purposes, then deletion or non-identifying processing, subject to its policy and legal exceptions | TypeSafe privacy · privacy@typesafe.ai |
| TravelTime Technologies Ltd — TravelTime API (United Kingdom) | When you get route guidance to a destination in Japan: your current location (origin) and destination coordinates and travel mode; coordinates between places and your lodging in the itinerary | Route and travel-time calculation in Japan | Applicable provider service, security and statutory retention rules. Immediate erasure of all records after delivery or response is not guaranteed. | michelle.gee@traveltime.com (Data Protection Officer) |
| Kakao Corp. — Kakao Map API (Republic of Korea) | When you get route guidance to a destination in Korea: your current location (origin) and destination coordinates and the destination search text; coordinates between places and your lodging in the itinerary | Route and travel-time calculation in Korea, place search | Applicable provider service, security and statutory retention rules. Immediate erasure of all records after delivery or response is not guaranteed. | Kakao Customer Center, +82-1577-3754 |
| Functional Software, Inc. — Sentry (United States) | On errors: device and app version, error details and request path (payment, reservation and community text excluded) | Diagnosing failures | Applicable provider service, security and statutory retention rules. Immediate erasure of all records after delivery or response is not guaranteed. | compliance@sentry.io |
| Google LLC — Firebase Cloud Messaging; Apple Inc. — APNs (United States) | Push token, notification text | Delivering notifications | Applicable provider service, security and statutory retention rules. Immediate erasure of all records after delivery or response is not guaranteed. | Google privacy contact · Apple privacy contact |
| Toss Payments Co., Ltd. (Republic of Korea) | Order number, amount, pseudonymous customer key (no name or contact details). You enter payment details directly with Toss Payments. | Processing payments in Korea | As required by law | privacy@tosspayments.com, +82-1544-7772 |
| Apple Inc., Google LLC — app store billing (United States) | In-app purchase results and receipts | Verifying in-app payments | As required by law | Apple privacy contact · Google privacy contact |
To fulfil bookings you request, we also provide personal data to third parties as follows.
| Recipient (country) | Data | Purpose | Recipient's retention | Privacy contact |
|---|---|---|---|---|
| The restaurant you asked us to book (Republic of Korea or Japan) | Booker name, phone number, party size, date and time, special requests (email is not shared) | Restaurant reservation | Under the restaurant's own policy | The restaurant (shown on the reservation screen) |
| Nuitée Travel Limited — LiteAPI (Ireland) and the hotel | Booker and guest names and contact details, booking details | Fulfilling the hotel booking | Under each company's own policy | info@nuitee.com |
5. Retention and deletion
- Account, trip plans, location history, AI Guide records, community data and push tokens: until you delete your account. We delete them within 30 days of the request as set out in the table in section 6.
- Ad sessions, impressions, clicks and SDK-reported revenue held by TripNaru: deleted within 30 days of an account deletion request. Unsent ad records on this device are also removed. Data processed directly by Google follows the Google Privacy Policy for retention and deletion.
- Records of contracts and withdrawals of offers, and records of payments and supply of goods or services: 5 years. Records of consumer complaints and dispute handling: 3 years (Korean Act on the Consumer Protection in Electronic Commerce, Article 6, and its Enforcement Decree, Article 6). These records are used only for that statutory purpose. They survive account deletion and are linked only through an internal identifier, without your name, email or phone number. Hotel booking records are the exception: the booker and guest names and contact details used to fulfil the booking are kept with them, encrypted.
- Technical records used for service operation, cost reconciliation, error investigation and quality checks can include portions of AI requests and responses, image-bearing requests, routing records and external product lookup results. Account deletion removes the direct account link. Technical or cost records that do not identify the user may be retained, while any retained content that still contains personal information remains subject to this policy and your privacy rights.
- Community moderation and sanction records: kept to handle sanctions and appeals. When you delete a comment we erase its text and leave only a "deleted comment" placeholder; a copy of content that was under review stays in the moderation record. When you delete your account we erase that copy, but the moderation outcome (categories that applied and actions taken), sanction records, guideline acceptance records and share records remain linked to the internal identifier. Reports you made are unlinked from your account and keep only the reason and detail.
- Launch notification requests: until you withdraw or we have sent the launch news. They are not linked to an app account, so deleting your account in the app does not remove them; email hello@tripnaru.com and we will delete them.
- Support and privacy requests: retained while needed to handle the request; records qualifying as consumer complaints or disputes follow the statutory three-year period. Unnecessary attachments or verification material not subject to statutory retention are deleted when their purpose ends.
Data whose retention period has ended is deleted in a way that cannot be recovered. Data kept under statutory obligations is stored separately from other data.
If a retained record contains personal information, you may request access, deletion or restriction at hello@tripnaru.com. Payment and dispute records that must be retained by law are kept separately for the required period; technical records that have been processed so they no longer identify a person are distinguished from personal information scheduled for deletion.
6. Deleting your account
In the app’s account settings, review what will be deleted and retained, verify your identity and request deletion. If the app is unavailable or its automatic flow is blocked, send the same request to hello@tripnaru.com.
- Immediately: you are signed out on all devices, your nickname and public posts (reviews, comments, photos) are no longer shown, and share links you created stop opening. Push tokens are deleted at this point.
- Within 30 days: we delete everything in the "Deleted" column below, and delete your sign-in account and the email and other profile data held by our authentication service (AWS Cognito).
- Any remaining points expire (Terms, points). The app shows the points that will expire before you confirm.
- An active restaurant request, pending refund, unused reservation-pack balance or pending pack refund can block the app’s automatic deletion flow. Support can receive a combined cancellation, unused-balance refund and account-deletion request. You do not have to spend a balance to exercise your privacy rights.
| Area | Deleted | Kept, and why |
|---|---|---|
| Account | Email, name and other profile data, your sign-in account at the authentication service, anonymous account sessions | The internal account identifier and a pseudonymous sign-in identifier — to block access through the deleted account and to link the records below |
| Trip planning | Destination, dates, party, budget, interests, mobility needs, dietary restriction and allergy answers, imported flight and hotel details, saved candidates, itinerary change requests, preparation tasks and reminders, recommendation results, places, coordinates, times, lodging and booking details in the itinerary | An emptied skeleton of the trip and itinerary records (identifiers, status, day, order and type) — the paid route results and payment records below are attached to it |
| Location | Location samples and movement records from trip memories, the lodging location used for route guidance | Raw requests, responses and results of paid route calculations (including origin and destination coordinates, routes and times) — section 5 |
| AI Guide | Conversation sessions, trip memories, tasks, itinerary change proposals | Raw requests and responses of paid AI calls (including conversation text) — section 5 |
| Activities | Recommendation and candidate lists built for this trip | Raw paid product lookups and their results (including the dates and party size looked up), records of affiliate checkout links issued |
| Community | Nickname (replaced with a deleted marker), review, comment and reply text and photos, likes, block list, notifications, copies of your posts in moderation records | Moderation outcomes, sanction records, guideline acceptance records, share records, the reason and detail of reports you made (unlinked from your account) — for sanctions, appeals and evidence |
| Restaurant reservation assist | Booker name, phone number, email and special requests, questions, answers and notes exchanged with the restaurant, review photos, unapproved reviews and the text of approved reviews, unsent notifications | Request, payment and refund records with contact details removed, and records of notifications already sent — statutory periods in section 5 |
| Payments and points | Remaining points (expired) | Payment, receipt and refund records, trip pass purchase records, points earned, spent and expired — statutory periods in section 5 |
| Hotel booking | Hotel comparison requests that did not lead to a payment | Hotel checkout sessions and booking attempts and the hotel choice they rely on (booker and guest names and contact details stored encrypted) — statutory periods in section 5 |
After account deletion, payment, refund and dispute records required by law and technical records needed to operate the service can remain. Personal information within retained records is managed for the stated purpose and period, while records that do not need to identify a person are managed separately from account information. See section 5 for retention details.
If you cannot use the app, email hello@tripnaru.com; after verifying your identity we follow the same process. You can disconnect TripNaru from the Kakao or Naver account you signed in with in that service's connected-apps settings. Data managed directly by other services (for example your Kakao, Naver or YouTube account) must be deleted with that service.
7. Affiliate links and ads
When ads are enabled, Google AdMob ads appear in some slots in Free trip restaurant recommendations and are labelled “Ad”. Trips with an active Trip Pass or Route Pass do not show ads. We do not add your itinerary, interests, precise GPS location, name, email or phone number to ad requests. The SDK can process an approximate region from your IP address.
Before requesting ads, we check Google privacy choices and display a consent message where needed. We request only non-personalized ads, but identifiers may still be used for frequency limits, aggregate reporting and fraud prevention. Where Google requires a privacy choices entry point, “Ad privacy settings” in restaurant recommendations opens the Google form again. You can also change advertising identifier and tracking permissions in your device settings.
Affiliate links can contain identifiers for the screen, city, partner, placement and booking attribution. We do not put names or contact details directly into these links. If an identifier can be combined with other records to identify a person, we treat it as personal information.
Processing on the partner site is governed by that partner's privacy policy. Partners may use their own cookies to attribute a booking to our link. Affiliate links do not pass your name, contact or payment details to partners.
8. YouTube Data API
TripNaru uses the YouTube Data API to find public videos related to destinations, restaurants and events. It processes public search terms such as place names and public video metadata such as ID, title, channel name and publish date. We do not request or collect your YouTube account, OAuth tokens, watch history or private data, and we do not upload or modify videos.
When you view a YouTube thumbnail or open the official player, your browser or app may communicate directly with YouTube or Google, which may process technical information under their own policies. TripNaru does not build personal viewing histories or per-video engagement profiles.
Use and storage of information received through the YouTube API follow the YouTube API Services Terms of Service and the Google Privacy Policy.
9. Security measures
- All transmission is encrypted with TLS. Push tokens and hotel guest details are stored with envelope encryption using keys from a key management service (AWS KMS).
- Access to operations tools is separated by role, and operator actions are logged.
- Error tracking and logs are configured to exclude booker details, payment data and community text.
10. Your rights
Request access, correction, deletion, restriction or withdrawal of consent at hello@tripnaru.com. An authorized representative may also apply. We use the minimum information needed to verify identity and follow the statutory deadline for the particular right. We explain any lawful delay or restriction and how to challenge it, rather than applying a universal 24-hour or ten-day promise.
TripNaru is not directed at children under 14. If we learn that a child’s information requiring guardian consent was collected without the required process, we take appropriate action including deletion. When entering a companion’s personal or health-related information, provide only what is needed for the trip.
For advice or dispute mediation about privacy, you may contact the Korean Personal Information Infringement Report Center (118, privacy.kisa.or.kr) or the Personal Information Dispute Mediation Committee (+82-1833-6972, www.kopico.go.kr).
11. Privacy officer
| Item | Details |
|---|---|
| Operator | LeafTime (리프타임) · Representative Myungseong Kim · Business registration 517-19-02380 |
| Privacy officer | Myungseong Kim (Representative) |
| Contact | hello@tripnaru.com |
| Governing law | Personal Information Protection Act of the Republic of Korea |
| Phone | +82-70-2948-4933 |
12. Legal grounds and choices
Data necessary for accounts and requested itinerary, booking or payment services is processed on the applicable contractual basis; statutory transaction records are processed under legal obligations. Optional launch notices or marketing and disclosures require appropriate consent, notice or another valid basis for the particular processing.
Dietary restrictions and allergies can include health-related information. Information you choose to provide is used to reflect foods or ingredients to avoid and to adjust itinerary or restaurant suggestions. You can leave optional information unprovided and still use features that do not require it.
For features using providers outside Korea, section 4 lists the relevant provider, information and purpose. Only the information needed for the feature is sent, and if you do not use that feature, that feature-specific transfer does not occur.
Where a fully automated decision using personal data significantly affects your rights or obligations and statutory conditions apply, you may request an explanation or review. We assess the applicable conditions and respond under the relevant law.
13. Cookies, browser storage and device permissions
Cookies and browser/device storage may support sign-in and security, language settings and an unfinished trip or order. You can clear or block cookies in browser settings, but sign-in or state recovery may be limited. Signing out or uninstalling the app is separate from deleting server-side account data.
Location, camera, photos, microphone and notification permissions are requested for the features that need them and can be changed in device settings. Refusing a permission can limit that feature without necessarily blocking public information. Background location is limited to the enabled feature and permission scope.
External ads and video services may process technical data. Advertising privacy choices and device tracking settings are addressed in section 7. New analytics or advertising processing requires checking the data scope and any necessary consent and updating this policy.
14. Policy changes and enquiries
We explain material changes to purposes, data, recipients, transfers or retention and when they apply. A policy edit does not itself begin processing that requires separate consent. You can request an earlier version of this policy through our contact channel. Send questions, corrections or objections to hello@tripnaru.com or use Contact.