Lunara Inc. (the "Operator"), which operates Lunara (the "Service"), explains below the information processed by the Service and how it is used.
1. Information we process
Some features are available without an account. Login, synchronization, community features, and AI conversation history use an account and server storage.
| Category | Information processed | Storage and processing location |
|---|---|---|
| Account and authentication | Social login provider user identifier, email, name and profile image supplied by the provider, authentication sessions and tokens | Supabase Auth, user device |
| Age and consent | Birth year, consent text version, consent timestamp | Supabase |
| Profile and preferences | Username, display name, profile image, bio, interests, travel pace, transportation preferences, dietary and avoidance information, and other preferences entered by the user | Supabase and user device |
| Travel plans | Origin and destination, dates, party size, itinerary, packing list, saved places, app settings; for an itinerary imported from a community post, the source post information (post title and identifier, author display name and identifier) (Amended 2026-11-04) | Primarily the user device. Necessary information may be sent to the Operator's backend and external services when AI, search, or synchronization features are used. Trips synced after logging in are stored in Supabase and are also synced to the devices of users who edit the trip together (Amended 2026-11-04) |
| Community | Posts, comments, photos, videos, tags, cities, likes, follows, saves, meetup information and participation, blocking information | Supabase, Cloudflare R2. Public posts, profiles, reactions, and meetup participation may be visible to other users |
| Operator AI Account activity | Displayed information an Operator AI Account reads on screen while using the Service, such as public posts, comments and usernames; the public usernames of users who have exchanged comments with an Operator AI Account and summaries of those conversations; activity memories compiled from them; screenshots (excluding login and verification screens); and observation records of screen navigation, errors and loading | Operator-managed operating device, Anthropic. Text information is sent to Anthropic after email addresses, phone numbers, verification codes and tokens in formats the app recognizes are masked. At the feature-check step, one screenshot of the Operator AI Account's own screen (such as its own profile, or a trip screen the app judges to be its own from in-app navigation) may also be sent. Before sending, the text information on that screen is checked, and no screenshot is sent if markers of other users that the app recognizes, or an email address, phone number, verification code or token in a format it recognizes, are detected; a screenshot that is sent is not itself masked. If a request fails or its response cannot be used and the same request is sent again, the same screenshot is sent with it, so a single screenshot may be sent up to three times in total, including the first (Newly inserted 2026-11-04) |
| Messages and reports | DM participants, messages and read timestamps; reported subject, reason, details, and processing status | Supabase. DMs are restricted to participants; reports to the reporter and authorized operations personnel |
| Notifications | Device push token, device type (iOS, Android, web), registration and revocation timestamps, notification delivery queue records (message identifier, conversation identifier, recipient, sender, timestamp) | Supabase, Cloudflare Workers, the Expo push service, and Apple and Google push servers. Notification bodies do not contain message content; only a generic phrase such as “You have a new message” is sent |
| Aurora personalization (AI features) | User questions, travel inputs, device preferences included in requests, server-stored AI memory and saved history, AI responses, conversation identifiers and history, personalization summaries and feedback, generation counts | Cloudflare Workers·AI Gateway, Anthropic, Supabase |
| Payments and subscriptions | Store type, product ID, transaction and original transaction IDs, event ID and type, purchase, expiration and refund timestamps, purchase and subscription status, entitlement tier, one-time entitlement grant, use and revocation records, and the user ID that links a transaction to the account (stored in the payment ledger and, for App Store purchases, also placed in the purchase request sent to the store) | App Store and Google Play, Cloudflare Workers, Supabase. Raw notification data received from the stores is stored with the payment ledger through the Worker and is deleted within seven days once the minimum fields needed to confirm payment status have been copied. The Operator does not directly collect or store card numbers or other store payment-method information |
| Media uploads | Selected image and video files, file format and size, object keys linked to the uploading user | Cloudflare Workers, Cloudflare R2, Amazon Web Services (automated harmful-content assessment). Media attached to posts may be served through public URLs |
| Feature queries | Place and address search terms, flight numbers and dates, travel city coordinates, route origin, destination and departure time | Google, Kakao, Mapbox, Apple or the device operating-system provider, AeroDataBox and RapidAPI, Open-Meteo, Operator backend |
| Visit verification | Current location coordinates and accuracy checked at the destination when the user enables visit verification, together with the trip ID, destination and dates | The current location is processed transiently in a Cloudflare Worker only during the distance and accuracy check and is not stored. Supabase stores only the verification result without coordinates, the rule version and the trip snapshot |
| Content queries | Remote image URLs displayed in the app, YouTube video identifiers, thumbnails and playback requests, network and device information such as IP addresses during connections | Unsplash, Google and YouTube. Home-screen YouTube thumbnails load when the screen opens; videos play when the user selects them |
| Booking links and affiliate measurement | Target URL, platform, category, screen and destination label, link token, click identifier, timestamp, partner, whether affiliate parameters were applied, and conversion postback click_id, status, transaction identifier, settlement amount, currency and timestamp | Cloudflare Workers, KV and operational logs; booking and map providers selected by the user. Link records do not contain a user ID |
| Error diagnostics | Error type, message and stack, app version, device and operating-system information, diagnostic context explicitly attached by the Operator such as error codes and feature areas, network information during connections | Sentry. The Operator disables automatic transmission of default personal information, but cannot guarantee that error messages or stacks contain no user input |
| Security and abuse prevention | IP address during API requests, request timestamp and path, authentication and usage-limit results | Cloudflare Workers, Rate Limiting and operational logs. Used to prevent abnormal requests and automated abuse and maintain service stability |
With location permission, the device's current location is used for the map's 'My location', visit verification you select, nearby recommendations and movement alerts during a trip, and Apple Watch navigation. Trip recommendations and alerts transiently use only the latest approximate location without storing it; with background location permission, this also works when the app is closed. Apple Watch navigation starts with location permission while using the app and sends the precise current location and destination coordinates directly from the app to Mapbox over HTTPS to find the route. During visit verification, the current location coordinates and accuracy are sent to a Cloudflare Worker over HTTPS and used transiently only to judge the distance to the destination and the accuracy; the coordinates themselves are not stored in the Worker, the Supabase database or app storage. Places, addresses and coordinates you enter in an itinerary may, however, be sent to external services to provide weather, search and route features.
Photos and videos are uploaded only when you select them yourself. The Operator re-encodes images before upload and stops the upload if this fails. The Operator assesses images and videos for harmful content on the server and removes MP4 location metadata. Locations displayed within the video itself are outside this removal scope. The Operator uses private-media references.
2. Purposes of processing
- Creating accounts, login, maintaining sessions, and checking age and consent status
- Providing travel planning, packing lists, search, weather, transportation and AI recommendations
- Providing community features including profiles, posts, comments, meetups, DMs, saves and follows
- Receiving reports, preventing abuse, reviewing content and protecting users
- Managing usage limits and service stability, and diagnosing errors
- Product usage analytics only with the user's separate permission
- Connecting external booking and map links, and measuring clicks, affiliate results and conversions for booking links that use the tracking redirector
- Verifying purchase and subscription status, granting and restoring entitlements, reflecting refunds and cancellations, and handling payment inquiries
- Running Operator AI Accounts, limited to the early operation of the Service, and through them improving the user experience, checking the performance of the Service and identifying errors and inconveniences (Newly inserted 2026-11-04)
3. Public information and access
- Usernames, display names, profile images, bios, public posts, comments, photos, videos, likes, follows and meetup participation may be visible to other users.
- The Operator runs Operator AI Accounts (Terms of Service, Article 2, item 6). An Operator AI Account is not a person; it may view the public information above on the same screens as other users, write comments, and like or follow. The information processed in doing so, its retention period and its cross-border transfer are described in Sections 1, 4 and 5. (Newly inserted 2026-11-04)
- Access policies restrict DM text and read status to participants in that conversation.
- Travel preferences, birth year, consent status, AI conversations and personalization information are restricted to the user and servers with the permissions required to provide the Service.
- When a user invites another user to edit a trip together and the invitation is accepted, the users editing together can view and edit the trip's information, such as its itinerary, dates and destination, its notes and, for an itinerary imported from a community post, the source post information (the post title and author display name, and the post identifier and author identifier, which are not shown on screen), and this information is also stored on their devices. Some information, such as packing lists, bookings and photos, is not shared. (Newly inserted 2026-11-04)
- Reports are restricted to the reporter and authorized operations personnel. After account deletion, they may be retained for safety measures and dispute handling with the reporter's identifier removed.
4. Retention and use periods
| Information | Retention basis |
|---|---|
| On-device trips and settings | Until the user deletes them in the app or uninstalls the app. Copies may remain under the operating system's backup and restore policies |
| Source post information of imported itineraries | Because it is a copy saved with the trip at the time of import, it remains with the trip for as long as the trip remains, even if the source post is deleted or its author deletes their account. The same applies to copies stored on the devices of users editing the trip together (Newly inserted 2026-11-04) |
| Account, profile, preferences, community, DMs and AI records | Until the user deletes the relevant item or account. When an account deletion request succeeds, the Operator cascade-deletes rows associated with the account in Supabase. However, comments, replies and likes a user leaves on an Operator AI Account's posts and the user's records of saving those posts, as well as replies and likes the user leaves on an Operator AI Account's comments (including comments on the user's own posts), are deleted when the Operator AI Account is retired and deleted. (Amended 2026-11-04) |
| Reports | The reporter's identifier is removed when the account is deleted; report details are retained for 3 years for safety measures and dispute handling. However, reports concerning an Operator AI Account or its posts, comments or messages, including those filed by other users, are deleted when that account is retired and deleted (Terms of Service, Article 6-2, paragraph 8). (Amended 2026-11-04) |
| Notification tokens and delivery records | Until the user logs out, turns off notification permission or deletes the account. Delivery queue records become subject to cleanup once the notification is delivered or retries end, and are deleted together with the rows linked to the account when the account is deleted |
| Public media | Until the deletion job associated with the post or account deletion request completes for R2 objects and caches. The Operator deletes media through the deletion queue and retry jobs and requests cache purging. |
| Worker and AI Gateway logs | The Operator's policy is 30 days for general operational logs, and 1 year for personal-information-system operator access records and security-incident investigation records. Request and response payload storage in AI Gateway is kept off, so no copy of the payload remains on the Operator's side. Neither Cloudflare's public policy nor the contract (Cloudflare Customer DPA v6.4) specifies a retention period for its own operational logs (as of 2026-09-22). |
| Access records constituting communication confirmation data | Under Article 41 of the Enforcement Decree of Korea's Protection of Communications Secrets Act, the minimum records within that scope (IP address, user identifier, access time) are kept separately from other information for 3 months and then destroyed; they are not retained beyond that period. |
| Records confirming the collection, use and provision of location information | The Operator automatically records location-use receipts when the server receives the device's current location for Aurora location-based guidance or visit verification. The records contain the user identifier, purpose of use and server recording time; they do not include location coordinates such as latitude or longitude. Records are retained from creation for 6 months separately from account deletion and then automatically destroyed. Access and notification requests are accepted through the existing privacy inquiry email address. |
| Sentry error events | The Operator's policy is 30 days for error events, transactions and spans alike, and the organization's retention setting is aligned to that value. The Operator's organization (lunara-inc) is on the Developer plan, whose event retention period is 30 days (as of 2026-09-22). Provider backups are deleted within 90 days of creation. |
| Anthropic API inputs and outputs | Anthropic retention policy provides for deletion following receipt or generation within 30 days (as of 2026-09-06). If flagged for usage-policy violations, inputs and outputs may be retained for up to 2 years and safety classifier scores for up to 7 years. Legal obligations, separate agreements and long-term retention services may create exceptions. The Operator's organization has no Zero Data Retention agreement in place, so this 30-day standard applies as stated (as of 2026-09-22). |
| Raw data received for payment verification | After the minimum items needed to confirm payment status are extracted, the raw data is deleted within 7 days. The retention period for the transferred transaction records follows the statutory retention item below |
| Copies remaining in backups and caches | After deletion from active data, backup copies expire within 30 days, and removal from the content-delivery cache is requested immediately at the time of deletion. If a backup is restored, the deletion request is applied again right after restoration |
| Booking links and affiliate measurement | Cloudflare KV link records containing the target URL, platform, category, screen and destination label: 90 days after registration or re-registration. Click and conversion operational logs: 6 months for booking-link performance measurement and fraudulent-click prevention |
| Operator AI Account activity records | Screenshots are deleted after 7 days, and the displayed screen information in observation records of screen navigation, errors and loading is also erased after 7 days. Error records (including copies of error reports kept on the operating device), whether resolved or not, are reduced 30 days after they were last observed to the feature and symptom, plus the basis for resolution for resolved records. The public usernames of users who have exchanged comments with an Operator AI Account, conversation summaries and activity memories are kept while that account is in operation and are deleted when the account is retired and deleted. At that time, the comments, replies and likes other users left on the Operator AI Account's posts and their records of saving those posts, as well as the replies and likes other users left on comments the Operator AI Account wrote on other users' posts or on articles and videos provided by the Service, are also deleted (Terms of Service, Article 6-2, paragraph 8). (Newly inserted 2026-11-04) |
| Contract, withdrawal, payment and service-supply records | 5 years under Article 6 of the Enforcement Decree of Korea's Act on the Consumer Protection in Electronic Commerce. Before enabling paid payments, we will configure and verify that transaction identifiers, products, and payment, supply, withdrawal and refund records are separated from account data, retained for the statutory period after account deletion, and then destroyed. |
Where retention is otherwise required by law, a security-incident investigation, or dispute handling, information may be retained separately to the extent and for the period necessary for that purpose.
5. External services and overseas processing
The providers below process information while providing the Service, and personal information is transferred overseas to foreign providers among them. Under Article 28-8 of Korea's Personal Information Protection Act, we disclose the transferred information, countries, timing and methods, recipients' purposes and retention periods, and recipient contact details below. The reference date for the factual values in the table is 2026-09-22; where an individual item has a different reference date, that date applies.
5-1. Overseas transfers
| Recipient | Destination country | Information transferred | Transfer timing and method | Purpose | Retention and use period | Recipient contact |
|---|---|---|---|---|---|---|
| Supabase, Inc. | Japan (Tokyo region ap-northeast-1, as of 2026-09-22) | Account, profile, preferences, UGC, DMs, reports and AI records; trips synced after logging in (including source post information of imported itineraries) (Amended 2026-11-04) | Network transfer (HTTPS) during login, synchronization, community use and storage of AI records | Authentication, database, real-time messaging and synchronization | The Operator's project is on the Pro plan, retaining daily managed backups for 7 days, and Point-in-Time Recovery is not used (as of 2026-09-22). User contact information, however, is retained for 60 days after the account is closed (Supabase Privacy Policy Version 3 · 2026-05-13 · EEA/UK/CH addendum item 3(f) "we retain this for as long as you have an account on our services, and for 60 days after you close your account" · as of 2026-09-07). | Privacy Policy · privacy@supabase.com |
| Cloudflare, Inc. | United States | API requests and responses, authentication identifiers, AI inputs and responses, uploaded media, current location coordinates and accuracy during visit verification, booking-link, click and conversion information, raw notification data used for payment verification, and network information including IP addresses | Transmitted over the network (HTTPS) when API, AI, media-upload, visit-verification or booking-link requests are made and when store receipts are verified or payment-status notifications are received | Worker API, AI Gateway, Workers AI embedding generation, R2 media storage and delivery, visit-verification distance and accuracy checks, booking-link and affiliate measurement, store receipt verification and payment-status notification intake, security, abuse prevention and operational logs | Values set by the Operator — visit-verification coordinates and accuracy are processed in memory only during the check and are not stored; booking-link KV records 90 days; travel-guide cache 30 days. R2 media has no fixed retention period: when a post or media item is deleted, it is queued for deletion and removed by a scheduled job. Neither Cloudflare's public policy nor the contract (Cloudflare Customer DPA v6.4) states a specific period for its own operational logs (as of 2026-09-22). | Privacy Policy |
| Anthropic, PBC | United States | Travel information, questions and preference context included in AI requests, and generated responses; receipt photos the user asks to have read, and photos the user sends to Aurora through sharing; public posts, comments and usernames an Operator AI Account reads on screen, and the public usernames of users who have exchanged comments with it, conversation summaries and activity memories (after masking email addresses, phone numbers, verification codes and tokens in formats the app recognizes); and a screenshot at the feature-check step (limited to the Operator AI Account's own screen — its own profile, or a trip screen the app judges to be its own from in-app navigation — and excluding any screen whose text information is found to contain markers of other users that the app recognizes, or an email address, phone number, verification code or token in a format it recognizes) (Amended 2026-11-04) | Network transfer (HTTPS) through the Operator backend during AI itinerary-generation and conversation requests, and when the user asks for a receipt or photo to be read. Sent directly over the network (HTTPS) from the Operator-managed operating device while an Operator AI Account is active (Amended 2026-11-04) | Generating AI itineraries, packing lists, conversations and personalized responses; reading the merchant, amount, currency and date on receipts; generating an Operator AI Account's next action and the text of its posts and comments, and checking screens at the feature-check step for display errors (such as clipped or overlapping text or hard-to-read contrast) (Amended 2026-11-04) | Anthropic retention policy — API inputs and outputs are deleted within 30 days of receipt or generation. If flagged for usage-policy violations, inputs and outputs may be retained for up to 2 years and safety classifier scores for up to 7 years. The Operator's organization has no Zero Data Retention agreement in place (as of 2026-09-22; see Section 4). | |
| Google LLC·YouTube | United States | Login identifiers, search terms, addresses and coordinates, route and flight inputs, video identifiers, and network and device information for content requests, store transaction and original transaction identifiers, product ID, purchase and subscription status, and the titles and bodies of community posts, comments, introductions and meetups to be translated automatically | Network transfer (HTTPS) during login, place search, maps, routes and flight queries, YouTube thumbnail loading and video playback. Network transfer (HTTPS) through the device or the Operator backend during Google Play payments, purchase restoration and subscription-status checks. Network transfer (HTTPS) through the Operator backend and Cloudflare AI Gateway when community content is translated automatically | Google and social login, Places, Maps, Routes, Geocoding, Flights, YouTube thumbnails and embedded videos, Google Play receipt verification and purchase and subscription-status checks, automatic translation of community posts, comments, introductions and meetups using the Gemini API | Google data retention policy — Server-log IP addresses are anonymized after 9 months and cookie information after 18 months; backups may retain them for up to 6 months. The public policy does not state a retention period for queries such as place search terms themselves (as of 2026-08-04). The public policy likewise does not state a retention period for the purchase records the store holds. The Operator's own copies follow the standards in Section 4 — seven days for raw notification data used for payment verification, and the statutory five years for contract, payment and service-supply records. The contract (Google Cloud Data Processing Addendum) §6.1 and §6.2 set no separate retention period and provide only for deletion or return of customer data on termination (as of 2026-09-22). Inputs and outputs of Gemini API requests are retained for 55 days to detect policy violations (Gemini API usage policies, as of 2026-10-08). | googlekrsupport@google.com (Google Privacy Policy, as of 2026-09-14) |
| Mapbox, Inc. | United States (primary processing region); passes through CDN caches in multiple regions for performance | Coordinates of up to 25 places saved in an itinerary, travel mode. During Apple Watch navigation, the device's precise current location coordinates, the destination coordinates, and the guidance language | Network transfer (HTTPS) during itinerary-route queries. When the user taps walking or driving directions for an itinerary item on an iPhone paired with an Apple Watch, the app sends it directly over the network (HTTPS) when guidance starts and when the user leaves the route (at most once every 30 seconds), and stops on arrival at the destination | Walking and driving route geometry, per-leg travel time and distance, and route and turn guidance for Apple Watch navigation | Mapbox Privacy Policy — IP addresses are retained for 30 days (this may be extended for security investigations or legal compliance). The public DPA limits retention to the period of business need for the processing purposes and provides for deletion upon the customer’s written request within 30 days after termination or expiry of the agreement, with exceptions for legal compliance or another lawful basis for retention (Mapbox DPA §7.1·Schedule B §7, as of 2026-09-14). | Privacy Policy |
| Unsplash, Inc. | Canada (Calgary, Alberta) | Image URLs and network and device information for content requests | Network transfer (HTTPS) when images load on destination, guide and feed screens | Serving remote images | The Operator has no separate agreement with Unsplash; the Unsplash API Terms and the public policy apply. The public policy provides for retention as long as needed for the collection purpose and does not state a specific period (as of 2026-09-22). | Privacy Policy |
| Trip.com Travel Singapore Pte. Ltd. | Singapore | Flights: origin and destination codes, departure and return dates, party size. Stays: destination name and cityId, check-in and check-out, number of adults. Affiliate click identifier when a tracked link is used | Network transfer (HTTPS) when the user selects a flight or accommodation booking link | Flight and accommodation booking search and links, affiliate performance measurement | The Trip.com privacy policy provides for retention until whichever applies of fulfilment of the purpose, objection to the use, or withdrawal of consent, and retains account-related information for as long as the user remains eligible. It does not state a specific period (as of 2026-09-07). | Privacy Policy · en_dataprotection@trip.com · 30 Raffles Place, #29-01, Singapore 048622 |
| Klook Travel Technology Limited | Hong Kong | Activity search terms or the selected product path; affiliate click identifier when a tracked link is used | Network transfer (HTTPS) when the user selects an activity booking link | Activity booking search and links, affiliate performance measurement | The Klook privacy policy provides for retention only for as long as necessary to fulfil the processing purpose or to comply with applicable law, after which the data is securely deleted or anonymised. It does not state a specific period (as of 2026-09-07). | Privacy Policy · privacy@klook.com · 24F, Kinwick Centre, 32 Hollywood Rd, Central, Hong Kong |
| OpenTable | United States | Place name, date, time and party size | Network transfer (HTTPS) when the user selects a restaurant booking link and when link availability is checked | Restaurant booking links and link-availability checks | The OpenTable privacy policy provides for retention while the account is active and for a period afterwards to allow reactivation, and permits additional retention to maintain analytics, security and audit records, to comply with statutory retention duties, and to handle complaints and disputes and defend rights. It does not state a specific period (as of 2026-09-07). | Privacy Policy · privacy@opentable.com · OpenTable, Inc. 425 Market Street, Suite 1200, San Francisco, CA 94105, U.S.A. |
| Apple Inc. | United States (Cupertino, California) | Login identifiers, location and address requests permitted by the user, store transaction and original transaction identifiers, product ID, purchase and subscription status, and the user ID placed in the purchase request | Transfer through the device operating system during Apple login and iOS location or geocoding use. Network transfer (HTTPS) through the device or the Operator backend during App Store payments, purchase restoration and subscription-status checks | Apple login, iOS location and geocoding, App Store receipt verification and purchase and subscription-status checks | The Apple privacy policy provides for retention until the collection purpose is fulfilled or for the period required by law, and states that where retention is necessary it works to keep the data for the shortest period permissible under law. It does not state a specific period (as of 2026-09-07). ("work to retain the personal data for the shortest possible period permissible under law" · Updated July 30, 2025) The public policy likewise does not state a retention period for the purchase records the store holds. The Operator's own copies follow the standards in Section 4 — seven days for raw notification data used for payment verification, and the statutory five years for contract, payment and service-supply records. | Privacy policy · Contact form (the policy provides no dedicated privacy email address, only a form and a telephone number) |
| Sentry (Functional Software, Inc.) | United States | Error, stack, device and app information, diagnostic context | Network transfer (HTTPS) when an error occurs | App error and performance diagnostics | Event retention policy applies: the Operator's organization (lunara-inc) is on the Developer plan, so error events are retained for 30 days and transactions and spans for 30 days as well (as of 2026-09-22). Backups are deleted within 90 days of creation. | Privacy Policy |
| Nokia of America Corporation (operator of the Rapid API Marketplace) | United States · the group data protection officer is Nokia Corporation in Finland | Flight-number and date query values | Network transfer (HTTPS) through the Operator backend (Cloudflare Worker) during flight queries; the app does not call it directly and authentication keys are stored only on the server | Relaying AeroDataBox flight-information queries | Retained for as long as necessary to fulfil the purposes set out in that policy, and for any period required by legal, tax, accounting or reporting obligations. Only the criteria for determining the retention period (duration of the relationship, legal obligations, legal position) are published; the specific period is set by an internal retention policy (as of 2026-09-07). | Privacy Policy · group.dpo@nokia.com · Nokia Corporation c/o Privacy, Karakaari 7, P.O. Box 226, FI-00045 Nokia Group, Finland |
| AeroDataBox (Timber Bytes LLP) | Canada (located in British Columbia, as of 2026-09-22) | Flight number and date. The Operator does not transmit personal-information fields identifying the user | Network transfer (HTTPS) through the RapidAPI marketplace during flight queries | Providing flight information | The AeroDataBox privacy policy (Last updated July 31, 2026) contains no retention-period clause at all (as of 2026-09-07). Its only sentence that states a period is limited to Flight Alerts webhook URLs, and the Operator does not use that feature. The separate agreement likewise contains no retention-period clause (as of 2026-09-22). | Contact form (the policy provides no dedicated privacy email address) |
| Open-Meteo (OpenMeteo GmbH) | Switzerland (Bürglen, Uri; Swiss law also governs) | Travel city coordinates and query time | Network transfer (HTTPS) during weather queries | Weather queries | Open-Meteo Terms of Service — Webserver log files, which may contain coordinates, are deleted after 90 days; only aggregated usage is retained | Terms of Service |
| Amazon Web Services, Inc. (Amazon Rekognition · Amazon S3) | Republic of Korea (fixed to the Seoul region, ap-northeast-2) | Original image and video files uploaded by the user and the quarantine object keys | Network transfer (HTTPS) through the Operator's backend when photos or videos are uploaded | Automated harmful-content assessment of images and videos in posts | The public DPA lets the customer determine the duration of processing and provides for return or deletion at the customer’s request before termination and for 90 days thereafter. The 90 days are not a universal automatic deletion deadline (AWS DPA §1.3.2·§14, as of 2026-09-14). Whether Rekognition inputs are used and stored for service improvement depends on separate settings (Official FAQ, as of 2026-09-14); the Operator applies the AWS Organizations AI services opt-out policy so that inputs are not used or stored for service improvement (as of 2026-09-22). Operator settings are 24 hours after quarantine-object approval, rejection or failure, and 90 days for completed decision jobs | Amazon Web Services, Inc., ATTN: AWS Legal, 410 Terry Avenue North, Seattle, WA 98109-5210, United States (AWS Privacy Notice, as of 2026-09-14) |
| Travelpayouts (Go Travel Un Limited) | Hong Kong (registered location of Go Travel Un Limited, Official terms §1.2, as of 2026-09-14) | The page address, browser information and other data collected by the script when the website is visited | When the affiliate-link automation script runs on every page of the website | Automatic conversion of travel links into affiliate links and performance measurement | The contract (partner terms) and the public policy set no separate period and provide for retention while the account remains active (as of 2026-09-22). | support@travelpayouts.com (Official terms §7.5, as of 2026-09-14) |
Information transferred to Anthropic, PBC as a result of Operator AI Account activity (the Operator AI Account items in the Anthropic, PBC row of the table above) is an overseas entrustment of processing, and its legal basis is Article 28-8(1)(iii)(a) of the Personal Information Protection Act (entrustment of processing for the performance of the service agreement, where the matters concerning the transfer are disclosed in this Policy). (Newly inserted 2026-11-04)
Where a provider's privacy-policy link appears in the contact column, contact methods can be found in that document. Information passed to booking partners is passed only when the user selects a booking link; if no link is selected, nothing is passed.
5-2. Domestic processing
The following are domestic providers; personal information is not transferred overseas to them.
| Provider | Information processed | Processing timing and method | Purpose | Retention and use period | Contact |
|---|---|---|---|---|---|
| Kakao Corp. | Place search terms, search area, and place names opened in an external map | Network transfer (HTTPS) during domestic place searches and KakaoMap link use | Domestic place search, external KakaoMap links selected by the user | Kakao Privacy Policy — Retention is specified by category (for example, rights-infringement reports: 5 years; location-information use and provision records: 6 months), but not for service-usage records such as place search terms (as of 2026-08-04). Information about users who signed in with Kakao is destroyed by the Operator on withdrawal, and may be retained by Kakao for up to one year after withdrawal (as of 2026-09-22). | Privacy Policy |
| Naver | Place names opened in an external map | Network transfer (HTTPS) when the user selects a Naver Map link | Connecting external Naver Map links selected by the user | The Naver privacy policy provides for destruction without delay once the purpose of use is fulfilled, while retaining data for the periods set by law — login records 3 months, records on display and advertising 6 months, records on consumer complaints and dispute handling 3 years, records on contracts and withdrawal of subscription and on payment and supply of goods 5 years each, tax-law books and supporting documents 5 years, and records on the circulation of electronic documents through a certified electronic address 10 years. Records confirming the collection, use and provision of personal location information are retained for 6 months or longer (as of 2026-09-07). | Privacy Policy · Data Protection Officer Lee Jin-kyu · privacy@naver.com · 1588-3820 |
You may decline the relevant overseas transfer by not using optional features such as AI, place search, flights and weather, while continuing to use other features such as manually creating itineraries. Where external processing is inherent to a feature, such as login, server synchronization or community, declining that processing means we cannot provide that feature. Overseas-transfer refusal inquiries: support@travellunara.com. Users who do not want their information transferred to Anthropic, PBC through Operator AI Accounts may request this at support@travellunara.com. Once the request has been processed, Operator AI Accounts will not send that user's public posts, comments or username to Anthropic, PBC. When processing the request, the Operator also deletes those activity memories and conversation summaries already stored on the operating device that contain the user's username or display name or that were made from screens showing the user's information, masks the user's username and display name in the screen records kept for 7 days, and deletes the related screenshots. Information already sent is deleted under the Anthropic API retention standard in Section 4. Declining this transfer does not restrict the user's use of the Service. (Amended 2026-11-04)
5-3. Payment-related disclosure (English translation)
The Korean disclosure above is the legally operative version. This English translation is provided for convenience. If the two versions differ, the Korean disclosure controls to the extent permitted by applicable law.
- Lunara processes the store, product ID, transaction and original transaction IDs, event type and ID, purchase and subscription status, purchase, expiration and refund timestamps, entitlement tier, one-time entitlement grant, use and revocation records, and the user ID that links a transaction to the account. The user ID is stored in the payment ledger and, for App Store purchases, is also placed in the purchase request sent to the store. These items are processed by the App Store and Google Play, Cloudflare Workers, and Supabase. Raw notification data received from the stores is stored with the payment ledger through the Worker and is deleted within seven days once the minimum fields needed to confirm payment status have been copied. Lunara does not directly collect or store card numbers or other store payment-method information.
- Apple Inc. and Google LLC receive the store transaction and original transaction identifiers, the product ID, and purchase and subscription status in the United States through HTTPS when a purchase, restore, or subscription-status check occurs; Apple additionally receives the user ID that Lunara places in the purchase request. They use the data to verify the store receipt and the purchase and subscription status. The stores do not publish a retention period for the purchase records they hold; Lunara's own copies follow Section 4 — raw notification data for seven days, and statutory contract, payment, refund and service-supply records for five years. Their retention periods and contact details are stated in the overseas-transfer table above.
- Deleting a Lunara account does not cancel a subscription purchased on the App Store or Google Play. The store holds the subscription contract and the payment method, so the subscription fee continues to be charged unless it is cancelled separately in the store account settings. Please cancel the subscription in the store before deleting the account.
- Lunara retains contract, withdrawal, payment, refund, and service-supply records for five years under Article 6 of the Enforcement Decree of Korea's Act on the Consumer Protection in Electronic Commerce. Before activating paid services, Lunara will configure and verify that these statutory records are separated from account data, remain after account deletion for the statutory period, and are then destroyed.
5-4. 決済関連の通知(日本語訳)
法的効力を有する開示は上記の韓国語版です。この日本語訳は便宜のために提供します。両者に相違がある場合、適用法令で認められる範囲で韓国語版が優先されます。
- Lunaraは、ストア、商品ID、取引ID・原取引ID、イベントID・種類、購入・購読状態、購入・満了・返金時刻、利用権限の等級、単品利用権の付与・使用・回収記録、および取引をアカウントに結び付ける利用者IDを処理します。利用者IDは決済台帳に保存し、App Storeでの購入時は購入リクエストに含めてストアにも送信します。これらの項目はApp Store・Google Play、Cloudflare Workers、Supabaseで処理します。ストアから受領した受信データの原本はWorkerを経て決済台帳とともに保存され、決済状態の確認に必要な最小項目へ移した後、7日以内に削除します。カード番号その他のストア決済手段情報をLunaraが直接収集・保存することはありません。
- Apple Inc.およびGoogle LLCは、購入・復元・購読状態の確認時に、ストアの取引識別子・原取引識別子、商品IDおよび購入・購読状態をHTTPSで米国に移転して受領します。Appleは加えて、Lunaraが購入リクエストに含める利用者IDを受領します。ストアの領収情報と購入・購読状態の確認に利用します。ストアが保有する購入記録の保有期間は、公開ポリシーに明示されていません。Lunara側の控えの保有基準は4項と同じで、受信データの原本は7日、契約・決済・返金・サービス提供の法定記録は5年です。保有期間および連絡先は、上記の国外移転の表に記載しています。
- Lunaraのアカウントを削除しても、App Store・Google Playで申し込んだ購読は自動的に解約されません。購読契約の当事者と決済手段はストアが管理するため、ストアのアカウント設定で別途解約しないかぎり購読料が請求され続けます。アカウントを削除する前に、ストアで購読を解約してください。
- Lunaraは、韓国「電子商取引等における消費者保護に関する法律施行令」第6条により、契約・申込みの撤回・決済・返金・サービス提供の記録を5年間保有します。有料サービスを有効化する前に、法定記録をアカウントデータから分離し、アカウント削除後も法定期間中は保有した後に破棄する構成を実装・検証します。
6. Optional analytics and automatic collection
- The Operator does not conduct advertising-identifier-based ad tracking or share data for sale.
- PostHog product analytics runs only if the user turns on "Allow optional analytics" in the app settings; it is off by default. Until it is turned on, the SDK is not loaded and no events are sent. Turning it off stops collection immediately and deletes any unsent events left on the device.
- The Operator enables optional analytics only after first disclosing the events collected, purposes and retention periods and providing separate consent and withdrawal features.
- Booking-link and affiliate measurement is separate from PostHog product usage analytics. Link registration and click and conversion measurement occur when the user selects a booking link using the tracking redirector; affiliate parameters may be added to some links. Ordinary map links do not pass through that redirector.
- Sentry error diagnostics may activate at app startup in builds with a DSN configured. This is separate from optional analytics and processes the error-diagnostic information in Section 1.
- There are two kinds of app notifications. Packing-list and departure reminders are local notifications scheduled on the device. New DM alerts are remote push notifications; for these, a signed-in user's device push token is linked to the account and stored on the Operator's server. Delivery to that token stops when the user logs out or switches accounts.
- Remote push notifications do not contain message content. The lock screen shows only a generic phrase such as “You have a new message” and the number of unread conversations; the content can be read after opening the app and signing in.
- Notifications can be turned off per conversation, and the server does not create push notifications for a muted conversation (the conversation and its unread indicator remain in the app).
7. Destruction procedures and account deletion
You may request account deletion in the app's settings. After server deletion succeeds, account-associated state on the device is also reset.
- When a Supabase account is deleted, the Operator cascade-deletes its associated profiles, preferences, posts, comments, reactions, meetups, DMs, AI records and usage ledger.
- Report records may remain with the reporter's identifier removed.
- Deleting a Lunara account does not cancel a subscription purchased on the App Store or Google Play. The store holds the subscription contract and the payment method, so the subscription fee continues to be charged unless it is cancelled separately in the store account settings. Please cancel the subscription in the store before deleting the account.
- The Operator processes public R2 media deletion through a deletion queue separate from database deletion. The job is marked complete after R2 objects are deleted and caches are purged, and failed jobs are retried every five minutes.
- Operational backups and external processors' copies may be deleted later under each service's deletion and backup policies.
8. Your rights and inquiries
You may request access to, correction or deletion of your information, suspension of processing, or withdrawal of consent. Each right may be exercised as follows.
| Right | How to exercise it |
|---|---|
| Access | View your information directly on the app's profile, trip, and post screens. For information not available on those screens, contact us using the details below |
| Correction | Use the app's profile, post, and comment editing features. For information without an editing feature, contact us using the details below |
| Deletion | Use the app's post and comment deletion features. To delete all server information associated with your account, use the account deletion feature in the app settings |
| Suspension of processing | Turn off AI personalization in the app settings (see AI personalization below). To request suspension of other processing, contact us using the details below |
| Withdrawal of consent | Turn off the relevant option on the settings screen for each consent item, or contact us using the details below |
- Contact: support@travellunara.com (Privacy Officer: Section 11)
- Requests may be made by you, your legal representative, or an authorized agent. A representative or agent making a request must provide documentation confirming their authority.
- Account ownership verification may be required to protect the requester's rights.
- Upon receipt of a request, we will take the necessary action within 10 days and notify you of the outcome. If applicable law requires us to defer or refuse action, we will also explain the reasons and how to raise an objection.
The relationship between AI personalization and suspension of processing is as follows.
- Aurora personalization (AI features) is how the Service provides tailored itineraries and recommendations by default, and consent for it is obtained at sign-up separately from consent for cross-border transfer. You can turn personalization off at any time on the Aurora personalization screen in app settings, and while it is off Aurora gives only general recommendations without your preferences. The Operator updates the device setting to turn personalization off after the server processing-stop request succeeds, disables personalization on the server, and deletes AI source events, feedback, learned preferences, relevant history and memory. To delete all existing conversation history, use account deletion or contact support@travellunara.com.
- Even after processing is suspended, other information you have entered directly, such as trips and posts, continues to be processed. To delete all server information associated with your account, use the account deletion feature in the app settings.
- Requests not resolved in the app and inquiries about report handling: support@travellunara.com
9. Security measures
- We use HTTPS (TLS) for network communications.
- Supabase Row Level Security and server authentication restrict access to non-public information.
- Administrative privileges and external API secret keys must be managed in the server environment, not included in the mobile app. Map keys shipped in the app are separated per platform and restricted by where they may be used.
- Authentication sessions and sensitive on-device items preferentially use supported device secure storage.
- Filters reduce known identifiers in error logs and AI inputs, but cannot guarantee removal of personal information from every free-text input. Users should not include unnecessary personal information in AI questions, posts or DMs.
10. Children's personal information
The Operator checks birth years and does not allow users under 14 to create accounts. The minimum registration age is 15. Because only the birth year, rather than the full date of birth, is checked, users near the age threshold may be restricted conservatively.
11. Privacy officer
| Category | Details |
|---|---|
| Company name | 주식회사 루나라 (Lunara Inc.) |
| Representative | 한우철 |
| Address | 충청남도 천안시 동남구 청수14로 68, 505호(청당동, 센타타워) |
| Business registration number | 412-86-03903 |
| Corporate registration number | 161511-0040391 |
| Mail-order business registration number | 2026-충남천안-2026 |
| Mail-order business registration authority | 천안시 |
| Privacy officer | 대표이사 한우철 |
| Contact | support@travellunara.com |
Privacy violation reports and advice: Personal Information Infringement Report Center (privacy.kisa.or.kr / 118 without an area code), Personal Information Dispute Mediation Committee (kopico.go.kr / 1833-6972)
12. Changes to this policy
Changes and their effective date will be announced in the app or on the official website at least 7 days before they take effect. Changes that materially affect or disadvantage users' rights will be announced at least 30 days in advance, with individual notice by email or similar means where necessary.
Supplementary provisions
- Notice date: 2026-09-23
- Effective date: 2026-09-23
- Notice date: 2026-10-20 · Effective date: 2026-10-27
- Notice date: 2026-11-04 · Effective date: 2026-11-11
Previous Privacy Policies
Previous versions of this Privacy Policy are available below.